- dovecot - dovecot.org

doveadm SSL problem with recent update
by Trever L. Adams 27 Oct '20

27 Oct '20

With a recent update, I started seeing this: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/letsencrypt/live/SERVER/fullchain.pem: Permission denied 1 4 * * * vmail /usr/bin/doveadm expunge -A mailbox MAILBOXINQUESTION savedbefore 1w is one of the crontab entries I am seeing this for. Is there an option to keep doveadm from trying to use the ssl cert from that configuration file? I do not want to have the vmail user having access to the pem cert. Thank you. Trever

2 2

Newbie question about replication
by Piotr Auksztulewicz 27 Oct '20

27 Oct '20

Hi, I am a long-time dovecot user/admin for my family mail server, but I had ventured into configuring replication only recently and I am not sure about how it should work and what are the good practices. My intent for replication was to have another instance to switch to in a short time if something fails. I have daily backups, but it will take much more time to rebuild and restore than just to switch to a good instance while taking time to restore the bad one. The setup seems to work just fine from IMAP client point of view (minus sieve scripts - but I have worked it around as I am not yet ready to upgrade dovecot beyond what's in stable Debian at the moment). I have my clients configured to access instance A exclusively; instance B is just sitting around with no clients routinely connected. Also only instance A is receiving deliveries from both my primary and secondary MTAs. I have some doubt however if this is the right thing to do and if it is correct from the dovecot server point of view. I have observed my mail storage directories on both instances and have noticed that they diverge a little over time - the instance B not having all the updates. However the moment I connect another client to instance B and log in as a particular user, the state on instance B springs to the correct state and I see the same content on both clients, and the storage directories become identical as well. I am afraid that, if instance A fails, I would not have the current state on instance B. Is there anything I should have done differently? Here is dovecot -n output of instance A. Instance B config is symmetrical with imap1/2 hostnames switched. FYI: actual domain is substituted for privacy. mail.mydomain.net is an internal subdomain with private IP addresses. Instances of dovecot are containerized with access to internal virtual bridge on which MTAs and supporting processes are present as well. The access from outside is provided by port forwarding/NAT, only for imaps and pop3s ports. Other ports are only internally accessible for local clients (postfix, mutt, doveadm command line tool etc.) or debug purposes. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-cloud-amd64 x86_64 # Hostname: imap1.mail.mydomain.net auth_failure_delay = 3 secs auth_verbose = yes auth_worker_max_count = 5 deliver_log_format = msgid=%m; from=%f: %$ disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 4551 first_valid_uid = 100 login_greeting = # <redacted> mail_attribute_dict = file:mail/dovecot-attributes mail_gid = 122 mail_home = /var/vmail/%u mail_location = maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 mail_plugins = " notify replication" mail_privileged_group = vmail mail_uid = 113 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader vnd.dovecot.debug namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext.local driver = sql } plugin { mail_replica = tcp:imap2.mail.mydomain.net sieve = ~/.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.debug +editheader sieve_user_log = ~/log/sieve.log } pop3_fast_size_lookups = yes pop3_lock_session = yes pop3_no_flag_updates = yes pop3_save_uidl = yes protocols = " imap lmtp sieve pop3" replication_max_conns = 5 service aggregator { fifo_listener replication-notify-fifo { group = root mode = 0660 user = vmail } unix_listener replication-notify { group = root mode = 0660 user = vmail } } service auth-worker { chroot = /etc/dovecot/db process_limit = 10 unix_listener auth-worker { mode = 0600 user = doveauth } user = doveauth } service auth { client_limit = 64 inet_listener sasl { address = imap1.mail.mydomain.net port = 9192 } unix_listener auth-userdb { group = vmail mode = 0660 user = doveauth } user = doveauth } service dict-async { protocol = none } service dict { protocol = none } service director { protocol = none } service doveadm { inet_listener doveadm { address = imap1.mail.mydomain.net port = 4551 } } service imap-hibernate { protocol = none } service imap-login { inet_listener imap { address = imap1.mail.mydomain.net port = 143 } process_limit = 30 service_count = 1 } service imap-urlauth-login { protocol = none } service imap-urlauth-worker { protocol = none } service imap-urlauth { protocol = none } service imap { chroot = /var/vmail client_limit = 15 process_limit = 30 service_count = 32 user = vmail } service indexer-worker { process_limit = 3 user = vmail } service indexer { chroot = $base_dir } service lmtp { client_limit = 1 extra_groups = group = vmail inet_listener lmtp { address = imap1.mail.mydomain.net port = 2306 } process_limit = 6 user = vmail } service log { user = $default_internal_user } service managesieve-login { inet_listener sieve { address = imap1.mail.mydomain.net port = 4190 } process_limit = 3 service_count = 1 } service managesieve { chroot = /var/vmail process_limit = 3 service_count = 1 user = vmail } service pop3-login { inet_listener pop3 { port = 0 } process_limit = 4 service_count = 1 } service pop3 { chroot = /var/vmail process_limit = 4 service_count = 1 user = vmail } service replicator { unix_listener replicator-doveadm { group = root mode = 0600 user = vmail } } service submission-login { protocol = none } service tcpwrap { protocol = none } ssl_cert = </etc/dovecot/private/dovecot.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext.local driver = sql } valid_chroot_dirs = /var/vmail /etc/dovecot/db verbose_proctitle = yes protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { imap_metadata = yes } -- Piotr "Malgond" Auksztulewicz firstname(a)lastname.net

2 5

Re: Dovecot replication not picking up new mail in maildir
by Justin Ridge 27 Oct '20

27 Oct '20

On 26/10/2020 19:25, John Fawcett wrote: > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote: >> I've got a basic dovecot master-master replication setup between two >> servers (imap1 and imap2). Actions such as deleting messages or moving >> them between folders are replicated correctly and quickly. >> >> However, when new mail is delivered by postfix, replication does not >> occur until something else triggers it, such as one of the delete/move >> actions mentioned earlier. A search suggested this may be due to the >> notify plugin, but I don't see any issue with the settings. Output of >> doveconf -n: > > Hi > > is there any error in the log? > > Can you show some evidence or an example? ie some email delivery in the > master but not on the slave? > > Can you be sure to check both new and cur subdirectories on master and > slave? > > John There's precisely nothing in the log. The new mail arrives on the master, and it is as though dovecot completely ignores it for the purposes of replication. However, I think I have solved the problem by enabling LMTP and forcing postfix to go through that rather than writing to the maildir directly. Perhaps LMTP is required for replication and I just didn't realize it. End result is (I think) it is working properly. J

3 3

imapsieve: setting imapsieve_url disables admin scripts
by Gedalya 27 Oct '20

27 Oct '20

Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url makes it all work again. # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-5-amd64 x86_64 Debian bullseye/sid xfs # Hostname: ------ auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes imapc_features = rfc822.size fetch-headers imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /srv/mail/domains/%d/%n mail_location = mdbox:/srv/mail/domains/%d/%n/mdbox mail_plugins = quota fts fts_solr mail_prefetch_count = 20 mail_privileged_group = mail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve mdbox_preallocate_space = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ fts_tika = http://127.0.0.1:9998/tika/ imapsieve_mailbox1_before = file:/usr/local/lib/imapsieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/local/lib/imapsieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/usr/local/lib/imapsieve/report-spam.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Junk2 imapsieve_mailbox4_before = file:~/sieve/IMAP-Sent.sieve imapsieve_mailbox4_causes = APPEND COPY imapsieve_mailbox4_name = Sent quota = count:User quota:noenforcing quota_rule = *:storage=5120M quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve-global/fileinto-spam.sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/local/lib/imapsieve sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_fast_size_lookups = yes pop3_no_flag_updates = yes protocols = " imap lmtp sieve pop3" quota_full_tempfail = yes service auth-worker { user = $default_internal_user } service auth { unix_listener auth-client { group = Debian-exim mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } service_count = 0 } service imap { vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = ------- port = 2525 } unix_listener lmtp { group = Debian-exim mode = 0660 user = root } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 } service pop3-login { inet_listener pop3 { port = 110 } service_count = 0 } ssl = required ssl_cert = </etc/letsencrypt/live/--------/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota fts fts_solr sieve ssl = no } protocol !indexer-worker { mail_vsize_bg_after_count = 100 } protocol lda { mail_plugins = quota fts fts_solr sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota fts fts_solr imap_quota imap_sieve } protocol sieve { mail_max_userip_connections = 10 }

2 2

imapc_port not working
by David Tildesley 27 Oct '20

27 Oct '20

Hi, Dovecot v2.3.7.2 on Ubuntu 18.04LTS I have configured for imap proxy to imap.gmail.com However whilst the imapc_host setting is working, imapc_port is not - it ignores the value I set and dovecot always tries to connect to gmail on port 143 (as per error log output). I have the imapc settings in the 10-mail.conf which gets loaded by dovecoat.conf Looks like a bug. Any assistance would appreciated. Regards,David.

2 9

forwarding email with sieve of spf domains
by Marc Roos 27 Oct '20

27 Oct '20

Say someone has setup spf for his domain and sends an email to a user that has in roundcube enabled the sieve forward. If the message is forwarded without altering the message headers, this could result in a message being blocked or not relayed, because sending hosts ip, is not in the spf of the from: domain. Possible solutions are: - add option if enabled, it replaces the From: with that of the email address of the sieve user. (Maybe move the original sender to the Reply-To header? Maybe exception for 'internal' forward?) - Upon processing the message, check the spf records, if they are enforced, do the above, otherwise do nothing. https://tools.ietf.org/html/rfc5228#section-4.2

6 7

Roundcube can't receive emails
by direktor 26 Oct '20

26 Oct '20

Hello, Can someone guide me how to test the mail software? I can send emails but can't receive. I have Dovecot - telnet to 143 port says Dovecot OK. Same with port 25. I get back mail delivery problem. 550. No mail shows in Roundcube. Log files maillog shows nothing, seems empty. It's clean install. On testing Exim log I get something like this: pop3-login auth Error: passrd-file: stat (/etc/exim/domains/myserver/passwd) failed: No such file or directory So what is wrong, how to check and how to fix it? -- Sent from: http://dovecot.2317879.n4.nabble.com/

1 0

Dovecot replication not picking up new mail in maildir
by jayare~dcml＠videocoding.org 26 Oct '20

26 Oct '20

I've got a basic dovecot master-master replication setup between two servers (imap1 and imap2). Actions such as deleting messages or moving them between folders are replicated correctly and quickly. However, when new mail is delivered by postfix, replication does not occur until something else triggers it, such as one of the delete/move actions mentioned earlier. A search suggested this may be due to the notify plugin, but I don't see any issue with the settings. Output of doveconf -n: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 4.19.118-0-vanilla x86_64 CentOS Linux release 7.8.2003 (Core) # Hostname: imap1 disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 haproxy_trusted_networks = 172.16.0.0/24 mail_location = maildir:~/Mail mail_plugins = zlib notify replication mailbox_list_index = yes mailbox_list_index_include_inbox = yes maildir_empty_new = yes mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcp:imap2:9943 replication_sync_timeout = 2 } protocols = imap service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service config { unix_listener config { user = dovecot } } service doveadm { inet_listener { port = 9943 } } service imap-login { inet_listener imap_hpx { haproxy = yes port = 943 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = no userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = zlib notify replication } protocol imap { mail_plugins = zlib notify replication imap_zlib } I specifically tried setting the following as no and yes as they can affect notifications: mailbox_list_index = yes mailbox_list_index_include_inbox = yes maildir_empty_new = yes The other server has the same settings except obviously mail_replica = tcp:imap1:9943. Any suggestions welcome, thanks!

2 1

dovecot-uidlist invalid data
by Maciej Milaszewski 26 Oct '20

26 Oct '20

Hello I have a problem with Invalid data System debian10 dovecot-2.2.36.4 # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10 Oct 23 15:57:52 dovecot6 dovecot: lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file /vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data: In debian9 - kernel-4.9.0-13 - problem exists In debian10 - kernel-4.19.0-12 - problem exist In debian8 - kernel 3.16.0-11-amd64 - problem not exists In debian9 - kernel 3.16.0-11-amd64 - problem not exists storage mount from storage NetApp storage:/vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.19.19.19,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=10.19.19.19) cat /etc/fstab storage:/vmail /vmail nfs rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120,nocto 0 0 Probably somthing in kernel or mount options. Any idea ?

1 1

Re: Looking for a guide to collect all e-mail from the ISP mail server
by R. Diez 26 Oct '20

26 Oct '20

> What you are looking for would be a very advanced setup > [...] I don't think so. But we'll see! I would be happy to take a pre-packaged mail server solution like iRedMail which includes RoundCube or whatever. I just need a "easy", practical guide to reconfigure it to 1) download e-mails from a multidrop, and 2) relay external e-mail to the ISP's SMTP server. Well, at least saying it like that does not sound hard. 8-) > More importantly, most ISPs are very limited in the way of support. > [...] While that assertion is generally true, most ISPs I have seen do get the basic e-mail service right. All have a kind of "catch all" e-mail address. Level of service is normally fine for a small business. If it is not, you can always change ISP. Hardware costs are not a problem. Most small companies I have seen have a file server sitting idle most of the time. Creating a VM with VirtualBox or KVM is relatively easy. Backing the mail server up is easy too: you just copy the VM as a big file. In a small business you may need a few Gigabytes per year if you want to keep all e-mails. I have even written a script that stops a KVM virtual machine every day at 4 am, backs the big file up to a NAS, and the restarts the VM. OK, I am not actually using it, and there is room for improvement, but the basic idea would work. If the server breaks, you have some downtime and you lose some data, but not too much. Most small businesses have more downtime and more data loss for other reasons. Retention is problematic anyway even if you use an external provider. With an external provider you also have to consider data protection issues. Small businesses are often exempt from difficult legal requirements (but I am not a lawyer either). > The server would still need to be accessible publicly for email to be routed to it. That's not the case. It hasn't been for an Exchange Server with "POP3 Connector" that I have seen. And it will not be the case with a Dovecote that fetches e-mail from the ISP over multidrop. > [...] > things unexpectedly and you still have maintenance regarding deliverability > (i.e. reputation, dkim/spf/dmarc) and will still be paying additional Not applicable. Reputation, SPF, etc. is handled by the ISP. Those are standard things, a commodity nowadays. > [...] > Webform attacks are rising so there would Not applicable. No web interface exposed. Only accessible over a VPN connection. > [...] > This includes the workaround.org guide which you'll inevitably run across. > That guide was designed for a personal server, its a good step forward > but there are many more requirements needed for business. That is true. On the other hand, you may be overestimating the needs of a small business. Some of them still use Hotmail addresses! > [...] > Stakeholders will need to include all emails related to it at the final signing. > [...] I am thinking of a small business here, where most things are rather more informal. Something along the lines of "I would do it this way, but if you need something professional, I am out of my depth, because I am not actually an admin at all, you know". That's how real life often works. 8-) In other words, I am looking for a workaround.org guide for multidrop. Just for fun! Regards, rdiez

3 4

Panic mbox_sync_handle_header
by Igor Russkih 25 Oct '20

25 Oct '20

Hello all, I'm getting a very often panic on my local dovecot setup when accessing some of the local folders. Error message is always Oct 25 14:34:50 imap(irusskikh): Panic: file mbox-sync.c: line 665 (mbox_sync_handle_header): assertion failed: (mail_ctx->mail.from_offset + move_diff != 1 && mail_ctx->mail.from_offset + move_diff != 2) Oct 25 14:34:50 imap(irusskikh): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa05a2) [0x7f05e40005a2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa069a) [0x7f05e400069a] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f05e3f901d8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x8b1d7) [0x7f05e432b1d7] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_sync+0x48) [0x7f05e432bbf8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_storage_sync_init+0x3b) [0x7f05e432bd3b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) [0x7f05e42eb704] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f05e42eb7a7] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7f05e43663c1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7f05e42ebb51] -> dovecot/imap(imap_status_get+0x77) [0x7f05e4c25017] -> dovecot/imap(cmd_status+0x19e) [0x7f05e4c171de] -> dovecot/imap(command_exec+0x5c) [0x7f05e4c1ce0c] -> dovecot/imap(+0x1b382) [0x7f05e4c1b382] -> dovecot/imap(+0x1b41c) [0x7f05e4c1b41c] -> dovecot/imap(client_handle_input+0x18d) [0x7f05e4c1b7dd] -> dovecot/imap(client_input+0xac) [0x7f05e4c1bd2c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f05e4016642] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f05e4017cee] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f05e40166d6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f05e4016888] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f05e3f9aa83] -> dovecot/imap(main+0x329) [0x7f05e4c0e139] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f05e3b81b97] -> dovecot/imap(_start+0x2a) [0x7f05e4c0e2ca] Oct 25 14:34:50 imap(irusskikh): Fatal: master: service(imap): child 12785 killed with signal 6 (core dumped) # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.4.0-17763-Microsoft x86_64 Ubuntu 18.04.4 LTS Running now on WSL, but have the same badness on generic ubuntu setup as well. Could somebody guide me if thats something known, or me doing bad things? I'm not on the list, so please CC me. Igor

1 0

dovecot.lda-dupes
by ＠lbutlr 24 Oct '20

24 Oct '20

What is the purpose and/or use of the dovecot.lda-dupes file that (sometimes) exists in the home folder for each user? I've seen some posts about issues with the file or losing track of the location, etc, but nothing on what the file actually does or how it could be useful. I assume it is just a dovecot file that helps not keep track of … I guess duplicate mails? It looks like it contains the message-ids and email destinations for certain, but not all, duplicate emails, but in a binary format. -- "The good news: Hadron Collider went live and did not destroy ALL reality. Bad: I'm the only one who remembers President Gore's 2 terms." --Andy Ihnatko

2 1

net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied
by mj 24 Oct '20

24 Oct '20

Hi, We are getting very occasional messags from dovecot: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.6 xfs snip... > service stats { > unix_listener stats-reader { > group = vmail > mode = 0660 > user = vmail > } > unix_listener stats-writer { > group = vmail > mode = 0660 > user = vmail > } > } and the on-disk permissions are: > root@dovecot:~# ls -l /var/run/dovecot/*stat* > srw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats > prw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats-mail > prw------- 1 root root 0 Oct 6 00:25 /var/run/dovecot/old-stats-user > srw-rw---- 1 vmail vmail 0 Oct 6 00:25 /var/run/dovecot/stats-reader > srw-rw---- 1 vmail vmail 0 Oct 6 00:25 /var/run/dovecot/stats-writer We're not sure what makes the Permission denied error happen... Anyone with an idea? MJ

3 3

Sieve_before
by ＠lbutlr 24 Oct '20

24 Oct '20

So, this is what I did instead of default_sieve: sieve_before = file:/usr/lib/dovecot/sieve/bcc.sieve sieve_before2 = file:/usr/lib/dovecot/sieve/filespam.sieve # cat /usr/lib/dovecot/sieve/bcc.sieve require ["variables", "copy"]; if address :matches ["To", "Cc"] ["*@*."] { redirect :copy "backup+295.${1}.${2}@. . ."; } # cat /usr/lib/dovecot/sieve/filespam.sieve require ["fileinto", "imap4flags"]; if header :contains "X-spam-flag" "YES" { fileinto :flags "\Seen" "Junk"; } The bcc.sieve file is generated each day with a little script to put in the day of the year, so that for the backup user the folder structure for backups for my list mail is, for example: 295 kremels kreme <messages> otheruser kreme <messages> And tomorrow new folders for 296 will be created. So far, I think it's working. 🤞 -- C code. C code run. Run, code, run.

4 17

antispam plugin again
by Maciej Milaszewski 23 Oct '20

23 Oct '20

Hello I have a problem with migrating dovecot from 2.2.36 to 2.3.8 - everything works fine, but a problem with migrating anti-spam plugins New dovecot 2.3.x has implemented own antispam-plugin like: ---- new from dovecot 2.3.8 ----- # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib64/dovecot/sieve/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/usr/lib64/dovecot/sieve/report-ham.sieve sieve_pipe_bin_dir = /usr/lib64/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment #setting_name = value sieve_global_dir = /etc/sieve_global sieve_max_redirects = 20 sieve_vacation_use_original_recipient = yes expire = SPAM #expire_dict = proxy::expire expire_dict = redis:host=127.0.0.1:prefix=expire/ --------------------------------------------------------------------------------------- In older version dovecot I use antispam_plugin + simple script: ---------------- old from 2.2.36.4 + antispam plugin ---------- ... antispam_backend = MAILTRAIN antispam_mail_spam = --spam antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/spam-learn.sh antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = spam;inbox.spam;Unwanted antispam_trash_pattern_ignorecase = trash;Deleted *;Junk*;kosz antispam_debug_target = syslog antispam_verbose_debug = 1 ------------------------- How do I change the bash file to make it work like on the old system (I use pyzor) like: cat /usr/local/bin/spam-learn.sh #!/bin/sh date >> /tmp/spam.txt echo $@ >> /tmp/spam.txt if [ "x$1" = "x--spam" ]; then /usr/bin/pyzor report >> /tmp/spam.txt 2>&1 fi if [ "x$1" = "x--ham" ]; then /usr/bin/pyzor whitelist >> /tmp/ham.txt 2>&1 fi

