May 2022 - dovecot - dovecot.org

FTS Solr -- no commit on message delete
by Shawn Heisey 18 May '22

18 May '22

I've been chasing down oddities in behavior related to FTS Solr for a while now. First the part that isn't a problem with dovecot: In cases where message deletes bypass the Trash folder (such as shift-delete and normal workflow with the Drafts and Sent folders), Thunderbird does not inform Dovecot about the change in a way that causes Dovecot to delete the entries from Solr. When you completely exit Thunderbird, it then sends something to dovecot that results in the messages being deleted from Solr. Today I discovered a related problem that I think IS in Dovecot. I did a shift-delete on some messages, and then exited Thunderbird. Dovecot did delete the messages from Solr, but it did not send a commit to make those changes affect subsequent searches. Is this something worth opening a bug? Where would I do that? Thanks, Shawn

1 1

Upgrading from 2.3.18 --> 2.3.19
by Paul Kudla (SCOM.CA Internet Services Inc.) 18 May '22

18 May '22

Ok currently running 2.3.18 Would like to upgrade to 2.3.19 (to keep current) Since these are production servers can i down grade back to 2.3.18 if nessesary? Issues at hand is there seems to be conflicting messages about the replication being fixed or not ? so would like to basically try 2.3.19 to see if it fixes some of my issues (large folder counts etc failing to replicate properly) If it does or stays the same then i am ok with that for now. if 2.3.19 causes issues can i go back to 2.3.18 as i already have scripts etc sorting out the sync issues? pls advise -- Happy Wednesday !!! Thanks - paul Paul Kudla Scom.ca Internet Services <http://www.scom.ca> 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266

1 0

Re: Can sync/migrate all mail from remote imap account except the main "INBOX"
by Darren Mobley 18 May '22

18 May '22

Your example pointed me to a solution, excellent ! In my case I only needed one pass, I had to supply both imapc_list_prefix AND imapc_prefix AND the "namespace/inbox/prefix=" options. In case anyone runs into this in the future, here's a decent place to start for debugging: /usr/bin/doveadm -Dv -o imapc_list_prefix=INBOX -o imapc_prefix=INBOX. -o "namespace/inbox/prefix=" -o mail_fsync=never -o dsync_commit_msgs_interval=100 -o imapc_features=rfc822.size,fetch-headers -o dsync_features=empty-header-workaround -o imapc_port=143 -o imapc_host=127.0.0.1 -o imapc_password=yayforpasswords -o imapc_user=mailto:wah@hellodemo.ppl -o imapc_rawlog_dir=/tmp/raww -o mail_prefetch_count=20 sync -1Ru mailto:saywhatnow@letest.tld imapc: Thanks again for digging through the old emails where the magic incantations were, I really appreciate it! Darren ---- On Wed, 18 May 2022 05:19:53 -0500 Sami Ketola <sami(a)ketola.io> wrote ---- So adding "-o imapc_list_prefix=INBOX" to the doveadm command line should fix that, I would think ? So is the remote INBOX really 'INBOX' or 'INBOX.INBOX'? Command line arguments depend on which one it is. I managed to find some old archived emails with some tips on how it was solved back then. It was done with something like this: normal doveadm command: 'LOG_STDERR_TIMESTAMP="%b %d %H:%M:%S.%{usecs} " ' + '/usr/bin/doveadm' + dsync_debug + \ " -o mail_prefetch_count=10 " + \ " -o imapc_features=fetch-headers " + \ " -o imapc_host=" + legacy_host + \ " -o imapc_port=" + legacy_port + \ " -o imapc_list_prefix=" + imapc_prefix + \ " -o imapc_prefix=" + imapc_prefix + \ " -o imapc_user=" + self.legacy_user + \ " -o imapc_master_user=" + self.legacy_user + \ " -o imapc_password=" + imapc_master_password + \ " -o mail_fsync=never " + \ " backup -u " + self.uid + \ " -R imapc: >> " + dsync_err_log_location + self.uid + ".dsync_err.log 2>&1" If I remember correctly imapc_prefix was 'INBOX/' since this customer had INBOX/INBOX setup with / as separator. and if user had INBOX/INBOX detected this command was run on top of that to migrate INBOX: 'LOG_STDERR_TIMESTAMP="%b %d %H:%M:%S.%{usecs} " ' + '/usr/bin/doveadm' + dsync_debug + \ " -o namespace/inbox/prefix= " + \ " -o mail_prefetch_count=10 " + \ " -o imapc_features=fetch-headers " + \ " -o imapc_host=" + legacy_host + \ " -o imapc_port=" + legacy_port + \ " -o imapc_user=" + self.legacy_user + \ " -o imapc_master_user=" + self.legacy_user + \ " -o imapc_password=" + imapc_master_password + \ " -o mail_fsync=never " + \ " backup -u " + self.uid + \ " -m INBOX/INBOX " + \ " -R imapc: >> " + dsync_err_log_location + self.uid + ".dsync_err.log 2>&1" HTH, Sami

