Re: system wakeup caused by write operations to /var/lib/dovecot/instances

On 2 Feb 2019, at 6.44, Tijl wrote: > How can dovecot be run without writing to /var/lib/dovecot/instances > everyday? Is there a configuration setting for this? You'd need to patch src/master/main.c instance_update_now() to remove: to_instance = timeout_add((3600 * 12 + i_rand_limit(60

Re: [grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15)

Hi, The rescan() function is a bit badly designed. Currently what you could do what fts-lucene does and: - Get list of UIDs for all mails in each folder - If Xapian has UID that doesn't exist -> delete it from Xapian - If UID is missing from Xapian -> expunge the rest of the UIDs in that fold

Re: submission-login: Fatal: master: service(submission-login):

On 11 Mar 2019, at 13.53, Marcelo Coelho via dovecot wrote: > > Hi everyone! > > I’m using dovecot 2.3.5. submission-login is crashing many times in a day: > > Here is a sample error message: > > dovecot: submission-login: Fatal: master: service(submission-login): child > 34247 killed with s

Re: imap-hibernate not working

On 8 Mar 2019, at 20.44, Marcelo Coelho via dovecot wrote: > > Hi, > > I follow different setup instructions and I can't make imap-hibernate work. > I've tried vmail and dovecot as users, tried to set mode to 0666, without > success. I'm using FreeBSD 11.2. > > Is imap-hibernate compatible wi

Re: Delayed flags changes over IDLE

On 10 Mar 2019, at 10.14, Kostya Vasilyev via dovecot wrote: > > My mail is stored under ~/mail/.imap (not sure what this format is called), I > mean not "single file mbox". > > I have not changed any IDLE related config settings: > > doveconf | grep -i idle > default_idle_kill = 1 mins > di

Re: Regression ACL & namespace prefix

On 18 Sep 2018, at 17.10, Michal Hlavinka wrote: > > Seems that for Global ACL directory, namespace prefix is not part of the > path, when looking for acl file. Is there a reason you're using ACL directory instead of ACL file? I've rather been thinking about removing code for ACL directories e

Re: “doveadm mailbox” command fails with UTF-8 mailboxes

On 12 Mar 2019, at 21.20, Felipe Gasper via dovecot wrote: > > Hello, > > I’ve got a strange misconfiguration where the following command: > > doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX > 'INBOX.*' > > … fails with error code 68, saying that it can’t find on

Re: dovecot-keywords are not preserved any more when moving mails between folders

On 12 Mar 2019, at 17.55, Dan Christensen via dovecot wrote: > > On Mar 12, 2019, Aki Tuomi via dovecot wrote: > >> On 12.3.2019 13.46, Piper Andreas via dovecot wrote: >> >>> after an upgrade of dovecot-2.2.5 to dovecot-2.3.4 the dovecot-keywords, >>> which in my case are set by thunderbird,

Re: Delayed flags changes over IDLE

On 12 Mar 2019, at 10.21, Kostya Vasilyev via dovecot wrote: > > It makes no difference if the IDLE connection does SELECT or SELECT > (CONDSTORE) prior to going IDLE. > > But then as far as I know (?) - in Dovecot, once any connection uses > CONDSTORE ever, even once, Dovecot creates data st

Re: question about %u and %h used in mail_location

On 12 Mar 2019, at 12.04, Joe Wong via dovecot wrote: > > Hello, > > I have defined the following: > > mail_location = maildir:~:INBOX=~/Maildir:LAYOUT=fs:INDEX=%u > > %u is retrieve via database in that my username contain ":", in which it > create some confusion to dovecot: > > doveadm i

Re: “doveadm mailbox” command fails with UTF-8 mailboxes

On 13 Mar 2019, at 1.07, Helmut K. C. Tessarek wrote: > > On 2019-03-12 17:23, Timo Sirainen via dovecot wrote >> https://wiki2.dovecot.org/MailLocation > > Sorry, this might be off-topic, but while reading up on the link you sent, > I've noticed the following senten

Re: flags not synced correctly with dovecot sync (dsync)

On 13 Mar 2019, at 22.43, Dan Christensen via dovecot wrote: > > On Mar 12, 2019, Dan Christensen via dovecot wrote: > >> In another thread, Timo wrote: >> >> On Mar 12, 2019, Timo Sirainen via dovecot wrote: >> >>> That bug is fixed with attache

Re: imap ---- LIST "" * The returned mailbox does not display quotes