1 0

Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: transaction context
by Graham Leggett 22 Oct '20

22 Oct '20

Hi all, While trying to reindex a large mailbox to take advantage of Apache Tika, dovecot logs the following message: Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: transaction context The message is vague in that a transaction has failed, but nowhere does it say what the transaction boundaries are. Did the transaction affect the indexing of one message, or many messages? Did the indexing of the whole mailbox get aborted and rolled back, or just a single message? A wide question. How do I ensure that my shiny new dovecot index gets completely reindexed? How do I know if dovecot is indexing just the new messages, and ignoring the existing messages? Regards, Graham —

1 0

Best prometheus exporter for Dovecot 2.3 with the new metrics/stats module
by Sidsel Jensen 22 Oct '20

22 Oct '20

Hi ppl. I am trying to locate the best prometheus exporter for use with Dovecot 2.3 in connection with the new metrics/stats module. Any pointers in the right direction will be appreciated - seems like there is a bunch out there which all works with the old stats module. Anybody have something “in the works” for 2.3 ? Kind Regards, Sidsel Jensen

2 1

Testing with imaptest to non existing folder makes imap service crash
by Marc Roos 22 Oct '20

22 Oct '20

FWIIW I had this message still in drafts /usr/bin/imaptest - append=100,0 logout=0 host=xxx port=143 user=xxx pass=xxx seed=100 secs=1 clients=1 mbox=64kb.mbox box=inbox/test msgs=100000 And inbox/test does not exist, results in: Fatal: master: service(imap): child 20282 killed with signal 11 (core dumped)

2 1

Understanding matches in sieve
by ＠lbutlr 22 Oct '20

22 Oct '20

RFC 5229 gives the following example: if address :matches ["To", "Cc"] ["coyote(a)**.com", "wile(a)**.com"] { # ${0} is the matching address # ${1} is always the empty string # ${2} is part of the domain name ("ACME.Example") fileinto "INBOX.business.${2}"; stop; And I do not understand why ${1} is always the empty string. In this example, ${1} is the part before the < so using ${2} makes sense. if header :matches "List-ID" "*<*@*" { fileinto "INBOX.lists.${2}"; stop; } I am laso not sure why the first example used **.com instead of *.com (or is that the reason $1 doesn't contain anything because it is the first * of **?). If so, my familiarity with the bash syntax for ** may have been my undoing. If I had # Given to kremels(a)kreme.com if address :matches ["To", "Cc"] ["*(a)*.*"] # ${1} would contain "kremels" # ${2} would contain "kreme" # ${3} would contain "com" Yes? -- "Are you pondering what I'm pondering?" "Sure, Brain, but how are we going to find chaps our size?"

2 2

Users unable to login
by jesus san miguel 22 Oct '20

22 Oct '20

I have certain power users who can't login through POP3 or IMAP from their computer while being receiving mail on their cell phones (pop3), despite pop3_lock_session = no Am I hitting some other limit? I don't see any error in dovecot.log but a generic failed login: Oct 21 10:31:44 imap-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<someuser(a)somedomain.com>, method=DIGEST-MD5, rip=::1, lip=::1, secured, session=<XSVQLSqy2IYAAAAAAAAAAAAAAAAAAAAB> Running version is 2.3.11.3

4 8

Restrictions on default.sieve
by ＠lbutlr 21 Oct '20

21 Oct '20

Are there actions that default.sieve cannot take? I tried adding redirect :copy "backup+foo(a)local.example.com" and… nothing. No errors I can find, but also no mail being redirected. I also tried # there must be 'from' in the received headers if header :contains "received" "from" { redirect :copy "backup+foo(a)local.example.com" } And if header :index 1 :contains "received" "from" { redirect :copy "backup+foo(a)local.example.com" } But still, no mail in .foo for the backup user (yes, dovecot is setup to autofile +address into mailboxes, and that works). -- You couldn't say, 'I had orders.' You couldn't say, 'It's not fair.' No one was listening. There were no Words. You owned yourself. ... Not Thou Shalt Not. Say I Will Not. --Feet of Clay

2 3

A user's last access time
by Victor Sudakov 21 Oct '20

21 Oct '20

Dear Colleagues, Is there a file or directory within a user's Maildir, whose date of modification or access indicates the last time the user accessed his/her E-mail via IMAP or POP3? I'd like to figure out the time a user last logged in into his/her mail account, not the last time a mail was delivered to the INBOX. This information is probably available in the log, but a file which is touched each time a user accesses his/her mail, is more convenient. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

7 13

Corrupted dbox file + assertion failure
by tim＠linux-daus.de 21 Oct '20

21 Oct '20

Hi all, a dsync failed due a corrupted mdbox file. Force-resync throws the same error. (Dovecot 2.3.9.2) Is there any change to fix/repair the file? dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: fscking index file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/dovecot.map.index dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Warning: mdbox /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage: rebuilding indexes dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Error: Corrupted dbox file /var/mail/12/DOMAIN.TLD/242/LOCALPART/mdbox/storage/m.6 (around offset=5191109): msg header has bad magic value dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Panic: file dbox-file-fix.c: line 219 (dbox_file_find_next_magic): assertion failed: (ret == -1) dsync-local(LOCALPART(a)DOMAIN.TLD)<MBF5EUC8j1/FfQAAkqONGQ>: Error: Raw backtrace: #0 t_askpass[0x7fbf4218b5f0] -> #1 backtrace_append[0x7fbf4218b860] -> #2 backtrace_get[0x7fbf4218b9c0] -> #3 i_syslog_error_handler[0x7fbf42196840] -> #4 default_fatal_handler[0x7fbf42196910] -> #5 i_fatal[0x7fbf420ec3b7] -> #6 dbox_attachment_file_get_stream[0x7fbf424c1010] -> #7 dbox_file_fix[0x7fbf424c1540] -> #8 mdbox_get_setting_parser_info[0x7fbf424b9290] -> #9 mdbox_storage_rebuild_in_context[0x7fbf424b99a0] -> #10 mdbox_sync_begin[0x7fbf424bbd00] -> #11 mdbox_sync[0x7fbf424bc730] -> #12 mdbox_storage_sync_init[0x7fbf424bc7f0] -> #13 mailbox_sync_init[0x7fbf4249ee80] -> #14 mailbox_sync[0x7fbf4249ef70] -> #15 dsync_brain_master_send_mailbox[0x55d6521dcaa0] -> #16 dsync_brain_run[0x55d6521daae0] -> #17 dsync_brain_run[0x55d6521db360] -> #18 dsync_ibc_has_pending_data[0x55d6521f0840] -> #19 io_loop_call_io[0x7fbf421b0490] -> #20 io_loop_handler_run_internal[0x7fbf421b1e20] -> #21 io_loop_handler_run[0x7fbf421b05c0] -> #22 io_loop_run[0x7fbf421b0810] -> #23 who_line_filter_match[0x55d6521bfa00] -> #24 doveadm_dsync_main[0x55d6521c2280] -> #25 doveadm_mail_single_user[0x55d6521c3090] -> #26 doveadm_mail_try_run[0x55d6521c3900] -> #27 main[0x55d6521b2030] -> #28 __libc_start_main[0x7fbf417c61f0] -> #29 _start[0x55d6521b2670] -> #30 [no start/end information] Regards, Tim

2 1

doveadm http api hign performance?
by hfh＠cndns.com 21 Oct '20

21 Oct '20

Does doveadm http api have high execution efficiency? I have a program that directly calls doveadm http api. Will there be an efficiency problem if a large number of users call it? hfh(a)cndns.com

1 0

How to move/reorganise existing e-mails to yearly subfolders
by R. Diez 21 Oct '20

21 Oct '20

Hi all: I am new to e-mail servers and I am evaluating Dovecot. Not really the best combination. 8-) I am trying to find a balance between legal data retention requirements and online mailbox size. I do not want huge online mailboxes, as doing offline, rotating data backups could then take forever (among other reasons). I would rather avoid online (cloud) backups (data protection etc.). If I set a mailbox size limit, users will have to delete old mails by themselves. Or I could somehow script the deletion of attachments from old e-mails, as attachments are usually the main cause of huge mailboxes. Incidentally, can anyone point me to an easy way to achieve this? Preferably over with IMAP, otherwise with Dovecot tools. With regards to legal data retention (which I am no expert about either), I thought I could use some Postfix BCC feature I heard about in order to copy all incoming and outgoing e-mails to a single "data retention" mailbox. Or maybe several of them. I could then archive e-mails from that mailbox on a yearly basis. I would like to automatically organise e-mails inside that mailbox into subfolders like this: 2019/alice 2019/bob 2020/alice 2020/bob That is: [year]/[username] With such a folder structure, it is easier to see what is going on. Is there a tool that can reorganise existing e-mails into such a folder structure? I found some tools on the Internet to backup and export mails from IMAP to IMAP or maildir destinations. But I could not find a tool that just reorganises (moves) e-mails in such a manner inside an existing mailbox, maybe with a user-defined pattern for the destination folders. I guess moving e-mails around on the same mailbox would be much faster than exporting and reimporting them in some clever way. I could always write a Perl script, but that takes time. Such a tool may already exist. Or perhaps somebody could mention a similar, good-written script I can use as a starting point. I am sure there are many small gotchas to avoid. At the moment, I am only confident with Perl and Java. Maybe JavaScript. It would be best to reorganise the e-mails over IMAP. This way, I am independent of the e-mail server. But a Dovecot-specific solution would also be helpful. I could use such a reorganisation tool not just for archiving or data retention purposes, but to reorganise other mailboxes too, like my personal mailbox. I would rather have a script. Clicking around in Thunderbird does not scale. I have seen that you can use a "sieve" in Dovecot to achieve this. But I guess that would only apply to new e-mails. And that would probably apply just to incoming mails, and not to outgoing ones. If I migrate from the existing e-mail servers, the e-mails will probably be mass-imported without going through any "sieve", right? Besides, I already have a few huge mailboxes with many years of e-mails, stored in a different e-mail server, and it would be nice to be able to reorganise them as they are. That way, I could archive the existing older e-mails before migrating to Dovecot, which would reduce the disk size and the export/import time for the migration. Many thanks in advance, rdiez

4 5

modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?
by PGNet Dev 21 Oct '20

21 Oct '20

I run dovecot + postfix with postfixadmin/sqlite3 I'm set up for all/only virtual users. All outbound mail submits via dovecot submission port. My current dovecot pass/user db queries are password_query = \ SELECT \ username as user, \ password, \ '/data/vmail/%d/%n/Maildir' as userdb_home, \ 5000 as userdb_uid, \ 5000 as userdb_gid \ FROM mailbox WHERE username = '%u' AND active = '1' user_query = \ SELECT \ '/data/vmail/%d/%n/Maildir' as home, \ 5000 AS uid, \ 5000 AS gid, \ ('dirsize:storage=' || quota) AS quota \ FROM mailbox WHERE username = '%u' AND active = '1' It works perfectly for real addresses. I've setup an alias address, e.g. REAL: realuser(a)example.com ALIAS: aliasuser(a)example.com INBOUND email to the ALIAS address -- from the 'net, delivered from postfix via LMTP to dovecot backend -- works fine. BUT any/all mail from local users TO the ALIAS addr fail at userDB lookup 2020-10-20 12:26:54 lmtp(aliasuser(a)example.com)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(aliasuser(a)example.com): auth USER input: 2020-10-20 12:26:54 lmtp(aliasuser(a)example.com)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(aliasuser(a)example.com): Userdb lookup failed What mods are required to the password_query &/or user_query in order to FIX the local->aliasuser mail lookup and delivery ... and ideally not break the rest of delivery?

1 1

lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register
by Mrinal Sharma 20 Oct '20

20 Oct '20

I am trying to use Lua Notification plugin for Event push But saw this error. Can anyone help me on this issue. Error In the logs when I receive an Email is given below. ========================================== Oct 15 21:55:41 master: Info: Dovecot v2.3.11.3 (502c39af9) starting up for imap, lmtp Oct 15 21:56:51 lmtp(36): Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib22_push_notification_lua_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib22_push_notification_lua_plugin.so: undefined symbol: dlua_dovecot_register ====================================================================== # dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 4.19.128-microsoft-standard x86_64 Debian 10.6 9p # Hostname: 238afcc76ba9 auth_debug = yes auth_mechanisms = plain oauthbearer xoauth2 auth_verbose = yes disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it log_path = /dev/stdout mail_debug = yes mail_location = maildir:/data/imap_store/%n mail_plugins = " quota" namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Greeting { auto = create } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = no special_use = \Trash } prefix = } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-oauth2.plain.conf.ext driver = oauth2 mechanisms = plain login } plugin { push_lua_url = http://localhost:5678/mailnotify push_notification_driver = lua:file=/notify.lua quota = maildir:User quota quota_rule = *:storage=5MB quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO } protocols = imap lmtp service doveadm { inet_listener http { port = 80 } } service health-check { executable = script -p health-check.sh inet_listener health-check { port = 5001 } } service lmtp { inet_listener lmtp { address = * port = 24 } process_min_avail = 5 } ssl = no userdb { driver = passwd } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota quota notify push_notification push_notification_lua" postmaster_address = postmaster@domainname } protocol lda { mail_plugins = " quota notify push_notification" } protocol imap { imap_metadata = yes mail_plugins = " quota imap_quota quota" }

2 4

Problem with LDAP-query (Active Directory) on filter by memberOf
by Luca Bertoncello 20 Oct '20

20 Oct '20

Hi list! We have a Dovecot 2.3.4 (from Debian 10 repository) that should connect to our AD to authenticate the users. It works, but now we would like to restrict using IMAP to all users in the Group "Funktion - E-Mail-Konto". So I changed the query from: (&(sAMAccountName=%n)(objectClass=user)(homeMDB=*)) to (&(sAMAccountName=%n)(objectClass=user)(homeMDB=*)(memberOf=CN=Funktion - E-Mail-Konto,OU=Funktionen,OU=People,DC=ad,DC=company,DC=org)) The baseDN is DC=ad,DC=company,DC=org With ldapsearch I can get all users and their attributes, but Dovecot fail with this error: Oct 20 15:57:10 mailgw02 dovecot: auth: Error: ldap(testuser,80.187.107.28,<eLf0mhqyLwlQu2sc>): ldap_search(base=dc=ad,dc=company,dc=org filter=(&(samAccountName=testuser)(objectClass=user)(homeMDB=*)(memberOf=CN=Funktion - E-Mail-Konto,OU=Funktionen,OU=People,DC=ad,DC=company,DC=org))) failed: Operations error I didn't found any explanation for this error... Can someone help me? The user used for the connection is the same in Dovecot and ldapsearch. Thanks a lot Luca Bertoncello (lucabert(a)lucabert.de)

1 0

Dovecot docker auto-responder - delegate to external SMTP
by Thomas Pronold 19 Oct '20

19 Oct '20

Hi all, I have dockerized my dovecot setup. Everything works fine besides auto-responder using sieve. Issue is that the my dovecot docker image does NOT come with a SMTP which could be used for outgoing mail. My SMTP setup (postfix) is in another image/container. I want to keep it that way, so that dovecot and postfix have separate images. So basically I have 2 containers running in the same internal network: a) dovecot IP 192.168.10.11 b) postfix IP 192.168.10.22 How do I have to configure dovecot so that it delegates all outgoing (autoresponder) mails to the SMTP on IP 192.168.10.22. The postfix image is configured in a way that certain IPs are allowed to send mails without authentication. So on postfix side I am set. Currently I did a quickfix: I added postfix to dovecot image and configured postfix to use the relayhost 192.168.10.22 for mailing. This works, still I would prefer having the dovecot image not containing an postfix SMTP. Thanks Tom

4 3

Unable to access mail via Outlook
by Odhiambo Washington 19 Oct '20

19 Oct '20

Hola, Dovecot- 2.3.11.3 with mdbox. I have a situation where I can access (view) the e-mails when I use a web-based IMAP client, but NOT M$ Outlook (configured for IMAP). Is there an easy way to solve this? When I send an e-mail to the mailbox address, I can see it on the webmail, but not on Outlook. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

4 13

Using NFS to extend local email storage
by Maciej Kokociński 19 Oct '20

19 Oct '20

We are running our IMAP mail server on a VPS in the cloud (dovecot+exim+horde webmail), and we are using our on-premises NAS for daily backups through custom rsync scripts (which work well with maildir). There is a lot of storage available on the NAS, while not so much on the VPS. Since, we often get downtime on-premises due to power outages we cannot move the mail server on-premises (though the outages do not interfere too much with the backups). Additional storage in the cloud is at a premium as we would like to avoid further increasing costs. Now, my idea is to set up an NFS volume on the NAS, and configure the cloud-based server as the client. I would like to store only the most recent emails on the main server, and keep the whole data set on the NAS. Naturally I have read the dovecot wiki concerning NFS, and I have browsed this mailing list's archive for answers, but I still have many concerns. Ideally, I would like to use as much storage as possible from the main server, so that only really old emails need to be fetched over the network if requested over IMAP. Also I would like the search function to work regardless whether the NAS is available or not. I wonder if anybody tried a similar configuration before. My concerns are: - should I use NFS volume directly and configure FS-Cache, or should I configure a cache volume separately using e.g. bcache or some other tool? - how to configure the cache to keep as many files and metadata locally? - is it possible to fine tune the cache so it always keeps all the newly created/modified files locally? - is it possible to tune the cache so it keeps at least n files for each user (each maildir)? - will it work fine if I put NFS traffic into an ssh tunnel for security? - will dovecot freeze/crash when the NFS volume disconnects or is temporarily unavailable, what will actually happen in such circumstances? - will the search function work when the NFS volume is unavailable? (I also plan to use solr in the future) - what happens when the main server crashes and then recovers from the NFS share? is the share guaranteed to be consistent? I hope that I have not asked too many questions for a single message... ;) I would really appreciate any help, because I am rather a newbie in dovecot administration, and it overwhelms me. Perhaps, what I am trying to achieve is not the way to go. I am open to suggestions. Best regards, Maciej

4 3

Strange permissions error - Failed to stat sieve storage path
by Graham Leggett 18 Oct '20

18 Oct '20