1 0

Re: dovecot Digest, Vol 229, Issue 23
by Thom Pol 18 May '22

18 May '22

I must say I was a bit sceptical if this sieve script would resolve it, but it seems like it totally did! Thanks a lot for your reply, hope this helps someone else in the future as well. Kind regards, Thom Pol On 16/05/2022 08:12, Paul Kudla (SCOM.CA Internet Services Inc.) wrote: > ok duplicsate emails (even across dsync, replication etc) is typically > handled via a global sieve script > > > I use : > > # cat duplicates.sieve > require "duplicate"; # for dovecot >= 2.2.18 > > if duplicate { > discard; > stop; > } > > for the scripts > > and setup sieve to work via my dovecot.conf file > > relative parts below : > > -------------------------------------------------------------------- > > protocols = imap pop3 lmtp sieve > > protocol lmtp { > mail_plugins = $mail_plugins sieve > postmaster_address =monitor(a)scom.ca > } > > > protocol lda { > mail_plugins = $mail_plugins sieve > } > > > plugin { > ..... > > sieve =file:~/sieve;active=~/sieve/.dovecot.sieve > > sieve_duplicate_default_period = 1h > sieve_duplicate_max_period = 1d > sieve_extensions = +duplicate +notify +imapflags +vacation-seconds > sieve_global_dir = /usr/local/etc/dovecot/sieve > sieve_before = /usr/local/etc/dovecot/sieve/duplicates.sieve > > ..... > } > > service managesieve-login { > process_limit = 1000 > vsz_limit = 1g > inet_listener sieve { > port = 4190 > } > } > > protocol sieve { > managesieve_implementation_string = Dovecot Pigeonhole > managesieve_max_line_length = 65536 > } > > > > ------------------------------------------------------------------ > > > note the sieve_before which handles duplictes during delivery etc. > > > Happy Monday !!! > Thanks - paul > > Paul Kudla > > > Scom.ca Internet Services<http://www.scom.ca> > 004-1009 Byron Street South > Whitby, Ontario - Canada > L1N 4S3 > > Toronto 416.642.7266 > Main?1.866.411.7266 > Fax?1.888.892.7266

2 1

dovecot virtual users with sendmail, my solution
by Christopher McCrory 18 May '22

18 May '22

Hello... I wanted to use dovecot virtual users with sendmail. As you probably know, this doesn't work by default. The more scalable solution is probably to use LDAP, but I really don't like it. This is how I did it https://github.com/chrismcc-gmail/dovecot-virtual-sendmail Basically I abused glibc's db feature in /etc/nsswitch in /var/db/Makefile something like this: $(VAR_DB)/passwd.db: /etc/dovecot/usersfile @printf %s "$(patsubst %.db,%,$(@F))... " @$(AWK) 'BEGIN { FS=":"; OFS=":" } \ /^[ \t]*$$/ { next } \ /^[ \t]*#/ { next } \ /^root/ { next } \ /^[^#]/ { printf ".%s ", $$1; \ printf "%s:x:65534:65534:%s:/home/vmail/%s:/sbin/nologin\n", $$1, $$1, $$1; \ }' $^ | \ $(MAKEDB) -o $@ - @echo "done." make -C /var/db getent passwd ; shows ... virtualuser:x:65534:65534:virtualuser:/home/vmail/virtualuser:/sbin/nologin othervuser:x:65534:65534:othervuser:/home/vmail/othervuser:/sbin/nologin A longer explanation and more info is in the github repository It takes about 10 minutes to go from new clean server to working email server with this I've been running this in production for about a week now without any problems. Question: Has anyone else done this? I don't see any downsides, but I might be missing something. -- Christopher McCrory To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the engineer, the glass is twice as big as it needs to be.