On 21 Mar 2019, at 6.22, lty via dovecot wrote: > > dovecot version > > v2.2.29 > > v2.2.36 > > v2.3.5 > > LIST "" * The returned mailbox does not display quotes > > v2.1.17 > LIST "" * The returned mailbox shows quotation marks > > Why is the quotation mark removed in the new version? >

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 27 Mar 2019, at 12.42, Arkadiusz Miśkiewicz via dovecot wrote: > > > Hello. > > I have one account with heavy traffic (big mails) and quite often > indexes get corrupted. > > This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28. > > When corruption happens lmtp and po

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot wrote: > >> dovecot isn't able to auto fix the indexes and manual deletion is >> required in all such cases > > So if it keeps repeating, it's very strange. Could you send me such broken > dovecot.index an

Re: v2.2.27 Panic: file rfc822-parser.h: line 23 (rfc822_parser_deinit): assertion failed: (ctx->data <= ctx->end)

On 27 Mar 2019, at 1.25, Jason Lewis via dovecot wrote: > > Hi Aki, > > debian jessie backports has been moved to archive.debian.org and > initially I was unable to install dovecot-dbg because of that. But I've > managed to resolve that issue now. > > This was the command I ran: > doveadm -D -f

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 28 Mar 2019, at 10.15, Arkadiusz Miśkiewicz wrote: > > error = 0x55e3e2b40ac0 "Fixed index file > /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", > nodiskspace = true, This was one of the things I was first wondering, but I'm not sure why it's not logging an error. Anyway,

Re: FTS delays

On 2 Apr 2019, at 6.38, Joan Moreau via dovecot wrote: > > Further on this topic: > > > > When choosing any headers in the search box, dovecot core calls the plugin > TWICE (and returns the results quickly, but not immediatly after getting the > IDs from the plugins) > > When choosing the B

Re: Trying to track down source of duplicate messages

On 1 Apr 2019, at 19.40, Alex via dovecot wrote: > > Hi, > > I haven't received any responses to my duplicate messages problem. It > occurred to me that I posted my full dovecot config instead of just > the changes we've made locally. I thought it might help to follow up > with just the specific

Re: sieve scripts not synching for 2.3.5.1 pre-built

On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot wrote: > > Hi, > > We're synching mailboxes, changing format from maildir to mdbox, using > doveadm backup/doveadm sync. > > When still running 2.2.36, 'doveadm backup' also synched the sieve scripts, > without issues. > > After the upg

Re: sieve scripts not synching for 2.3.5.1 pre-built

On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot wrote: > > On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot <mailto:dovecot@dovecot.org>> wrote: >> >> Hi, >> >> We're synching mailboxes, changing format from maildir to mdbox, using >&

Re: FTS delays

On 3 Apr 2019, at 20.30, Joan Moreau via dovecot wrote: > doveadm search -u j...@grosjo.net mailbox inbox text milan > output > > doveadm(j...@grosjo.net): Info: Query : ( bcc:inbox OR body:inbox OR cc:inbox > OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid:inbox ) > AND (

Re: FTS delays

> d82b4b0f550d3859364495331209 3121 -> LOOPING FOREVER > > > > > > > On 2019-04-21 09:57, Timo Sirainen via dovecot wrote: > >> On 3 Apr 2019, at 20.30, Joan Moreau via dovecot > <mailto:dovecot@dovecot.org>> wrote: >>> >>>

Re: FTS delays

have a look deeper > > And the loop is a very big problem as it times out all the time (and once > again, this is not in any of the backend functions) > > > > > On 2019-04-21 10:42, Timo Sirainen via dovecot wrote: > >> Inbox appears in the list of arguments, be

Re: Dovecot LMTP mixing up users on multi-recipient mail

On 27 Jun 2019, at 14.21, Bernhard Schmidt via dovecot wrote: > > Hi, > > I've upgraded a mailstore from Debian Jessie (aka oldstable) with > Dovecot 2.2.13 to Debian Buster (next stable) with Dovecot 2.3.4.1 > today. It worked pretty well, except that we're seeing error messages > very similar

Re: Dovecot 2.3.6 on Solaris10: build issues, segfaults

On 9 Jul 2019, at 3.02, Joseph Tam via dovecot wrote: > > Issue 3) dovecot/doveconf segfaults on startup > > It crashes here while processing dovecot.conf, as does "doveconf" > > (settings-parser.c:1519 in setting_copy()) > *dest_size = *src_size; This is corr

Re: Applying Dovecot for a large / deep folder-hierarchy archive - BUG REPORTS!