Hi all I have dovecot-lda set up to run as vmail:vmail, with some sieve scripts in /var/lib/dovecot/sieve. The sieve scripts fail to be found with the following (detailed and very helpful) error message: Oct 14 16:13:33 gatekeeper dovecot[8109]: lda(minfrin(a)example.com)<8109><ZJ9nMo0Hh1+tHwAAKdTwig>: Error: sieve: file storage: Failed to stat sieve storage path: stat(/var/lib/dovecot/sieve/vacation.sieve) failed: Permission denied (euid=387(vmail) egid=387(vmail) missing +x perm: /var/lib/dovecot, we're not in group 97(dovecot), dir owned by 97:97 mode=0750) In this case, the user vmail is a member of the dovecot group: [root@gatekeeper dovecot]# cat /etc/group | grep vmail mail:x:12:postfix,vmail,opendmarc,opendkim,openarc dovecot:x:97:vmail vmail:x:387: [root@gatekeeper dovecot]# sudo su - vmail Last login: Wed Oct 14 16:15:48 SAST 2020 on pts/0 [vmail@gatekeeper ~]$ wc -c /var/lib/dovecot/sieve/vacation.svbin 530 /var/lib/dovecot/sieve/vacation.svbin Does dovecot-lda do anything odd with respect to group memberships? Regards, Graham —

2 1

Problem reading SSL key
by Tech Support 18 Oct '20

18 Oct '20

All; I'm trying to setup dovecot to use SSL, but I'm getting an error message in the logs. I'm getting the error imap-login: Fatal: Couldn't parse private ssl_key. I'm using a commercial cert so I know that the .crt and .key files themselves are not the problem. I have them configured like so: ssl_cert = </etc/pki/tls/certs/mail_acmewidgets_net.crt ssl_key = </etc/pki/tls/private/mail_acmewidgets_net.key The crt is mode 444 and the key is mode 400. Since the log is not giving any other information, I don't know what the problem is. Any insight at all would be greatly appreciated. Thanks; Frank

2 1

backup of namespace, is still looking at (touching?) other namespace?
by Marc Roos 17 Oct '20

17 Oct '20

When I am doing this: doveadm backup -f -n inbox -F /root/backup-accounts.txt tcp:mailxx.local:542 I am getting an error on the distributed storage, which I exactly did not wanted to be touched. doveadm(testaccount): Error: remote(mailxx.local:542): User initialization failed: Namespace 'Archive/': stat(/home/mail-archive/testaccount/Archive/mailboxes) failed: Permission denied (euid=xxx(testaccount) egid=xx(xxxxx) missing +x perm: /home/mail-archive, dir owned by 0:0 mode=0700) doveadm(testaccount): Error: remote(mailxx.local:542): dsync-server: User init failed doveadm(testaccount): Error: Failed to start remote dsync-server command: Remote exit_code=75

1 0

how to set smtp-client -> submission_relay_host for IPv4 only?
by PGNet Dev 16 Oct '20

16 Oct '20

In dovecot conf, for submission relay, I've config'd submission_relay_host = lan.example.com submission_relay_port = 465 hostname -- not IP -- must be used, to inform relay for cert verification match. Here, host lan.example.com lan.example.com has address 10.0.1.47 lan.example.com has IPv6 address fd80:25:01::47 The receiving smtp relay listens only on IPv4 -- no IPv6 service, telnet 10.0.1.47 465 Trying 10.0.1.47... Connected to 10.0.1.47. Escape character is '^]'. telnet -6 fd80:25:01::47 465 Trying fd80:25:01::47... telnet: connect to address fd80:25:01::47: Connection refused On the lan, all boxes are set, in "/etc/gai.conf", for IPv6 to take precedence over IPv4. On submission to dovecot submission port, after login/auth, dovecot smtp-client subsequently connects to the relay lan.example.com:465 IPv6 1st, & fails 2020-10-15 12:51:45 submission(mua(a)example.com)<8OJP+rqxuvho7Z95>: Error: smtp-client: conn lan.example.com:465 ([fd80:25:01::47]:465) [1]: connect(lan.example.com:465) failed: Connection refused then falls back to IPv4, and continues OK 2020-10-15 12:51:45 submission(mua(a)example.com)<8OJP+rqxuvho7Z95>: Info: Successfully relayed message: from=<test(a)remote.example.com>, size=84, id=LMe...Aw, nrcpt=1, reply=`247 2.0.0 Ok: queued as 4CC0KY1wXNzWf93' not fatal, but wasted effort, and noise in the logs. how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4?

3 4

Dovecot won't accept IMAP TLS 1 connections from older devices [SOLVED]
by Brian Martin 16 Oct '20

16 Oct '20

I've spent days scouring the Internet and trying various solutions on a problem with my Dovecot installation, so I thought I'd share what I learned in hopes of saving other people a lot of time. The dedicated Dovecot hands will know all of the following already. This is for those of us that have to cover a lot of bases. I upgraded my mail server from Ubuntu 18.04.1 to Ubuntu 20.04.1, and found that older Mac-books and iPads (and probably other devices) could no longer establish IMAP connections to Dovecot. Dovecot logged: SSL routines:tls_early_post_process_client_hello:unsupported protocol and TCP/IP traces showed that it dropped the connection after the client's initial HELLO. I tested what kinds of connections Dovecot would accept with (for example): openssl s_client -tls1_1 -connect localhost:993 # Test whether TLSv1.1 is accepted - received "unsupported protocol" message. Searching showed that Dovecot has a parameter "ssl_min_protocol", which is documented as defaulting to TLSv1. Nevertheless I explicitly set it to TLSv1 with no effect. This was a red herring. I spent a long time looking to see if Dovecot had a bug in handling this newish parameter, etc. Eventually I came across one posting regarding a web server, that told me the OpenSSL libraries that Dovecot and lots of other packages use has a single configuration file for the entire system. In Ubuntu 20.04 it defaults to requiring TLSv1.2 or above. Changing the configuration for OpenSSL affects everything on the system using the library. I changed the file, restarted Dovecot, and it immediately accepted TLSv1 connections. Obviously I'd prefer to maintain the improved security of TLSv1.2, but in my case it was better to continue providing mail service at a lower security level than to deny service to some users until they upgraded their personal devices. You'll need to make your on decision on that score. The file to change is (on Ubuntu, at least) /usr/lib/ssl/openssl.cnf. The change consists of adding a line of code in the initial section that invokes several new sections later: In the initial section I added: openssl_conf = default_conf Then at the bottom of the file I added: [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1 CipherString = DEFAULT@SECLEVEL=1 There is an alternative approach that I have read of but not tested. Basically you can create a new file elsewhere with the customized content, and then set an environmental variable (OPENSSL_CONF) just before launching Dovecot that points to your new file. This way, only Dovecot is using downgraded security. Since my mail server is a dedicated system and I didn't want to muck with the Dovecot start-up environment, I didn't feel the need to go that route. So all my digging into why Dovecot wouldn't accept TLSv1 connections and how to change it were completely on the wrong path. It would be nice if Dovecot could log a message when its ssl_min_protocol is set lower than what OpenSSL will accept, but Dovecot may not be able to tell what OpenSSL is doing. In any case, those are the symptoms, the real problem, and how to fix it. Good luck, and thanks to Matt Caswell for posting the answer that I eventually found. Ref: https://askubuntu.com/questions/1233186/ubuntu-20-04-how-to-set-lower-ssl-s…

3 2

Auro expunge
by ＠lbutlr 15 Oct '20

15 Oct '20

When using autoexpunge = 14 days in, for example. The trash of junk folders, does that physically remove the messages from disk or simply mark them to be removed and some other action needs to be taken? I ask because my mail server crapped out today and I discovered a Junk folder with 490,000 messages in it, and the sa-spamd and mariadb processes died a horrible death. Haven't had time to track down what was going on, but there were definitely messages in that junk folder from 2019 (though, of course, they may have been added within the last 14 days, I can't verify that as my solution was to remove the folder and recreate a new empty maildir). -- I don't believe there's a power in the 'verse can stop Kaylee from bein' cheerful. Sometimes you just wanna duct-tape her mouth and dump her in the hold for a month.

5 5

RE: dovecot Digest, Vol 210, Issue 27
by webadmin＠exalt.com.au 15 Oct '20

15 Oct '20

I am investigating whether dovecot(https://github.com/dovecot/core/) handles case insensitive Message-ID headers as per RFC. I can't raise a support issue with cPanel team (https://tickets.cpanel.net/review/login.cgi) as that needs an paid account with them. There may be an issue with the CPANEL/WHM DKIM module. Is the source code online? Rob

3 2

How do I enable sieve trace debugging?
by Graham Leggett 14 Oct '20

14 Oct '20

Hi all, I want to enable trace debugging for sieve. Most specifically, I want to know what sieve scripts are running, and whether they’re doing anything. I cannot get anything other than dead silence from dovecot with respect to sieve. I have tried the same as asked in this question: https://unix.stackexchange.com/questions/550618/dovecot-sieve-trace-does-no… In my case, the config looks like this: ## TRACE DEBUGGING # Trace debugging provides detailed insight in the operations performed by # the Sieve script. These settings apply to both the LDA Sieve plugin and the # IMAPSIEVE plugin. # # WARNING: On a busy server, this functionality can quickly fill up the trace # directory with a lot of trace files. Enable this only temporarily and as # selective as possible. # The directory where trace files are written. Trace debugging is disabled if # this setting is not configured or if the directory does not exist. If the # path is relative or it starts with "~/" it is interpreted relative to the # current user's home directory. sieve_trace_dir = /tmp/sieve-trace # The verbosity level of the trace messages. Trace debugging is disabled if # this setting is not configured. Possible values are: # # "actions" - Only print executed action commands, like keep, # fileinto, reject and redirect. # "commands" - Print any executed command, excluding test commands. # "tests" - Print all executed commands and performed tests. # "matching" - Print all executed commands, performed tests and the # values matched in those tests. sieve_trace_level = actions,command,tests,matching # Enables highly verbose debugging messages that are usually only useful for # developers. sieve_trace_debug = yes This looks sensible, syslog would be a great place to log, but nothing related to sieve appears. [root@gatekeeper dovecot]# doveadm log find Looking for log files from /var/log Debug: /var/log/maillog Info: /var/log/maillog Warning: /var/log/maillog Error: /var/log/maillog Fatal: /var/log/maillog Regards, Graham —

3 3

Changing IMAP separator - does it break things?
by Victor Sudakov 14 Oct '20

14 Oct '20

Dear Colleagues, I am using Dovecot 2.3.4.1 with maildirs. Just found out that MacOS Mail clients cannot work with nested folders, presumably because the MacOS Mail does not understand "." as the IMAP separator. Other clients (ThunderBird, Sylpheed, mutt) work fine. Do you think I can change the hierarchy separator in the "inbox" namespace without breaking other clients and the mail layout on disk, losing mail etc? I don't want to break mail for 50 people just to please one Mac Mail user. The users are advanced developers actively using mail sorting rules, nested folders etc. My `doveconf -n` is here: https://termbin.com/w1wd -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/

5 20

Re: Fatal: setgid from userdb lookup fails with wrong gid
by J. de Meijer 14 Oct '20

14 Oct '20

Hi, Not sure if this is it, but I used to have the same error when I started with dovecot. Aki's response was the following (and solved my problem). ------------- Hi! You can't set service imap { service_count = 256 } if you are using multiple system UIDs. See https://wiki.dovecot.org/Services#imap.2C_pop3.2C_submission.2C_managesieve *service_count* can be changed from 1 if only a single UID is used for mail users. This is improves performance, but it's less secure, because bugs in code may leak email data from another user's earlier connection. Aki ----------- Regards, Jeroen > Hello all, > > I'm quite new as well to Dovecot, just installed it on a FreeBSD system with Postfix and Rspamd as side apps. Things are running semi-smoothly for all users but I do have quite a few errors in the logs : > > Oct 13 19:43:56 apollo dovecot[24478]: > imap(user1)<34412><zIeI9ZCxXDmsFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), > egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1022(user4)) Oct 13 19:43:59 apollo dovecot[24478]: > imap(user1)<37376><pPS79ZCx+kasFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1124(user3), gid=1124(user3), > egid=1124(user3): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1124(user3)) Oct 13 19:46:45 apollo dovecot[24478]: > imap(user2)<38858><3hOk/5CxVO1dBDTq>: Fatal: setgid(1136(user2) from userdb lookup) failed with euid=1038(user5), gid=1038(user5), > egid=1038(user5): Operation not permitted (This binary should probably be called with process group set to 1136(user2) instead of 1038(user5)) Oct 13 19:48:55 apollo dovecot[24478]: > imap(user3)<40607><jQtWB5GxHuwKAkQ2>: Fatal: setgid(1124(user3) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), > egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1124(user3) instead of 1022(user4)) > > There seems to be confusion. The logs are trying to be helpful but I can't quite process it. Could someone point me in the right direction ? > > system is used by about 60 users. > > Thanks, > > j. > > -- > > doveconf -n > # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.11 (d71e0372) > # OS: FreeBSD 12.1-RELEASE-p10 amd64 > # Hostname: apollo.domain1.tld > auth_mechanisms = plain login cram-md5 > auth_username_format = %Ln > mail_location = maildir:~/Maildir > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope > encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify > environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve > namespace inbox { > inbox = yes > location = > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent Messages" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > prefix = > type = private > } > passdb { > args = scheme=cram-md5 /usr/local/etc/dovecot/cram-md5.pwd > driver = passwd-file > } > plugin { > imapsieve_mailbox1_before = > file:/var/vmail/sieve/global/learn-spam.sieve > imapsieve_mailbox1_causes = COPY > imapsieve_mailbox1_name = Spam > imapsieve_mailbox2_before = > file:/var/vmail/sieve/global/learn-ham.sieve > imapsieve_mailbox2_causes = COPY > imapsieve_mailbox2_from = Spam > imapsieve_mailbox2_name = * > quota = maildir:User quota > quota_exceeded_message = Benutzer %u hat das Speichervolumen > Ã¼berschritten. / User %u has exhausted allowed storage space. > sieve = file:~/sieve;active=~/.dovecot.sieve > sieve_before = /var/vmail/sieve/global/spam-global.sieve > sieve_global_extensions = +vnd.dovecot.pipe > sieve_pipe_bin_dir = /usr/local/bin > sieve_plugins = sieve_imapsieve sieve_extprograms > } > postmaster_address = postmaster(a)apollo.domain1.tld > protocols = imap lmtp sieve > service auth { > client_limit = 3000 > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > } > service imap-login { > service_count = 0 > } > service imap { > process_min_avail = 4 > service_count = 512 > vsz_limit = 1 G > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > vsz_limit = 1 G > } > ssl_cert = > </usr/local/etc/letsencrypt/live/apollo.domain1.tld/fullchain.pem ssl_cipher_list = > EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_prefer_server_ciphers = yes > syslog_facility = local5 > userdb { > driver = passwd > } > protocol lda { > mail_plugins = sieve > } > protocol lmtp { > mail_plugins = quota sieve > postmaster_address = postmaster(a)domain1.tld > } > protocol imap { > mail_max_userip_connections = 100 > mail_plugins = " quota imap_quota imap_sieve" > } > local_name imap.domain2.tld { > ssl_cert = > </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem > ssl_key = # hidden, use -P to show it > } > local_name mail.domain2.tld { > ssl_cert = > </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem > ssl_key = # hidden, use -P to show it > } >

2 1

Re: zlib errors after upgrading to 2.3.11.3
by Robert Nowotny 14 Oct '20

14 Oct '20

On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966(a)gmail.com> wrote: Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171: read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed: read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) failed: Broken pipe (FETCH BODY[]) Also this way you can see if the broken mail is actually xz or zstd or zlib. It would be nice to know if there are any zstd or zlib compressed mails that have problems. We did a lot of stress testing with zstd and also with xz, but haven't been able to reproduce any problems. It's also strange that it says taht the error is "Broken pipe" - that doesn't indicate that the mail is corrupted but that there is something more strange going on. So perhaps you don't actually have any mails written as corrupted, but Dovecot is just somehow having trouble reading the mails. I managed to reproduce this. The files aren't corrupted, it's just that reading is failing. The attached patch should fix the xz code and should make your files readable again. Yes, it works ! I switched now to "zstd" compression and currently re-compressing all user imap folders (one by one) Actually, with further testing it looks like the mails were written truncated. My patch simply hides the truncation when reading the mail. But it's anyway best that can be done about them. zstd also has a bug in writing compressed output, but it should always crash instead of writing broken output. We'll try to get fixes to these merged to git soon. currently I am re-compressing the mailboxes and so far i can see only one (1) Error, after about 120GB of recomresses emails : Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion failed: (!stream->blocking) Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x41) [0x7f5b00de6da1] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f5b00de6ec2] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfe5eb) [0x7f5b00df05eb] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfe687) [0x7f5b00df0687] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x598e1) [0x7f5b00d4b8e1] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5e2c1) [0x7f5b00d502c1] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_sendv+0x32) [0x7f5b00e14a92] -> /usr/local/lib/dovecot/libdovecot.so.0(io_stream_copy+0x5a) [0x7f5b00e1535a] -> /usr/local/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x50) [0x7f5b00e15060] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2d) [0x7f5b00f9659d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(dbox_save_continue+0x30) [0x7f5b00f3d3b0] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x3e) [0x7f5b00f1a34e] -> dovecot/imap [ebay 192.168.168.228 APPEND](+0x13801) [0x55d6905bf801] -> dovecot/imap [ebay 192.168.168.228 APPEND](command_exec+0x6c) [0x55d6905ce3ec] -> dovecot/imap [ebay 192.168.168.228 APPEND](+0x12fdb) [0x55d6905befdb] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x7f5b00e06ced] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x145) [0x7f5b00e08305] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x7f5b00e06d94] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f5b00e06f08] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f5b00d7f8d7] -> dovecot/imap [ebay 192.168.168.228 APPEND](main+0x459) [0x55d6905bec99] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f5b00b0e0b3] -> dovecot/imap [ebay 192.168.168.228 APPEND](_start+0x2e) [0x55d6905bed2e] Sep 10 11:32:24 lxc-imap dovecot: imap-login: Panic: epoll_ctl(del, 21) failed: Bad file descriptor Sep 10 11:32:24 lxc-imap dovecot: imap(ebay)<37070><1aDvPvKus+/AqKjk>: Fatal: master: service(imap): child 37070 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) until now I only have one broken mailbox, I need to repair (I will try that later, just finish all the other users before): Sep 10 12:13:13 lxc-imap dovecot: imap(mtrenner)<41872><KVTf0PKu7+7AqKi0>: Error: lzma.read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349): corrupted data at 3763912 Sep 10 12:13:13 lxc-imap dovecot: imap(mtrenner)<41872><KVTf0PKu7+7AqKi0>: Error: Mailbox Sent: UID=1480: read(zlib(/home/vmail/virtualmailboxes/mtrenner/storage/m.349)) failed: read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349) failed: lzma.read(/home/vmail/virtualmailboxes/mtrenner/storage/m.349): corrupted data at 3763912 (FETCH BODY[]) > zstd also has a bug in writing compressed output, but it should always crash instead of writing broken output. > We'll try to get fixes to these merged to git soon. Uh-Oh, that would be good ... pls notify ! how such thing can slip through the tests ? I just can not remember, the last error with compression was like 10 years ago (dont know if it was me who reported that) However, thank You for Your fast response and taking care !!! Robert

3 2

Spam learning for rspamd
by Dan Egli 14 Oct '20

14 Oct '20

I'm quite new to Dovecot, so forgive me if this is a simple question. I've got rspamd running, and it's rewriting the subject of many messages as spam even when they are not. I've moved things out of the spam folder, which I was under the impression would teach rspamd since I've connected a sieve script that is supposed to call rspamd's learning tool, but nothing is happening. I'm really at a loss as to where to even begin searching for an answer, so any help is appreciated! -- Dan Egli On my Test server

4 5

Procmail with Dovecot
by Dan Egli 13 Oct '20

13 Oct '20

Hey folks, here's a question. I want to enable procmail for the users so that they can have their incoming messages sorted info various folders and such regardless of MUA access or web access. I know I can set procmail to deliver to a maildir, but wouldn't that screw up dovecot's indexes? If it would, what can I do to ensure that the indexes stay correct? Thanks! -- Dan Egli On my Test server

5 5

Fatal: setgid from userdb lookup fails with wrong gid
by Julien Beauviala 13 Oct '20

13 Oct '20

Hello all, I'm quite new as well to Dovecot, just installed it on a FreeBSD system with Postfix and Rspamd as side apps. Things are running semi-smoothly for all users but I do have quite a few errors in the logs : Oct 13 19:43:56 apollo dovecot[24478]: imap(user1)<34412><zIeI9ZCxXDmsFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1022(user4)) Oct 13 19:43:59 apollo dovecot[24478]: imap(user1)<37376><pPS79ZCx+kasFhZG>: Fatal: setgid(1030(user1) from userdb lookup) failed with euid=1124(user3), gid=1124(user3), egid=1124(user3): Operation not permitted (This binary should probably be called with process group set to 1030(user1) instead of 1124(user3)) Oct 13 19:46:45 apollo dovecot[24478]: imap(user2)<38858><3hOk/5CxVO1dBDTq>: Fatal: setgid(1136(user2) from userdb lookup) failed with euid=1038(user5), gid=1038(user5), egid=1038(user5): Operation not permitted (This binary should probably be called with process group set to 1136(user2) instead of 1038(user5)) Oct 13 19:48:55 apollo dovecot[24478]: imap(user3)<40607><jQtWB5GxHuwKAkQ2>: Fatal: setgid(1124(user3) from userdb lookup) failed with euid=1022(user4), gid=1022(user4), egid=1022(user4): Operation not permitted (This binary should probably be called with process group set to 1124(user3) instead of 1022(user4)) There seems to be confusion. The logs are trying to be helpful but I can't quite process it. Could someone point me in the right direction ? system is used by about 60 users. Thanks, j. -- doveconf -n # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) # OS: FreeBSD 12.1-RELEASE-p10 amd64 # Hostname: apollo.domain1.tld auth_mechanisms = plain login cram-md5 auth_username_format = %Ln mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = type = private } passdb { args = scheme=cram-md5 /usr/local/etc/dovecot/cram-md5.pwd driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * quota = maildir:User quota quota_exceeded_message = Benutzer %u hat das Speichervolumen überschritten. / User %u has exhausted allowed storage space. sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/local/bin sieve_plugins = sieve_imapsieve sieve_extprograms } postmaster_address = postmaster(a)apollo.domain1.tld protocols = imap lmtp sieve service auth { client_limit = 3000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { service_count = 0 } service imap { process_min_avail = 4 service_count = 512 vsz_limit = 1 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 1 G } ssl_cert = </usr/local/etc/letsencrypt/live/apollo.domain1.tld/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA256:EECDH:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!IDEA:!ECDSA:kEDH:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes syslog_facility = local5 userdb { driver = passwd } protocol lda { mail_plugins = sieve } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)domain1.tld } protocol imap { mail_max_userip_connections = 100 mail_plugins = " quota imap_quota imap_sieve" } local_name imap.domain2.tld { ssl_cert = </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem ssl_key = # hidden, use -P to show it } local_name mail.domain2.tld { ssl_cert = </usr/local/etc/letsencrypt/live/mail.domain2.tld/fullchain.pem ssl_key = # hidden, use -P to show it }

1 0

Re: LMTP Authentication Error
by David Morsberger 13 Oct '20

13 Oct '20

On 2020-10-07 12:43, Alexander Dalloz wrote: > Am 07.10.2020 um 18:20 schrieb david(a)mmpcrofton.com: >> Any ideas on how to resolve the Userdb connect/lookup problem? My users are pinging me on Sieve support. >> Thanks, >> David > Provide a full output of "doveconf -n"? > Alexander Alexandar, Thanks and here you go. # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-48-generic x86_64 Ubuntu 20.04.1 LTS # Hostname: mmp-mail.mmpcrofton.com base_dir = /var/run/dovecot/ first_valid_uid = 150 login_greeting = Dovecot ready. mail_gid = 150 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mail_uid = 150 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:/home/mail/rules/%u/;active=/home/mail/rules/%u/.dovecot.sieve sieve_dir = /home/mail/rules/%u } protocols = " imap lmtp sieve pop3 sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/letsencrypt/live/imap.mmpcrofton.com/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " sieve" postmaster_address = david(a)mmpcrofton.com } protocol imap { mail_max_userip_connections = 50 }

2 4

Move older messages to Old folder after a bunch of changes (sql + other stuff)
by Chris Bennett 13 Oct '20

13 Oct '20

I'm starting to get things better done now. Moved to all virtual users over IMAP. Using a SQL database for users/passwords. Setting up folders working properly with neomutt. Right now, that leaves me with just new mail in the INBOX, and other folders. I have a bunch of old mail in each users Maildirs in their real home folders. Right now, I'd like to move all the old mail into a folder (doesn't really matter what it's called). Right now is actually a perfect time to do this by good luck in timing. How should I go about creating a new folder for those messages and then adding the old mail from system user home Maildir folders to the virtual users folders I'm using? Thanks for any help, Chris Bennett

1 0

DKIM fail if WHM adds Message-ID, should be Message-Id
by Robert Martin 13 Oct '20

13 Oct '20

I created a client library to send emails for a webapp. After connecting to the SMTP server with credential setup in CPANEL, and then do NOT add Message-Id header, the DKIM signature 'h' record created by dovecot/WHM is wrong, and a Message-ID (with a capital D) header is added, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email recipients to add 'dkim:fail' to the message, and thus relegate it to junk or spam. The work around is to add to the message a Message-Id with a little 'd' header. Then the SMTP server processes the email with the correct generated DKIM, correct DKIM 'h' record and does not add a Message-ID header. My SMTP hosting providers that run the WHM/dovecot/CPANEL software are refusing to raise this as a bug and have requested that I do it. Regards Robert

4 3

Preparing for replication: dsync-local(testaccount): Panic: file mbox-lock.c
by Marc Roos 12 Oct '20

12 Oct '20

I am preparing a bit for setting up replication. However when I manually try to dsync an account, the first time I execute this[1] command it seems to be ok. The 2nd time I am getting this error[2]. If I add -1 (one way syncing) the error disappears. Does this mean I will have problems with setting up replication between these two servers? [1] [@ ~]# doveadm sync -n inbox -u testaccount tcp:mail.local:542 [2] [@ ~]# doveadm sync -n inbox -u testaccount tcp:mail.local:542 dsync-local(testaccount): Panic: file mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) dsync-local(testaccount): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xa192e) [0x7fd4f827992e] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fd4f827999a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fd4f8209257] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_lock+0xef) [0x7fd4f858feef] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mbox_save_begin+0x658) [0x7fd4f8591958] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x83) [0x7fd4f855a573] -> doveadm(+0x4a6a3) [0x55e5ae8276a3] -> doveadm(dsync_mailbox_import_mail+0xca) [0x55e5ae82a9fa] -> doveadm(dsync_brain_sync_mails+0xb3) [0x55e5ae824963] -> doveadm(dsync_brain_run+0x551) [0x55e5ae820551] -> doveadm(+0x438e0) [0x55e5ae8208e0] -> doveadm(+0x5899f) [0x55e5ae83599f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7fd4f828f672] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fd4f8290d5f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7fd4f828f70c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fd4f828f8c8] -> doveadm(+0x297c9) [0x55e5ae8067c9] -> doveadm(+0x2bdcc) [0x55e5ae808dcc] -> doveadm(+0x2c9ca) [0x55e5ae8099ca] -> doveadm(doveadm_mail_try_run+0x215) [0x55e5ae80a325] -> doveadm(main+0x46a) [0x55e5ae7f949a] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd4f7e2c555] -> doveadm(+0x1c605) [0x55e5ae7f9605] Aborted CentOS Linux release 7.8.2003 (Core) dovecot-pigeonhole-2.2.36-6.el7_8.1.x86_64 dovecot-2.2.36-6.el7_8.1.x86_64

2 2

Doveadm-Sync for sieve / control
by Marc Roos 12 Oct '20

12 Oct '20

How to dsync sieve rules and maybe other necessary files like in control?

1 0

DKIM fail if WHM adds Message-ID, should be Message-Id
by webadmin＠exalt.com.au 12 Oct '20

12 Oct '20

I created a client library to send emails for a webapp. When the client library makes a connection to the SMTP server, and then do NOT add Message-Id header, Message-ID (with a capital D) header is added, and the SMTP server adds a incorrect DKIM-Signature record 'h' part, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email recipients to add 'dkim:fail' to the message which pushes it into junk/spam folder. The work around is to add to the message a Message-Id with a little ‘d’ header. Then the SMTP server processes the email with the correct DKIM-Signature, correct DKIM ‘h’ part and does not add a Message-ID header. Message-ID fails DKIM, Message-Id is better by OzBob · Pull Request #142 · dovecot/core (github.com) https://github.com/dovecot/core/pull/142 Regards Robert

2 1

where to specify dovecot v2.3.11.3 SSL configs for fts solr indexer/backend connection?
by PGNet Dev 12 Oct '20

12 Oct '20

I'm running. dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 solr's configured to use SSL. dovecot correctly uses SSL for transport fts_solr = url=https://solr.example.com:8984/solr/dovecot/ adding solr-side SSL client auth, - SOLR_SSL_NEED_CLIENT_AUTH=false + SOLR_SSL_NEED_CLIENT_AUTH=need I need to specify client cert for dovecot to present -- specific to the fts indexer connection. It apparently does not use dovecot's general/global SSL configs; that^ toggle immediately breaks MUA-originated search, reporting only 2020-10-11 18:23:30 imap(myuser@example)<oKpmJW+xQKCsHgsH>: Error: fts_solr: Lookup failed: 401 Unauthorized All other protocols SSL configs certainly work, and can be individually configured with specific key/crt pairs. Where do I config dovecot specifically for the search backend? I.e., where do I assign the ssl key/cert for dovecot to present as client to the solr server ?

1 0

Providers running dovecot?
by Olivier Cailloux 11 Oct '20

11 Oct '20

Dear list, I am looking for providers of free e-mail addresses known to run Dovecot (or a variant thereof) for IMAP access. I need only a few MB storage space and no particular features beyond SMTP and IMAP. The reason I ask is that Dovecot is known to implement the IMAP spec quite respectfully, and I am writing a software which uses IMAP search (so I would suggest my users to register an e-mail to a provider implementing correctly the IMAP Search specifications, to reduce the probability of bugs). (More details here: https://www.webhostingtalk.com/showthread.php?t=1821627.) Do you know of any such provider? -- Olivier

7 12

Expiry in kmail
by mh＠mike.franken.de 11 Oct '20

11 Oct '20

Hi *, is there any setting/plugin/... for dovecot, that would enable the "expiry" feature in kmail, i.e. let the client decide, what mails in what folder will expire and should be deleted by the server? TIA. Bye. Michael.

1 0

Replication process Out of memory error
by Joelly Alexander 11 Oct '20

11 Oct '20

Running replication between two nodes and every time a out of memory error is logged when a replication triggered: 2020.10.11 01:43:39 replicator: Panic: data stack: Out of memory when allocating 268435496 bytes 2020.10.11 01:43:39 replicator: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7fcb4403662b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7fcb440366c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7fcb43fa5149] -> /usr/lib/dovecot/libdovecot.so.0(+0x49d9d) [0x7fcb43fa4d9d] -> /usr/lib/dovecot/libdovecot.so.0(+0xd7c7d) [0x7fcb44032c7d] -> /usr/lib/dovecot/libdovecot.so.0(+0xfa9b8) [0x7fcb440559b8] -> /usr/lib/dovecot/libdovecot.so.0(+0xd52dc) [0x7fcb440302dc] -> /usr/lib/dovecot/libdovecot.so.0(buffer_write+0x66) [0x7fcb440304d6] -> dovecot/replicator(replicator_queue_push+0xd9) [0x55933ecc4ad9] -> dovecot/replicator(+0x5266) [0x55933ecc4266] -> dovecot/replicator(+0x4952) [0x55933ecc3952] -> dovecot/replicator(+0x4af0) [0x55933ecc3af0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6f) [0x7fcb4404cadf] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7fcb4404e0d6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7fcb4404cb7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fcb4404cce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fcb43fcd0d3] -> dovecot/replicator(main+0x196) [0x55933ecc2c56] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fcb43db509b] -> dovecot/replicator(_start+0x2a) [0x55933ecc2d1a] 2020.10.11 01:43:39 replicator: Fatal: master: service(replicator): child 7834 killed with signal 6 (core dumped) Setting vsz_limit doesn't change behavior, the OOM error indicates that it seems trying to allocate even more memory: vsz_limit = 64M says says OOM Error when trying to allocate 67108904 bytes which is 40 bytes more than what is set vsz_limit = 128M says says OOM Error when trying to allocate 268435496 bytes which is 40 bytes more than twice what is set vsz_limit = 256M says says OOM Error when trying to allocate 268435496 bytes which is 40 bytes more than what is set vsz_limit = 512M says says OOM Error when trying to allocate 1073741864 bytes which is 40 bytes more than twice what is set vsz_limit = 1024M says says OOM Error when trying to allocate 1073741864 bytes which is 40 bytes more than what is set vsz_limit = 2048M says says OOM Error when trying to allocate 4294967336 bytes which is 40 bytes more than twice what is set vsz_limit = 4096M says says OOM Error when trying to allocate 4294967336 bytes which is 40 bytes more than what is set vsz_limit = 8192M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than twice what is set vsz_limit = 16384M says says OOM Error when trying to allocate 17179869224 bytes which is 40 bytes more than what is set everything set larger than 16384M stays at OOM Error when trying to allocate 17179869224... Replication itself seems to work but the error is always logged. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.8.0-0.bpo.2-amd64 x86_64 Debian 10.6 ext4 Thanks, Alex -- ======================================================== Alexander Joelly Bachweg 2 A-8501 Lieboch, AUSTRIA

1 0

Feature request.
by Rogier Wolff 10 Oct '20

10 Oct '20

Hi, I get my Email from my own SMTP server on the internet using "fetchmail". Some time ago I did the smart thing and configured dovecot to use SSL and the letsencrypt certificate that automatically renews. Welllll..... a few days ago my certificate expired and the fetchmail deamon running in the background had nowhere to complain. So I didn't notice. It turns out that dovecot had been running uninterrupted since august 13th, the certificate was renewed on september 7th and I suspect it expired on october 7th. So.... Feature request: check the expiry date on the SSL certificate as it is being loaded and check for a new certificate if it HAS expired. If you worry about performance, this could be done where: TLS handshaking: SSL_accept() failed: error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired: SSL alert number 45 is reported. That would mean that ONE client will once get the error before dovecot fixes it. My personal fix is to restart dovecot once a week from now on. I might be running an older version: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-34-generic x86_64 Ubuntu 18.04.5 LTS if it has already been fixed, please accept my apologies. Roger. -- ** R.E.Wolff(a)BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.

13 17

Core dump with search in a virtual folder with FTS enabled
by Jonathan Moesli 09 Oct '20

09 Oct '20

Hi all, when I try to search in a virtual mailbox with FTS enabled, imap cores dump. Sample IMAP session in a virtual mailbox: 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY] Logged in2 SELECT Search/All* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 1 EXISTS* 0 RECENT* OK [UNSEEN 1] First unseen.* OK [UIDVALIDITY 1602234810] UIDs valid* OK [UIDNEXT 2] Predicted next UID2 OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs).2 UID SEARCH HEADER From userConnection closed by foreign host. When I search in INBOX all OK: 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY] Logged in 2 SELECT INBOX* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 1 EXISTS* 0 RECENT* OK [UNSEEN 1] First unseen.* OK [UIDVALIDITY 1602234520] UIDs valid* OK [UIDNEXT 2] Predicted next UID* OK [NOMODSEQ] No permanent modsequences2 OK [READ-WRITE] Select completed (0.003 + 0.000 + 0.002 secs).2 UID SEARCH HEADER From user* SEARCH 12 OK Search completed (0.002 + 0.000 + 0.001 secs). Error log: Oct 09 12:58:22 Panic: imap(user)<31554><Y3pl0zqx3s9/AAAB>: Module context fts_mailbox_list_module missingOct 09 12:58:22 Error: imap(user)<31554><Y3pl0zqx3s9/AAAB>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fbe88afddf2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fbe88afdefe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xec42e) [0x7fbe88b0842e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xec4d1) [0x7fbe88b084d1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbe88a5f4ea] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x123f7) [0x7fbe8821f3f7] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xe2f4) [0x7fbe8821b2f4] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_search_lookup+0xd4) [0x7fbe8821b7b4] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x11a98) [0x7fbe8821ea98] -> dovecot/imap(imap_search_start+0x70) [0x55e251f4e620] -> dovecot/imap(cmd_search+0xd6) [0x55e251f3ea86] -> dovecot/imap(command_exec+0x64) [0x55e251f46cc4] -> dovecot/imap(+0x1ce4f) [0x55e251f44e4f] -> dovecot/imap(+0x1ced7) [0x55e251f44ed7] -> dovecot/imap(client_handle_input+0x205) [0x55e251f45365] -> dovecot/imap(client_input+0x75) [0x55e251f45925] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7fbe88b20b45] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7fbe88b2249b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7fbe88b20c49] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbe88b20e88] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbe88a90393] -> dovecot/imap(main+0x332) [0x55e251f36f12] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fbe88670555] -> dovecot/imap(+0xf115) [0x55e251f37115]Oct 09 12:58:22 Fatal: imap(user)<31554><Y3pl0zqx3s9/AAAB>: master: service(imap): child 31554 killed with signal 6 (core dumped) Dovecot configuration (doveconf -n):# 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1127.19.1.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core)first_valid_uid = 1000 mail_debug = yesmail_location = maildir:~/Maildir:INDEX=MEMORYmail_plugins = virtual fts fts_lucenembox_write_locks = fcntlnamespace inbox { inbox = yes location = prefix = separator = /}namespace virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=~/virtual prefix = Search/ separator = / subscriptions = no type = private}passdb { args = scheme=PLAIN username_format=%u /etc/dovecot/users driver = passwd-file}plugin { fts = lucene fts_lucene = whitespace_chars=@.}userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file} Backtrace:#0 0x00007fbe88684387 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007fbe88685a78 in __GI_abort () at abort.c:90#2 0x00007fbe88b083e7 in default_fatal_finish (status=0, type=<optimized out>) at failures.c:459#3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471#4 0x00007fbe88b084d1 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:848#5 0x00007fbe88a5f4ea in i_panic (format=format@entry=0x7fbe88225058 "Module context fts_mailbox_list_module missing") at failures.c:523#6 0x00007fbe8821f3f7 in fts_mailbox_backend (box=<optimized out>) at fts-storage.c:957#7 0x00007fbe8821b2f4 in fts_search_lookup_level_multi (and_args=<optimized out>, args=0x55e253347698, fctx=0x55e2533be330) at fts-search.c:182#8 fts_search_lookup_level (fctx=fctx@entry=0x55e2533be330, args=0x55e253347698, and_args=and_args@entry=true) at fts-search.c:210#9 0x00007fbe8821b7b4 in fts_search_lookup (fctx=fctx@entry=0x55e2533be330) at fts-search.c:360#10 0x00007fbe8821ea98 in fts_mailbox_search_init (t=0x55e253342e60, args=0x55e2533475c8, sort_program=<optimized out>, wanted_fields=0, wanted_headers=0x0) at fts-storage.c:260#11 0x000055e251f4e620 in imap_search_start (ctx=ctx@entry=0x55e2533353f0, sargs=0x55e2533475c8, sort_program=sort_program@entry=0x0) at imap-search.c:540#12 0x000055e251f3ea86 in cmd_search (cmd=0x55e253335238) at cmd-search.c:48#13 0x000055e251f46cc4 in command_exec (cmd=cmd@entry=0x55e253335238) at imap-commands.c:201#14 0x000055e251f44e4f in client_command_input (cmd=cmd@entry=0x55e253335238) at imap-client.c:1178#15 0x000055e251f44ed7 in client_command_input (cmd=0x55e253335238) at imap-client.c:1243#16 0x000055e251f45365 in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x55e2533349c8) at imap-client.c:1285#17 client_handle_input (client=client@entry=0x55e2533349c8) at imap-client.c:1299#18 0x000055e251f45925 in client_input (client=0x55e2533349c8) at imap-client.c:1343#19 0x00007fbe88b20b45 in io_loop_call_io (io=0x55e25332dfe0) at ioloop.c:713#20 0x00007fbe88b2249b in io_loop_handler_run_internal (ioloop=ioloop@entry=0x55e253311de0) at ioloop-epoll.c:222#21 0x00007fbe88b20c49 in io_loop_handler_run (ioloop=ioloop@entry=0x55e253311de0) at ioloop.c:765#22 0x00007fbe88b20e88 in io_loop_run (ioloop=0x55e253311de0) at ioloop.c:738#23 0x00007fbe88a90393 in master_service_run (service=0x55e253311c40, callback=callback@entry=0x55e251f53340 <client_connected>) at master-service.c:851#24 0x000055e251f36f12 in main (argc=1, argv=0x55e253311960) at main.c:534 I tried with both solr and lucene engines, always core dump. Packages installed: - dovecot-2.3.11.3-4.x86_64 - dovecot-debuginfo-2.3.11.3-4.x86_64 Maybe I missed a configuration parameter? Thank you.

1 0

Dovecot 2.3.10-2.3.11.3 pop3/imap login problem after upgrade
by Michał Smyczyński 09 Oct '20

09 Oct '20

Hi, I came across a following issue. After upgrading dovecot from 2.3.10 to 2.3.11.3 pop/imap logins fail. Auth method is plain/login ,with ssl required and shadow passdb driver, runnning on Slackware Linux 14.1. The configuration in both cases is the same, and in the past, after each uprgade i had no problems. I did not come across also of any information if upgrading from 2.3.10 to 2.3.11.3 require any significant change to auth configuration. Dovecot v2.3.10 (0da0eff44) starting up for pop3, imap (core dumps disabled) pop3-login: Login: user=<test>, method=PLAIN, rip=89.78.12.2, lip=192.168.100.30, mpid=8109, TLS, session=<7aCIhC6xzehZTgwC> Dovecot v2.3.11.3 (502c39af9) starting up for pop3, imap (core dumps disabled) pop3-login: Disconnected (tried to use unsupported auth mechanism): user=<test>, method=USER, rip=89.78.12.2, lip=192.168.100.30, TLS, session=<CYwFfS6xouhZTgwC> I appreciate help if someone knows the cause and solution. Regards

1 0

Sieve not exists
by ＠lbutlr 08 Oct '20

08 Oct '20

I thought this was working as intended, but I have recently been getting some random messages put into this mailbox that definitely have list-ip headers (including some messages from this list) and that do not have multiple addresses. I believe this started happening on 20200922, which would hav been when I applied the most recent update to dovecot, as that is when the listCC box seemed to explode, but I do not have traces over 7 days old. if allof (address :count "ge" :comparator "i;ascii-numeric" ["to", "cc"] ["2"], not exists ["list-id","mailing-list", "x-loop"] ) { fileinto :create "listCC"; stop;} Headers of a message that triggered this (minus Received and signature headers, just removed for length) This is the trace: 23: address test 23: starting `:count-ge' match with `i;ascii-numeric' comparator: 23: extracting `to' headers from message 23: parsing address header value `Kurt Jaeger <dovecot(a)opsec.eu>, dovecot(a)dovecot.org' 23: address value `dovecot(a)opsec.eu' 23: address value `dovecot(a)dovecot.org' 23: extracting `cc' headers from message 23: matching count value `2' 23: with key `2' => 1 23: finishing match with result: matched So, it looks like it is matching Reply-To and/or X-Original-To as well as To? Or is something else happening here? 23: jump if result is false 23: not jumping 24: exists test 24: header `list-id' exists 24: header `mailing-list' is missing 24: headers are missing 24: jump if result is true 24: not jumping Or the logic of "not exists" has changed from AND (meaning none of those headers exist)? 26: fileinto action 26: store message in mailbox `listCC' 27: stop command; end all script execution ## Finished executing script '.active_sieve' Headers of that message (minute received and signature headers, elided just for length) Reply-To: dovecot(a)dovecot.org Return-Path: <dovecot-bounces(a)dovecot.org> X-Original-To: dovecot(a)dovecot.org Delivered-To: dovecot(a)dovecot.org Date: Wed, 30 Sep 2020 17:06:54 +0200 From: Kurt Jaeger <dovecot(a)opsec.eu> To: dovecot(a)dovecot.org Subject: debugging TLS with wireshark and a custom application ? Message-ID: <20200930150654.GT53210(a)home.opsec.eu> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: dovecot(a)dovecot.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Dovecot Mailing List <dovecot.dovecot.org> List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe> List-Archive: <https://dovecot.org/pipermail/dovecot/> List-Post: <mailto:dovecot@dovecot.org> List-Help: <mailto:dovecot-request@dovecot.org?subject=help> List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe> Errors-To: dovecot-bounces(a)dovecot.org Sender: "dovecot" <dovecot-bounces(a)dovecot.org> There is one address in the To and no CC header at all, so why was this filed into listCC? (This is the only incidence of listCC in the sieve file for the list user) -- "I used to hate the sun, because it'd shone on everything I'd done. Made me feel that all that I had done was overfill the ashtray of my life."

2 1

How do I make "vnd.dovecot.environment" available?
by Graham Leggett 08 Oct '20

08 Oct '20

Hi all, According to the docs at https://wiki.dovecot.org/Pigeonhole/Sieve, some extensions are not available by default. The docs tell me the sieve_plugins, sieve_extensions and/or sieve_global_extensions configs are involved, but I can find no authoritative documentation as to what the values should be. What values must I use to make “vnd.dovecot.environment” available? Adding "sieve_global_extensions = +vnd.dovecot.environment” to 90-sieve.conf seems to not be enough. [root@gatekeeper ~]# sievec -D /var/lib/dovecot-sieve/default.sieve sievec(root): Debug: sieve: Pigeonhole version 0.5.8 (b7b03ba2) initializing sievec(root): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. sievec(root): Debug: sieve: file storage: Using Sieve script path: /var/lib/dovecot-sieve/default.sieve sievec(root): Debug: sieve: file script: Opened script `default' from `/var/lib/dovecot-sieve/default.sieve' default: line 5: error: require command: unknown Sieve capability `vnd.dovecot.environment'. default: line 19: error: referring to variable in unknown namespace 'vnd'. default: error: validation failed. sievec(root): Fatal: failed to compile sieve script '/var/lib/dovecot-sieve/default.sieve' Regards, Graham —

3 5

dovecot: lmtp: Error: fatal error: failed to reserve page summary memory
by Roman Vasilyev 08 Oct '20

08 Oct '20

Sorry for offtopic, don't know where to ask it after updating from `ubuntu` 18 to 20 started getting this on running golang binary from sieve rules file ``` Sep 17 08:54:00 lonjemail spamd[3231]: spamd: connection from ::1 [::1]:57844 to port 783, fd 5 Sep 17 08:54:00 lonjemail spamd[3231]: spamd: setuid to Debian-exim succeeded Sep 17 08:54:00 lonjemail spamd[3231]: spamd: processing message <CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV=Pf95Pxusbww(a)mail.gmail.com> for Debian-exim:114 Sep 17 08:54:00 lonjemail systemd-resolved[527]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 17 08:54:00 lonjemail systemd-resolved[527]: message repeated 8 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Sep 17 08:54:00 lonjemail spamd[3231]: spamd: clean message (1.1/5.0) for Debian-exim:114 in 0.3 seconds, 2760 bytes. Sep 17 08:54:00 lonjemail spamd[3231]: spamd: result: . 1 - DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,RDNS_NONE,SPF_HELO_NONE,SPF_PASS scantime=0.3,size=2760,user=Debian-exim,uid=114,required_score=5.0,rhost=::1,raddr=::1,rport=57844,mid=<CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV= Pf95Pxusbww(a)mail.gmail.com>,autolearn=no autolearn_force=no Sep 17 08:54:00 lonjemail dovecot: lmtp(4254): Connect from local Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: fatal error: failed to reserve page summary memory Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime stack: Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.throw(0x1a48db5, 0x25) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/panic.go:1116 +0x72 fp=0x7ffe160d5860 sp=0x7ffe160d5830 pc=0x4ce5d2 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*pageAlloc).sysInit(0x232c268) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mpagealloc_64bit.go:80 +0x185 fp=0x7ffe160d58f0 sp=0x7ffe160d5860 pc=0x4c4e25 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*pageAlloc).init(0x232c268, 0x232c260, 0x25cb8d8) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mpagealloc.go:317 +0x75 fp=0x7ffe160d5918 sp=0x7ffe160d58f0 pc=0x4c2815 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.(*mheap).init(0x232c260) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/mheap.go:743 +0x24b fp=0x7ffe160d5940 sp=0x7ffe160d5918 pc=0x4bf84b Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.mallocinit() Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/malloc.go:480 +0x109 fp=0x7ffe160d5968 sp=0x7ffe160d5940 pc=0x4a4c49 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.schedinit() Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/proc.go:563 +0x65 fp=0x7ffe160d59c0 sp=0x7ffe160d5968 pc=0x4d1f25 Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: runtime.rt0_go(0x7ffe160d5ad8, 0x2, 0x7ffe160d5ad8, 0x1813580, 0x7fd3cc8a80b3, 0x7fd3cca6cb80, 0x7ffe160d5ad8, 0x200011c00, 0x501080, 0x1813580, ...) Sep 17 08:54:00 lonjemail dovecot: lmtp: Error: #011/usr/local/go/src/runtime/asm_amd64.s:214 +0x125 fp=0x7ffe160d59c8 sp=0x7ffe160d59c0 pc=0x5011c5 Sep 17 08:54:00 lonjemail dovecot: lmtp(roman)<4254></X0wOCgkY1+eEAAAgcArzw>: program exec:/usr/lib/dovecot/sieve-execute/smtp (4255): Terminated with non-zero exit code 2 Sep 17 08:54:00 lonjemail dovecot: lmtp(roman)<4254></X0wOCgkY1+eEAAAgcArzw>: sieve: msgid=<CANcP0tbws-r=L8KrTug_NKLk0EuPwo1vKotdpV=Pf95Pxusbww(a)mail.gmail.com>: stored mail into mailbox 'Unsubscribe.Neighbors' Sep 17 08:54:00 lonjemail dovecot: lmtp(4254): Disconnect from local: Client has quit the connection (state=READY) Sep 17 08:55:01 lonjemail CRON[4257]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) ``` here is sieve rules: ``` require ["variables", "fileinto", "mailbox", "vnd.dovecot.execute"]; if address :matches "from" "*" { set "from" "${1}"; } if anyof ( header :contains "subject" "unsubscribe neighbours", header :contains "subject" "unsubscribe neighbors") { execute "smtp" "-neighbors=${from}"; fileinto :create "Unsubscribe.Neighbors"; } elsif address :contains "from" ["mailer-daemon", "postmaster", "internet mail delivery"] { if header :matches "X-Failed-Recipients" "*" { execute "smtp" "-email=${1}"; fileinto :create "Mail Delivery System"; } else { fileinto :create "Mail Delivery System.Warning"; } } else { # The rest goes into INBOX # default is "implicit keep", we do it explicitly here keep; } ``` Attempted in `/etc/dovecot/conf.d/90-sieve.conf` vsz_limit = 256M with no luck Can somebody help me in fixing it?