2 1

Preventing deletion of mails in some directories?
by Philip Rhoades 18 May '22

18 May '22

People, I can't get the system "chattr" to do what I want so I am wondering if there is some way to prevent deletion of mails in the INBOX and the Sent folders? Renaming and moving files needs to be possible for Maildir functions and also for me - so I only need deletion prevention . . Is this possible from Dovecot? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

3 2

Can sync/migrate all mail from remote imap account except the main "INBOX"
by Darren Mobley 18 May '22

18 May '22

Greetings! I've been trying to sync my email to a server, however it only syncs the mail in folders other than INBOX. For testing purposes, I've created a fake domain, "letest.tld" and a new empty user account "mailto:saywhatnow@letest.tld" to receive the copy of the mail being migrated. What I've been trying are iterations of: /usr/bin/doveadm -D -o mail_fsync=never -o dsync_features=empty-header-workaround -o imapc_ssl=imaps -o imapc_features=rfc822.size,fetch-headers -o dsync_commit_msgs_interval=100 -o imapc_port=993 -o imapc_host=imap.zoho.com -o imapc_password=NoNoTRe4LLyMyP4$$ -o imapc_user=mailto:decker@n3t.net -o mail_prefetch_count=20 sync -1Ru mailto:saywhatnow@letest.tld imapc: Regardless of running sync -1 or backup (I want to keep original mailbox as-is for now) I get errors related to INBOX. With sync -1 ; May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Ignore nonexistent mailbox GUID c92f64f79f0d1ed01e6d5b314f04886c with -1 sync May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: We don't have mailbox c92f64f79f0d1ed01e6d5b314f04886c May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: brain M: Ignoring missing remote box GUID c92f64f79f0d1ed01e6d5b314f04886c May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX.Archive: Mailbox opened May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX.Archive: Mailbox opened May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Skipping unchanged mailbox 51a58e1d1d5c491aac71488647b20224 May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX.Commercial Spam: Mailbox opened May 10 16:53:29 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX.Commercial Spam: Mailbox opened With backup : May 10 16:54:55 doveadm(mailto:saywhatnow@letest.tld): Debug: brain M: Namespace INBOX. has location maildir:/home/letest/mail/letest.tld/saywhatnow:UTF-8 May 10 16:54:55 doveadm(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX: Mailbox opened May 10 16:54:55 doveadm(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX: Mailbox opened May 10 16:54:55 doveadm(mailto:saywhatnow@letest.tld): Debug: Namespace INBOX.: Using permissions from /home/letest/mail/letest.tld/saywhatnow: mode=0700 gid=default ... May 10 16:54:55 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Namespace INBOX. has location imapc: May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain M: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1 uid_next=1 subs=yes last_change=0 last_subs=1652217475 May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1 uid_next=8230 subs=yes last_change=0 last_subs=0 ... May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain M: Remote mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1 uid_next=8230 subs=yes last_change=0 last_subs=0 ... May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain M: Mailbox INBOX: local=c92f64f79f0d1ed01e6d5b314f04886c/0/1, remote=c92f64f79f0d1ed01e6d5b314f04886c/0/1: Mailboxes are equal ... May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX: Mailbox opened May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Mailbox INBOX: local=c92f64f79f0d1ed01e6d5b314f04886c/0/1, remote=c92f64f79f0d1ed01e6d5b314f04886c/0/1: Mailboxes are equal ... May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: Mailbox INBOX: Mailbox opened May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: Change during sync: Mailbox GUID c92f64f79f0d1ed01e6d5b314f04886c was lost May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain S: We don't have mailbox c92f64f79f0d1ed01e6d5b314f04886c May 10 16:54:57 dsync(mailto:saywhatnow@letest.tld): Debug: brain M: Change during sync: Remote lost mailbox GUID c92f64f79f0d1ed01e6d5b314f04886c (maybe it was just deleted?) ... May 10 16:55:33 dsync(mailto:saywhatnow@letest.tld): Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID c92f64f79f0d1ed01e6d5b314f04886c (maybe it was just deleted?) This is odd, since that very GUID is in the uidlist file for the base folder: # grep -R Gc92f64f79f0d1ed01e6d5b314f04886c /home/letest/mail/letest.tld/saywhatnow /home/letest/mail/letest.tld/saywhatnow/dovecot-uidlist:3 V1 N1 Gc92f64f79f0d1ed01e6d5b314f04886c I've tried all sorts of things to get this to work, including removing the entire /home/letest/mail/letest.tld/saywhatnow/ directory so there could be no conflicts with existing mailbox, set mailbox_list_index=no , set lda_mailbox_autocreate=no , etc. The errors appear to originate from src/doveadm/dsync/dsync-brain-mailbox.c but it's not really telling me a lot. I'm using dovecot version 2.3.18 (9dd8408c18) on a cPanel server. `dovecot -n` output attached. Any help would be greatly appreciated! Thanks, Darren

3 5

Dovecot and RFC6856
by Tan Mientras 17 May '22

17 May '22

Hi. Just after upgrading *courier* from an old version, we are receiving warning messages instead of mails stating: "This E-mail message was determined to be Unicode-formatted but your E-mail reader does not support Unicode E-mail." warnings. It looks much like: *https://bugzilla.mozilla.org/show_bug.cgi?id=1571672 <https://bugzilla.mozilla.org/show_bug.cgi?id=1571672>* https://talk.plesk.com/threads/messages-with-unicode-unable-to-pick-up-via-… it seems, malformed mails (they showed errors before migration, but they were shown at least!) are handled incorrectly by thunderbird and the only option is to *revert backwards or migrate to dovecot*. *Does dovecot also implement RFC8656*? Will the same happen if we migrate to dovecot? Any plans for future adoption of that RFC?

2 1

Shared mailboxes, users with dots and a bug in subscriptions
by Tobias Stein 17 May '22

17 May '22

Hi, i'm running Dovecot 2.3.14.alpha0 with shared namespaces and stumbled across some errors messages logged, when the list of subscribed mailboxes is queried by a client. For every distinct account of in the list of subscriptions two corresponding lines are logged: Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/noc@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/info@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/root@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Similar messages are logged, when invalid entries are listed in '/var/lib/dovecot/db/shared-mailboxes', which i already pruned and haven't received them anymore since. I think these errors are caused by an unintended behaviour when writing "~/Maildir/subscriptions", which looks (shortened) like this. V 2 INBOX/INBOX shared/noc@example com/INBOX shared/info@example com/INBOX shared/root@example com/test shared/root@example com/test test_sub The subscription-file.c explodes the name on every hierarchy separator ('.','\0') and inserts a TAB character. Unfortunately it also explodes on the DNS label delimiter „.‟. This should probably be fixed by passing a structure containing the required information to the formatter to distinguish mailboxes from domain-names. Subscription in combination with multiple domains and shared mailboxes seems broken to me. Actually i can't even explain to me, why it is working in face of the errors. :-) Unfortunately in Maildir++ the separator dot is hard-coded. There is a very old thread on this mailing list, that suggests using „auth_username_translation‟ to replace dots with a different character, but this idea is getting worse the longer i think about it. I absolutely dislike the idea to set LAYOUT=fs, namespace/separator = § to change the separators to split on, because this would mean to restructure the physical layout of all mailboxes (hierarchically) and mess around with lots of files. I attached a dovecot-sysreport to reproduce the behaviour. /etc/dovecot/private/example.com/users looks like this: ### user:password:uid:gid:(gecos):home:(shell):extra_fields noc:{SSHA512}_hash_:::::: info:{SSHA512}_hash_:::::: root:{SSHA512}_hash_:::::: Please correct me if i'm wrong or point me to a workaround, but i think the layout code needs some love. :-) Best regards Tobias

2 4

Re: Permissions and ownership on /dev/shm/dovecot
by doug 16 May '22

16 May '22

1 0