On 7 Jul 2019, at 18.12, Arnold Opio Oree via dovecot wrote: > > Dovecot Team, > > I'd like to report a number of bugs, that are to my view all critical. It would help to get your doveconf -n, example command lines causing the problems and the error messages it outputs or what the wrong behav

Re: Error: o_stream_send_istream and Disconnected in APPEND

On 11 Jul 2019, at 10.13, Alessio Cecchi via dovecot wrote: > > Hi, > > I'm running some Dovecot servers configured with LVS + Director + Backend + > NFS and version 2.2.36.3 (a7d78f5a2). > > In the last days I see an increased number of these error: > > Error: > o_stream_send_istream(/nfs/

Re: Frequent Out of Memory for service(config)

On 13 May 2019, at 22.56, Root Kev via dovecot wrote: > > May 13 11:35:43 config: Fatal: master: service(config): child 26900 returned > error 83 (Out of memory (service config { vsz_limit=1024 MB }, you may need > to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) If you set

Re: Dovecot release v2.3.7

On 12 Jul 2019, at 21.05, Michael Grimm via dovecot wrote: > > Aki Tuomi via dovecot wrote: > >> We are pleased to release Dovecot release v2.3.7. > > My upgrade from 2.3.6 to 2.3.7 broke replication (FreeBSD 12.0-STABLE > r349799): > > | dovecot[76032]: master: Dovecot v2.3.7 (494d20bdc) st

Re: Pigeonhole release v0.5.7

On 12 Jul 2019, at 21.09, Reio Remma via dovecot wrote: > >> - dsync: dsync-replication does not synchronize Sieve scripts. > > Sieve replication still doesn't work for me. dsync now replicated sieve and > sieve/tmp directories, but neither actual sieve files nor @.dovecot.sieve > link. What

Re: 2.3.7/FreeBSD: Seeing lots of stats-writer errors.

On 12 Jul 2019, at 22.10, Larry Rosenman via dovecot wrote: > > A user reported this to me, and I'm seeing it too: > Hi all :) > > After mail/dovecot upgrade to v2.3.7 it seems something went wrong with > stat-writer... > > IMAP and POP3 logs: > > Jul 12 19:45:34 mail dovecot: imap-login: Er

Re: Purpose of stats-writer and why doveadm try to open it to dump stats ?

On 14 Jul 2019, at 10.10, Jean-Daniel via dovecot wrote: > > Hello, > > I want to monitor dovecot stats, and so I have an exporter process that run > with limited rights. > The monitoring user has only access to /var/run/dovecot/stats-reader and it > works fine. > Doveadm stats dump returns t

Re: Error since Dovecot v2.3.7

On 15 Jul 2019, at 10.58, Paul Hecker via dovecot wrote: > > Hi, > > since upgrading to Dovecot 2.3.7 I get the following new errors: What was the old version? Did you upgrade your kernel as well? > 2019-07-15 09:10:52 mail dovecot: > imap(p...@iwascoding.com)<32484>: Error: file_lock_free()

Re: [ext] 2.3.7 slower than 2.3.6?

On 15 Jul 2019, at 23.17, Ralf Hildebrandt via dovecot wrote: > > * Ralf Hildebrandt via dovecot : >> We're using dovecot (via LMTP) as a backup for all incoming mail. >> >> I upgraded from 2.3.6 to 2.3.7 on the 12th: >> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic >> 2:2.3

Re: Dovecot release v2.3.7

On 13 Jul 2019, at 18.39, Michael Grimm via dovecot wrote: > > Now replication is working from my point of view, besides occational error > messages like: > > | imap-login: Error: file_ostream.net_set_tcp_nodelay(, TRUE) failed: > Connection reset by peer Here's the final fix for it: https:/

Re: Dovecot release v2.3.7

On 13 Jul 2019, at 14.44, Tom Sommer via dovecot wrote: > > LMTP is broken on director: > > Jul 13 13:42:41 lmtp(34824): Panic: file smtp-params.c: line 685 > (smtp_params_mail_add_body_to_event): assertion failed: ((caps & > SMTP_CAPABILITY_8BITMIME) != 0) Thanks, fixed: https://github.com/

Re: Unexpected result from LIST EXTENDED command

On 16 Jul 2019, at 9.51, Emil Kalchev via dovecot wrote: > > I am executing this command below to dovecot-2.3.5-6.cp1178.x86_64 server > > Notice that some status responses are missing (For folders INBOX.Archive, > INBOX.spam.&-BD0EOQQ9BDkEPQ-). I wonder If this is a bug or working as > expec

Re: Unexpected result from LIST EXTENDED command

On 16 Jul 2019, at 11.41, Emil Kalchev wrote: > > There is no error in the server logs. I checked those particular folders on > the server and they don’t seems to have anything special about them, like > permission or etc. > > Yes, calling STATUS on those particular folders returns the status

Re: [ext] 2.3.7 slower than 2.3.6?

On 16 Jul 2019, at 11.15, Ralf Hildebrandt via dovecot wrote: > > * Timo Sirainen via dovecot : > >>> And alas, I had a look at the monitoring and found that disk IO has >>> increase A LOT after the update: >>> https://www.arschkrebs.de/images/dovecot-disk-

Re: Dovecot v2.3.7 - TLS/SSL issue

On 17 Jul 2019, at 13.59, Christos Chatzaras via dovecot wrote: > > I use a helpdesk system that connects to dovecot using POP3 with SSL enabled > to fetch the e-mails. > > After I upgrade to v2.3.7 the helpdesk randomly (some times it works, some > times not) doesn't fetch the e-mails. If I

Re: auth: Warning: Event 0x1280fe20 leaked

On 17 Jul 2019, at 22.13, Jos Chrispijn via dovecot wrote: > > On 16-7-19 9:30, John Doe Vecot via dovecot wrote: >> Lately I get some errors in my logfile, saying: >> >> dovecot[72337]: auth: Warning: Event 0x1280fe20 leaked (parent=0x0): >> auth-client-connection.c:338: 1 Time(s) > Same overh

Re: Dovecot Director upgrade from 2.2 to 2.3

On 18 Jul 2019, at 11.44, Alessio Cecchi via dovecot wrote: > > Hi, > > I have a setup with 3 Dovecot Director v2.2.36 and > director_consistent_hashing = yes ;-) > > Now I would like to upgrade to 2.3.7, first only Director and after also > Backend. > > Can works fine a ring of director wi