2 2

custom userdb server, Exim, and proxying
by Felipe Gasper 08 Oct '20

08 Oct '20

Hi all, We have Exim using Dovecot for authentication. Dovecot, in turn, consults a custom internal server that answers Dovecot’s userdb queries. When IMAP connections arrive, for some users we want to forward those connections--without authentication--to an external IMAP server. For these users, we return “proxy_maybe” and “nopassword” in the authn response from our userdb server. This tells Dovecot to proxy the connection to a new server without trying to authenticate. Exim, though, doesn’t grok “proxy_maybe”, so it just sees “nopassword”. In response, it just skips SMTP authentication entirely. We could address this if our custom service could know whether the authn is for Exim or not. Exim does send a “service=smtp” in its request to /var/run/dovecot/auth-client, but thus far I don’t see that that’s being passed on to the userdb server. Is there any way I can configure Dovecot so that our userdb server can detect when it’s Exim doing the authentication? Alternatively we could just authenticate on the proxy (i.e., stop sending “nopassword”), but that will entail a new requirements for passwords to be in sync; ideally we’d like to avoid that. Any insight from this group would be much appreciated. Thank you! cheers, -Felipe Gasper

2 1

replication flag default setting?
by Norman King 08 Oct '20

08 Oct '20

Hello. I'm playing with dovecot replication. I have a working replication config on a test server and would like to copy that to production but i don't know what's going to happen with existing accounts. Will they automatically start replicating without any further input from me? Is there a flag on the account somewhere that can tell me what the replication status is? Any thoughts on this would be appreciated. dovecot version 2.3.7.2 -- regards Norman King Compass Foundation sysadmin/tech support Phone, 856-974-5335 ext 221 support(a)compassfoundation.io <mailto:support@compassfoundation.io> Website <https://compassfoundation.io>

2 1

dovecot 2.3.11.3 namespace/ACL shared folder not accessible in sharing-user's Mail folder tree? have a working config?
by PGNet Dev 08 Oct '20

08 Oct '20

I'm running dovecot --version 2.3.11.3 (502c39af9) I'm setting up folder sharing. Following https://wiki.dovecot.org/SharedMailboxes/Shared I've configured a folder to be shared, but it's not seen/accessible in the target user's Mail folder tree. My config includes, mail_plugins = virtual acl protocol imap { mail_plugins = $mail_plugins imap_acl imap_quota mail_log notify quota imap_sieve ... } imap_capability = +SPECIAL-USE namespace inbox { inbox = yes type = private separator = / prefix = hidden = no list = yes subscriptions = yes ... } namespace shared { type = shared separator = / prefix = shared/%%u/ location = maildir:/srv/vmail/%%d/%%n/Maildir:INDEXPVT=/var/vmail-index/shared/%%u hidden = no list = yes subscriptions = yes } plugin { acl_globals_only = no acl = vfile acl = vfile:/etc/dovecot/dovecot-acl acl_shared_dict = file:/srv/vmail/%d/shared-mailboxes.db } I've two users user1(a)example.com user2(a)example.com I've shared a folder, 'SHARED' (containing files & subfolders), from user1(a)example.com's folder hierarchy to user2(a)example.com, doveadm acl set -u user1(a)example.com SHARED user=user2(a)example.com lookup read write write-seen write-deleted insert create checking cat /srv/vmail/virtual/dovecot-acl-list (empty) cat /srv/vmail/example.com/user2/Maildir/dovecot-acl-list (empty) cat /srv/vmail/example.com/user1/Maildir/SHARED/dovecot-acl user=user2(a)example.com kilrwts cat /srv/vmail/example.com/user1/Maildir/dovecot-acl-list 1602040901 SHARED Logging into Roundcube as User: user2(a)example.com I do NOT see the 'shared' folder in the Mail window. If I nav to Settings -> Folders, I *DO* see the 'shared' folder, but it's unchecked -- and there are no subfolders displayed beneath it. on-click of the 'shared' folder, in dovecot logs: 2020-10-06 20:31:27 imap-login: Info: Login: user=<user2(a)example.com>, method=PLAIN, rip=10.0.1.50, lip=10.0.1.50, mpid=7673, TLS ==> /var/log/dovecot/dovecot-debug.log <== 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Loading modules from directory: /usr/lib64/dovecot 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib02_imap_acl_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib15_notify_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib20_mail_log_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib20_virtual_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Module loaded: /usr/lib64/dovecot/lib95_imap_sieve_plugin.so 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Added userdb setting: plugin/quota=dirsize:storage=10240000 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/example.com/user2/Maildir 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota root: name=storage=10240000 backend=dirsize args= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=* bytes=10737418240 messages=0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=Trash bytes=+1073741824 (10%) messages=0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=Junk ignored 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=10737418240 (100%) messages=0 reverse=no command=quota-warning 100 user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=10200547328 (95%) messages=0 reverse=no command=quota-warning 95 user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=9663676416 (90%) messages=0 reverse=no command=quota-warning 90 user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=9126805504 (85%) messages=0 reverse=no command=quota-warning 85 user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota grace: root=storage=10240000 bytes=52428800 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/example.com/user2/Maildir:CONTROL=/srv/vmail/ex… 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: fs: root=/srv/vmail/example.com/user2/Maildir, index=/var/vmail-index/example.com/user2, indexpvt=, control=/srv/vmail/example.com/user2/_control, inbox=/srv/vmail/example.com/user2/Maildir, alt= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: initializing backend with data: vfile:/home/vmail/conf.d/example.com/acls:cache_secs=300 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: acl username = user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: owner = 1 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: Global ACL legacy directory: /home/vmail/conf.d/example.com/acls 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Namespace shared: type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=maildir:/srv/vmail/%d/%n/Maildir:INDEXPVT=/var/vmail-index/shared/%u 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: shared: root=/run/dovecot/, index=, indexpvt=, control=, inbox=, alt= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: initializing backend with data: vfile:/home/vmail/conf.d/example.com/acls:cache_secs=300 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: acl username = user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: owner = 0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: Global ACL legacy directory: /home/vmail/conf.d/example.com/acls 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Namespace virtual: type=private, prefix=virtual/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=virtual:/srv/vmail/virtual:INDEX=MEMORY 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: fs: root=/srv/vmail/virtual, index=, indexpvt=, control=, inbox=, alt= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: initializing backend with data: vfile:/home/vmail/conf.d/example.com/acls:cache_secs=300 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: acl username = user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: owner = 1 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: Global ACL legacy directory: /home/vmail/conf.d/example.com/acls 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/ not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/Drafts not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /srv/vmail/example.com/user2/Maildir/Drafts/dovecot-acl not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/Sent not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /srv/vmail/example.com/user2/Maildir/Sent/dovecot-acl not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/Junk not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /srv/vmail/example.com/user2/Maildir/Junk/dovecot-acl not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/Trash not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /srv/vmail/example.com/user2/Maildir/Trash/dovecot-acl not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota root: name=storage=10240000 backend=dirsize args= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=* bytes=10737418240 messages=0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=Trash bytes=+1073741824 (10%) messages=0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota rule: root=storage=10240000 mailbox=Junk ignored 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=10737418240 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=10200547328 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=9663676416 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota warning: bytes=9126805504 (85%) messages=0 reverse=no command=quota-warning 85 user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Quota grace: root=storage=10240000 bytes=52428800 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: maildir++: root=/srv/vmail/example.com/user1/Maildir, index=, indexpvt=/var/vmail-index/shared/user1(a)example.com, control=, inbox=/srv/vmail/example.com/user1/Maildir, alt= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: initializing backend with data: vfile:/home/vmail/conf.d/example.com/acls:cache_secs=300 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: acl username = user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: owner = 1 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: Global ACL legacy directory: /home/vmail/conf.d/example.com/acls 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: maildir++: root=/srv/vmail/example.com/user1/Maildir, index=, indexpvt=/var/vmail-index/shared/user1(a)example.com, control=, inbox=/srv/vmail/example.com/user1/Maildir, alt= 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: initializing backend with data: vfile:/home/vmail/conf.d/example.com/acls:cache_secs=300 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: acl username = user2(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: owner = 0 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: Global ACL legacy directory: /home/vmail/conf.d/example.com/acls 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/ not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/shared/user1(a)example.com not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /srv/vmail/example.com/user1/Maildir/dovecot-acl not found 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl: No lookup right to mailbox: shared/user1(a)example.com 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: Namespace shared/: Using permissions from : mode=0700 gid=default 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/ not found ==> /var/log/dovecot/dovecot-info.log <== 2020-10-06 20:31:27 imap(user2(a)example.com)<6m3LWQyx8LesHgsy>: Info: Logged out in=84 out=732 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 NO "error", simply no view of 'SHARED', or the files/folder in it, seen under 'shared' in @ user2's account. What's missing/incorrect about that^ config, in order to see/access the shared folder, 'SHARED' in @ user2's account ? If you have a working config, please share.

2 1

Version controlled (git) Maildir generated by Dovecot
by Adam 07 Oct '20

07 Oct '20

Hi Everybody, I'd like to start archiving e-mails by moving them to a server with running Dovecot. I installed "dovecot-core" and "dovecot-imapd" (version 2.3.4.1) on Debian 10. One of a few configurations I made is to use Maildir: # grep '^mail_location = ' /etc/dovecot/conf.d/10-mail.conf mail_location = maildir:~/Maildir I successfully moved some e-mails (at this moment it's just a test) to subfolders that describe a year of the backup. I'd like to start using git on the whole Maildir. After going through the Maildir directory and subdirectories I realized that Dovecot saves some extra files that I might not need to backup (version control). Based on my understanding and after reading https://wiki.dovecot.org/IndexFiles I believe that the only files I need to archive are files in "cur/" directory and these files should start with Unix time. So I decided to write a ".gitignore" whitelist that will include only files in "cur/" that start with a number: # cat .gitignore ----------------------------------- !.gitignore !*/ !/Maildir/cur/[0-9]* !/Maildir/*/cur/[0-9]* ----------------------------------- and it's working: # git add . --dry-run ----------------------------------- add '.gitignore' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M110302P17113.mail1,S=8066,W=8276:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M134554P17113.mail1,S=8024,W=8234:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M157569P17113.mail1,S=8005,W=8215:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M180965P17113.mail1,S=8021,W=8231:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M205518P17113.mail1,S=8017,W=8227:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M355896P17113.mail1,S=8042,W=8252:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M52133P17113.mail1,S=8053,W=8263:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M555847P17113.mail1,S=8029,W=8239:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M581502P17113.mail1,S=8047,W=8257:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M606379P17113.mail1,S=8044,W=8254:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M628850P17113.mail1,S=8036,W=8246:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M657431P17113.mail1,S=8069,W=8279:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M681265P17113.mail1,S=8039,W=8249:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M706585P17113.mail1,S=8073,W=8283:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M730046P17113.mail1,S=8059,W=8269:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M753487P17113.mail1,S=8034,W=8244:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M776202P17113.mail1,S=8019,W=8229:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M799238P17113.mail1,S=8085,W=8295:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M822106P17113.mail1,S=8081,W=8291:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M844397P17113.mail1,S=8102,W=8312:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M867952P17113.mail1,S=7964,W=8174:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M889882P17113.mail1,S=7992,W=8202:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M912429P17113.mail1,S=8005,W=8215:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M935326P17113.mail1,S=8027,W=8237:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M959570P17113.mail1,S=8037,W=8247:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986418.M987388P17113.mail1,S=8018,W=8228:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M112704P17113.mail1,S=8044,W=8254:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M13262P17113.mail1,S=8025,W=8235:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M321294P17113.mail1,S=8012,W=8222:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M347297P17113.mail1,S=8014,W=8224:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M36960P17113.mail1,S=8037,W=8247:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M371029P17113.mail1,S=8005,W=8215:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M395270P17113.mail1,S=8024,W=8234:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M418277P17113.mail1,S=8046,W=8256:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M441021P17113.mail1,S=8047,W=8257:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M466329P17113.mail1,S=8025,W=8235:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M491134P17113.mail1,S=8038,W=8248:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M515650P17113.mail1,S=8046,W=8256:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M539950P17113.mail1,S=8017,W=8227:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M563073P17113.mail1,S=7983,W=8193:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M587009P17113.mail1,S=7963,W=8173:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M611652P17113.mail1,S=7994,W=8204:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M65180P17113.mail1,S=8015,W=8225:2,S' add 'Maildir/.INBOX.years.2020.family/cur/1601986419.M90376P17113.mail1,S=8036,W=8246:2,S' ----------------------------------- Would you be so kind and confirm that this is all I need to archive and that Dovecot will/can re-create all files ignored by git? For example based on my research the following files / directories would be ignored: - new/ (empty dir) - tmp/ (empty dir) - maildirfolder/ (dir with maildirfolder file) - dovecot-uidlist - dovecot-uidvalidity - dovecot-uidvalidity.5f7c4f24 - dovecot.index - dovecot.index.cache - dovecot.index.log - dovecot.index.log.2 - dovecot.list.index - dovecot.list.index.log - dovecot.list.index.log.2 - dovecot.mailbox.log In case of my test: # git status --ignored ----------------------------------- On branch master No commits yet Untracked files: (use "git add <file>..." to include in what will be committed) .gitignore Maildir/ Ignored files: (use "git add -f <file>..." to include in what will be committed) Maildir/.INBOX.years.2020.family/dovecot-uidlist Maildir/.INBOX.years.2020.family/dovecot.index Maildir/.INBOX.years.2020.family/dovecot.index.cache Maildir/.INBOX.years.2020.family/dovecot.index.log Maildir/.INBOX.years.2020.family/dovecot.index.log.2 Maildir/.INBOX.years.2020.family/maildirfolder Maildir/dovecot-uidlist Maildir/dovecot-uidvalidity Maildir/dovecot-uidvalidity.5f7c4f24 Maildir/dovecot.index.log Maildir/dovecot.list.index Maildir/dovecot.list.index.log Maildir/dovecot.list.index.log.2 Maildir/dovecot.mailbox.log Maildir/subscriptions nothing added to commit but untracked files present (use "git add" to track) ----------------------------------- Thank you. Adam