Re: index worker 2.3.7 undefined symbol errors (more info)

On 21 Jul 2019, at 23.14, Dirk Koopman via dovecot wrote: > > Some supplemental information: > > This is happening on every email delivered into Dovecot via LMTP. The curious > things are that the message is a) successfully delivered and b) sieved into > the correct directory. > > Another ob

Re: Dovecot with MySQL over SSL.

On 20 Jul 2019, at 23.02, Reio Remma via dovecot wrote: > > On 20.07.2019 22:37, Aki Tuomi via dovecot wrote: >> >>> On 20/07/2019 21:07 Reio Remma via dovecot >>> wrote: >>> >>> >>> On 20.07.2019 18:03, Aki Tuomi via dovecot wrote: > On 20/07/2019 13:

Re: Dovecot 2.3.6 on Solaris10: build issues, segfaults

Ah, okay, I see. submission_max_mail_size should be defined as uoff_t instead of size_t in struct submission_settings and struct submission_settings. > On 20 Jul 2019, at 1.47, Joseph Tam via dovecot wrote: > > > Looking further into this segfault at > > settings-parser.c:setting_copy()

Re: index worker 2.3.7 undefined symbol errors

On 19 Jul 2019, at 13.20, Dirk Koopman via dovecot wrote: > But I am left with this: > > Jul 19 14:09:52 localhost dovecot: indexer-worker: Error: User > lookup failed: Couldn't load required plugin > /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() faile: > /usr/lib/dovecot/modules/l

Re: Character not allowed in mailbox name

On 22 Jul 2019, at 10.34, Lothar Schilling via dovecot wrote: > > Hi Arnold, > > thanks for your assistance. I solved the issue right now by changing > > prefix = Shared/%%u/ > to > prefix = Shared/%%n/ > > This omits the @mydomain.de part which holds the dot causing the > trouble. Why this b

Re: Dovecot Director upgrade from 2.2 to 2.3

On 22 Jul 2019, at 17.45, Alessio Cecchi wrote: > > one server of the ring is now running Dovecot 2.3.7 and works fine with the > others Dovecot 2.2 since 3 days. > I notice only that the load avarage of this CentOS 7 server is higher > compared with CentOS 6 and Dovecot 2.2, but I don't know i

Dovecot v2.3.7.1 & Pigeonhole v0.5.7.1 released

https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.7.1.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.7.1.tar.gz.sig Binary packag

Re: corrupt mdbox index / zero mails showing in imap

On 25 Jul 2019, at 20.55, Mike via dovecot wrote: > > Hi, > > > I have recently migrated (under emergency conditions) a dovecot imap/pop > based server to a new instance. The mailboxes used mdbox format and due > to various screwups I had corrupt indexes. I thought I'd cleaned this up > but the