7 13

Setting up Development Environment for Plugins development/ Debugging
by Mrinal Sharma 07 Oct '20

07 Oct '20

Hello Everyone, I am very new to Dovecot development so I am sorry for asking this very basic question. Is there a document which can be referred to setup/debug plugin development environment? Thanks, Mrinal Sharma

1 1

LMTP Authentication Error
by David Morsberger 07 Oct '20

07 Oct '20

3 2

RE: How to Modify Message and add more Attachments
by Marc Roos 07 Oct '20

07 Oct '20

I have clients that process personal data and they even need to have 'special' processing agreements with companies like wetransfer and outlook.com. I had to sign also such agreement and prepare a vm for hot/cold data encryption for processing personal data. If someone leaves a voice mail message, he does not expect that this is going to be send to a third party. I think this expectation causes the gdpr 'by default' highest privacy/security of personal data protection to be applicable. Lots of companies are being fined currently for breaching gdpr, small, large, international even nation governmental organisations. Better check this. -----Original Message----- Subject: RE: How to Modify Message and add more Attachments Can you elaborate on the concern? -----Original Message----- From: Marc Roos <M.Roos(a)f1-outsourcing.eu> Sent: Tuesday, October 6, 2020 4:17 PM To: dovecot <dovecot(a)dovecot.org>; Mrinal Sharma <msharma(a)smithmicro.com> Subject: RE: How to Modify Message and add more Attachments CAUTION - EXTERNAL EMAIL This email originated from outside of Smith Micro Software. Do not click links or open attachments unless you recognize the sender and know the content is safe. If are processing Europeans voice mail you have to check if that is even allowed, could be a problem with GDPR legislation. -----Original Message----- Subject: RE: How to Modify Message and add more Attachments Thanks, am planning to use Google's Speech-to-Text. -----Original Message----- Sent: Tuesday, October 6, 2020 3:39 PM To: dovecot <dovecot(a)dovecot.org>; Mrinal Sharma <msharma(a)smithmicro.com> Subject: RE: How to Modify Message and add more Attachments CAUTION - EXTERNAL EMAIL This email originated from outside of Smith Micro Software. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hmmm, that does not sound nice storing files as email. Maybe use document database? Look at this[1], see if it is possible to use the rados plugin to store files directly as objects? What are you using for speech to text? [1] https://github.com/ceph-dovecot/dovecot-ceph-plugin -----Original Message----- To: dovecot(a)dovecot.org Subject: How to Modify Message and add more Attachments Hello Everyone, I am working on a product in which we are planning to store voice messages in Dovecot sent by a user to another user. The message would be stored as an email with .wav attachment. Once the Voice message is received, it may get Transcribed. The message can be further be processed and more information can be added to the message later. The original plan was to Modify the email and add New information as attachments to same message. As I understood, messages stored in Dovecot are immutable. What is the best option to achieve this functionality? Thanks, Mrinal

2 3

How to Modify Message and add more Attachments
by Mrinal Sharma 07 Oct '20

07 Oct '20

Hello Everyone, I am working on a product in which we are planning to store voice messages in Dovecot sent by a user to another user. The message would be stored as an email with .wav attachment. Once the Voice message is received, it may get Transcribed. The message can be further be processed and more information can be added to the message later. The original plan was to Modify the email and add New information as attachments to same message. As I understood, messages stored in Dovecot are immutable. What is the best option to achieve this functionality? Thanks, Mrinal

3 5

Strange errors after updating to 2.3.11.3
by Samuel Williams 06 Oct '20

06 Oct '20

Hello, After a recent update, I saw lots of errrors like this: Oct 05 23:55:35 mail.[redacted] dovecot[1053]: imap(samuel@[redacted])<10580><JUizN/WwWGKX0qt0>: Error: Mailbox INBOX: UID=364587: read(zlib(/srv/mail/[redacted]/samuel/mail.mdbox/storage/m.10688)) failed: read(/srv/mail/[redacted]/samuel/mail.mdbox/storage/m.10688) failed: Broken pipe (FETCH BODY[]) Oct 05 23:55:35 mail.[redacted] dovecot[1053]: imap(samuel@[redacted])<10580><JUizN/WwWGKX0qt0>: FETCH read() failed in=140 out=1440544 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=1 body_bytes=467441 I have been using xz compression for a long time and it has been reliable. However, the latest update seemed to corrupt some attachments. So, I downgraded back to: warning: downgrading package dovecot (2.3.11.3-2 => 2.3.10.1-2) warning: downgrading package pigeonhole (0.5.11-1 => 0.5.10-2) Now, I see a different error message: Oct 06 00:13:38 mail.[redacted] dovecot[833]: imap(samuel@[redacted])<4019><efc9ePWwgiOX0qt0>: Error: Corrupted record in index cache file /srv/mail/[redacted]/samuel/mail.mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 364587: Broken virtual size in mailbox INBOX: read(zlib(/srv/mail/[redacted]/samuel/mail.mdbox/storage/m.10688)): FETCH BODY[] got too little data: 467441 vs 475397 1/ Why did this happen and is there a safe way to upgrade? 2/ Is downgrading a temporary solution? 3/ Are these files lost or can I rebuild them somehow? Kind regards, Samuel

1 0

Dsync issues since 2.3.11.3.
by Reio Remma 02 Oct '20

02 Oct '20

Hello! I've started seeing intermittent dsync failures since upgrading Dovecot to 2.3.11.3-3 (CentOS 8 using the official Dovecot repo). Sep 27 17:49:04 host dovecot[130]: dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 66543 no longer in transaction log (highest=66547, last_common_uid=46346, nextuid=46347)) Sep 27 17:49:04 host dovecot[130]: dsync-local(user@host)<5GWFD2CmcF+TJwAAsNnMGQ>: Error: Remote command returned error 75: ssh <options> doveadm dsync-server -u user@host It seems to happen at random times to random users. My setup has 2 servers - users are connecting to the main server and the secondary server is just for backup - noone is actually connecting to it. Any suggestions? Thanks! Reio

1 2

Re: BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
by PGNet Dev 01 Oct '20

01 Oct '20

hi, On 10/1/20 12:21 AM, JEAN-PAUL CHAPALAIN wrote: > I had the same problem when migrating from Dovecot V2.2.36 on, Centos-7 to Dovecot v2.3.8 on Centos-8 My report is specifically/solely about the addition/use of the Options = ServerPreference parameter. I don't see that in your configuration. Are you using it? In a config using Dovecot's submission proxy?

2 3

dovecot lda deliver_log_format question
by rudolf＠padaru.de 01 Oct '20

01 Oct '20

Hey, i have an question about the deliver_log_format. My log looks sometimes like: Oct 1 09:38:01 dd44414 dovecot: lda(user)<20009><9MYzGVmHdV8pTgAA+v7NQw>: msgid=<20201001073801.628713AC05DC(a)myserver.com>: saved mail to INBOX The deliver_log_format settings are still on default. Are somebody able to explain me this part of the log message? <20009><9MYzGVmHdV8pTgAA+v7NQw>: What want dovecot to say with this? Mit freundlichen Grüßen Yours sincerely Pascal Rudolf

2 1

debugging TLS with wireshark and a custom application ?
by Kurt Jaeger 01 Oct '20

01 Oct '20

Hi! My question is: can dovecot be used to debug/decrypt TLS sessions ? The reason I'm asking: A custom application wants to speak IMAP with TLS with a dovecot instance. It fails, and the error message is, unfortunatly, not very helpful. tcpdump shows that the session is established, but fails. The custom application says error 60000, not much more. There is a way to decode TLS sessions in some cases: https://wiki.wireshark.org/TLS using firefox and the enviroment variable SSLKEYLOGFILE. Basically, the TLS client (firefox), while negotiating keys with the other side, writes those logfiles to a logfile specified by SSLKEYLOGFILE and at the same time, wireshark is used to capture / write the pcap of the session. Then wireshark can be used to decode the contents of the TLS-encrypted session. Is something similiar possible with dovecot as the server and from the server side ? Is, by chance, the session=<...> value already such a key so that a tcpdump pcap file would be able to descrypt that session ? Sep 29 08:51:30 imap-login: Info: Login: user=<someuser>, method=PLAIN, rip=<someip>, lip=<someotherip>, mpid=63667, TLS, session=<GGF0Nm6wxy0qAQHoAAMAAwAAAAAAAAAB> -- pi(a)opsec.eu +49 171 3101372 Now what ?

3 2

auth_username_format effective only within passdb/userdb
by Bob 30 Sep '20

30 Sep '20

Hello dovecot list. I have multiple passdb/userdb, some use %Ln some use %Lu. How to make auth_username_format effective only within passdb/userdb?

2 2

Leaked files in maildir "tmp" after vsz_limit crashes
by Peter Mogensen 30 Sep '20

30 Sep '20

Hi, Lately I've seen a few examples of users hitting the vsz_limit (usually trying to "delete" mails i Spam/Junk by moving them to Trash with a large dovecot.index.cache - which resulted in mails left/leaked in the tmp directory of Trash. Sometimes it seems the client gets into a state were it repeatedly tried to sync the client and server state so it does it again and again, building up the number of files/links in tmp. It seems the default 1 week interval to "unlink_old_files()" is not enough to prevent this from blowing up inode wise. However, ... lowering it, - or increasing vsz_limit feels a bit like kicking the can down the road. PS: This on dovecot 2.2.36 /Peter

2 1

Re: Dovecot permission denied errors on NFS after upgrade to 2.2.17
by Claudio Corvino 29 Sep '20

29 Sep '20

Thanks Jochen, no mixups present at all, file assigned to UID 501. Since this problem started few hours after the Debian upgrade, I think it is related to it. I don't know if something has changed on the NFS client side on Debian, but I don't think so as aptlistchanges didn't notify me about it, nor if Dovecot 2.2.17 treat NFS in other way. I'm stuck. On 13/07/20 16:07, Jochen Bern wrote: > On 07/13/2020 03:45 PM, Claudio Corvino wrote: >> in addition the "permission denied" error is >> random, most of the time Dovecot works well. > In *that* case, I'd say that UID/GID mapping problems can be ruled out. > >> How can I check the mappings NFS uses? > You don't have any relevant options in the client's fstab entry, and > I'll assume that there are none in the server's /etc/exports, either. > That leaves only potential default mappings, which should be documented > in the corresponding manpages. > > Also, since there's only *one* user/group involved, you can always > "chown" a test file on one side and check with "ls -n" on the other to > verify whether there are mixups. > > *Intermittent* failures of an NFS mount over a well-functioning LAN ... > I'm thinking "file locking" now, but that's a *complicated* topic, to > say the least ... > > https://en.wikipedia.org/wiki/File_locking#Problems > https://unix.stackexchange.com/questions/553645/how-to-install-nfslock-daem… > > Regards,

4 8

Re-sieve emails
by ＠lbutlr 29 Sep '20

29 Sep '20

Is it possible to take the contents of a mailbox and feed them to the account's .active_sieve file for reprocessing? (For example, when editing the sieve file for my list account I introduced a typo, so a hundred or some list messages ended up in the inbox instead of filed properly into the maildir hierarchy. Not a huge deal, as it was simple enough to move them manually, but it got me wondering. This would also be useful for testing. -- Clarke's Law: Sufficiently advanced technology is indistinguishable from magic Clark's Law: Sufficiently advanced cluelessness is indistinguishable from malice Clark Slaw: Anything that has been severely damaged or destroyed by application of Clark's Law

2 4

dovecot warns (non-fatal) "invalid EHLO response line: Unexpected character in EHLO keyword" connecting to submission relay ?
by PGNet Dev 29 Sep '20

29 Sep '20

I'm setting up an alternative submission relay host for dovecot. Atm, it's pointing @ fastmail.com. with dovecot config, submission_relay_host = smtp.fastmail.com submission_relay_port = 465 submission_relay_ssl = smtps submission_relay_ssl_verify = no submission_relay_trusted = yes submission_relay_user = 'acctID(a)mydomain.com' submission_relay_password = 'acctPWD' submission relay via dovecot proxy works as expected -- mail's delivered/received by intended recipient. in local dovecot logs I notice ==> /var/log/dovecot/dovecot.log <== 2020-09-24 16:22:19 submission(recipient(a)example.com)<xxxxxxxxxxxxxxxx>: Warning: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword at debug level ==> /var/log/dovecot/dovecot-debug.log <== 2020-09-24 16:22:19 submission(recipient(a)example.com)<xxxxxxxxxxxxxxxx>: Debug: smtp-client: conn smtp.fastmail.com:465 (66.111.4.140:465) [1]: command EHLO: Got reply (1/1): 250 mail.messagingengine.com PIPELINING SIZE 73000000 AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN ENHANCEDSTATUSCODES 8BITMIME (1 commands pending, 0 commands queued) it's clearly non-fatal, simply a warning. i certainly do _not_ see this with every relay host, so suspect it's unique to fastmail's EHLO response. at least within the set of hosts I've tested. i'd like to find/fix it ... either at my dovecot instance, or @ fastmail. what's specifically invalid about 250 mail.messagingengine.com PIPELINING SIZE 73000000 AUTH DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN AUTH=DIGEST-MD5 CRAM-MD5 NTLM LOGIN PLAIN ENHANCEDSTATUSCODES 8BITMIME by dovecot's 'measure'?

3 3

managesieve script 'redirect' fails @ "Error: sieve: ... aborted due to temporary failure; Error: smtp-server: ... failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number"; direct send OK ?
by PGNet Dev 29 Sep '20

29 Sep '20

I run dovecot --version 2.3.10.1 (a3d0e1171) postconf mail_version mail_version = 3.5.7 with three valid accounts on the server, user1(a)example1.net user2(a)example2.net admin(a)mx.example.com I can send/receive from each -- both to/from external addresses, as well as between one another. E.g., on mail sent to user2(a)example2.net -> admin(a)mx.example.com logs of the successful delivery are ==> /var/log/dovecot/dovecot-info.log <== 2020-09-26 16:00:33 submission-login: Info: Login: user=<sender(a)mx.example.com>, method=PLAIN, rip=10.0.1.9, lip=10.0.1.17, mpid=7178, TLS 2020-09-26 16:00:33 submission(sender(a)mx.example.com)<gQePZj+wUuesHgsH>: Info: Successfully relayed message: from=<user2(a)example2.net>, size=449, id=WjpMLRHIb18KHAAA+IOfAw, nrcpt=1, reply=`250 2.0.0 Ok: queued as 4BzPQ95QwwzWf9g' 2020-09-26 16:00:33 submission(sender(a)mx.example.com)<gQePZj+wUuesHgsH>: Info: Disconnect from 10.0.1.9: Client has quit the connection in=566 out=114 (state=READY) 2020-09-26 16:00:33 imap(user2(a)example2.net)<YzPbWj+wzNCsHgsH>: Info: save: box=Sent, uid=42, msgid=<9ca622bd-cdc3-ca26-8650-556d4132fe6c(a)example2.net>, size=434 2020-09-26 16:00:33 lmtp(7183): Info: Connect from local 2020-09-26 16:00:33 lmtp(admin(a)mx.example.com)<2HI4MBHIb18PHAAA+IOfAw>: Info: msgid=<9ca622bd-cdc3-ca26-8650-556d4132fe6c(a)example2.net>: saved mail to INBOX 2020-09-26 16:00:33 lmtp(7183): Info: Disconnect from local: Client has quit the connection (state=READY) ==> /var/log/postfix/postfix.log <== Sep 26 16:00:33 mx postfix/submit-from-dovecot-proxy/smtpd[7179]: connect from internal.mx.example.com[10.0.1.17] Sep 26 16:00:33 mx postfix/submit-from-dovecot-proxy/smtpd[7179]: Trusted TLS connection established from internal.mx.example.com[10.0.1.17]: TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature ECDSA (P-384) client-digest SHA384 Sep 26 16:00:33 mx postfix/submit-from-dovecot-proxy/smtpd[7179]: 4BzPQ95QwwzWf9g: client=internal.mx.example.com[10.0.1.17] Sep 26 16:00:33 mx postfix/qmgr[6928]: 4BzPQ95QwwzWf9g: from=<user2(a)example2.net>, size=824, nrcpt=1 (queue active) Sep 26 16:00:33 mx postfix/submit-from-dovecot-proxy/smtpd[7179]: disconnect from internal.mx.example.com[10.0.1.17] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Sep 26 16:00:33 mx postfix/lmtp[7182]: 4BzPQ95QwwzWf9g: to=<admin(a)mx.example.com>, relay=mx.example.com[private/dovecot-lmtp], delay=0.06, delays=0.03/0.01/0.01/0.02, dsn=2.0.0, status=sent (250 2.0.0 <admin(a)mx.example.com> 2HI4MBHIb18PHAAA+IOfAw Saved) Sep 26 16:00:33 mx postfix/qmgr[6928]: 4BzPQ95QwwzWf9g: removed ==> /var/log/dovecot/dovecot-info.log <== 2020-09-26 16:00:33 imap(user2(a)example2.net)<YzPbWj+wzNCsHgsH>: Info: Connection closed (IDLE running for 0.001 + waiting input for 0.009 secs, 2 B in + 10 B out, state=wait-input) in=1199 out=3082 deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=271 body_count=0 body_bytes=0 2020-09-26 16:00:33 imap-login: Info: Login: user=<user2(a)example2.net>, method=PLAIN, rip=10.0.1.9, lip=10.0.1.17, mpid=7185, TLS I've added a user sieve script for user == user2(a)example2.net cat /srv/mail/sieve-scripts/user2(a)example2.net.sieve # rule:[SIEVETEST] if header :contains "subject" "SIEVETEST" { redirect "admin(a)mx.example.com"; } where the redirect is to the valid address tested/demonstrated above, admin(a)mx.example.com in dovecot config, submission_host = internal.mx.example.com:60465 currently, host mx.example.com mx.example.com has address 10.0.1.17 mx.example.com has IPv6 address fd70:10:0:1::17 host internal.mx.example.com internal.mx.example.com has address 10.0.1.17 internal.mx.example.com has IPv6 address fd70:10:0:1::17 on test send from user1(a)example1.net to user2(a)example2.net, with Subject == SIEVETEST the user sieve _is_ triggered/executed cat 20200926-160636.7461.1.trace Sieve trace log for message delivery: Username: user2(a)example2.net Session ID: E851MXzJb18lHQAA+IOfAw Sender: <user1(a)example1.net> Final recipient: <user2(a)example2.net> Default mailbox: INBOX ## Started executing script 'managesieve' 2: not jumping 4: redirect action 4: forward message to address <admin(a)mx.example.com> ## Finished executing script 'managesieve' but the mail redirect delivery fails 2020-09-26 16:06:36 submission-login: Info: Login: user=<sender(a)mx.example.com>, method=PLAIN, rip=10.0.1.9, lip=10.0.1.17, mpid=7455, TLS 2020-09-26 16:06:36 submission(sender(a)mx.example.com)<VbsxfD+wXOesHgsH>: Info: Successfully relayed message: from=<user1(a)example1.net>, size=466, id=lvK6LnzJb18fHQAA+IOfAw, nrcpt=1, reply=`250 2.0.0 Ok: queued as 4BzPY85g9czWf8L' 2020-09-26 16:06:36 submission(sender(a)mx.example.com)<VbsxfD+wXOesHgsH>: Info: Disconnect from 10.0.1.9: Client has quit the connection in=567 out=114 (state=READY) 2020-09-26 16:06:36 lmtp(7461): Info: Connect from local 2020-09-26 16:06:36 imap(user1(a)example1.net)<0ZZlej+w2NCsHgsH>: Info: save: box=Sent, uid=13177, msgid=<28930f55-5a39-c8bd-67c2-39e581aa7551(a)example1.net>, size=450 ==> /var/log/postfix/postfix.log <== Sep 26 16:06:36 mx postfix/submit-from-dovecot-proxy/smtpd[7456]: connect from internal.mx.example.com[10.0.1.17] Sep 26 16:06:36 mx postfix/submit-from-dovecot-proxy/smtpd[7456]: Trusted TLS connection established from internal.mx.example.com[10.0.1.17]: TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384 client-signature ECDSA (P-384) client-digest SHA384 Sep 26 16:06:36 mx postfix/submit-from-dovecot-proxy/smtpd[7456]: 4BzPY85g9czWf8L: client=internal.mx.example.com[10.0.1.17] Sep 26 16:06:36 mx postfix/qmgr[7362]: 4BzPY85g9czWf8L: from=<user1(a)example1.net>, size=812, nrcpt=1 (queue active) Sep 26 16:06:36 mx postfix/submit-from-dovecot-proxy/smtpd[7456]: disconnect from internal.mx.example.com[10.0.1.17] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 ==> /var/log/dovecot/dovecot.log <== 2020-09-26 16:07:06 lmtp(user2(a)example2.net)<E851MXzJb18lHQAA+IOfAw>: Error: smtp-client: conn internal.mx.example.com:60465 (10.0.1.17:60465) [1]: connect(internal.mx.example.com:60465) failed: Connection timed out after 30 seconds 2020-09-26 16:07:06 lmtp(user2(a)example2.net)<E851MXzJb18lHQAA+IOfAw>: Error: sieve: msgid=<28930f55-5a39-c8bd-67c2-39e581aa7551(a)example1.net>: redirect action: failed to redirect message to <admin(a)mx.example.com>: smtp(internal.mx.example.com:60465): RCPT TO failed: Connect timed out (temporary failure) 2020-09-26 16:07:06 lmtp(user2(a)example2.net)<E851MXzJb18lHQAA+IOfAw>: Error: sieve: Execution of script /srv/mail/sieve-scripts/user2(a)example2.net.sieve was aborted due to temporary failure (user logfile /srv/mail/sieve-scripts/user2(a)example2.net.sieve.log may reveal additional details) 2020-09-26 16:07:06 submission-login: Error: smtp-server: conn 10.0.1.17:50578 [1]: Connection lost: read((conn:10.0.1.17:50578,id=1)) failed: SSL_accept() failed: error:1408F10B:SSL routines:ssl3_get_record:wrong version number 2020-09-26 16:07:06 submission-login: Info: Read failure (client didn't send a cert): user=<>, rip=10.0.1.17, lip=10.0.1.17, TLS handshaking: SSL_accept() syscall failed: Invalid argument 2020-09-26 16:07:06 lmtp(7461): Info: Disconnect from local: Client has quit the connection (state=READY) ==> /var/log/postfix/postfix.log <== Sep 26 16:07:06 mx postfix/lmtp[7460]: 4BzPY85g9czWf8L: to=<user2(a)example2.net>, relay=mx.example.com[private/dovecot-lmtp], delay=30, delays=0.04/0/0/30, dsn=4.2.0, status=deferred (host mx.example.com[private/dovecot-lmtp] said: 451 4.2.0 <user2(a)example2.net> Execution of Sieve filters was aborted due to temporary failure (in reply to end of DATA command)) & cat /srv/mail/sieve-scripts/user2(a)example2.net.sieve.log sieve: info: started log at Sep 26 16:07:06. error: msgid=<28930f55-5a39-c8bd-67c2-39e581aa7551(a)example1.net>: redirect action: failed to redirect message to <admin(a)mx.example.com>: smtp(internal.mx.example.com:60465): RCPT TO failed: Connect timed out (temporary failure). and remains stuck in postfix queue postqueue -p ----Queue ID----- --Size-- ---Arrival Time---- --Sender/Recipient------ 4BzPY85g9czWf8L 812 Sat Sep 26 16:06:36 user1(a)example1.net (host mx.example.com[private/dovecot-lmtp] said: 451 4.2.0 <user2(a)example2.net> Execution of Sieve filters was aborted due to temporary failure (in reply to end of DATA command)) user2(a)example2.net -- 0 Kbytes in 1 Request. it appears there's an SSL/cert problem -- but only in the case of the redirect. i.e.., this direct send, user2(a)example2.net --SEND--> admin(a)mx.example.com works, but the redirect user1(a)example1.net (subjet == "SIEVETEST") --SEND--> user2(a)example2.net --REDIRECT--> admin(a)mx.example.com does not, failing as above. i suspect i'm missing config, but what/where in the dovecot submission/sieve configs addresses this^ point in the SSL transaction?

1 3

maildir -> sdbox migration command for _all_ accounts, with split maildir/CONTROL/INDEX locations?
by PGNet Dev 26 Sep '20

26 Sep '20

in a recent post, sven made a clear/cogent arg for sdbox vs maildir > While Maildir seems to be an obvious choice, it has some hidden > performance impacts, namely it relies heavily on information encoded in > the filename, which results in a big overhead in meta-operations, > because Dovecot needs to stat() every file in a directory to gather > those information. i've initially avoided sdbox, assuming the index-file dependency to be an additional failure pt, but that^^ is somewhat compelling. i'd like to migrate maildir -> sdbox. the given migration example $ doveadm -D -v -o backup -u sven sdbox:~/sdbox examples in the docs generally demonstrate a single user migration, from a consolidated ~/Maildir tree, and use the 'dsync ...' command (full alias?) atm, my 'mail_location' is set with split CONTROL & INDEX locations, in fs-layout, as mail_location = maildir:/data/vmail/%d/%n/Maildir:CONTROL=/data/vmail/%d/%n/_control:INDEX=/var/vmail-index/%d/%n:LAYOUT=fs:UTF-8 and I've a significant number of domains & users. I'd like to migrate the ENTIRE server -- all domain/user accounts. For the moment, I'd like to ensure that I do not change/destroy the current Maildir stores/indexes, and end up with a parallel store in mail_location = sdbox:/data/vmail/%d/%n/Sdbox:CONTROL=/data/vmail/sdbox/%d/%n/_control:INDEX=/var/sdbox/vmail-index/%d/%n:LAYOUT=fs:UTF-8 which I can then double-check, and eventually switch to. What's the correct procedure/syntax for an all-accounts, in-place migration command from maildir->sdbox?

1 0

Shared folders using mbox format
by Alex 26 Sep '20

26 Sep '20

Hi, I'd like to create a shared folder to be used with an Outlook client and a Thunderbird client. We're currently using mboxes. I've read the documentation here about creating a shared folder: https://wiki.dovecot.org/SharedMailboxes/Shared It doesn't make reference to how to do this using mbox format. Is it possible? Should we convert to Maildir? Perhaps there's a way to provide both formats?

3 4

dovecot TSL 1.3 config option 'ssl_ciphersuites' causes fatal error on launch. not supported, bad config, or bug?
by PGNet Dev 24 Sep '20

24 Sep '20

I've installed grep PRETTY /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" dovecot --version 2.3.10.1 (a3d0e1171) openssl version OpenSSL 1.1.1g FIPS 21 Apr 2020 iiuc, Dovecot has apparently had support for setting TLS 1.3 ciphersuites since v2.3.9, per this commit lib-ssl-iostream: Support TLSv1.3 ciphersuites https://github.com/dovecot/core/commit/8f6f04eb21276f28b81695dd0d3df57c7b8f… checking openssl rpm -ql openssl-devel-1.1.1g-1.fc32.x86_64 | grep -i ciphersuites /usr/share/man/man3/SSL_CTX_set_ciphersuites.3ssl.gz /usr/share/man/man3/SSL_set_ciphersuites.3ssl.gz man SSL_set_ciphersuites ... SSL_set_cipher_list() sets the list of ciphers (TLSv1.2 and below) only for ssl. SSL_CTX_set_ciphersuites() is used to configure the available TLSv1.3 ciphersuites for ctx. This is a simple colon (":") separated list of TLSv1.3 ciphersuite names in order of preference. Valid TLSv1.3 ciphersuite names are: TLS_AES_128_GCM_SHA256 TLS_AES_256_GCM_SHA384 TLS_CHACHA20_POLY1305_SHA256 TLS_AES_128_CCM_SHA256 TLS_AES_128_CCM_8_SHA256 An empty list is permissible. The default value for the this setting is: "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256" SSL_set_ciphersuites() is the same as SSL_CTX_set_ciphersuites() except it configures the ciphersuites for ssl. ... checkin in dovecot tag 2.3.10.1's src, m4/ssl.m4 (m4) ... AC_CHECK_LIB(ssl, SSL_CTX_set_ciphersuites, [ AC_DEFINE(HAVE_SSL_CTX_SET_CIPHERSUITES,, [Build with SSL_CTX_set_ciphersuites() support]) ],, $SSL_LIBS) ... and, src/lib-ssl-iostream/iostream-openssl.c ... #ifdef HAVE_SSL_CTX_SET_CIPHERSUITES if (set->ciphersuites != NULL && strcmp(ctx_set->ciphersuites, set->ciphersuites) != 0) { if (SSL_set_ciphersuitesl(ssl_io->ssl, set->ciphersuites) == 0) { *error_r = t_strdup_printf( "Can't set ciphersuites to '%s': %s", set->ciphersuites, openssl_iostream_error()); return -1; } } #endif ... suggests that ciphersuite support exists. bug, checking in ./src/lib-master/master-service-ssl.c ... void master_service_ssl_ctx_init(struct master_service *service) { const struct master_service_ssl_settings *set; struct ssl_iostream_settings ssl_set; const char *error; if (service->ssl_ctx_initialized) return; service->ssl_ctx_initialized = TRUE; /* must be called after master_service_init_finish() so that if initialization fails we can close the SSL listeners */ i_assert(service->listeners != NULL || service->socket_count == 0); set = master_service_ssl_settings_get(service); if (strcmp(set->ssl, "no") == 0) { /* SSL disabled, don't use it */ return; } i_zero(&ssl_set); ssl_set.min_protocol = set->ssl_min_protocol; ssl_set.cipher_list = set->ssl_cipher_list; ssl_set.curve_list = set->ssl_curve_list; ssl_set.ca = set->ssl_ca; ... there's only mention of set->ssl_cipher_list , not set->ssl_ciphersuites or equivalent, afaict. if in dovecot's 10-ssl.conf I set ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256 + ssl_ciphersuites = TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256 on restart journalctl -f -u dovecot -- Logs begin at Sun 2020-09-20 14:30:30 PDT. -- Sep 23 18:28:42 mx.example.com dovecot[4269]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 92: Unknown setting: ssl_ciphersuites _is_ setting TLS 1.3 ssl_ciphersuites = in fact currently supported, and usage is wrong here^?

3 3

Importing Mail
by Odhiambo Washington 24 Sep '20

24 Sep '20

Hi good people, I have an old server that holds old mail (mdbox) and a new server that also uses mdbox. I'd like to import the old mail from the old server into the live/new server. The imported mail should not be treated as new mail for the existing mail accounts. What is the best way to achieve this? Lastly, is there a way to convert mdbox to Maildir? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

2 2

Vacation sieve explained: how does it work?
by Graham Leggett 24 Sep '20

24 Sep '20

Hi all, I have a legacy system that uses gnarwl to handle vacation messages, most specifically the vacation messages are stored in LDAP. We have a web based tool that allows people to update their vacation message, all they’re doing is modifying LDAP. I am trying to find out if dovecot’s vacation sieve can do the same thing. I am struggling however to find something that describes to me how dovecot vacation sieve is configured. Is there a howto or walkthrough anywhere? Specific burning questions: - If I was to configure the dovecot vacation sieve, where is the body of each vacation message stored? File on disk? In a store like an LDAP store? Somewhere else? - How is the body of vacation message modified? Does this happen through the IMAP protocol, a command line tool, something else? - How is the vacation message switched on and off? Does this happen through the IMAP protocol, a command line tool, or something else? The docs at https://wiki2.dovecot.org/Pigeonhole/Sieve/Extensions/Vacation describe how to control how often the vacation messages are sent, but very little else. I am very confused :( Regards, Graham —

4 8

BUG: _presence_ of valid openssl.cnf Option = 'ServerPreference' causes Dovecot submission relay FAIL: "failed: Failed to initialize SSL: ..."
by PGNet Dev 24 Sep '20

24 Sep '20

I've dovecot --version 2.3.10.1 (a3d0e1171) openssl version OpenSSL 1.1.1g FIPS 21 Apr 2020 , atm on Fedora32. I configure /etc/pki/tls/openssl.cnf to set preferences for apps' usage, e.g. Postfix etc; Typically, here cat /etc/pki/tls/openssl.cnf openssl_conf = default_conf [default_conf] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] MinProtocol = TLSv1.2 Ciphersuites = TLS_CHACHA20_POLY1305_SHA256:TLS_AES_256_GCM_SHA384:TLS_AES_128_GCM_SHA256 CipherString = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256 Options = PrioritizeChaCha,ServerPreference However, any/all sends from local client via Dovecot submission -- from an instance on the same server -- FAILS with that^^ openssl.cnf, ==> /var/log/dovecot/dovecot.log <== ... 2020-08-24 17:04:42 submission(testuser(a)example.com)<D4c5c6itUg2sHgsH>: Error: smtp-client: conn int.mx.example.net:465 (10.0.4.65:465) [1]: connect(int.mx.example.net:465) failed: Failed to initialize SSL: Couldn't initialize SSL context: Can't load SSL certificate: error:14187180:SSL routines:ssl_do_config:bad value: section=system_default, cmd=Options, arg=ServerPreference,PrioritizeChaCha 2020-08-24 17:04:42 submission(testuser(a)example.com)<D4c5c6itUg2sHgsH>: Error: Failed to establish relay connection: Failed to connect to remote server ... editing, - Options = PrioritizeChaCha,ServerPreference + Options = PrioritizeChaCha cures the error ==> /var/log/dovecot/dovecot.log <== ... 2020-08-24 17:08:04 submission(testuser(a)example.com)<Uow+f6itZg2sHgsH>: Info: Successfully relayed message: from=<testuser(a)example.com>, size=433, id=Mh4pJWRWRF9jHQAAVDn7pA, nrcpt=1, reply=`250 2.0.0 Ok: queued as 4Bb8TJ4VQbz7v6t' ... checking ssl docs https://www.openssl.org/docs/man1.1.1/man3/SSL_CONF_cmd.html BOTH are valid 'Options', ... ServerPreference: use server and not client preference order when determining which cipher suite, signature algorithm or elliptic curve to use for an incoming connection. Equivalent to SSL_OP_CIPHER_SERVER_PREFERENCE. Only used by servers. PrioritizeChaCha: prioritizes ChaCha ciphers when the client has a ChaCha20 cipher at the top of its preference list. This usually indicates a mobile client is in use. Equivalent to SSL_OP_PRIORITIZE_CHACHA. Only used by servers. ... The mere presence of that option in a system-wide openssl.cnf shouldn't cause a Dovecot submission failure.

2 7

At a loss with antispan and imap_sieve
by Ferenc 24 Sep '20

24 Sep '20

Hi, It seems I can’t google my way out of this one. I’m trying to set up spam/ham learning but getting nowhere. I tried Johannes Berg Antispam plugin, and syslog shows: Sep 20 22:22:06 proefmail imap: antispam: running mailtrain backend program /usr/lib/dovecot/retrain.sh Sep 20 22:22:06 proefmail imap: antispam: running mailtrain backend program /usr/lib/dovecot/retrain.sh Sep 20 22:22:06 proefmail imap: antispam: running mailtrain backend program parameter 1 /mail/klaas Sep 20 22:22:06 proefmail imap: antispam: running mailtrain backend program parameter 2 ham The file retrain.sh is simply: #!/bin/sh echo hi >> debug.log ...with debug.log being an empty world-writeable file in /usr/lib/dovecot. Absolutely nothing happens. The file debug.log is not even touched. But when I remove retrain.sh there’s an error logged so up until then, *something* happens. After this I tried imap_sieve, following the wiki on dovecot.org, but again nothing happens. My imap.log says: Info: sieve: pipe action: piped message to program `retrain.sh’ But again debug.log is untouched. I’m fresh out of ideas here. Any help would be most welcome. I’m on Debian in virtual machine, Postfix delivering mail to Dovecot LMTP delivering to virtual maildirs, bogofilter for scanning incoming mail. Sieve does work for moving incoming spam to the spam mailbox. Cheers and thanks, Ferenc

3 6

implementing folder hashing
by Adrian Minta 23 Sep '20

23 Sep '20

Hi everyone, I want to ask if any of you has done a migration from a single storage to multiple back-end storages and what is the best strategy for folder hashing that you use. Using something like %H or %M how do you predict where the mail will end up in order to move the existing folders ? Thank you ! -- Best regards, Adrian Minta

2 4

Dovecot SASL
by Jorge Bastos 22 Sep '20

22 Sep '20

Howdy, I know i've asked this before, but i think i got really no answer. I'd like to have dovecot SASL, to check AUTH against an SQL table, instead of dovecot SASL use the AUTH MECH for imap/pop3. I want this, to have the same behavior as I have now, where i use postfix with cyrus SASL on a different table (with the same login details), and when i have an user that his accounts was hacked for sending spam, i just block the send and allow the user to keep receiving emails, for example to warn him. Would this be possible? Dovecot SASL against a SQL table? Havent found much info about it, Thanks in advanced,

2 2

Re: Leaked Events
by bobby 22 Sep '20

22 Sep '20

Is this an affected version of the bug? > 2.3.8 (9df20d2db) > > On Tue, Sep 8, 2020 at 12:42 PM Stephan Bosch <stephan(a)rename-it.nl> > wrote: > >> >> >> On 08/09/2020 18:01, bobby wrote: >> > I am going through my maillog file, and noticed these events: >> > >> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event >> > 0x55db5bc41200 leaked (parent=0x55db5bc3b830): >> mail-storage-service.c:1325 >> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event >> > 0x55db5bc3b830 leaked (parent=0x55db5bc34450): >> smtp-server-recipient.c:38 >> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event >> > 0x55db5bc34450 leaked (parent=0x55db5bc34130): connection.c:523 >> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event >> > 0x55db5bc34130 leaked (parent=0x55db5bc20ce0): >> > smtp-server-connection.c:773 >> > Sep 8 15:56:17 mail dovecot[294462]: lmtp(391257): Warning: Event >> > 0x55db5bc20ce0 leaked (parent=(nil)): lmtp-client.c:164 >> > >> > Is this something to be concerned about? >> >> Usually, not. >> >> But, it is a bug. What version is this? >> >> Regards, >> >> Stephan. >> >

3 6

FTS Index based on UserDB preference
by Scott Q. 22 Sep '20

22 Sep '20

Does anyone know if it's possible to do FTS Index based on a userdb preference ? Basically if the preference is 'on' , dovecot goes ahead with the fts indexing for that particular user. I'm guessing right now it's not possible but is there anyone that could envision writing such a patch ? If so, can you contact me off-list ?

2 2

[SOLVED]AW: AW: doveadm search segfault Dovecot 2.2.22
by rudolf＠padaru.de 22 Sep '20

22 Sep '20

Dear Aki thank you! With version 2.3.11 of dovecot it works fine. Yours sincerely Pascal Rudolf -----Ursprüngliche Nachricht----- Von: dovecot <dovecot-bounces(a)dovecot.org> Im Auftrag von Aki Tuomi Gesendet: Montag, 21. September 2020 17:37 An: rudolf(a)padaru.de; Dovecot Mailing List <dovecot(a)dovecot.org> Betreff: Re: AW: doveadm search segfault Dovecot 2.2.22 > On 21/09/2020 15:14 rudolf(a)padaru.de wrote: > > > Hey, > > i am now a bit deeper into dovecot debugging with gdb and have a full bt now, with debugging infos. > > Is there a patch that resolve this Problem in dovecot 2.2.22-1ubuntu2.13 for ubuntu 16? > > Here the bt: > Hi! We don't really support 2.2.22 since it was released several years ago. Please try to reproduce this issue with 2.2.36 or 2.3.11. You can find packages for 2.3.11 from https://repo.dovecot.org Aki

1 0

Default sieve mark seen?
by ＠lbutlr 22 Sep '20

22 Sep '20

I have the following in my default.sieve file: require "fileinto"; if header :contains "X-spam-flag" "YES" { require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "imap4flags"]; setflag "\\Seen"; fileinto "Junk"; } This is largely unchanged, except that I added imap4flags and set flag "\\Seen"; recently. The messages still get filed into the user's Junk folder, but they are still marked as unread. I also have imapsieve_mailbox3_name = Archive imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_before = file:/usr/lib/dovecot/sieve/mark-read.sieve # cat /usr/lib/dovecot/sieve/mark-read.sieve require ["imap4flags"]; setflag "\\seen"; Which works fine. How do I fix this? -- "The female of all species are most dangerous when they appear to retreat." - Don Marquis