Re: corrupt mdbox index / zero mails showing in imap

On 27 Jul 2019, at 14.13, Timo Sirainen wrote: > > On 25 Jul 2019, at 20.55, Mike via dovecot wrote: >> >> Hi, >> >> >> I have recently migrated (under emergency conditions) a dovecot imap/pop >> based server to a new instance. The mailboxes used mdbox format and due >> to various screwups I

Re: Autoexpunge not working for Junk?

On 25 Jul 2019, at 7.18, Amir Caspi via dovecot wrote: > > Hi all, > > I set up dovecot a couple of months ago and am having trouble getting > autoexpunge=30d to work on my Trash and Junk mailboxes. Not sure why not > because I'm not getting error messages in my log. > Running "do

Re: doveadm: Error: open(/proc/self/io) failed

On 31 Jul 2019, at 20.45, A. Schulze via dovecot wrote: > > > > Am 31.07.19 um 08:27 schrieb Sami Ketola via dovecot: >> service lmtp { >> user = vmail >> } >> >> please remove user = vmail from here or change it to root. >> >> for security reasons lmtp service must be started as root since v

Re: IMAP frontend authenticating proxy with GSSAPI/Kerberos SSO

On 1 Aug 2019, at 12.26, Gert van Dijk via dovecot wrote: > > passdb { > args = proxy=y host=127.0.0.1 port=1143 pass=#hidden_use-P_to_show# .. > auth: Info: static(username,1.2.3.4,<9WOjSwWP8toKAAYE>): No password > returned (and no nopassword) I think this is why it's not using the passdb at

Re: Dovecot Director upgrade from 2.2 to 2.3

On 31 Jul 2019, at 15.41, Alessio Cecchi via dovecot wrote: > > Hi Timo, > > here you can see two images with the load average and CPU usage with Dovecot > 2.2 (Centos 6) and 2.3 (Centos 7) on the same hardware and same configuration: > > https://imgur.com/a/1hsItlc

Re: [BUG?] Double quota calulation when special folder is present

> On 6 Aug 2019, at 21.08, Mark Moseley via dovecot wrote: > >> >> I've bisected this down to this commit: >> >> git diff >> 7620195ceeea805137cbd1bae104e385eee474a9..97473a513feb2bbd763051869c8b7b83e24b37fa >> >> Prior to this commit, anything updating the quota would do the right thing >

Re: Autoexpunge not working for Junk?

On 13 Aug 2019, at 5.57, Amir Caspi via dovecot wrote: > > On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot > wrote: >> >> * Amir Caspi via dovecot, 12.08.19 22:01 >> >>> [~]# doveadm mailbox status -u cepheid firstsaved Junk >>> Junk firstsaved=1563154976 >>> >>> I can't tell how that

Re: Should dovecot not be using different logging facility and severity levels?

On 9 Aug 2019, at 17.39, Marc Roos via dovecot wrote: > > Should dovecot not be using different severity levels like auth.warn? On > my system everything goes to loglevel info: My thinking has been: * Panic: There's a bug that needs fixing * Fatal: Somewhat stronger error * Error: Something

Re: Auth driver

On 9 Aug 2019, at 15.08, Riccardo Paolo Bestetti via dovecot wrote: > > > Could you point me to any documentation or examples? While I can find many > plugins in the repo and around the Internet, I could find none which add > authdb drivers. https://dovecot.org/patches/2.2/passdb-openam.c <

Re: Autoexpunge not working for Junk?

On 14 Aug 2019, at 22.35, Amir Caspi via dovecot wrote: > > On Aug 14, 2019, at 1:26 PM, Timo Sirainen via dovecot <mailto:dovecot@dovecot.org>> wrote: >> >> It probably has something to do with using mbox format. Are the IMAP UIDs >> changing unexpectedly?

Re: Emails not visible after renaming folders

Looks like this happens when you use a combination of FULLDIRNAME and INDEX in mail_location. Without one of these, or using DIRNAME instead of FULLDIRNAME it works correctly. Tracking internally in DOP-1348. > On 6 Aug 2019, at 14.22, Aleksandr via dovecot wrote: > > Hi guys. > > Does anyone

Re: dovecot-uidlist invalid data

On 4 Aug 2019, at 22.57, Király Balázs via dovecot wrote: > > Hi! > > I’m struggling with the following error: > > Aug 4 21:32:00 mx02 dovecot: imap(x...@xxx.tld)<17693>: > Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist > line 6246: Invalid data: > Aug 4 21:49:

Re: auth module logging

On 4 Aug 2019, at 6.23, AP via dovecot wrote: > > On Sat, Aug 03, 2019 at 11:27:24AM -0600, Michael Slusarz wrote: >>> Errors hit the logs but I would appreciate seeing successful auths >>> happen for the additional piece of mind. Cmouse and I couldn't >>> find a way to do it on irc and it appear

Re: segmentation fault in fs_list_get_path

On 3 Aug 2019, at 21.22, David M. Johnson via dovecot wrote: > > There seems to be a straightforward bug in > src/lib-storage/list/mailbox-list-fs.c:79. set->index_dir is unchecked prior > to dereferencing (unlike on line 126 in the same file, where it is properly > checked). This manifeste

Re: 2.3.7 + stats

On 16 Aug 2019, at 14.35, Jean-Daniel via dovecot wrote: > > Some of the behaviours you observe may be due to the same bug I encountered: > > https://dovecot.org/pipermail/dovecot/2019-July/116475.html > > Especially, regarding the ‘successful' field for auth, which does not exists > and is re

Re: Dovecot and hard links?

On 17 Aug 2019, at 1.57, @lbutlr via dovecot wrote: > > On 16 Aug 19, at 07:33 , @lbutlr wrote: >> I was looking at a mail folder and I noted that a file in the inbox had a >> total of 11 hard links to it: > > Ack. I checked the junk folder and there are 379 files in there with 379 > links! >

Re: Feature wishlist: Allow to hide client IP/host in submission service

On 25 Aug 2019, at 21.51, Sebastian Krause via dovecot wrote: > > Hi, > > In many mail setups a required feature (for privacy reasons) is to > hide the host and IP of clients (in the "Received" header) that use > the authenticated submission over port 587. In Postfix that's > possible (https://

Re: Dovecot 2.3.7 - char "-" missing

On 30 Aug 2019, at 13.44, Domenico Pastore via dovecot wrote: > > Hello, > > i have update dovecot from version 2.2.15 to 2.3.7.2. > I have a problem with mine java software because there is a different > response when open connection to doveadm. > > I need open socket to doveadm for get imap

Re: WARNING: using attachment_dir with plugin zlib can corrupt mails

On 19 Jul 2019, at 17.52, Patrick Cernko via dovecot wrote: > > Hello list, hello Dovecot developers, > > this week, I discovered a serious bug in Dovecot, that lead to several broken > mails on our servers. The bug corrupts the first few characters of the mail > header during saving. On our

Re: WARNING: using attachment_dir with plugin zlib can corrupt mails

On 19 Jul 2019, at 17.52, Patrick Cernko via dovecot wrote: > > Hello list, hello Dovecot developers, > > this week, I discovered a serious bug in Dovecot, that lead to several broken > mails on our servers. The bug corrupts the first few characters of the mail > header during saving. On our

Re: dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

On 1 Oct 2019, at 16.31, Ralf Hildebrandt via dovecot wrote: > > I set up system copying all mails to a backup system. > > This used to work without a hitch - now in the last few days mails > would pile up in the Postfix Queue, waiting to be delivered using the > lmtp transport into dovecot. >

Re: [ext] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

On 1 Oct 2019, at 16.45, Ralf Hildebrandt via dovecot wrote: > > * Ralf Hildebrandt via dovecot : > >> But why is that? Why would the index file be updated so often? > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back > in July. Fixed by https://github.com/dovec

Re: Using attachment_dir with plugin zlib corrupt mails

Can you test if https://github.com/dovecot/core/commit/5068b11e594ad7cc1f7cedf2bd9280520e0e534d.patch fixes it for you? > On 10 Oct 2019, at 11.34, MAREN ZUBIZARRETA via dovecot > wrote: > > Hello: > >

Re: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting

On 25 Sep 2019, at 17.03, Alex Ha via dovecot mailto:dovecot@dovecot.org>> wrote: > > Hi all! > > I have two dovecot servers with dsync replication over tcp. > Replication works fine except for one user. > > # doveadm replicator status > username

Re: Coredump v2.3.8 specific msg fetch, corrupted record in index cache, Broken physical size

On 18 Oct 2019, at 15.36, Erik de Waard via dovecot wrote: > > Hi, i'm getting a coredump on a specific msg, i've attached the gdb. > > file on disk i noticed W= is missing. > 1571209735.M744550P1608.rwvirtual65,S=15886:2,S .. > mail.log > Oct 18 14:41:39 rwvirtual10 dovecot: imap(john...@compan

Re: Dovecot v2.3.8 released

> On 18 Oct 2019, at 13.43, Tom Sommer via dovecot wrote: > >> I am seeing a lot of errors since the upgrade, on multiple client accounts: >> Info: Connection closed: read(size=7902) failed: Connection reset by >> peer (UID FETCH running for 0.242 + waiting input/output for 108.816 >> secs, 60

Re: Dovecot v2.3.8 released

On 20 Oct 2019, at 11.37, Tom Sommer via dovecot wrote: > >>> This is mail_debug from one of the accounts in question: >>> Oct 18 13:39:37 imap()<7552>: Debug: Mailbox INBOX: >>> Mailbox opened because: SELECT >>> Oct 18 13:39:37 imap()<7552>: Debug: Mailbox INBOX: >>> UID 17854: Opened

Re: BUG: Mailbox renaming algorithm got into a potentially infinite loop, aborting

On 17 Oct 2019, at 13.01, Alex Ha via dovecot wrote: > >> dsync-local(custo...@example.com ): Error: BUG: >> Mailbox renaming algorithm got into a potentially infinite loop, aborting >> dsync-local(custo...@example.com ): Error: >> Mailb

Re: [2.3.8] possible replication issue

I think there's a good chance that upgrading both will fix it. The bug already existed in old versions, it just wasn't normally triggered. Since v2.3.8 this situation is triggered on one dsync side, so the v2.3.9 fix needs to be on the other side. > On 5. Dec 2019, at 8.34, Piper Andreas via do

Re: doveadm sync - I/O has stalled

We haven't found any specific bugs with lib-ssl-iostream so far, but we did find istream-multiplex bug that could cause hangs with doveadm-doveadm connections. Could be worth testing if it helps: https://github.com/dovecot/core/commit/bbe546bc637a6ac5c9e91fc8abefce62e4950d07 > On 30. Dec 2022,

Re: maintainer-feedback requested: [Bug 280929] mail/dovecot move bogus warning "Time moved forwards" to debug

The way Dovecot works is: - It finds the next timeout, sees that it happens in e.g. 5 milliseconds. - Then it calls kqueue() to wait for I/O for max 5 milliseconds - Then it notices that it actually returned more than 105 milliseconds later, and then logs a warning about it. So kqueue() appare

Re: maintainer-feedback requested: [Bug 280929] mail/dovecot move bogus warning "Time moved forwards" to debug

On 21. Aug 2024, at 12.35, Timo Sirainen wrote: > > The way Dovecot works is: > - It finds the next timeout, sees that it happens in e.g. 5 milliseconds. > - Then it calls kqueue() to wait for I/O for max 5 milliseconds > - Then it notices that it actually returned more than 105 milliseconds late

Re: maintainer-feedback requested: [Bug 280929] mail/dovecot move bogus warning "Time moved forwards" to debug

On 24. Aug 2024, at 5.06, Jochen Bern via dovecot wrote: > > On 21.08.24 11:35, Timo Sirainen wrote: >>> [Lots and lots of "but my NTP sync is much more precise than that" in >>> the FreeBSD thread] >> The way Dovecot works is: >> - It finds the next timeout, sees that it happens in e.g. 5 milli

Re: maintainer-feedback requested: [Bug 280929] mail/dovecot move bogus warning "Time moved forwards" to debug

On 30. Aug 2024, at 19.00, dco2024--- via dovecot wrote: > > This is not limited to FreeBSD. I'm seeing it on Gentoo Linux. Kernel is > 6.6.47-gentoo-x86_64, dovecot 2.3.21.1 (d492236fa0). The warning is logged > once every 12-15 hours. > > Syslog: > 2024-08-24 18:03:49 UTC myhost dovecot: ma

Re: Inconsistency in map index with dovecot v2.3.21

On 30. Aug 2024, at 16.39, Nikolaos Pyrgiotis via dovecot wrote: > > But is there a possible bug in dovecot 2.3.21 version linked with the mdbox > format that is causing the `inconsistency in map index` in the first place or > it is just a configuration error? Other users have also reported th

Re: Dovecot v2.3.21.1 released

On 2. Sep 2024, at 15.44, Guilhem Moulin via dovecot wrote: > > Hi Aki, > >> we are releasing a CVE patch release 2.3.21.1. > > Your message to the oss-security list [0] says both 2.2 and 2.3 versions > are vulnerable to CVE-2024-23184. Using the following test message as > reproducer > >

Re: Bug Report: Missing parent folders will cause some clients to not retrieve messages

On 9. Oct 2024, at 2.18, Brendon Meyer via dovecot wrote: > > > When creating subfolders with tools such as imapfilter, if the parent of the > subfolder does not exist, Dovecot will allow that folder to be created, and > the tool will allow you to populate that folder with messages. What abou

Re: Missing IMAP folders after upgrading from 2.3.17 to 2.3.21.1

On 21. Oct 2024, at 15.50, Frank Kirschner via dovecot wrote: > > Hi, > > I have upgraded from 2.3.17 to 2.3.21.1. > mail_location = maildir > > Now in some mailboxes are IMAP folder in subdir of INBOX missing. > When I do a 'ls -la' in filesystem, I see the subfolder like other folder > with

Re: bug? dsync extremely much slower on forward than reverse direction

It's probably fixed by https://github.com/dovecot/core/commit/3001c1410e72440e48c285890dd31625b7e12555 > On 25. Nov 2024, at 14.51, Bjørnar Ness via dovecot > wrote: > > Here are some numbers from a test run: > > dst: full pull sync from src > 6m19s > dst: delta pull sync from src > 2s > >

Re: dovecot, virtiofs, fchown, invalid argument

On 26. Nov 2024, at 15.34, Кирилл Шигапов via dovecot wrote: > > We are using virtiofs share mounted to /var/vmail > When dovecot tries to make a directory structure, it fails with error - > fchown: Invalid argument > > strace doveadm mailbox create -u testu...@testdomain.com >

Re: Problem email client iPhone ios18.2

On 3. Feb 2025, at 16.17, stephen--- via dovecot wrote: > > funny - i also talked to apple business support and have a case since my > FB15701211 never went anywhere. they took a day or so and talked to engineers > and stated that there were no other official apple support requests for this >

Re: IMAP dovecot\postgres low authentication performance

On 3. Feb 2025, at 7.05, Anatoliy Zhestov via dovecot wrote: > > Hi. We have a performance problem with imap authentication through > postgresql. > Our servers(modoboa based) have a big amount of permanent imap > connections(5000-5). > Current performance is about 3000 successful authenticat

Re: Problem email client iPhone ios18.2

On 4. Feb 2025, at 3.53, stephen--- via dovecot wrote: > > in my experience the only users who complained were mail abusers - with tens > of thousands of messages in each folder - tons of folders etc etc. smaller > mailboxes seemed fine. i think apple uses some threshold where this new > pipel

Re: IMAP dovecot\postgres low authentication performance

On 3. Feb 2025, at 20.18, Anatoliy Zhestov via dovecot wrote: > >> >> Are you sure the problem is authentication / pgsql? You could test with >> looping "doveadm auth lookup $user" rapidly. Of course for different users >> to avoid them coming from cache. Or if you can reproduce it that way, tr

Re: Problem email client iPhone ios18.2

On 10. Feb 2025, at 15.24, Florian Effenberger via dovecot wrote: > > Hello, > > frido--- via dovecot wrote on 10.02.25 at 14:07: >> The problem as described at the start of this thread is not solved in iOS >> 18.3. A bit more testing shows that it only appears to happen with >> attachments a

Re: Bad Signature - Mustiple domains

On 11. Feb 2025, at 2.09, Ken Wright via dovecot wrote: > > Sorry, I sent that this morning just before running off to my job. > Here's the section of dovecot.conf that I'm working on: Nothing wrong with that part. > When I was running Dovecot 2.3, I was able to send and receive email to > and

Re: Error in tests for Dovecot 2.4.0 aarch64

> On 7. Feb 2025, at 9.48, Peter via dovecot wrote: > > When attempting to build Dovecot 2.4.0 on the aarch64 platform, when running > tests... > > test-file-cache.c:268: Assert failed: file_cache_set_size(cache, 1024) == -1 This test attempts to shrink allowed address space with setrlimit(R

Exim / Dovecot v2.4.0 authentication patch

Hi, Dovecot v2.4.0 changed authentication protocol slightly to allow new functionality (SCRAM TLS channel binding). It attempted to preserve backwards compatibility by checking client-provided VERSION first before sending data that the client wouldn't handle correctly. However, Exim's Dovecot

Re: 2.4.0 on MacOS

On 1. Feb 2025, at 10.27, John Muccigrosso via dovecot wrote: > > Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > > > The old(?) solution doesn't work for me: > > default_vsz_limit = 0 > > It reports: doveconf: Fatal: Error in configuration file > /opt/homebrew/etc/dovecot/dov

  1   2   >