2 2

Dovecot virtual folders usage: seen in Tbird client if subscribed, treated as _real_ folders -- and archived to local/offline storage? How to prevent?
by PGNet Dev 22 Sep '20

22 Sep '20

i run a dovecot v2.3.10 server. config includes virtual folders, dovecot.conf mail_plugins = virtual mail_location = maildir:/data/mail/%d/%n/Maildir:LAYOUT=fs:UTF-8 imap_capability = +SPECIAL-USE namespace inbox { inbox = yes type = private separator = / prefix = hidden = no list = yes subscriptions = yes ... mailbox virtual/All { special_use = \All auto = no comment = All } mailbox virtual/Flagged { special_use = \Flagged auto = no comment = Flagged } ... } namespace virtual { prefix = virtual/ separator = / location = virtual:/data/mail/virtual:INDEX=MEMORY hidden = no list = yes subscriptions = yes } and /data/mail/virtual/All/dovecot-virtual * -Trash -Trash/* All /data/mail/virtual/Flagged/dovecot-virtual * Flagged in Thunderbird client, without subscribing to the virtula folders, per account, they're undisplayed/inaccessible. if I select 'subscriptions', virtual All [X] Flagged [X] I see the aggregated/flagged messages. When I sync for offline usage, TBird copies messages to local storage for offline use, as expected but it ALSO *copies* all the 'virtual' messages to dirs in the local store cd ImapMail/user001-maildir tree -L 1 -d virtual.sbd/ virtual.sbd/ ├── All <========== └── Flagged <========== **DUPLICATING** messages stored in BOTH the parent/original dirs, AND a second copy in the Virtual dir. What needs to be done in order to see/use the subscribed Virtual folders in TBird enable Offline Sync/Storage & PREVENT the duplication and local storage of the 'virtual' mail instances ?

1 0

extra fields question
by joao＠7lan.net 21 Sep '20

21 Sep '20

Hi, I'm trying to configure the use of plugins per user in dovecot, more specifically, fts and fts_solr. It happen to have other necessary plugins per protocol, for example "imap_quota" which would be specifically for the imap protocol and which does not apply for the lmtp protocol. For this I need to specify that for the imap protocol I have: protocol imap { mail_plugins = quota imap_quota zlib imap_sieve mail_log notify } and for the lmtp protocol I have: protocol lmtp { mail_plugins = quota zlib fts fts_solr sieve } I did it according to the "extra fields" documentation and separated the name and key with /. My queries are correct but are not being applied to dovecot. Then in the case when the user has fts fts_solr he returns: procotol/imap/mail_plugins -> quota imap_quota zlib imap_sieve mail_log notify fts fts_solr procotol/lmtp/mail_plugins -> quota zlib sieve fts fts_solr but it does not work. Doing it for "mail_plugins" (without accessing config levels) extra fields works, but it also enable some plugins that are not compatible with some protocols. I thought about separating an instance of dovecot lmtp on the same server, but I would like a more direct configuration in the same instance. Does anyone have experience with this? Thanks in advance.

2 1

AW: doveadm search segfault Dovecot 2.2.22
by rudolf＠padaru.de 21 Sep '20

21 Sep '20

Hey, i am now a bit deeper into dovecot debugging with gdb and have a full bt now, with debugging infos. Is there a patch that resolve this Problem in dovecot 2.2.22-1ubuntu2.13 for ubuntu 16? Here the bt: (gdb) bt full #0 0x00007ffff73cf3f3 in array_count_i (array=0x555555810d38) at ../../src/lib/array.h:155 No locals. #1 message_part_finish (ctx=ctx@entry=0x555555810ce0) at message-parser.c:227 __FUNCTION__ = "message_part_finish" #2 0x00007ffff73d132c in message_parser_parse_next_block (ctx=0x555555810ce0, block_r=block_r@entry=0x7fffffffdc40) at message-parser.c:1244 ret = <optimized out> eof = false full = false __FUNCTION__ = "message_parser_parse_next_block" #3 0x00007ffff73d2218 in message_search_msg_real (error_r=0x7fffffffdca0, parts=<optimized out>, input=0x5555558159c0, ctx=0x55555580a870) at message-search.c:217 new_parts = 0x7fffffffdd50 ret = <optimized out> parser_ctx = 0x555555810ce0 raw_block = {part = 0x55555580cc50, hdr = 0x0, data = 0x0, size = 0} #4 message_search_msg (ctx=ctx@entry=0x55555580a870, input=0x5555558159c0, parts=<optimized out>, error_r=error_r@entry=0x7fffffffdca0) at message-search.c:244 _data_stack_cur_id = 6 error = <optimized out> ret = 1 #5 0x00007ffff7705c2f in search_body (arg=0x5555557ec948, ctx=0x7fffffffdd30) at index-search.c:649 msg_search_ctx = 0x55555580a870 error = 0x7fffffffdd40 "0ˀUUU" ret = <optimized out> __FUNCTION__ = "search_body" #6 0x00007ffff7690345 in mail_search_args_foreach (args=0x5555557ec948, args@entry=0x5555557ec8b0, callback=callback@entry=0x7ffff7705ba0 <search_body>, context=context@entry=0x7fffffffdd30) at mail-search.c:440 result = 1 #7 0x00007ffff7705870 in search_arg_match_text (ctx=0x55555580c0a0, args=0x5555557ec8b0) at index-search.c:779 hdr_parser_flags = MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE real_mail = 0x55555580c320 headers = <optimized out> hdr_ctx = {index_ctx = 0x55555580c0a0, imail = 0x55555580c320, args = 0x5555557ec8b0, decoded_block = {part = 0x0, hdr = 0x0, data = 0x0, size = 0}, decoded_block_set = false, hdr = 0x55555580a7e0, parse_headers = 0, custom_header = 0, threading = 0} body_ctx = {index_ctx = 0x55555580c0a0, input = 0x5555558159c0, part = 0x55555580cb30} have_headers = true have_body = true ret = <optimized out> imail = 0x55555580c320 input = 0x5555558159c0 headers_ctx = 0x0 failed = false #8 search_match_once (ctx=0x55555580c0a0) at index-search.c:1329 ctx = 0x55555580c0a0 ret = <optimized out> #9 0x00007ffff77078c1 in search_match_next (ctx=0x55555580c0a0) at index-search.c:1434 _data_stack_cur_id = 5 i = 2 n = 3 ret = <optimized out> #10 search_more_with_mail (mail=0x55555580c320, ctx=0x55555580c0a0) at index-search.c:1547 _data_stack_cur_id = 4 _ctx = 0x55555580c0a0 box = 0x5555557fc530 match = -1 ret = -1 imail = 0x55555580c320 cost1 = 3218534 #11 search_more_with_prefetching (mail_r=0x7fffffffde90, ctx=0x55555580c0a0) at index-search.c:1628 ---Type <return> to continue, or q <return> to quit--- _data_stack_cur_id = 3 count = <optimized out> ret = <optimized out> mail = 0x55555580c320 #12 search_more (ctx=ctx@entry=0x55555580c0a0, mail_r=mail_r@entry=0x7fffffffde90) at index-search.c:1700 imail = <optimized out> ret = <optimized out> #13 0x00007ffff7707fc4 in index_storage_search_next_nonblock (_ctx=0x55555580c0a0, mail_r=0x7fffffffdf58, tryagain_r=0x7fffffffdf07) at index-search.c:1728 mail = 0x5555557e4ce0 seq = 0 ret = <optimized out> #14 0x00007ffff7696ba2 in mailbox_search_next_nonblock (ctx=0x55555580c0a0, mail_r=0x7fffffffdf58, tryagain_r=<optimized out>) at mail-storage.c:1784 box = <optimized out> #15 0x00007ffff7696c0f in mailbox_search_next (ctx=0x55555580c0a0, mail_r=mail_r@entry=0x7fffffffdf58) at mail-storage.c:1769 tryagain = false #16 0x00005555555809d2 in doveadm_mail_iter_next (iter=<optimized out>, mail_r=mail_r@entry=0x7fffffffdf58) at doveadm-mail-iter.c:154 No locals. #17 0x00005555555839dd in cmd_search_box (info=<optimized out>, ctx=0x5555557e9800) at doveadm-mail-search.c:36 iter = 0x5555557fbb60 box = <optimized out> ret = 0 mail = 0x0 metadata = {guid = "\242\n\337\066\322|c_\330\004\000\000\303B(\247", virtual_size = 0, physical_size = 0, first_save_date = 0, cache_fields = 0x0, precache_fields = (unknown: 0), backend_ns_prefix = 0x0, backend_ns_type = (unknown: 0)} guid_str = 0x5555557da3f0 "a20adf36d27c635fd8040000c34228a7" #18 cmd_search_run (ctx=0x5555557e9800, user=<optimized out>) at doveadm-mail-search.c:61 _data_stack_cur_id = 2 iter = 0x5555557f3ed0 info = <optimized out> ret = <optimized out> #19 0x000055555557acef in doveadm_mail_next_user (ctx=ctx@entry=0x5555557e9800, cctx=cctx@entry=0x7fffffffe0f0, error_r=error_r@entry=0x7fffffffe0e8) at doveadm-mail.c:400 input = {module = 0x0, service = 0x5555555afc11 "doveadm", username = 0x5555557d8360 "m056e04b", session_id = 0x0, session_id_prefix = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = (unknown: 0), flags_override_remove = (unknown: 0), no_userdb_lookup = 0} error = 0x12830 <error: Cannot access memory at address 0x12830> ip = <optimized out> ret = <optimized out> __FUNCTION__ = "doveadm_mail_next_user" #20 0x000055555557b78d in doveadm_mail_single_user (ctx=ctx@entry=0x5555557e9800, cctx=cctx@entry=0x7fffffffe0f0, error_r=error_r@entry=0x7fffffffe0e8) at doveadm-mail.c:431 __FUNCTION__ = "doveadm_mail_single_user" #21 0x000055555557b876 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x5555557e9800, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:594 cctx = {cmd = 0x0, argc = 0, argv = 0x0, username = 0x5555557d8360 "m056e04b", cli = false, local_ip = {family = 0, u = {ip6 = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0} ret = <optimized out> error = 0x7ffff73dc07d <buffer_alloc+45> "\200K0\001H\211C\020H\211k H\211\003H\203\304\b[]\303\017\037D" #22 0x000055555557c5b6 in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=0x7fffffffe320) at doveadm-mail.c:1010 mctx = 0x5555557e9800 wildcard_user = <optimized out> fieldstr = 0x5555557df41b "Hallo" i = <optimized out> mail_cmd = {alloc = 0x555555583890 <cmd_search_alloc>, name = 0x5555555b1e54 "search", usage_args = 0x5555555b1e88 "[-u <user>|-A] [-S <socket_path>] <search query>"} #23 0x000055555558a165 in doveadm_cmd_run_ver2 (argc=argc@entry=7, argv=argv@entry=0x5555557df3a0, cctx=cctx@entry=0x7fffffffe320) at doveadm-cmd.c:519 ---Type <return> to continue, or q <return> to quit---quit Quit (gdb) quit Von: rudolf(a)padaru.de <rudolf(a)padaru.de> Gesendet: Donnerstag, 17. September 2020 17:28 An: 'Dovecot Mailing List' <dovecot(a)dovecot.org> Betreff: doveadm search segfault Dovecot 2.2.22 Good Evening, i have a serius problem by usung the search function via imap or via doveadm. If i run this command: doveadm search -u <user> mailbox INBOX text 'Hello' I receive this line in my maillog: dovecot: imap(<user>): Fatal: master: service(imap): child 7472 killed with signal 11 (core dumped) in my /var/log/apport.log i can see this: ERROR: apport (pid 17785) Thu Sep 17 17:19:01 2020: called for pid 17777, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 17785) Thu Sep 17 17:19:01 2020: executable: /usr/bin/doveadm (command line "doveadm search -u <user> mailbox INBOX text Hello") ERROR: apport (pid 17785) Thu Sep 17 17:19:01 2020: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 17785) Thu Sep 17 17:19:01 2020: this executable already crashed 2 times, ignoring A ‘gdb $(cat ExecutablePath) CoreDump‘ from the unpackes dumpe show this: GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/doveadm...(no debugging symbols found)...done. [New LWP 1441] Core was generated by `doveadm search -u <user> mailbox INBOX text Hello'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fb4da1f83f3 in ?? () from /usr/lib/dovecot/libdovecot.so.0 A doveconf -n show this output: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.15.0-117-generic x86_64 Ubuntu 16.04.7 LTS auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@üÜöÖäÄ auth_worker_max_count = 60 disable_plaintext_auth = no imap_capability = +XLIST imap_logout_format = in=%i out=%o del=%{deleted} fetched_mails=%{fetch_hdr_count} lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lock_method = flock login_greeting = <myServer> mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_cache_min_mail_count = 30 mail_location = auto: mail_max_userip_connections = 30 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader imapflags notify vnd.dovecot.pipe vnd.dovecot.filter vnd.dovecot.execute mbox_read_locks = dotlock mbox_very_dirty_syncs = yes mdbox_rotate_size = 250 M namespace inbox { inbox = yes location = mailbox Archiv { auto = no special_use = } mailbox Drafts { auto = no special_use = } mailbox Junk { auto = no special_use = } mailbox Sent { auto = no special_use = } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = no special_use = } prefix = } passdb { args = /etc/dovecot/conf.d/zDovecot-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_after = ~/sieve_after/.dovecot_after.sieve sieve_before = ~/sieve_before/.dovecot_before.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/local/bin/ sieve_execute_input_eol = lf sieve_extensions = +notify +imapflags +vnd.dovecot.pipe +vnd.dovecot.filter +vnd.dovecot.execute +editheader -reject sieve_filter_bin_dir = /usr/local/bin/ sieve_filter_input_eol = lf sieve_global_dir = /etc/dovecot/sieve/ sieve_max_redirects = 25 sieve_pipe_bin_dir = /usr/local/bin/ sieve_pipe_input_eol = lf sieve_plugins = sieve_extprograms sieve_redirect_envelope_from = recipient zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 sieve service auth-worker { idle_kill = 1 mins } service auth { idle_kill = 1 mins unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 4 service_count = 0 user = dovecot } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 user = dovecot } service managesieve { process_limit = 1024 user = dovecot } service pop3-login { executable = /usr/lib/dovecot/pop3-login process_min_avail = 4 service_count = 0 user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 process_limit = 1024 } shutdown_clients = no ssl_ca = </etc/apache2/zertifikate/*.<myServer>.pem ssl_cert = </etc/apache2/zertifikate/*.<myServer>.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = </etc/apache2/zertifikate/*.<myServer>.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 userdb { args = /etc/dovecot/conf.d/zDovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_plugins = " sieve zlib" rejection_reason = Your message to <%t> was automatically discarded:%n%r } protocol imap { imap_client_workarounds = delay-newmail mail_plugins = " mail_log notify zlib" ssl = yes } protocol pop3 { mail_plugins = zlib pop3_client_workarounds = oe-ns-eoh outlook-no-nuls pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv ssl = yes } What surprises me is that this problem only occurs with a text search in the inbox, I search in other mailboxes or only in the header this problem does not occur. Can anyone give me a tip on how I can solve this problem without upgrading to 2.33? Mit freundlichen Grüßen Yours sincerely <https://padaru.de/> Pascal Rudolf | Geschäftsführer PADARU-IT | Bielebohstraße 10 | 02736 Beiersdorf @: <mailto:rudolf@padaru.de> rudolf(a)padaru.de | www: <http://padaru.de/> padaru.de mobil: +49 (0) 17 772 595 32

2 1

migrations from 2.2.36
by Maciej Milaszewski 21 Sep '20

21 Sep '20

Hi I started migrations dovecot cluster from 2.2.36.4 (debian) to 2.3.8 (cetos8) .I read https://wiki2.dovecot.org/Upgrading/2.3 In 10-director.conf I must disable director_doveadm_port like: #director_doveadm_port = 2424 and add: ..... service doveadm { inet_listener { port = 2424 } } Is this correct ? the rest of the contents of the file service director { unix_listener login/director { mode = 0666 } fifo_listener login/proxy-notify { mode = 0666 } unix_listener director-userdb { mode = 0600 } inet_listener { port = 9090 } } service imap-login { executable = imap-login director } service pop3-login { executable = pop3-login director } # Enable director for LMTP proxying: protocol lmtp { auth_socket_path = director-userdb } service managesieve-login { executable = managesieve-login director } protocol doveadm { auth_socket_path=director-userdb }

1 0

auth_passdb_request_finished request fires twice on IMAP login
by Eirik Rye 21 Sep '20

21 Sep '20

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once. This is confirmed by monitoring queries made against Redis. Configuration: -------------- metric auth_passdb_request_finished { event_name = auth_passdb_request_finished } auth_debug = yes passdb { auth_verbose = yes override_fields = proxy=y name = redis driver = dict args = /etc/dovecot/dovecot-redis.conf.ext } -------------- With the above configuration, I am seeing the auth_passdb_request_finished metric being incremented twice for every successful login: -------------- / # doveadm stats dump metric_name field count sum min max avg median stddev %95 auth_passdb_request_finished duration 0 0 0 0 0.00 0 0.00 0 / # curl imap://localhost -u foo:bar -XNOOP / # doveadm stats dump metric_name field count sum min max avg median stddev %95 auth_passdb_request_finished duration 2 20327 6240 14087 10163.50 10163 3923.50 14087 -------------- This is the (anonymized) debug output emitted for the above commands: -------------- Sep 19 15:03:32 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=msC166uvOL0K9HPG lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=48440 resp=<hidden> Sep 19 15:03:32 auth: Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Performing passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: conn unix:auth-worker (pid=30,uid=90): auth-worker<3>: Handling PASSV request Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Performing passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Lookup: shared/users/foo = {"user":"foo","password":"{SHA256-CRYPT}[...]","host":"other_host","uid":1000,"home":"\/mail\/foo"} Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Finished passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: conn unix:auth-worker (pid=30,uid=90): auth-worker<3>: Finished Sep 19 15:03:32 auth: Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Finished passdb lookup Sep 19 15:03:32 auth: Debug: auth(foo,127.0.0.1,<msC166uvOL0K9HPG>): Auth request finished Sep 19 15:03:32 auth: Debug: client passdb out: OK 1 user=foo proxy host=other_host uid=1000 home=/mail/foo hostip=127.0.0.2 pass=<hidden> -------------- Best regards, Eirik

2 1

lmtp multiple mailboxes
by Janis 20 Sep '20

20 Sep '20

Hello, What would be the best way to implement "deliver mail to multiple maildirs" through LMTP in Dovecot? Like in Postfix virtual_maps. Thank you! Best wishes, Janis

2 1

auth_passdb_request_finished request fires twice on IMAP login
by Eirik Rye 19 Sep '20

19 Sep '20

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup against Redis is only performed once. This is confirmed by monitoring queries made against Redis. Configuration: -------------- metric auth_passdb_request_finished { event_name = auth_passdb_request_finished } auth_debug = yes passdb { auth_verbose = yes override_fields = proxy=y name = redis driver = dict args = /etc/dovecot/dovecot-redis.conf.ext } -------------- With the above configuration, I am seeing the auth_passdb_request_finished metric being incremented twice for every successful login: -------------- / # doveadm stats dump metric_name field count sum min max avg median stddev %95 auth_passdb_request_finished duration 0 0 0 0 0.00 0 0.00 0 / # curl imap://localhost -u foo:bar -XNOOP / # doveadm stats dump metric_name field count sum min max avg median stddev %95 auth_passdb_request_finished duration 2 20327 6240 14087 10163.50 10163 3923.50 14087 -------------- This is the (anonymized) debug output emitted for the above commands: -------------- Sep 19 15:03:32 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=msC166uvOL0K9HPG lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=48440 resp=<hidden> Sep 19 15:03:32 auth: Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Performing passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: conn unix:auth-worker (pid=30,uid=90): auth-worker<3>: Handling PASSV request Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Performing passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Lookup: shared/users/foo = {"user":"foo","password":"{SHA256-CRYPT}[...]","host":"other_host","uid":1000,"home":"\/mail\/foo"} Sep 19 15:03:32 auth-worker(76): Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Finished passdb lookup Sep 19 15:03:32 auth-worker(76): Debug: conn unix:auth-worker (pid=30,uid=90): auth-worker<3>: Finished Sep 19 15:03:32 auth: Debug: redis(foo,127.0.0.1,<msC166uvOL0K9HPG>): Finished passdb lookup Sep 19 15:03:32 auth: Debug: auth(foo,127.0.0.1,<msC166uvOL0K9HPG>): Auth request finished Sep 19 15:03:32 auth: Debug: client passdb out: OK 1 user=foo proxy host=other_host uid=1000 home=/mail/foo hostip=127.0.0.2 pass=<hidden> -------------- Best regards, Eirik -- Eirik

1 0