- dovecot - dovecot.org

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

Dovecot core-2.3.11.3 compile error on macOS with src/lib/ioloop-notify-kqueue.c
by Steven Smith 19 Sep '20

19 Sep '20

I’ve hit this compile error on macOS 10.15 with the file src/lib/ioloop-notify-kqueue.c: > error: implicit declaration of function 'i_gettimeofday' is invalid in C99 The fix is to #include "time-util.h" > --- ./src/lib/ioloop-notify-kqueue.c 2020-09-18 19:56:38.000000000 -0400 > +++ ./src/lib/ioloop-notify-kqueue.c 2020-09-18 20:54:36.000000000 -0400 > @@ -11,6 +11,7 @@ > > #include "ioloop-private.h" > #include "llist.h" > +#include "time-util.h" > #include <unistd.h> > #include <fcntl.h> > #include <sys/types.h>

1 0

How to use dovecot only as POP3 server / prevent it from creating .imap directories?
by Binarus 18 Sep '20

18 Sep '20

Dear all, on our mail server, I let sendmail deliver incoming messages to a file in mbox format called "inbox" in each user's home directory. Now I would like to use dovecot as POP3 server so that users can let their MUA download their messages via POP3. I do not want to use any IMAP functionality. The POP3 part works with the configuration shown below, but nevertheless there is a problem which is a show stopper: Although I think I have turned off IMAP (e.g. no IMAP listener), dovecot still creates .imap directories and does so in a very weird way. It creates one .imap subdirectory in every subdirectory of each user's home directory, and for every file in each user's home directory creates an additional subdirectory with the same name in its .imap directories. It does this recursively, and 1000 files in a user's home directory would mean 1000 additional subdirectories. Of course, I can't live with that. I know that the dovecot documentation discourages using the home directory as mail location, but in my case this should not be a problem at all if IMAP is not used. I have played around with dovecot for several days, but could not solve that problem. So how can I turn off IMAP completely and prevent dovecot from creating any .imap directories or IMAP related files? This happens with dovecot 2.3.4.1 (f79e8e7e4) on Debian buster (with all updates applied). My configuration (doveconf -n) is (the configuration is complete - I don't use SQL or LDAP): # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: host.example.com listen = aaa.bbb.ccc.ddd mail_location = mbox:~:INBOX=~/inbox mail_privileged_group = mail 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 { driver = pam } pop3_lock_session = yes protocols = " pop3" service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 0 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/dovecot/tls/xxxx.crt ssl_cipher_list = DHE-RSA-AES256-GCM-SHA384 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = passwd } Thank you very much in advance for any idea! Regards, Binarus

4 8

pam dovecot not working with authentication from roundcube
by Ranbir 18 Sep '20

18 Sep '20

Hi Everyone, I made some small changes in my dovecot setup to switch it from looking up users and passwords from a mix of ldap (i.e. freeipa) and password files. One of the changes was to switch from using one id for all authentication to using individual ids) It's working fine with Evolution. I have one account authenticating with GSSAPI, which is my userid for logging into my desktop and for email. The other account in Evolution is logging in using PLAIN and is only used for email (it's shell is set to /sbin/nologin). The problem is with roundcube: I can login with the second, email only account, but my personal ID always errors out. I never use the domain with either one. auth worker: PASSV: pam_sss(dovecot:auth): authentication failure; logname= uid=97 euid=97 tty=dovecot ruser=ranbir rhost=1.2.3.4 user=ranbir auth worker: PASSV: pam_sss(dovecot:auth): received for user ranbir: 17 (Failure setting user credentials) It doesn't matter what user or group I use for unix_listener. If I use 0777 for the mode, I still see the failure and dovecot goes to try the name against the passwd-file, where it obviously fails. This is the pam error: auth-worker(4474): pam(ranbir,1.2.3.4,<oS10hHmv7qkKyAkP>): pam_authenticate() failed: Authentication failure (password mismatch?) What have I misconfigured? Here's the "service auth" section: service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 inet_listener { address = 9.8.7.5 haproxy = no port = 17900 reuse_port = no ssl = no } privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener auth-client { group = mode = 0600 user = $default_internal_user } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = mode = 0600 user = } unix_listener auth-userdb { group = mode = 0777 user = $default_internal_user } unix_listener login/login { group = mode = 0666 user = } unix_listener token-login/tokenlogin { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } Any guidance is appreciated. -- Ranbir

1 2

doveadm search segfault Dovecot 2.2.22
by rudolf＠padaru.de 17 Sep '20

17 Sep '20

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-G CM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AE S128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA25 6: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-AES1 28-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:AES12 8-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!DES-CBC3-SHA:!aNU LL:!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

1 0

another problem with 2.3.36.4 after update os
by Maciej Milaszewski 17 Sep '20

17 Sep '20

Hi A few days ago I upgraded debian8 to debian9 dovecot is from source # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.2 (aaba65b7) # OS: Linux 4.9.0-13-amd64 x86_64 Debian 9.13 Today I get some times in logs: "dovecot-uidlist line 112: Invalid data" and I dont know why This is claster dovecot: dovecot1 - debian8 dovecot2 - debian8 dovecot3 - debian8 dovecot4 - debian9 dovecot5 - debian8 director - debian8 storage is mont via nfs I upgrade os debian8->debian9 to one node like documentations

1 1

Cannot load key: Invalid dovecot key version
by Mrinal Sharma 16 Sep '20

16 Sep '20

I am trying to use a newly added Local Validation functionality in dovecot version 2.3.11. I am running dovecot inside a Docker container With base image " debian:buster-slim". When I try to login through below command , a crash is seen. Algorithm Used is RS256 and certificate is self-signed. ''' a1 login admin eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJhZG1pbiIsIm5hbWUiOiJKb2huIERvZSIsImV4cCI6MTcwMDIyNDg3MiwiaWF0IjoxNTE2MjM5MDIyfQ.gCXOiUDKV5Bjxp_Vkd-I76A86qxxsCCm5YTtvoLhS5CwOV5rBQozcvnkAOkaIEWWMQqFqEIdA6V9RBztl0XlMe5tyil-2NFaXiKsbv6aYmNnBgX678MZlXRi8UFrIK1ymc4ya7Xi11hV5tuTQHAqi6MPEOdB9zTrFBa9CPCKU25G458cd8SMy7t6i_pb-CrBKCA0KKLFF-SJyz4gSu4ce9FFBTx8oYS1lDaQvf6drNw-_N6FfA1k4HVgEK9bU-SEZkeqE0t5nsFA-7V1-BgYvNaR5-tpzOjymeJP7dZ7rJzUqchVz-Z9V3hONGJEuromcEzgve_r9NSBlUTZlcT8Eg '''' dovecot_1 | Sep 16 03:29:36 auth-worker(25): Info: pam(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): pam_authenticate() failed: Authenticat ion failure (Password mismatch?) dovecot_1 | Sep 16 03:29:36 auth-worker(25): Debug: pam(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Finished passdb lookup dovecot_1 | Sep 16 03:29:36 auth-worker(25): Debug: conn unix:auth-worker (pid=24,uid=101): auth-worker<1>: Finished dovecot_1 | Sep 16 03:29:36 auth: Debug: pam(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Finished passdb lookup dovecot_1 | Sep 16 03:29:36 auth: Debug: oauth2(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Performing passdb lookup dovecot_1 | Sep 16 03:29:36 auth: Debug: oauth2(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Attempting to locally validate token dovecot_1 | Sep 16 03:29:36 auth: Debug: oauth2(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): callback(result: password_mismatch, error: Ca nnot load key: Invalid dovecot key version) dovecot_1 | Sep 16 03:29:36 auth: Info: oauth2(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): oauth2 failed: Cannot load key: Invalid doveco t key version dovecot_1 | Sep 16 03:29:36 auth: Debug: oauth2(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Finished passdb lookup dovecot_1 | Sep 16 03:29:36 auth: Debug: auth(admin,172.18.0.1,<Q5Bc4GWv9tqsEgAB>): Auth request finished dovecot --version 2.3.11.3 (502c39af9) dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 4.19.76-linuxkit x86_64 Debian 10.5 fuse.grpcfuse # Hostname: 45e39b46f6ab 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 { 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 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 postmaster_address = postmaster@domainname } protocol lda { mail_plugins = " quota notify push_notification" } protocol imap { imap_metadata = yes mail_plugins = " quota imap_quota quota" } Any help would be appreciated. Thanks, Mrinal

2 2

dovecot 2.2.36.4 problem with ulimit
by Maciej Milaszewski 16 Sep '20

16 Sep '20

Hi I update os from debian8 to debian9 # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.2 (aaba65b7) # OS: Linux 4.9.0-13-amd64 x86_64 Debian 9.13 All works fine but sometimes I get: Sep 16 09:17:00 dovecot4 dovecot: master: Error: service(pop3): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:00 dovecot4 dovecot: master: Error: service(imap): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:00 dovecot4 dovecot: master: Error: service(doveadm): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:02 dovecot4 dovecot: master: Error: service(doveadm): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:02 dovecot4 dovecot: master: Error: service(pop3): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:02 dovecot4 dovecot: master: Error: service(imap): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Sep 16 09:17:04 dovecot4 dovecot: master: Error: service(imap): fork() failed: Resource temporarily unavailable (ulimit -u 257577 reached?) Other dovecot is debian8 and problem not exists - any idea ?

2 3

Imaptest using the 'DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA'
by Marc Roos 16 Sep '20

16 Sep '20

I just noticed that the imaptest program is using this default first message 'DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA' of the mbox file to test with. I think this should be execluded, as one does not expect this behaviour.

1 0

correct usage for Pigeonhole sieve message *redirect* to external server?
by PGNet Dev 16 Sep '20

16 Sep '20

i've installed rpm -qa | grep dovecot dovecot-2.3.10.1-1.fc32.x86_64 dovecot-pigeonhole-2.3.10.1-1.fc32.x86_64 i'm setting up imapsieve spam reporting; following, https://doc.dovecot.org/configuration_manual/spam_reporting/ https://wiki.dovecot.org/HowTo/AntispamWithSieve https://wiki.dovecot.org/Pigeonhole/Sieve/Examples my config currrently includes protocol imap { mail_plugins = $mail_plugins acl imap_acl quota imap_quota imap_sieve mail_log notify mail_max_userip_connections = 20 imap_client_workarounds = tb-extra-mailbox-sep } protocol sieve { mail_plugins = $mail_plugins mail_max_userip_connections = 10 } plugin { # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/scripts/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/scripts/report-ham.sieve sieve_plugins = sieve_imapsieve sieve_pipe_bin_dir = /etc/dovecot/scripts } service submission-login { inet_listener submission { address = 10.0.1.70, 127.0.0.1 port = 60465 ssl = yes } } examples @ wiki include report-spam.sieve require "vnd.dovecot.report"; report "abuse" "User added this message to the Spam folder." "spam-report(a)example.com"; instead of a 'report', i want to *redirect* the _unmodified_ Spam message to an _external_ email that's a feed for a bayes spam learner. to that end i modified /etc/dovecot/scripts/report-spam.sieve require ["vnd.dovecot.report", "vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables"]; if environment "imap.mailbox" "Trash" { stop; } if environment "imap.mailbox" "Spam" { stop; } redirect "spam.learn(a)othermx.example.net"; with that^, when I drag a spam message into my user account's Spam folder, I see in logs only 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: Mailbox Junk: Mailbox opened because: UID move 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: acl vfile: file /home/vmail/conf.d/example.com/acls/Junk not found 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: acl vfile: file /data/vmail/example.com/myuser/Maildir/Junk/dovecot-acl not found 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: imapsieve: mailbox Junk: MOVE event 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: sieve: Pigeonhole version 0.5.10 (bf8ef1c2) initializing 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.5.10 (bf8ef1c2) loaded 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(COPY) => before=`file:/etc/dovecot/scripts/report-spam.sieve' after=(none) 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(COPY) => before=`file:/etc/dovecot/scripts/report-ham.sieve' after=(none) ==> /var/log/dovecot/dovecot-info.log <== 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Info: copy from INBOX: box=Junk, uid=4, msgid=<0e9fc21a-c046-46bd-a4ae-e7a1b6424ca7.maildroid@localhost>, size=5647 2020-09-15 08:52:16 imap(myuser(a)example.com)<bCdiIOuhPImsDgsd>: Info: expunge: box=INBOX, uid=50, msgid=<0e9fc21a-c046-46bd-a4ae-e7a1b6424ca7.maildroid@localhost>, size=5647 but no redirect occurs; nothing's sent. what additional/different config is required to get the sieve processor to *send* that email? in sieve redirect, _is_ the dovecot submission port implicitly used for sending/redirect? or does the report-spam script need additional capability to exec the send?

1 1

Auth Panic hmac.c while Local Validation
by Mrinal Sharma 16 Sep '20

16 Sep '20

I am trying to use a newly added Local Validation functionality in dovecot version 2.3.11. I am running dovecot inside a Docker container With base image " debian:buster-slim". When I try to login through below command , a crash is seen. ''' a1 login admin eyJhbGci44444zUxMiIsInR5cCI6IkpXVCJ9.eyJ1c2fyX25hbWUiOiJhZG1pbiIsInNjb3BlIjpbIm9wZW5pZCJdLCJleffiOjE3MDAxODAwNTksInN1YiI6ImFkbWluIiwiaWF0IjoxNjAwMTc5NzU5LCJhdXRob3JpdGllcyI6WyJST0xFX0FETUlOIiwiUk9MRV9VU0VSIl0sImp0aSI6ImRyOUV0MVVJWkdJZkZ0emFVZW5VRzRzcmQtQSIsImNsaWVudF9pZCI6IndlYl9hcHAifQ.T9BTZYW52p0VG9gxmTb-cf5GXF5jTOjdkqMaUMAGX-tffffft7YfdPptphGKE8FO9opxcnL--Bjy9ip-XYuWqA '''' Crash: dovecot_1 | Sep 15 16:11:50 auth: Panic: file hmac.c: line 26 (hmac_init): assertion failed: (meth->context_size <= HMAC_MAX_CONTEXT_SIZE) dovecot_1 | Sep 15 16:11:50 auth: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7ff77b36beed] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff77b36c00e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf465b) [0x7ff77b37565b] -> /usr/lib/dovecot/libdovecot.so.0(+0xf46f1) [0x7ff77b3756f1] -> /usr/lib/dovecot/libdovecot.so.0(+0x514a6) [0x7ff77b2d24a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x52415) [0x7ff77b2d3415] -> /usr/lib/dovecot/libdovecot.so.0(+0x59c09) [0x7ff77b2dac09] -> /usr/lib/dovecot/libdovecot.so.0(oauth2_try_parse_jwt+0x7bb) [0x7ff77b2db60b] -> dovecot/auth(+0x3bf71) [0x55576d3cdf71] -> dovecot/auth(db_oauth2_lookup+0x350) [0x55576d3cf030] -> dovecot/auth(auth_request_default_verify_plain_continue+0x2d6) [0x55576d3b3386] -> dovecot/auth(auth_request_verify_plain_callback_finish+0x5c) [0x55576d3b214c] -> dovecot/auth(auth_request_verify_plain_callback+0x51) [0x55576d3b2281] -> dovecot/auth(+0x30171) [0x55576d3c2171] -> dovecot/auth(+0x27ebb) [0x55576d3b9ebb] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7ff77b38b989] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7ff77b38ced1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ff77b38ba2c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ff77b38bba0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff77b3059c3] -> dovecot/auth(main+0x3e1) [0x55576d3a6fa1] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ff77b03809b] -> dovecot/auth(_start+0x2a) [0x55576d3a713a] dovecot_1 | Sep 15 16:11:50 auth-worker(25): Debug: conn unix:auth-worker (pid=24,uid=101): Disconnected: Connection closed (fd=-1) dovecot_1 | Sep 15 16:11:50 imap-login: Debug: Ignoring unknown passdb extra field: temp dovecot --version 2.3.11.3 (502c39af9) dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 4.19.76-linuxkit x86_64 Debian 10.5 fuse.grpcfuse # Hostname: 45e39b46f6ab 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 { 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 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 postmaster_address = postmaster@domainname } protocol lda { mail_plugins = " quota notify push_notification" } protocol imap { imap_metadata = yes mail_plugins = " quota imap_quota quota" } Any help would be appreciated. Thanks, Mrinal

2 2

Shared mailboxes setups and dictionaries
by Matej Tyc 16 Sep '20

16 Sep '20

Hello, I am relatively new to the world of MTAs and MDAs, and I try to set up shared mailboxes. So far I have somehow succeeded - I have defined a shared namespace and I have managed to create per-mailbox ACL files thanks to the doveadm command. However, I have been following these resources and there were bits that have puzzled me: When learning about how ACL work in e.g. https://doc.dovecot.org/settings/plugin/acl/ - when one wishes to use the Global ACL file, how does one link it to a particular user's mailboxes? Examples that are listed in the documentation are far too generic. For example does "* user=foo lrw" imply that all mailboxes of all accounts are shared to the user foo? The doveadm command works only if dovecot is set up with per-mailbox ACL files, so I can't use it to reverse-engineer the correct syntax. An interesting aspect to ACLs are dictionaries. I understood it as some kind of cache - if there is no dictionary or it is empty, then shared mailboxes don't work. Conversely, dictionary itself is not enough, one needs actual ACLs set up correctly. Is this a correct understanding? Next what https://wiki.dovecot.org/SharedMailboxes/Shared and https://wiki.dovecot.org/Dictionary describe is a possibility to reference LDAP data to define an ACL dictionary. Do I understand it correctly that if a LDAP database is the single source of truth, then I don't have to worry about updating dictionaries as long as LDAP itself is up-to-date, but I have to keep ACLs and LDAP in sync manually (or using an application)? Thanks, Matej

2 3

Btrfs RAID-10 performance
by Miloslav Hůla 15 Sep '20

15 Sep '20

Hello, I sent this into the Linux Kernel Btrfs mailing list and I got reply: "RAID-1 would be preferable" (https://lore.kernel.org/linux-btrfs/7b364356-7041-7d18-bd77-f60e0e2e2112@le…) May I ask you for the comments as from people around the Dovecot? We are using btrfs RAID-10 (/data, 4.7TB) on a physical Supermicro server with Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz and 125GB of RAM. We run 'btrfs scrub start -B -d /data' every Sunday as a cron task. It takes about 50 minutes to finish. # uname -a Linux imap 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1 (2020-01-20) x86_64 GNU/Linux RAID is a composition of 16 harddrives. Harddrives are connected via AVAGO MegaRAID SAS 9361-8i as a RAID-0 devices. All harddrives are SAS 2.5" 15k drives. Server serves as a IMAP with Dovecot 2.2.27-3+deb9u6, 4104 accounts, Mailbox format, LMTP delivery. We run 'rsync' to remote NAS daily. It takes about 6.5 hours to finish, 12'265'387 files last night. Last half year, we encoutered into performace troubles. Server load grows up to 30 in rush hours, due to IO waits. We tried to attach next harddrives (the 838G ones in a list below) and increase a free space by rebalace. I think, it helped a little bit, not not so rapidly. Is this a reasonable setup and use case for btrfs RAID-10? If so, are there some recommendations to achieve better performance? Thank you. With kind regards Milo # megaclisas-status -- Controller information -- -- ID | H/W Model | RAM | Temp | BBU | Firmware c0 | AVAGO MegaRAID SAS 9361-8i | 1024MB | 72C | Good | FW: 24.16.0-0082 -- Array information -- -- ID | Type | Size | Strpsz | Flags | DskCache | Status | OS Path | CacheCade |InProgress c0u0 | RAID-0 | 838G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdq | None |None c0u1 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sda | None |None c0u2 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdb | None |None c0u3 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdc | None |None c0u4 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdd | None |None c0u5 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sde | None |None c0u6 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdf | None |None c0u7 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdg | None |None c0u8 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdh | None |None c0u9 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdi | None |None c0u10 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdj | None |None c0u11 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdk | None |None c0u12 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdl | None |None c0u13 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdm | None |None c0u14 | RAID-0 | 558G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdn | None |None c0u15 | RAID-0 | 838G | 256 KB | RA,WB | Enabled | Optimal | /dev/sdr | None |None -- Disk information -- -- ID | Type | Drive Model | Size | Status | Speed | Temp | Slot ID | LSI ID c0u0p0 | HDD | SEAGATE ST900MP0006 N003WAG0Q3S3 | 837.8 Gb | Online, Spun Up | 12.0Gb/s | 53C | [8:14] | 32 c0u1p0 | HDD | HGST HUC156060CSS200 A3800XV250TJ | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 38C | [8:0] | 12 c0u2p0 | HDD | HGST HUC156060CSS200 A3800XV3XT4J | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 43C | [8:1] | 11 c0u3p0 | HDD | HGST HUC156060CSS200 ADB05ZG4XLZU | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 46C | [8:2] | 25 c0u4p0 | HDD | HGST HUC156060CSS200 A3800XV3DWRL | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 48C | [8:3] | 14 c0u5p0 | HDD | HGST HUC156060CSS200 A3800XV3XZTL | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 52C | [8:4] | 18 c0u6p0 | HDD | HGST HUC156060CSS200 A3800XV3VSKJ | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 55C | [8:5] | 15 c0u7p0 | HDD | SEAGATE ST600MP0006 N003WAF1LWKE | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 56C | [8:6] | 28 c0u8p0 | HDD | HGST HUC156060CSS200 A3800XV3XTDJ | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 55C | [8:7] | 20 c0u9p0 | HDD | HGST HUC156060CSS200 A3800XV3T8XL | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 57C | [8:8] | 19 c0u10p0 | HDD | HGST HUC156060CSS200 A7030XHL0ZYP | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 61C | [8:9] | 23 c0u11p0 | HDD | HGST HUC156060CSS200 ADB05ZG4VR3P | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 60C | [8:10] | 24 c0u12p0 | HDD | SEAGATE ST600MP0006 N003WAF195KA | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 60C | [8:11] | 29 c0u13p0 | HDD | SEAGATE ST600MP0006 N003WAF1LTZW | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 56C | [8:12] | 26 c0u14p0 | HDD | SEAGATE ST600MP0006 N003WAF1LWH6 | 558.4 Gb | Online, Spun Up | 12.0Gb/s | 55C | [8:13] | 27 c0u15p0 | HDD | SEAGATE ST900MP0006 N003WAG0Q414 | 837.8 Gb | Online, Spun Up | 12.0Gb/s | 47C | [8:15] | 33 # btrfs --version btrfs-progs v4.7.3 # btrfs fi show Label: 'DATA' uuid: 5b285a46-e55d-4191-924f-0884fa06edd8 Total devices 16 FS bytes used 3.49TiB devid 1 size 558.41GiB used 448.66GiB path /dev/sda devid 2 size 558.41GiB used 448.66GiB path /dev/sdb devid 4 size 558.41GiB used 448.66GiB path /dev/sdd devid 5 size 558.41GiB used 448.66GiB path /dev/sde devid 7 size 558.41GiB used 448.66GiB path /dev/sdg devid 8 size 558.41GiB used 448.66GiB path /dev/sdh devid 9 size 558.41GiB used 448.66GiB path /dev/sdf devid 10 size 558.41GiB used 448.66GiB path /dev/sdi devid 11 size 558.41GiB used 448.66GiB path /dev/sdj devid 13 size 558.41GiB used 448.66GiB path /dev/sdk devid 14 size 558.41GiB used 448.66GiB path /dev/sdc devid 15 size 558.41GiB used 448.66GiB path /dev/sdl devid 16 size 558.41GiB used 448.66GiB path /dev/sdm devid 17 size 558.41GiB used 448.66GiB path /dev/sdn devid 18 size 837.84GiB used 448.66GiB path /dev/sdr devid 19 size 837.84GiB used 448.66GiB path /dev/sdq # btrfs fi df /data/ Data, RAID10: total=3.48TiB, used=3.47TiB System, RAID10: total=256.00MiB, used=320.00KiB Metadata, RAID10: total=21.00GiB, used=18.17GiB GlobalReserve, single: total=512.00MiB, used=0.00B I do not attach whole dmesg log. It is almost empty, without errors. Only lines about BTRFS are about relocations, like: BTRFS info (device sda): relocating block group 29435663220736 flags 65 BTRFS info (device sda): found 54460 extents BTRFS info (device sda): found 54459 extents

6 18

[BUG] GSSAPI auth doesn't work on 2.3.11
by Carlos Mogas da Silva 15 Sep '20

15 Sep '20

Hi list! I have a CentOS 7 server running dovecot with GSSAPI auth enabled. Version 2.3.10 was working fine but after the upgrade to 2.3.11 it stopped working. On thing I see on the logs is that the user field comes up empty when compared to the 2.3.10. Example: 2.3.10: Sep 14 13:39:20 mail.r3pek.org dovecot[10189]: imap-login: Login: user=<r3pek(a)r3pek.org>, method=GSSAPI, rip=xxxx, lip=2a01:4f8:1c17:61c0::1, mpid=10195, TLS, session=<PaDSUkWvAOkgAQgY3LZuALKwbzMw3BW/> 2.3.11: Sep 14 12:19:24 mail.r3pek.org dovecot[9264]: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<>, method=GSSAPI, rip=2001:818:dcb6:6e00:b2b0:6f33:30dc:15bf, lip=2a01:4f8:1c17:61c0::1, TLS, session=<pRubNESvMuQgAQgY3LZuALKwbzMw3BW/> Reverting back to 2.3.10 confirmed it's a 2.3.11 thing. Is there any change necessary after the upgrade to 2.3.11 or is this really a bug?

2 2

Is it possible to only replicate indexes and not the mail data
by Marc Roos 14 Sep '20

14 Sep '20

Is it possible to only replicate indexes and not the mail data? (Because the data is already on distributed storage)

2 2

logging LMTP activity
by Janis 11 Sep '20

11 Sep '20

Hello, I've been trying to set up Postfix + Dovecot LMTP setup. Basic idea taken from https://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP, but since Postfix is on different host inet listener is used instead of unix socket. Message delivery works. Messages are delivered to correct mailboxes, if they exist. But the problem is with logging on Dovecot side; i can not get any lmtp logs at all. I kind of expected that i could get logs about: 1) Postfix has connected and delivering mail to mail(a)address.com, 2) If mailbox does not exists, would expect to see in logs the reason for rejection - mailbox does not exist 3) any other useful info would be nice as well. How do you get LMTP to log something? My Dovecot version is 2.3.11.3. Basic IMAP logging is working. I see when users have connected, etc. I tried as suggested at https://doc.dovecot.org/configuration_manual/protocols/lmtp_server/#logging If the given logging example block is used in configuration, i get no logs in file /var/log/dovecot-lmtp.log. I thought maybe file is not created automatically, so i tried to create it myself as well. Does not work. chmod 0777 does not either, chown to dovecot:dovecot neither. In a way i am curious about "executable = lmtp -L" part. What is -L flag? Are there any more flags? Where could i learn about them? I have read all the docs that come with the buld and mention something of lmtp, it's basically wiki, i guess... but i could not find any helpful info. I found that file lmtp is at /usr/local/libexec/dovecot/lmtp. When i execute it with -L flag it works. Other flags don't. The problem is that there are no -h or --help flags. Then i tried raw logging as described here: https://doc.dovecot.org/admin_manual/debugging/debugging_rawlog/#debugging-… As i understand, only 4th possibility is applicable to LMTP, am i right? 2nd kind of seems maybe somehow could be usable, but i don't see how... It is not clearly stated in wiki where "lmtp_rawlog_dir" should be added, but i add it within "protocol lmtp { .. }" block, similar as imap. Does not work for me - no logs while messages arrive. The catchy part in wiki is that for imap special arguments are used "-R rawlog" in service imap-login, postlogin. But i don't see any lmtp-login or such service available. So should it work only with "lmtp_rawlog_dir" option? What could i be doing wrong? Does anyone have working lmtp configuration with logging available? Thank you very much! I am sorry that my message is so long, but i tried even more to get it working... :) Any help or idea of how to better debug the situation or search for solution is kindly appreciated.

2 2

Re: Doveadm error since 2.3.11.3 when run as unprivileged user
by Olav Seyfarth 11 Sep '20

11 Sep '20

On Thu, Aug 13, 2020, Arjen de Korte wrote: > include optional config file and suppress errors if it doesn't exist I followed this workaround, which is nicely summarized at https://github.com/postfixadmin/postfixadmin/issues/381#issuecomment-678269… Yet, not all errors are suppressed this way: $ doveadm pw doveadm(olav): Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied $ ls -l /run/dovecot/stats-writer srw-rw---- 1 root dovecot 0 11. Sep 00:27 stats-writer Olav

2 2

Re: Btrfs RAID-10 performance
by Robert Nowotny 11 Sep '20

11 Sep '20

"Miloslav" == Miloslav Hůla <miloslav.hula(a)gmail.com> <miloslav.hula(a)gmail.com> writes: Miloslav> Dne 09.09.2020 v 17:52 John Stoffel napsal(a): Miloslav> There is a one PCIe RAID controller in a chasis. AVAGO Miloslav> MegaRAID SAS 9361-8i. And 16x SAS 15k drives conneced to Miloslav> it. Because the controller does not support pass-through for Miloslav> the drives, we use 16x RAID-0 on controller. So, we get Miloslav> /dev/sda ... /dev/sdp (roughly) in OS. And over that we have Miloslav> single btrfs RAID-10, composed of 16 devices, mounted as Miloslav> /data. I will bet that this is one of your bottlenecks as well. Get a secord or third controller and split your disks across them evenly. Miloslav> That's plan for a next step. Miloslav> We run 'rsync' to remote NAS daily. It takes about 6.5 hours to finish, Miloslav> 12'265'387 files last night. That's.... sucky. So basically you're hitting the drives hard with random IOPs and you're probably running out of performance. How much space are you using on the filesystem? Miloslav> It's not so sucky how it seems. rsync runs during the Miloslav> night. And even reading is high, server load stays low. We Miloslav> have problems with writes. Ok. So putting in an SSD pair to cache things should help. And why not use brtfs send to ship off snapshots instead of using rsync? I'm sure that would be an improvement... Miloslav> We run backup to external NAS (NetApp) for a disaster Miloslav> recovery scenario. Moreover NAS is spreaded across multiple Miloslav> locations. Then we create NAS snapshot, tens days Miloslav> backward. All snapshots easily available via NFS mount. And Miloslav> NAS capacity is cheaper. So why not run the backend storage on the Netapp, and just keep the indexes and such local to the system? I've run Netapps for many years and they work really well. And then you'd get automatic backups using schedule snapshots. Keep the index files local on disk/SSDs and put the maildirs out to NFSv3 volume(s) on the Netapp(s). Should do wonders. And you'll stop needing to do rsync at night. Miloslav> It's the option we have in minds. As you wrote, NetApp is very solid. Miloslav> The main reason for local storage is, that IMAP server is completely Miloslav> isolated from network. But maybe one day will use it. It's not completely isolated, it can rsync data to another host that has access to the Netapp. **grin** Miloslav> Unfortunately, to quickly fix the problem and make server Miloslav> usable again, we already added SSD and moved indexes on Miloslav> it. So we have no measurements in old state. That's ok, if it's better, then its better. How is the load now? Looking at the output of 'iostat -x 30' might be a good thing. Miloslav> Situation is better, but I guess, problem still exists. I Miloslav> takes some time to load be growing. We will see. Hmm... how did you setup the new indexes volume? Did you just use btrfs again? Did you mirror your SSDs as well? Do the indexes fill the SSD, or is there 20-30% free space? When an SSD gets fragmented, it's performance can drop quite a bit. Did you put the SSDs onto a seperate controller? Probably not. So now you've just increased the load on the single controller, when you really should be spreading it out more to improve things. Another possible hack would be to move some stuff to a RAM disk, assuming your server is on a UPS/Generator incase of power loss. But that's an unsafe hack. Also, do you have quotas turned on? That's a performance hit for sure. Miloslav> Thank you for the fio tip. Definetly I'll try that. It's a good way to test and measure how the system will react. Unfortunately, you will need to do your testing outside of normal work hours so as to not impact your users too much. Good luck! Please post some numbers if you get them. If you see only a few disks are 75% or more busy, then **maybe** you have a bad disk in the system, and moving off that disk or replacing it might help. Again, hard to know. Rebalancing btrfs might also help, especially now that you've moved the indexes off that volume. Robert: Fio is an acronym for *Flexible IO Tester* and describes a tool for measuring IO performance. With Fio, devices such as hard drives or SSDs can be tested for their speed by executing a *user-defined **workload* and collecting performance data. Therefore it might be difficult to really simulate the load with that, because You need to define the workload Yourself. But, at least, You might use it to get an idea of maximum transfer rates, random I/O etc. *iotop* shows the *current I/O transfer **rates* for the currently running processes / threads. It uses the I/O usage information of the Linux kernel, so it might be a good tool for You. *htop *might also be Your friend. and of course, as someone else pointed out : > Looking at the output of 'iostat -x 30' might be a good thing. my default setup for such diagnosis is to run iotop, htop, ntop to get an idea whats going on and measure ... for the index-SSD (on a different Channel ? NvMe ?) I strongly suggest to compare EXT4 vs BTRFS - some Benchmarks suggest that on fast SSD´s EXT4 is much (factor 4-5) faster then btrfs. You might also try ZSTD transparent compression on the remaining (non-SSD) btrfs disks - this can boost the transfer rate (since the data is compressed) if the Server CPU´s have enough juice. But from my guts feeling, its not the transfer rate - its the random I/O (in that case the situation will get worse with compression), but You really need to measure that. In general I dont understand that (old fashioned) configuration - using a bunch of 2TB or even 4TB TLC SSD in Raid10 is nowadays really affordable. You can keep the old disks for (local) rsync before You rsync from there to the NAS ... Robert

1 0

Bug in sieve script compilation
by Иннокентий Сенновский 10 Sep '20

10 Sep '20

Hi, this is Rumata888 from hackerone. This is the other bug I found in sievec. If you try to compile the following script, it will result in a panic. The reason is: export expects its arguments to be either strings or lists of strings. When we issue an export command with a number immediately followed by an export command with a string argument, on parsing the second command sievec tries to merge the commands by merging the arguments. When it encounters an argument of unexpected type, it panics. Once again, I would advise unlinking invalid commands from ast, so that parsing of following commands was not dependent on previous irregularities.

1 0

dbox alternate storage and archived namespace
by Daniel Miller 10 Sep '20

10 Sep '20

This may (and probably does) come under the heading of "really dumb ideas", but... Before I develop this further I need to ask - is it possible to have a "primary" mail_location using single-dbox with an alternate storage using multi-dbox? This is *not* the same as different storages for different namespaces (already have that). -- Daniel

1 0

Re: zlib errors after upgrading to 2.3.11.3
by Robert Nowotny 09 Sep '20

09 Sep '20

On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966(a)gmail.com> wrote: Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. What kind of errors? Probably this? : Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion failed: (!stream->blocking) can be - unfortunately I do not have the log files anymore... 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) thank You so much ! Robert

2 1

Leaked Events
by bobby 08 Sep '20

08 Sep '20

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?

2 1

zlib errors after upgrading to 2.3.11.3
by Robert Nowotny 08 Sep '20

08 Sep '20

Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails). After restoring the backup (what was made after switching to version 2.3.11.3) I still have some broken mdfiles, but not too many. Interestingly always in the "Sent" Mailbox on a number of Users. I just can not go back to 20.08.2020 before I updated to 2.3.11.3 - too many emails would have been lost. So - the current status is 2.3.11.3, with "gz" compression. I force-synced and re-indexed all the mdbox files (250 GB), but still have some broken - please how can I fix those ? You stated : (In theory you could leave the existing mails xz-compressed, but best would be to re-compress everything via dsync so old mails can be read when we eventually remove xz support.) what is the optimal way to do that, expecially not loosing the index (?) for outlook/thunderbird, for third party tools that rely on some index/hash (dunno how exactly that works) ? 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<48089><YRio1GKuEdHAqKi3>: 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<49228><p/0g9WKuVdHAqKi3>: 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<49229><GMAm9WKuVtHAqKi3>: 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[]) Sep 3 08:35:27 lxc-imap dovecot: imap(mpaul)<49230><YYot9WKuV9HAqKi3>: 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[]) ... Sep 3 09:04:44 lxc-imap dovecot: imap(cpotzinger)<49040></X+P72KuUNHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:04:51 lxc-imap dovecot: imap(cpotzinger)<54382><eYT1XWOux9HAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:04:59 lxc-imap dovecot: imap(cpotzinger)<54396><nKllXmOuyNHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:05:06 lxc-imap dovecot: imap(cpotzinger)<54409><m2TOXmOuydHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:05:12 lxc-imap dovecot: imap(cpotzinger)<54422><IP86X2OuytHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) ... Sep 3 09:08:58 lxc-imap dovecot: imap(cpotzinger)<54867><BtGtbGOu49HAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:19:15 lxc-imap dovecot: imap(mpaul)<56030></kHNkWOuAO3AqKjk>: 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[]) Sep 3 09:29:41 lxc-imap dovecot: imap(cpotzinger)<57274><c4rCtWOuKuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:29:47 lxc-imap dovecot: imap(cpotzinger)<57320><K3Uqt2OuLOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:29:54 lxc-imap dovecot: imap(cpotzinger)<57333><e4aMt2OuLezAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:01 lxc-imap dovecot: imap(cpotzinger)<57346><JEfzt2OuLuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:08 lxc-imap dovecot: imap(cpotzinger)<57360><mH1YuGOuMOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:14 lxc-imap dovecot: imap(cpotzinger)<57382><IzLBuGOuMezAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:21 lxc-imap dovecot: imap(cpotzinger)<57397><q10kuWOuM+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:27 lxc-imap dovecot: imap(cpotzinger)<57410><CSuJuWOuNOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:31:22 lxc-imap dovecot: imap(mpaul)<57525><TfoOvWOuWO3AqKjk>: 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[]) Sep 3 09:31:49 lxc-imap dovecot: imap(cpotzinger)<57423><Be/ruWOuNuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:31:55 lxc-imap dovecot: imap(cpotzinger)<57584><yvXOvmOuQuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:02 lxc-imap dovecot: imap(cpotzinger)<57597><e/8tv2OuQ+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:08 lxc-imap dovecot: imap(cpotzinger)<57611><BLSOv2OuROzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:19 lxc-imap dovecot: imap(cpotzinger)<57633><Ky0twGOuR+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:26 lxc-imap dovecot: imap(cpotzinger)<57646><ljSRwGOuS+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:33 lxc-imap dovecot: imap(cpotzinger)<57659><rn75wGOuT+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:39 lxc-imap dovecot: imap(cpotzinger)<57672><GP9jwWOuUuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:33:45 lxc-imap dovecot: imap(mpaul)<57795><2CEwxWOubu3AqKjk>: 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[]) Sep 3 09:38:29 lxc-imap dovecot: imap(mpaul)<58347><CKyX1mOuie3AqKjk>: 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[]) Sep 3 09:38:32 lxc-imap dovecot: imap(mpaul)<58352><osHU1mOuiu3AqKjk>: 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[]) Sep 3 09:38:44 lxc-imap dovecot: imap(cpotzinger)<54527><5ZpiYmOuBOfAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:38:51 lxc-imap dovecot: imap(cpotzinger)<58378><kAuN12OumuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:38:57 lxc-imap dovecot: imap(cpotzinger)<58392><xJLx12Oum+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) ... Am 26.08.2020 um 09:42 schrieb Robert Nowotny: I had 4 broken mdbox files for 4 different users. After deleting them, dovecot re-indexed, now everything is ok again. I can try to update tonight again to 2.3.11.3 and see if some broken files will appear again tomorrow. Am 25.08.2020 um 14:51 schrieb Aki Tuomi: On 25/08/2020 14:35 Robert Nowotny <rnowotny(a)rotek.at> <rnowotny(a)rotek.at> wrote: I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]).... many of those entries.... after installing2.3.10.1 those files are still broken - but new files are working again. anything I can tweak or do ? Hi! Is it possible your mdbox file is corrupted? Can you share doveconf -n? Aki

2 3

Re: Re: Outlook problems on Apple systems(Mac os)
by hfh＠cndns.com 08 Sep '20

08 Sep '20

Outlook version is 16.40 hfh(a)cndns.com From: Jerry Date: 2020-09-08 13:22 To: Dovecot Mailing List Subject: Re: Outlook problems on Apple systems(Mac os) On Tue, 8 Sep 2020 09:57:59 +0800, hfh(a)cndns.com <hfh(a)cndns.com> stated: >Dovecot is on version 2.2.36. I tested it. Outlook on the Apple system >successfully logged in with the imap protocol, and then sent the LIST >command and outlook did not send any further. Dovecot returns the >results as follows: > >A003 OK LIST completed (0.001 + 0.000 secs). > > >There is no problem with version 2.1.17 using dovecot before. The >information returned by dovecot in version 2.1.17 is as follows: > >A003 OK LIST completed. > > >I suspect that the feedback of the following information causes >Outlook to not recognize it normally: > >(0.001 + 0.000 secs) What version of Outlook? -- Jerry

2 1

Outlook problems on Apple systems(Mac os)
by hfh＠cndns.com 08 Sep '20

08 Sep '20

Dovecot is on version 2.2.36. I tested it. Outlook on the Apple system successfully logged in with the imap protocol, and then sent the LIST command and outlook did not send any further. Dovecot returns the results as follows: A003 OK LIST completed (0.001 + 0.000 secs). There is no problem with version 2.1.17 using dovecot before. The information returned by dovecot in version 2.1.17 is as follows: A003 OK LIST completed. I suspect that the feedback of the following information causes Outlook to not recognize it normally: (0.001 + 0.000 secs) hfh(a)cndns.com

2 1

Search in Mailbox via doveadm REST-API
by rudolf＠padaru.de 07 Sep '20

07 Sep '20

Hey, i need some help with the http-api from doveadm, i try to search a string in the mail-text from all mails in my inbox. My curl-post looks like these: curl -v -X POST -u <user>:<password> -H "Content-Type: application/json" -d '[["search",{"query":["mailbox","INBOX","TEXT","8887"],"user":"<mailUser>"}, "tag1"]]' http://<server>:8080/doveadm/v1 | python -mjson.tool > out.json I receive only empty results, do have anyone an idea? Mit freundlichen Grüßen Yours sincerely <https://padaru.de/> Pascal Rudolf | Geschäftsführer PADARU-IT | Bielebohstraße 10 | 02736 Beiersdorf @: rudolf(a)padaru.de | www: <http://padaru.de/> padaru.de mobil: +49 (0) 17 772 595 32

1 0

LMTP-Process stays in RCPT TO state
by Pascal Christen 07 Sep '20

07 Sep '20

Hi We tried to update our Dovecot Director-Ring to 2.3 (latest version) and had one problem/bug. When we try to deliver an email from Exim to a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process stays open forever and never closes. So after a few hours, we hit the LMPT-Process limit. The problem only exists if the receiving Dovecot reports "Quota exceeded (mailbox for user is full)" back to the Exim. If this is the case the state on the LMPT process stays at "lmtp: [_IP_ RCPT TO] (lmtp) and never closes. The TCP-Connection to the Exim is then in CLOSE_WAIT state on the Proxy. On the receiving Dovecot we set the "lmtp_rcpt_check_quota=yes" option. For me, it sounds similar to this bug: https://dovecot.org/list/dovecot/2018-January/110697.html but without the SEGFAULT which makes it harder to debug it. May you guys know why it doesn't change the state to IDLE or READY after reporting the quota issue or see something fishy in the commit above. If not I try to get a trace of the hanging process. Greetings Pascal

2 6

Backup questions - errors
by Mark Patruck 07 Sep '20

07 Sep '20

Hi, although i've search the archives, there are questions left regarding backup strategies and errors that occur. I'm using dovecot 2.3.11.3 with mdbox (mailbox size 50MB - 30GB). Every night, i ran the following command: doveadm -o mail_fsync=never -o plugin/quota= -o plugin/zlib_save=gz \ backup -u account mdbox:/nfs/storage/account/mdbox ### incremental backup Thanks to zlib compression, i save a lot of storage space, nonetheless i'd go with an incremental backup, but it seems to only merge changes, comparing to rsyncs' --link-dest option where you can put all "changes of the day" in an extra folder. I'd like to prevent loosing mail that gets deleted by accident/on purpose. How can i achieve this with dsync and w/o doing a full backup every day? ### backup errors After a few days w/o any errors, doveadm prints the following lines (only for the biggest, 30GB mailbox) two days in a row. As dovecot has self- healing capabilities, i think these errors/warnings can be ignored and should go away...? Error: Transaction log ....mdbox/dovecot.list.index.log: duplicate transaction log sequence (38) Error: Index ....mdbox/dovecot.list.index: Lost log for seq=38 offset=63312: Missing middle file seq=38 (between 38..4294967295, we have seqs 37,39): .log.2 contains file_seq=37 (initial_mapped=1, reason=Index mapped) Warning: fscking index file ....mdbox/dovecot.list.index Error: Fixed index file ....mdbox/dovecot.list.index: log_file_seq 38 -> 39 Error: Mailbox list index was marked as fsck'd ....mdbox/dovecot.list.index Error: Mailbox list index was marked as fsck'd ....mdbox/dovecot.list.index Error: Mailbox list index was marked as fsck'd ....mdbox/dovecot.list.index Thanks, -Mark -- Mark Patruck ( mark at wrapped.cx ) GPG key 0xF2865E51 / 187F F6D3 EE04 1DCE 1C74 F644 0D3C F66F F286 5E51 https://www.wrapped.cx

1 1

sieve_max_script_size is ignored
by Zdeněk Zámečník 06 Sep '20

06 Sep '20

I am in troubles with compiling sieve scripts larger than 1MB. I see in logs following errors: Aug 19 13:10:26 mail dovecot: lmtp(z.z(a)xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: line 16818: quoted string started at line 3 is too long (longer than 1048576 bytes) Aug 19 13:10:26 mail dovecot: lmtp(z.z(a)xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: autoreply: parse failed Aug 19 13:10:26 mail dovecot: lmtp(z.z(a)xxx.xxx)<22117><uNBGHKIIPV9lVgAA5ldI4A>: Error: sieve: Failed to compile script `/var/vmail/xxx.xxx/z.z/sieve/autoreply.sieve' I tried to set sieve_max_script_size = 2M or 0 (unlimited). I also tried to run "sievec -o sieve_max_script_size=2M /var/vmail/xxx.xxx/z.z/sieve/autoreply.sieve" but the result is still same. Below is my config. Can you please advice where can be the problem? # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 5.4.44-2-pve x86_64 Debian 10.4 # Hostname: mail.xxx.xxx auth_cache_size = 2 M auth_cache_ttl = 5 mins auth_master_user_separator = * auth_mechanisms = plain login auth_policy_check_before_auth = no auth_policy_hash_nonce = # hidden, use -P to show it auth_policy_report_after_auth = no auth_policy_server_timeout_msecs = 1500 auth_policy_server_url = http://127.0.0.1:8090/ dict { acl = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no imap_client_workarounds = delay-newmail imap_id_log = * imap_id_retain = yes login_trusted_networks = 127.0.0.0/8 mail_gid = 2000 mail_home = /var/vmail/%d/%n mail_location = mdbox:~/mdbox:ALT=/var/vmail-archive/%d/%n/mdbox mail_max_userip_connections = 60 mail_plugins = acl zlib fts quota mail_uid = 2000 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 vacation-seconds editheader imapsieve vnd.dovecot.imapsieve mdbox_rotate_interval = 1 days mdbox_rotate_size = 16 M namespace { inbox = yes location = mailbox "Deleted Items" { auto = no special_use = \Trash } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = no special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } prefix = separator = / type = private } namespace { inbox = no list = children location = mdbox:/var/vmail/%%d/%%n/mdbox:ALT=/var/vmail-archive/%%d/%%n/mdbox prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/dovecot/masters.db driver = passwd-file master = yes pass = yes } plugin { acl = vfile acl_shared_dict = proxy::acl imapsieve_mailbox1_before = file:/var/vmail/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/var/vmail/sieve/report-spam.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = Junk imapsieve_mailbox4_before = file:/var/vmail/sieve/report-ham.sieve imapsieve_mailbox4_causes = COPY imapsieve_mailbox4_from = Junk imapsieve_mailbox4_name = * mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_new3 = Deleted Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent mailbox_alias_old3 = Trash quota = dict:User quota::proxy::quota quota_grace = 10%% quota_rule2 = Trash:ignore quota_rule3 = Junk:ignore quota_warning = storage=80%% quota-warning 90 %u quota_warning2 = storage=85%% quota-warning 95 %u quota_warning3 = storage=95%% quota-warning 105 %u sieve = /var/vmail/%d/%n/sieve/.sieve sieve_after = /var/vmail/%d/%n/sieve/autoreply.sieve sieve_before = /var/vmail/sieve/global.sieve sieve_dir = /var/vmail/%d/%n/sieve sieve_extensions = +editheader +vacation-seconds sieve_global_dir = /var/vmail/sieve/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_redirects = 20 sieve_max_script_size = 2M sieve_pipe_bin_dir = /usr/lib/dovecot sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_send_from_recipient = yes } protocols = imap sieve lmtp pop3 service auth-worker { unix_listener auth-worker { user = vmail } user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = vmail } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { process_min_avail = 10 service_count = 0 vsz_limit = 512 M } service imap { executable = imap process_limit = 3500 unix_listener imap-master { user = $default_internal_user } vsz_limit = 2 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 400 } service pop3-login { process_min_avail = 3 service_count = 0 vsz_limit = 320 M } service pop3 { process_limit = 200 vsz_limit = 320 M } service quota-warning { executable = script /etc/dovecot/quota_warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = vmail } ssl_cert = </etc/ssl/private/multi.z-technics.cz.dovecot.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it stats_writer_socket_path = userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole managesieve_max_compile_errors = 5 } protocol imap { mail_plugins = quota imap_quota fts mailbox_alias imap_acl acl imap_zlib imap_sieve } protocol lda { mail_fsync = optimized } protocol lmtp { mail_fsync = optimized mail_plugins = quota sieve acl }

2 4

imapc master user & shared mailboxes
by Toma 04 Sep '20

04 Sep '20

Hello, I am trying to configure dovecot like this: https://wiki.dovecot.org/SharedMailboxes/ClusterSetup imapc_host = 127.0.0.1 imapc_master_user = %u #imapc_user = imapc_password = XXXXXXXX namespace { type = shared separator = / prefix = shared/%%u/ location = imapc:~/shared/%%u } plugin { acl_shared_dict = proxy::acl } However, contrary to the article claims, imapc master user is set to the destination username. This makes it impossible to check the ACLs against the logged user. If user.b shares mailbox with user.a, accessing /shared/user.b as user.a a will log in as "user.b*user.b". Can we tell dovecot to use the currently authenticated user for imapc_master_user and the remote user for imapc_user, so it logs in as "user.b*user.a"? I'm using dovecot 2.3.11.3 (502c39af9). Thanks! Toma

1 0

syslog logging + 2.3.10 + centos 7
by Matt Bryant 04 Sep '20

04 Sep '20

All, Running dovecot 2.3.10 on a CentOS 7.x and logging via syslog seems to stop when i restart rsyslog process. Reload doesnt get it working again only a dovecot restart. Tested this with dovecot 2.2.36 and this did not exhibit the same behaviour. systemctl restart dovecot rsyslog ----- this gets a working state systemctl restart rsyslog ------------- this restarts syslog other processes like exim continue to log but dovecot stops systemctl reload dovecot -------------- this has no impact logging still does not work systemctl restart dovecot ------------- this fixes the issue. Are there any changes to the log process between 2.2 and 2.3 that might explain this ? rgds Matt

1 1

How to backup maildir
by Robert Moskowitz 04 Sep '20

04 Sep '20

I have been thinking, and reading, on how to back up my mailserver. I have not found any approach that seems ready to use. I have run years without any backup, but would really like to have something in place. I figure I can attach a USB drive and backup to that, then from there rsync to something elsewhere. Further if that USB drive is a full mailserver image, I actually have a 'hot backup' where I only have to put the backup drive into a system and boot up at the last backup. But this means properly copying all of /home/vmail and probably /home/sieve plus the /var/lib/mysql Are there good tools that nicely does this? Or do I choose a time late at night (only I am sometimes in non-US timezones) to shut down all services and just use rsync? And stopping services itself is thought provoking. What if Dovecot, amavis, mysql, or whatelse is in the middle of writing out a mail file what happens to that file and restart. Just scary stuff and, in part, why I have never tackled this in the past. thanks for all feedback

4 6

Deleted mail reappearing
by John S 04 Sep '20

04 Sep '20

Recently I upgraded dovecot quite a few major versions. Since then some mailboxes are experiencing deleted mail reappearing. It seems to be happening roughly once a day, but not for every mail client or mailbox, I have at least two clients with this issue: Thunderbird and Outlook. Storage is local under two partitions, one as alternative storage. # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-29-generic x86_64 Ubuntu 20.04 LTS ext4 auth_mechanisms = plain login digest-md5 base_dir = /var/run/dovecot/ default_client_limit = 4000 default_vsz_limit = 512 M dict { expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lda_mailbox_autocreate = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = mdbox:/home/vmail/%d/%n mail_max_userip_connections = 240 mail_plugins = quota mail_privileged_group = mail mdbox_rotate_size = 64 M namespace { inbox = yes location = prefix = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { quota = dict:user_quota::proxy:/var/run/dovecot/dict:quota quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ } protocols = imap pop3 service anvil { client_limit = 2615 } service auth { client_limit = 5536 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = root mode = 0600 user = vmail } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { client_limit = 2115 executable = /usr/lib/dovecot/imap-login inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 2000 } service imap { executable = /usr/lib/dovecot/imap process_limit = 2000 } service pop3-login { client_limit = 1024 executable = /usr/lib/dovecot/pop3-login inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_limit = 512 } service pop3 { executable = /usr/lib/dovecot/pop3 } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = < /etc/dovecot/ssl/crt.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes syslog_facility = local0 userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { imap_max_line_length = 64 k mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota sieve postmaster_address = postmaster@localhost sendmail_path = /usr/lib/sendmail } dovecot-sql.conf: driver = mysql connect = host=127.0.0.1 dbname=mail user=mail password=#### password_query = SELECT IF('%m' = 'DIGEST-MD5', users.password_digest_md5, NULL) as password, IF('%m' = 'DIGEST-MD5', NULL, 'Y') as nopassword, username FROM users LEFT JOIN domains ON users.domain = domains.domain WHERE users.username = '%u' AND users.domain = '%d' AND users.active = 'yes' AND domains.state = '1' AND ((users.password = encrypt('%w', LEFT(users.password, 11)) AND ('%m' = 'PLAIN' OR '%m' = 'LOGIN')) OR ('%m' = 'DIGEST-MD5')) user_query = SELECT maildir as home, uid, gid, CONCAT(CONCAT(type, ':', maildir), ':ALT=/home/altmail/%d/%n') AS mail FROM users LEFT JOIN domains ON users.domain = domains.domain WHERE users.username = '%u' AND domains.state = '1' iterate_query = SELECT SUBSTRING_INDEX(email, '@', 1) AS username, domain FROM users;

3 3

Sieve: deleteheader now working with duplicate filter for implicit keep
by Alec Moskvin 04 Sep '20

04 Sep '20

Hello, I have a rule to always delete a header. If the message gets fileinto'd, the header is gone, but if it's delivered into the INBOX through implicit keep, the header does not get deleted. Interestingly, if I remove the "if duplicate" filter, the header does get deleted as expected. I'm using the latest Dovecot 2.3.11.3 / Pigeonhole 0.5.11. Any idea why this is happening? Thanks, Alec === Sieve filter require ["fileinto", "editheader", "duplicate", "mailbox"]; deleteheader "X-Bad-Header"; if duplicate { fileinto :create "Trash"; stop; } if header :matches "subject" "*filter*" { fileinto :create "Filtered"; } === Example (note ${RANDOM} to bypass duplicate filter) $ /usr/libexec/dovecot/deliver << -end- To: me(a)example.com From: someone(a)example.com Subject: Test Message Message-Id: <${RANDOM}(a)example.net> Date: Thu, 20 Aug 2020 00:21:24 +0000 (UTC) X-Bad-Header: DELETE ME Hello world -end-

2 4

ltmp delivery with ldap and prefetch
by Marc Roos 04 Sep '20

04 Sep '20

I am able to authorize and connect via imap. But I am not able to deliver a message via lmtp I am getting this error message. passdb didn't return userdb entries, trying the next userdb [1] dovecot-ldap.conf.ext pass_attrs = uid=user,userPassword=password,host=host,homeDirectory=userdb_home,uidNu mber=userdb_uid,gidNumber=userdb_gid user_attrs = uid=%{ldap:uidNumber},gid=%{ldap:gidNumber},home=%{ldap:homeDirectory} [2] pass / user db's passdb { args = /etc/dovecot/dovecot-ldap.conf.ext auth_verbose = default default_fields = deny = no driver = ldap master = no mechanisms = name = override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never username_filter = } userdb { args = /etc/dovecot/special-userdb auth_verbose = default default_fields = driver = passwd-file name = override_fields = result_failure = continue result_internalfail = continue result_success = return-ok skip = never } userdb { args = auth_verbose = default default_fields = driver = prefetch name = override_fields = result_failure = continue result_internalfail = continue result_success = return-ok skip = never }

1 0

Moving Spam to Junk Folder
by bobby 03 Sep '20

03 Sep '20

I am following this tutorial: https://www.linuxbabe.com/redhat/spamassassin-centos-rhel-block-email-spam. I followed the steps in "Move Spam into the Junk Folder". When I send an email from a blacklisted e-mail address, I get a bounce e-mail from my e-mail server. Here is what is in my spamass-milter file: EXTRA_FLAGS="-m -r 8 -R NO_SPAM -i 127.0.0.1 -g sa-milt -- --max-size=5120000" I would prefer it to go into my Junk folder. How can I make this happen?

3 3

Fwd: zlib errors after upgrading to 2.3.11.3
by Robert Nowotny 03 Sep '20

03 Sep '20

Dear Aki, I switched to "gz" now, since "zstd" also gave some errors on writing to files. I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails). After restoring the backup (what was made after switching to version 2.3.11.3) I still have some broken mdfiles, but not too many. Interestingly always in the "Sent" Mailbox on a number of Users. I just can not go back to 20.08.2020 before I updated to 2.3.11.3 - too many emails would have been lost. So - the current status is 2.3.11.3, with "gz" compression. I force-synced and re-indexed all the mdbox files (250 GB), but still have some broken - please how can I fix those ? You stated : (In theory you could leave the existing mails xz-compressed, but best would be to re-compress everything via dsync so old mails can be read when we eventually remove xz support.) what is the optimal way to do that, expecially not loosing the index (?) for outlook/thunderbird, for third party tools that rely on some index/hash (dunno how exactly that works) ? 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<48089><YRio1GKuEdHAqKi3>: 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<49228><p/0g9WKuVdHAqKi3>: 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[]) Sep 3 08:35:26 lxc-imap dovecot: imap(mpaul)<49229><GMAm9WKuVtHAqKi3>: 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[]) Sep 3 08:35:27 lxc-imap dovecot: imap(mpaul)<49230><YYot9WKuV9HAqKi3>: 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[]) ... Sep 3 09:04:44 lxc-imap dovecot: imap(cpotzinger)<49040></X+P72KuUNHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:04:51 lxc-imap dovecot: imap(cpotzinger)<54382><eYT1XWOux9HAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:04:59 lxc-imap dovecot: imap(cpotzinger)<54396><nKllXmOuyNHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:05:06 lxc-imap dovecot: imap(cpotzinger)<54409><m2TOXmOuydHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:05:12 lxc-imap dovecot: imap(cpotzinger)<54422><IP86X2OuytHAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) ... Sep 3 09:08:58 lxc-imap dovecot: imap(cpotzinger)<54867><BtGtbGOu49HAqKi3>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:19:15 lxc-imap dovecot: imap(mpaul)<56030></kHNkWOuAO3AqKjk>: 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[]) Sep 3 09:29:41 lxc-imap dovecot: imap(cpotzinger)<57274><c4rCtWOuKuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:29:47 lxc-imap dovecot: imap(cpotzinger)<57320><K3Uqt2OuLOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:29:54 lxc-imap dovecot: imap(cpotzinger)<57333><e4aMt2OuLezAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:01 lxc-imap dovecot: imap(cpotzinger)<57346><JEfzt2OuLuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:08 lxc-imap dovecot: imap(cpotzinger)<57360><mH1YuGOuMOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:14 lxc-imap dovecot: imap(cpotzinger)<57382><IzLBuGOuMezAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:21 lxc-imap dovecot: imap(cpotzinger)<57397><q10kuWOuM+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:30:27 lxc-imap dovecot: imap(cpotzinger)<57410><CSuJuWOuNOzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:31:22 lxc-imap dovecot: imap(mpaul)<57525><TfoOvWOuWO3AqKjk>: 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[]) Sep 3 09:31:49 lxc-imap dovecot: imap(cpotzinger)<57423><Be/ruWOuNuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:31:55 lxc-imap dovecot: imap(cpotzinger)<57584><yvXOvmOuQuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:02 lxc-imap dovecot: imap(cpotzinger)<57597><e/8tv2OuQ+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:08 lxc-imap dovecot: imap(cpotzinger)<57611><BLSOv2OuROzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:19 lxc-imap dovecot: imap(cpotzinger)<57633><Ky0twGOuR+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:26 lxc-imap dovecot: imap(cpotzinger)<57646><ljSRwGOuS+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:33 lxc-imap dovecot: imap(cpotzinger)<57659><rn75wGOuT+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:32:39 lxc-imap dovecot: imap(cpotzinger)<57672><GP9jwWOuUuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:33:45 lxc-imap dovecot: imap(mpaul)<57795><2CEwxWOubu3AqKjk>: 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[]) Sep 3 09:38:29 lxc-imap dovecot: imap(mpaul)<58347><CKyX1mOuie3AqKjk>: 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[]) Sep 3 09:38:32 lxc-imap dovecot: imap(mpaul)<58352><osHU1mOuiu3AqKjk>: 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[]) Sep 3 09:38:44 lxc-imap dovecot: imap(cpotzinger)<54527><5ZpiYmOuBOfAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:38:51 lxc-imap dovecot: imap(cpotzinger)<58378><kAuN12OumuzAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Sep 3 09:38:57 lxc-imap dovecot: imap(cpotzinger)<58392><xJLx12Oum+zAqKiU>: Error: Mailbox Sent: UID=29534: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) ... Am 26.08.2020 um 09:42 schrieb Robert Nowotny: > I had 4 broken mdbox files for 4 different users. > After deleting them, dovecot re-indexed, now everything is ok again. > > I can try to update tonight again to 2.3.11.3 and see if some broken > files will appear again tomorrow. > > Am 25.08.2020 um 14:51 schrieb Aki Tuomi: >>> On 25/08/2020 14:35 Robert Nowotny<rnowotny(a)rotek.at> wrote: >>> >>> >>> I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 >>> >>> >>> Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]).... >>> >>> many of those entries.... >>> >>> after installing2.3.10.1 those files are still broken - but new files are working again. >>> >>> anything I can tweak or do ? >>> >>> >> Hi! >> >> Is it possible your mdbox file is corrupted? Can you share doveconf -n? >> >> Aki >

1 0

Submission proxy warning connecting to Exim
by Alec Moskvin 03 Sep '20

03 Sep '20

Hello, When connecting to Exim 4.94, dovecot submission logs this warning: dovecot[25235]: submission(alec)<25347><QNydV8+t+oMKAgAF>: Warning: smtp-client: conn localhost:25 ([::1]:25) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword Looks like it doesn't like the underscore in "X_PIPE_CONNECT", since it's neither "isalnum" nor a dash [1]: 1598480923.401085 220 myhostname ESMTP Exim 4.94 Wed, 26 Aug 2020 18:28:43 -0400 1598480923.401906 250-myhostname Hello localhost [::1] 1598480923.401906 250-SIZE 52428800 1598480923.401906 250-8BITMIME 1598480923.401906 250-PIPELINING 1598480923.401906 250-X_PIPE_CONNECT 1598480923.401906 250-CHUNKING 1598480923.401906 250-STARTTLS 1598480923.401906 250 HELP 1598480923.409242 250 OK 1598480923.434743 250 Accepted 1598480923.578335 250- 511 byte chunk, total 511 1598480923.578335 250 OK id=1kB3uN-0006ar-HU Adding the line "pipelining_connect_advertise_hosts =" to Exim's config fixes the issue by disabling X_PIPE_CONNECT. Is this a bug in Exim or is Dovecot being too strict? Thanks, Alec [1] https://github.com/dovecot/core/blob/2.3.11.3/src/lib-smtp/smtp-syntax.c#L2…

3 2

Sumbission crashes when relaying over TLS
by Alec Moskvin 03 Sep '20

03 Sep '20

Hello, I'm trying to set up the submission proxy, but if I set submission_relay_ssl = starttls, it crashes. Without it, it works. Please find the details below. Thanks, Alec dovecot[256855]: submission-login: Login: user=<alec>, method=PLAIN, rip=::1, lip=::1, mpid=257033, secured, session=<kMd1B9uthLUAAAAAAAAAAAAAAAAAAAAB> dovecot[256855]: submission(alec)<257033><kMd1B9uthLUAAAAAAAAAAAAAAAAAAAAB>: Panic: file smtp-client-connection.c: line 290 (smtp_client_connection_fail): assertion failed: (conn->to_connect == NULL) dovecot[256855]: submission(alec)<257033><kMd1B9uthLUAAAAAAAAAAAAAAAAAAAAB>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fbbfb2bcaf2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fbbfb2bcc0e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf5f09) [0x7fbbfb2c5f09] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf5fa1) [0x7fbbfb2c5fa1] -> /usr/lib64/dovecot/libdovecot.so.0(+0x51eec) [0x7fbbfb221eec] -> /usr/lib64/dovecot/libdovecot.so.0(+0x44d5e) [0x7fbbfb214d5e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x6c431) [0x7fbbfb23c431] -> /usr/lib64/dovecot/libdovecot.so.0(smtp_client_command_input_reply+0x201) [0x7fbbfb235261] -> /usr/lib64/dovecot/libdovecot.so.0(+0x6ccfd) [0x7fbbfb23ccfd] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x68) [0x7fbbfb2dc048] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fbbfb2dd662] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x51) [0x7fbbfb2dc0f1] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fbbfb2dc2b0] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbbfb255ee3] -> dovecot/submission(main+0x4df) [0x561d486b3daf] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7fbbfb054b8a] -> dovecot/submission(_start+0x2a) [0x561d486b3e3a] dovecot[256855]: submission(alec)<257033><kMd1B9uthLUAAAAAAAAAAAAAAAAAAAAB>: Fatal: master: service(submission): child 257033 killed with signal 6 (core dumped) (gdb) bt #0 0x00007fbbfb069a31 in raise () from /lib64/libc.so.6 #1 0x00007fbbfb0532b6 in abort () from /lib64/libc.so.6 #2 0x00007fbbfb22223c in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007fbbfb2c5fa1 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:848 #5 0x00007fbbfb221eec in i_panic (format=format@entry=0x7fbbfb30fd08 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:523 #6 0x00007fbbfb214d5e in smtp_client_connection_fail (status=9002, error=<optimized out>, conn=0x561d491296a8) at smtp-client-connection.c:290 #7 smtp_client_connection_fail (conn=0x561d491296a8, status=<optimized out>, error=<optimized out>) at smtp-client-connection.c:282 #8 0x00007fbbfb23c431 in smtp_client_connection_starttls_cb (reply=0x561d4912d048, conn=0x561d491296a8) at smtp-client-connection.c:788 #9 0x00007fbbfb235261 in smtp_client_command_input_reply (cmd=<optimized out>, reply=reply@entry=0x561d4912d048) at smtp-client-command.c:971 #10 0x00007fbbfb23ccfd in smtp_client_connection_input_reply (reply=0x561d4912d048, conn=0x561d491296a8) at smtp-client-connection.c:1045 #11 smtp_client_connection_input (_conn=<optimized out>) at smtp-client-connection.c:1116 #12 0x00007fbbfb2dc048 in io_loop_call_io (io=0x561d49109cb0) at ioloop.c:713 #13 0x00007fbbfb2dd662 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x561d490fd050) at ioloop-epoll.c:222 #14 0x00007fbbfb2dc0f1 in io_loop_handler_run (ioloop=0x561d490fd050) at ioloop.c:765 #15 0x00007fbbfb2dc2b0 in io_loop_run (ioloop=0x561d490fd050) at ioloop.c:738 #16 0x00007fbbfb255ee3 in master_service_run (service=0x561d490fceb0, callback=<optimized out>) at master-service.c:851 #17 0x0000561d486b3daf in main (argc=<optimized out>, argv=<optimized out>) at main.c:396 $ openssl version OpenSSL 1.1.1g 21 Apr 2020 # doveconf -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # OS: Linux 5.8.4 x86_64 Gentoo Base System release 2.7 # Hostname: haswell listen = localhost mail_location = maildir:~/.maildir 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 = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = submission ssl_cert = </etc/ssl/dovecot/server.pem ssl_client_ca_file = </etc/dovecot/ca.crt ssl_key = # hidden, use -P to show it submission_relay_host = localhost submission_relay_port = 2525 submission_relay_rawlog_dir = %h/rawlog submission_relay_ssl = starttls userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol submission { rawlog_dir = %h/rawlog }

2 2

submission message quota
by Gerry 03 Sep '20

03 Sep '20

Hello, I am trying to come up with a way to have individual quotas per user for the submission service. Similar to what I could achieve with Postfix and policyd. More specifically, the quota I am most interested in, is limiting the number of messages a single account can send within a given timeframe. Ideally, I'd also like to limit the number of total recipients within a given timeframe, to mitigate the loophole of adding multiple recipients to a single message. Example: account Y is allowed to send 500 messages per 60 minutes, with a maximum of 2000 recipients overall. What would be the best path to take? Thanks! Gerry

4 5

Metric label values truncated when using OpenMetrics endpoint
by Daan van Gorkum 02 Sep '20

02 Sep '20

Hi, Recently we upgraded to Dovecot 2.3.11.3 and configured an example metric like this: metric imap_command { event_name = imap_command_finished group_by = cmd_name tagged_reply_state user remote_ip } And enabled the OpenMetrics listener like this: service stats { inet_listener http { port = 5000 } } While the result is great, I noticed that some metrics are being truncated (three dots at the end of the label value): dovecot_imap_command_duration_usecs_sum{cmd_name="FETCH",tagged_reply_state="OK",user="xxxxxxxxxxx.inbox@xxxxxxxxxxxxx…",remote_ip="XXXX:XXXX:XXXX:XXXX:cc6b:cc7a:d…"} 2346 1598055662473 I couldn't find this information in the documentation so I'm wondering if this is a bug. Thank you for your time. Regards, Daan

2 5

systemctl unit should depend on remote-fs
by Tom Sommer 02 Sep '20

02 Sep '20

The shipped systemctl unit file should have "remote-fs.target" added in "After="? -- Tom

1 0

Mail replication does not work
by Pavel Just 02 Sep '20

02 Sep '20

Hi, I have installed two Debian 10.5 (SSH server) systems and I would like replicate mails between them. But the replication is very unstable. Before start of dovecot Source mailbox: 278 messages, Destination mailbox: 0 messages Another mailbox: 16887 messages, D.. 0 messages After start of dovecot Source mailbox: 278 messages, Destination mailbox: 303 messages Another mailbox: 16887 messages, Dest..: 31904 messages In many cases replication hangs. Error message is in the end of the message. If replication hangs, after restart a lot of mail are copied from destination back to source and mailbox grows without new messages. Postfix was stopped during replication. Please, what is wrong in my configuration (except security :-) ? -- Pavel # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.5 # Hostname: mail.simac.cz disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 1001 last_valid_uid = 32000 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" mail_privileged_group = mail mail_temp_dir = /var/tmp 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 { 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 { driver = pam } plugin { mail_replica = tcp:192.168.240.2:12345 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap sieve pop3" service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = root } unix_listener replication-notify { mode = 0666 user = root } } service doveadm { inet_listener { port = 12345 ssl = no } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = root } } service stats { unix_listener stats-reader { mode = 0666 user = root } unix_listener stats-writer { mode = 0666 user = root } } ssl = no userdb { driver = passwd } protocol lmtp { mail_plugins = " notify replication sieve" } protocol lda { mail_plugins = " notify replication sieve" } ____________________________________ Error message ________________ Sep 2 14:08:00 backup dovecot: doveadm: Panic: file mbox-lock.c: line 796 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) Sep 2 14:08:00 backup dovecot: doveadm: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7f300ef00eed] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f300ef0100e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf465b) [0x7f300ef0a65b] -> /usr/lib/dovecot/libdovecot.so.0(+0xf46f1) [0x7f300ef0a6f1] -> /usr/lib/dovecot/libdovecot.so.0(+0x514a6) [0x7f300ee674a6] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x438e5) [0x7f300f0108e5] -> /usr/lib/dovecot/libdovecot-storage.so.0(mbox_save_begin+0x6fd) [0x7f300f05fa7d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_begin+0x92) [0x7f300f0299e2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x89) [0x7f300f01c4e9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x246f) [0x7f300e71846f] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5cb3c) [0x7f300f029b3c] -> dovecot/doveadm-server(+0x4f805) [0x556ee519a805] -> dovecot/doveadm-server(+0x501f7) [0x556ee519b1f7] -> dovecot/doveadm-server(dsync_mailbox_import_changes_finish+0x164) [0x556ee519dba4] -> dovecot/doveadm-server(dsync_brain_sync_mails+0x735) [0x556ee5198e85] -> dovecot/doveadm-server(dsync_brain_run+0x218) [0x556ee5194858] -> dovecot/doveadm-server(+0x49eae) [0x556ee5194eae] -> dovecot/doveadm-server(+0x5aa6f) [0x556ee51a5a6f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f300ef20989] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7f300ef21ed1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f300ef20a2c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f300ef20ba0] -> dovecot/doveadm-server(+0x2e20e) [0x556ee517920e] -> dovecot/doveadm-server(+0x2fa56) [0x556ee517aa56] -> dovecot/doveadm-server(+0x45cad) [0x556ee5190cad] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f300ef20989] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7f300ef21ed1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f300ef20a2c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f300ef20ba0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f300ee9a9c3] Sep 2 14:08:00 backup dovecot: doveadm: Fatal: master: service(doveadm): child 1977 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps)

2 1

Incremental purge?
by Jesus Cea 02 Sep '20

02 Sep '20

I am using mdbox storage format. As far as I know, “doveadm purge” does a complete purge. The time and disk activity would be proportional to the number mdbox files on the storage. The purge time could be huge. I wonder if there is some way of doing a kind of incremental purge, stopping/restarting purging, etc. Purging by file range would be nice too. Advice? Thanks Enviado desde mi iPhone

5 7

Dovecot Proxy
by Thoralf Rickert-Wendt 02 Sep '20

02 Sep '20

Hello everyone, it's my first post here on this mailing list and I hope, I make it right. I posted a question on https://serverfault.com/questions/1031441/dovecot-as-proxy-with-submission and nobody was able to answer it. So I decided to push that question here (I'm talking about any new dovecot version and I've tested it with 2.3.4.1 (f79e8e7e4)). I try to run a dovecot proxy in front of a big number of mail servers (serving SMTP-in, submission, IMAP, POP3, Sieve). I need that proxy, because I run out of IPv4 addresses. Of course I use IPv6 too, but many customers still have problems with there providers and they really don't want to share their mails on a "shared-mailserver". I planed to use Dovecot for IMAPS, POP3S, SMTP-submission(465) and postfix for the rest. If I find a solution for sieve, I would try that too, but that is very optional. With the documentation https://wiki1.dovecot.org/HowTo/ImapProxy (which is really old and should be updated) and some other ascii docs (from an Apple mirror somewhere deep in the web) I was able to build a IMAP/POP3 proxy that forwards requests from outside to a specific backend using SSL (993,995). That works - I think.You can find the config on the serverfault page. In general - all known domains in backend are using SSL and the passdb forwards all requests to the backend via SSL. So - I understand:|| |password_query = SELECT NULL AS password, NULL AS destuser, host, 'Y' AS nologin, 'Y' AS nodelay, 'Y' AS nopassword, 'Y' AS proxy, 'any-cert' AS `ssl` FROM proxy_domain WHERE domain = '%d' | But that is only 50% of the show. The rest ist submission (and maybe sieve). Practically the submission implementation in dovecot works too. But because dovecot by default only opens port 587 (starttls), my passdb setting has a problem. When I try to use that port Dovecot tries to use SSL on the backend/587 too - but that is wrong (it should either use 465 or should try to use starttls). So, I have the following options. - find a way to configure dovecot-proxy to listen on 465 with SSL for submission service and hope that it uses the same port - but I didn't find any documentation for that and need help - find a way to configure dovecot-proxy/passdb to return starttls=y when dovecot-submission is used (use a different passdb) - but I didn't find any documentation for that and I'm not sure, if this worls on service/protocol level - find a way to configure the passdb answer based on the used port/protocol. But I only know the parameter %u, %d and %p. - so it would be nice to find a way to also select the protocol (if already developed) - find a way to make a patch in dovecot (which isn't easy for me, because I don't really know the code) Has somebody an idea, how I can configure the dovecot-proxy in that way. bye Thoralf

3 4

about header address parsing
by TACHIBANA Masashi 02 Sep '20

02 Sep '20

Hi, Is this expected or not? From: user1(a)fuga.example.com <user1(a)example.com> To: user2(a)hoge.example.com <user2(a)example.com> ↓ a uid fetch 43055 (envelope) * 1860 FETCH (UID 43055 ENVELOPE ("Thu, 30 Jul 2020 13:52:59 +0900" "test1" ((NIL NIL "user1" "fuga.example.com")) ((NIL NIL "user1" "fuga.example.com")) ((NIL NIL "user1" "fuga.example.com")) ((NIL NIL "user2" "hoge.example.com")) NIL NIL NIL "<WLXvFmpAZFNeQbPPITjRwimDyamnBm1@test>")) From: "user1(a)fuga.example.com" <user1(a)example.com> To: "user2(a)hoge.example.com" <user2(a)example.com> ↓ a uid fetch 43056 (envelope) * 1861 FETCH (UID 43056 ENVELOPE ("Thu, 30 Jul 2020 13:53:59 +0900" "test1" (("user1(a)fuga.example.com" NIL "user1" "example.com")) (("user1(a)fuga.example.com" NIL "user1" "example.com")) (("user1(a)fuga.example.com" NIL "user1" "example.com")) (("user2(a)hoge.example.com" NIL "user2" "example.com")) NIL NIL NIL "<WLXvFmpAZFNeQbPPITjRwimDyamnBm2@test>")) Regards, -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana@qualitia.co.jp 株式会社クオリティア https://www.qualitia.co.jp/

3 3

Bug: Dovecot appending "MISSING_DOMAIN" to fetch envelope responses
by Michael Gratton 02 Sep '20

02 Sep '20

Hi all, I'm seeing Dovecot include the string "MISSING_DOMAIN" in fetch envelope requests when an mailbox's `addr-spec` part does not have a `domain` part. For example: > C: a022 uid fetch 40 (envelope rfc822.header) > S: * 5 FETCH (UID 40 ENVELOPE ("Sat, 15 Aug 2020 12:53:05 +1000" > "test {{name}}" (("Michael Gratton" NIL "mike" "vee.net")) (("Michael > Gratton" NIL "mike" "vee.net")) (("Michael Gratton" NIL "mike" > "vee.net")) (("postgres" NIL "postgres" "MISSING_DOMAIN")) NIL NIL > NIL NIL) RFC822.HEADER {literal/244b}) I understand that RFC 5322 require a mailbox to have a domain part, however it is still possible for mail to contain mailboxes that do not. In these cases, Dovecot returning random string such as the above is harmful, since it not possible for IMAP clients to determine whether host name string is actually present or something that the IMAP server has made up. As a result, an IMAP client has two options: Either display the string as-is, preventing it from providing an appropriately localised explanation or visual indication of the problem in the user interface, or simply avoid ever requesting IMAP envelopes from the server and always download and parse the complete RFC822 headers itself (as I believe Thunderbird does). The former is untenable since "MISSING_DOMAIN" does not mean anything to non-English speakers, the latter is untenable since it unnecessarily inflates the of volume of data that must be transmitted over the wire to work around a server bug. In these cases, or when any other part of a required IMAP address structure is missing, Dovecot should return the empty string, e.g. "". Cheers, //Mike Dovecot details: > *REDACTED*:~$ sudo dovecot -n > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 ext4 > # Hostname: *REDACTED* > first_valid_uid = *REDACTED* > hostname = *REDACTED* > last_valid_uid = *REDACTED* > lda_original_recipient_header = X-Original-To > lmtp_rcpt_check_quota = yes > lmtp_save_to_detail_mailbox = yes > mail_gid = *REDACTED* > mail_home = *REDACTED* > mail_location = mdbox:*REDACTED*:UTF-8 > mail_privileged_group = mail > mail_server_admin = mailto:*REDACTED* > mail_temp_dir = *REDACTED* > mail_uid = *REDACTED* > 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 { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > autoexpunge = 30 days > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox Trash { > auto = subscribe > autoexpunge = 30 days > special_use = \Trash > } > prefix = > separator = . > type = private > } > passdb { > args = *REDACTED* > driver = ldap > } > plugin { > imapsieve_mailbox1_before = file:*REDACTED* > imapsieve_mailbox1_causes = COPY > imapsieve_mailbox1_name = Junk > imapsieve_mailbox2_before = file:*REDACTED* > imapsieve_mailbox2_causes = COPY > imapsieve_mailbox2_from = Junk > imapsieve_mailbox2_name = * > recipient_delimiter = + > sieve = file://*REDACTED* > sieve_before = /etc/dovecot/sieve-before.d > sieve_global_extensions = +vnd.dovecot.pipe > +vnd.dovecot.environment +vnd.dovecot.report > sieve_pipe_bin_dir = /etc/dovecot/sieve-scripts > sieve_plugins = sieve_imapsieve sieve_extprograms > sieve_quota_max_storage = 50M > } > postmaster_address = *REDACTED* > protocols = " imap lmtp sieve" > service auth-worker { > user = mail > } > service auth { > unix_listener *REDACTED* { > group = postfix > mode = 0666 > user = postfix > } > } > service lmtp { > process_min_avail = 2 > unix_listener *REDACTED* { > group = postfix > mode = 0600 > user = postfix > } > user = mail > } > ssl = required > ssl_cert = <*REDACTED* > ssl_client_ca_dir = *REDACTED* > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > submission_host = *REDACTED*:587 > userdb { > args = uid=8 > driver = static > } > protocol lmtp { > mail_plugins = " sieve" > } > protocol imap { > mail_plugins = " imap_sieve" > } -- Michael Gratton. <https://mjog.vee.net>

2 3

using %d as a variable in the ldap search base
by Luke Schierer 01 Sep '20

01 Sep '20

Hi, I'm trying to configure dovecot to use LDAP authentication directly, and I'm having a bit of trouble. I have a somewhat unusual setup, in that I have an LDAP directory that has 3 OUs each of which have their own set of users, some of which overlap. As I was trying to figure things out, I was setting the search base in my /etc/dovecot/dovecot-ldap.conf.ext file which is referenced by /etc/dovecot/conf.d/auth-ldap.conf.ext file to base = ou=%d,dc=thecrazyguys,dc=net however, the resulting searches against the directory endup just dropping the %d, resulting in ou=,dc=thecrazyguys,dc=net which is invalid. On a whim, I tried a search base of base = dc=%d,dc=thecrazyguys,dc=net and found that it did correctly substitute in the variable, which would be correct, except that my ldap tree is set up with OUs and not an extra DC segment. for whatever reason, it will do variable substitution for dc=%d, but not for ou=%d. this is certainly not documented, and seems like wrong behavior, since having an ou in a search base is valid. I'm including configuration information below. Please let me know if I've missed including information that is required. Thanks! Luke luke@schierer@littera001:/etc/dovecot$ lsb_release -rd Description: Ubuntu 18.04.5 LTS Release: 18.04 luke@schierer@littera001:/etc/dovecot$ luke@schierer@littera001:/etc/dovecot$ dpkg -l | grep -i dovecot ii dovecot-core 1:2.2.33.2-1ubuntu4.6 amd64 ii dovecot-imapd 1:2.2.33.2-1ubuntu4.6 amd64 ii dovecot-ldap 1:2.2.33.2-1ubuntu4.6 amd64 ii dovecot-pop3d 1:2.2.33.2-1ubuntu4.6 amd64 luke@schierer@littera001:/etc/dovecot$ root@littera001:/etc/dovecot# dovecot -n # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-112-generic x86_64 Ubuntu 18.04.5 LTS auth_verbose = yes first_valid_uid = 1001 imap_hibernate_timeout = 100 secs lock_method = dotlock mail_cache_min_mail_count = 15 mail_fsync = always mail_location = maildir:~/Maildir:LAYOUT=fs:INDEX=MEMORY mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mailbox_list_index = yes maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes mbox_min_index_size = 10 B mmap_disable = yes 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 = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap pop3" ssl_cert = </etc/dovecot/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_max_userip_connections = 20 } root@littera001:/etc/dovecot# root@littera001:/etc/dovecot# cat /etc/dovecot/dovecot-ldap.conf.ext | grep -v ^# | uniq | more hosts = censor001.plerumque.thecrazyguys.net tls = yes tls_require_cert = allow debug_level = 4 auth_bind = yes base = ou=%d,dc=thecrazyguys,dc=net scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%n)) blocking = no root@littera001:/etc/dovecot#

2 4

Re: replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 01 Sep '20

01 Sep '20

So nobody has any idea why this could happen? Let me know if I should provide more Information Thanks Thomas Tsiakalakis Team Applikationsbetrieb GDV Dienstleistungs-GmbH Tel: +49(40)33449-4318 Fax: E-Mail: Thomas.Tsiakalakis(a)gdv-dl.de<mailto:Thomas.Tsiakalakis@gdv-dl.de> GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de<http://www.gdv-dl.de> Niederlassungen: Wilhelmstraße 43 / 43 G 10117 Berlin Frankenstraße 18 20097 Hamburg Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123 Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella Aufsichtsratsvorsitzender: Werner Schmidt ------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet. This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Von: Thomas Tsiakalakis Gesendet: Dienstag, 23. Juni 2020 11:25 An: dovecot(a)dovecot.org Betreff: AW: replicator: Panic: data stack: Out of memory I managed to convince the System that I really want a core dump Von: Thomas Tsiakalakis Gesendet: Donnerstag, 18. Juni 2020 16:26 An: 'dovecot(a)dovecot.org' <dovecot(a)dovecot.org> Betreff: replicator: Panic: data stack: Out of memory Hi, I have set up 2 SLES 15 Hosts with dovecot and replication. Everything seems to work fine but every time a message is delivered, I get an out of memory error in the logs. The Replication itself seems to work fine though. I increased default_vsz_limit to 512M but the only thing that changed was that dovecot was trying to allocate 1073741864 bytes instead of 268435496 As I said, I’m running SLES 15 SP1 and Dovecot 2.3.10 (0da0eff44) (both Hosts have the same version) Each Host currently has 8GB of Memory. # free -h total used free shared buff/cache available Mem: 7.8Gi 278Mi 7.3Gi 47Mi 183Mi 7.2Gi Swap: 4.0Gi 0B 4.0Gi # journalctl -f Jun 18 15:55:48 mail1 postfix/pickup[3457]: 18533C009C8: uid=0 from=<root> Jun 18 15:55:48 mail1 postfix/cleanup[3669]: 18533C009C8: message-id=<20200618135548.18533C009C8@mail1> Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: from=<root@mail1>, size=431, nrcpt=1 (queue active) Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Connect from local Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Panic: data stack: Out of memory when allocating 268435496 bytes Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8346d6d262] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8346d6d37e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebcee) [0x7f8346d77cee] -> /usr/lib64/dovecot/libdovecot.so.0(+0xebd91) [0x7f8346d77d91] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8346cd1f8b] -> /usr/lib64/dovecot/libdovecot.so.0(t_pop_last_unsafe+0) [0x7f8346d73660] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe7a50) [0x7f8346d73a50] -> /usr/lib64/dovecot/libdovecot.so.0(+0x10eb58) [0x7f8346d9ab58] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe3ac5) [0x7f8346d6fac5] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_write+0xf2) [0x7f8346d6fdb2] -> dovecot/replicator(replicator_queue_push+0xde) [0x5648989a5cde] -> dovecot/replicator(+0x5464) [0x5648989a5464] -> dovecot/replicator(+0x4a0b) [0x5648989a4a0b] -> dovecot/replicator(+0x4c02) [0x5648989a4c02] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8346d90c99] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x134) [0x7f8346d92574] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f8346d90d9c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f8346d90fc8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8346d01873] -> dovecot/replicator(main+0x1a0) [0x5648989a3cb0] -> /lib64/libc.so.6(__libc_start_main+0xea) [0x7f83468f534a] -> dovecot/replicator(_start+0x2a) [0x5648989a3d5a] Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Sync failure: Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: Warning: replication(test(a)example.com): Remote sent invalid input: - Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(test(a)example.com)<3673><q5sLCGRy615ZDgAATn/NZw>: msgid=<20200618135548.18533C009C8@mail1>: saved mail to INBOX Jun 18 15:55:48 mail1 dovecot[1833]: lmtp(3673): Disconnect from local: Client has quit the connection (state=READY) Jun 18 15:55:48 mail1 postfix/lmtp[3672]: 18533C009C8: to=<test(a)example.com>, orig_to=<test(a)domain.com>, relay=mail1[private/dovecot-lmtp], delay=0.17, delays=0.02/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 2.0.0 <test(a)example.com> q5sLCGRy615ZDgAATn/NZw Saved) Jun 18 15:55:48 mail1 postfix/qmgr[3458]: 18533C009C8: removed Jun 18 15:55:48 mail1 dovecot[1833]: replicator: Fatal: master: service(replicator): child 2948 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2)

2 3

shutdown_clients ignored on Director upgrade/restart
by Tom Sommer 01 Sep '20

01 Sep '20

When yum updates a Dovecot Director, it restarts all processes - however a few imap-login and pop3-login processes hang because they are still proxying connections. It's like the now orphaned processes are stalled, and needs a kill -9 to die. This is a problem because those stalled connections are still connected to backends, so when new connections are made from the same account, they do not end up on the same backend and thus index corruption happens (same account, two different backends). shutdown_clients is enabled but it appears Dovecot restarts regardless of verifying all processes/clients are shut down. Just had this happen upon yum update from dovecot-2.3.11.3-3 to dovecot-2.3.11.3-4 -- Tom

1 0

how fetch zlibed mails with doveadm
by rudolf＠padaru.de 31 Aug '20

31 Aug '20

Hey there, i need some help with an administrativ dovecot question. I run a dovecot 2.2.33 ubuntu server with mdbox and "zlib_save = gz zlib_save_level = 6". Now i want to fetch the mailheader from some mails via doveadm fetch -u <user> hdr uid <uid>. The only thing what i receive is some binary stuff. Is there a way, i can tell the dovemadm fetch command, that he should deflate the output for me? Yours sincerely Pascal Rudolf

2 4

zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
by Robert Nowotny 31 Aug '20

31 Aug '20

I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Thunderbird reports some error when try to save/open a bigger attachment. Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63871><9A0...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:11 lxc-imap dovecot: imap(cpotzinger)<63889><Ig6...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:17 lxc-imap dovecot: imap(cpotzinger)<64169><GXe...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug anything I can tweak or do ? Robert

3 9

PBKDF2 password hashing as in ASP.NET Core
by Yves Goergen 30 Aug '20

30 Aug '20

Hello, I'm setting up a new server and, again, seek for a decently secure (from a security specialist's POV) way to store and verify user passwords in a database. Additionally now, GDPR requires me to use a solid state-of-the-art solution. My OS is Ubuntu 20.04, Dovecot version 2.3.7, database backend with PostgreSQL 12. Obviously, storing the plaintext password is a terrible idea. SHA-based methods aren't suitable either. bcrypt has been recommended often [1]. PBKDF2 was preferred over bcrypt even more [2]. I'm managing all database contents with an ASP.NET Core application that implements the management user frontend. It's a bit hard to find bcrypt support for .NET (there are a few NuGet packages of unknown quality [3]). .NET does however implement, use and recommend PBKDF2 for its own user management. If this is by far the best way to go, I'm already covered on that side. Now the problem is, once again*, how I can use this in applications to make them as secure. I need a solution for Dovecot and Exim. Exim seems to be able to ask Dovecot (IMAP) for user authentication, so I might try that and only need to solve the problem in Dovecot alone. Dovecot documentation says that PBKDF2 is somewhat possible [4]. It requires the hash in the format "$1$salt$rounds$hash". I guess that "salt", "rounds" and "hash" are the parameters here. But what is their format? The .NET implementation [5] describes its format as "{ 0x01, prf (UInt32), iter count (UInt32), salt length (UInt32), salt, subkey }" with big-edian integers. The result is base64-encoded. Prf is an enum value, describing the HMAC SHA-256. Subkey is the hash value part. I might find a way to convert .NET's format into what Dovecot understands. The hmac is SHA-256, the rounds is 10000. But I wasn't able to get it working. My test password is: simplepassword The .NET hash: AQAAAAEAACcQAAAAEG0Anzb9vKOqsAKxLyhXedCTJoHrP381hKiKBHuPHhMdkjqW8Bks8RFOQZLssJ2grQ== The converted hash for Dovecot: $1$bQCfNv28o6qwArEvKFd50A==$10000$kyaB6z9/NYSoigR7jx4THZI6lvAZLPERTkGS7LCdoK0= I've also found the source code in Dovecot that should verify the hash [6]. It gives some more hints about the expected format that are sadly missing from the documentation, making it almost useless. I also tried with the "{PBKDF2}" prefix, with the base64 padding "=" removed and with the hash part converted from base64 to hex. Nothing works. The source mentions "SHA1" somewhere. Is that all it can accept? No up-to-date SHA-256? So what have I done wrong here? Why can't I authenticate? The Dovecot log isn't helpful, it doesn't even mention the user name I tried to log in with from Thunderbird, most of the time (it's unpredictable). What is the correct usage of Dovecot's PBKDF2 feature? Is it functional at all? There's a test case for it [7] but that's not helpful to me. If Dovecot's PBKDF2 support is not functional or not compatible with ASP.NET Core's parameters, what options do I have? Can I build my own authentication service that Dovecot can communicate with, to fill the gap of missing crypto support? Yves *) During my research today, I find myself finding my own questions from 6 years ago when I did this the last time. The situation hasn't changed much since then. Secure password hashing is still impossible or complicated in server applications like Exim or Dovecot. [1] https://codahale.com/how-to-safely-store-a-password/ (linked from the Dovecot documentation) [2] https://www.reddit.com/r/node/comments/4u1jcn/is_bcrypt_the_best_possible_p… [3] https://nugetmusthaves.com/Tag/bcrypt [4] https://doc.dovecot.org/configuration_manual/authentication/password_scheme… [5] https://github.com/dotnet/AspNetCore/blob/master/src/Identity/Extensions.Co… [6] https://github.com/dovecot/core/blob/81b5b188c478ec36bea8bda8fcad1e5f32ac61… [7] https://github.com/dovecot/core/blob/ff5305136ae747867b6f6af9a1737188ae7b3b…

2 4

moving /var/vmail/vmail1 Maildir tree to another partition?
by Voytek Eymont 30 Aug '20

30 Aug '20

I have a small Postfix/Dovecot/MariaDB on Centos 7 with a dozen virtual domains, I'm running out of space in /var but got space can I simply move the entire /var/vmail/vmail1 tree elsewhere ? like say /vmail/vmail1 is it as simple as shutting Dovecot/Postfix, move tree, edit conf and re start ? or am I missing something ..? or is the a better way of doing this ? # grep 'var/vmail' *.conf dovecot.conf: sieve_global_dir = /var/vmail/sieve dovecot.conf: sieve_global_path = /var/vmail/sieve/dovecot.sieve dovecot.conf:# location = maildir:/var/vmail/public/:CONTROL=~/Maildir/public:INDEX=~/Maildir/public # cd ../postfix # grep 'var/vmail' *.cf main.cf:virtual_mailbox_base = /var/vmail # dovecot --version 2.3.11.3 (502c39af9)

2 1

Rsync the dovecot repo
by Marc Roos 30 Aug '20

30 Aug '20

Is it possible to rsync some repo that has centos7 2.3.11? http://repo.dovecot.org/ce-2.3-latest/centos/7/RPMS/x86_64/2.3.11.3-3_ce/

2 1

Imaptest stalls when removing msgs argument
by Marc Roos 30 Aug '20

30 Aug '20

I have had this imaptest[1] stall. I compared this command with what you have on the website and I was a bit surprised that what is on the website is working. What I have noticed is that if you remove this msgs argument, the imaptest stalls. I am not sure if this is according to design, but one might expect that specifying a secs, makes specifying msgs redundant? [1] imaptest - append=100,0 logout=0 host=xx.local port=143 user=xxx pass=xxx seed=100 secs=240 clients=1 mbox=64kb.mbox box=inbox/test. [2] https://doc.dovecot.org/admin_manual/sample_tests/ Using: dovecot-imaptest-2.3.10-2.x86_64

1 0

lazy_expunge and fts_autoindex
by Gregory Heytings 29 Aug '20

29 Aug '20

Hi list, I have both lazy_expunge and fts_autoindex activated (with fts-xapian), as follows: plugin { lazy_expunge = EXPUNGED/ } plugin { fts = xapian fts_xapian = partial=2 full=20 attachments=1 verbose=0 fts_autoindex = yes fts_enforced = yes fts_autoindex_exclude = EXPUNGED fts_autoindex_exclude2 = EXPUNGED/* } However, I still see "indexer-worker...: Info: Indexed 1 messages in EXPUNGED/..." in the dovecot log each time I expunge an email. I tried various other settings for "fts_autoindex_exclude" (EXPUNGED alone, EXPUNGED + EXPUNGED/ + EXPUNGED/*, ...), but none of them seem to work. Thanks for your help, Gregory

2 2

Expuning & Purging doesn't fully remove emails?
by Zelic Bojan 27 Aug '20

27 Aug '20

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated. I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error: Corrupted dbox file /var/mail/virtual/mailbox(a)domain.com/mdbox/storage/m.3228 (around offset=1988744): msg header has bad magic value which caused the index to get rebuilt... however several times now, the indexes got rebuilt even though there doesnt seem like there was any error... so im not sure why that is. lmtp(13910): Warning: fscking index file /var/mail/virtual/mailbox(a)domain/mdbox/storage/dovecot.map.index lmtp(13910): Warning: fscking index file /var/mail/virtual/mailbox(a)domain/mdbox/storage/dovecot.map.index lmtp(13910): Warning: mdbox /var/mail/virtual/mailbox@domain/mdbox/storage: rebuilding indexes I'm not sure why these mails keep coming back though... or if there's anything that I can do to limit the number of emails that get restored. I want to make sure expunged & purged emails stay expunged & purged. If I run a purge and then force index recreation... why would expunged emails come back? Shouldn't I expect them all to be deleted & purged? Does expunge not expunge all emails? (In production, I'm running autoexpunge but this test below shows what happens when I attempt to expunge everything) doveadm search -u email@domain all | wc -l # output 22096 doveadm expunge -u email@domain mailbox '*' all doveadm search -u email@domain all | wc -l # output: 0 doveadm purge -u email@domain doveadm dump /var/mail/virtual/email@domain/mdbox/storage/ | grep -c 'ref.*\b0\b' # output: 0 doveadm force-resync -u email@domain Inbox # output: # doveadm(email@domain): Warning: fscking index file /var/mail/virtual/email(a)domain/mdbox/storage/dovecot.map.index # doveadm(email@domain): Warning: mdbox /var/mail/virtual/email@domain/mdbox/storage: rebuilding indexes # doveadm(email@domain): Warning: fscking index file /var/mail/virtual/email(a)domain/mdbox/storage/dovecot.map.index doveadm search -u email@domain all | wc -l # output: 843 I would expect the output to be 0. Theoretically I deleted all emails and purged all emails. Nothing should be left on the disk? However... I can see there are still m.* files in mdbox/storage for the mailbox. Overall, I'm not sure why the index got recreated... but I'm trying to limit the impact of mailbox corruption so that deleted emails do not come back if the index is somehow recreated again. If I were to re-run expunge, purge, and force-resync a 2nd time... it does get emptied out, but I'm not looking to run force-resync intentially since it causes dataloss with mdbox, and re-running only expunge & purge doesn't seem to do anything. Bojan Zelic Sr. IT Infrastructure Engineer

2 3

when are these conf.ext files loaded
by Marc Roos 27 Aug '20

27 Aug '20

Are these .conf.ext always loaded? Or only when they are configured somewhere else?

2 3

Environment variable in config
by Marc Roos 26 Aug '20

26 Aug '20

I am getting errors addressing environment variables. Are they supposed to work in such sections. Not really clear from this[1] page. service health-check { # example health-check. executable = script -p /bin/health-check.sh inet_listener health-check { port = env:PORT0 } } [1] https://doc.dovecot.org/configuration_manual/config_file/config_variables/

1 0

userdb_mail_crypt_private_password: unknown variable after upgrading Dovecot
by f_ckmail＠web.de 26 Aug '20

26 Aug '20

1 0

Dovecot 2.3.11.4 - Centos 6&7 packages
by Aki Tuomi 26 Aug '20

26 Aug '20

Hi! We have pushed new versions for these packages that now support tcpwrappers. They were inadvertendly left out from last time, but now they have been restored. Sorry for the inconvenience. Regards, Aki Tuomi Open-Xchange oy

2 1

Dovecot search message problem
by Claudio Junior 25 Aug '20

25 Aug '20

Hi I have a dovecot installed on debian 10 using solr to have a better search speed in emails. I am observing after an upgrade of the debian dovecot package the error below: Aug 25 00:33:45 server01 dovecot: imap(username(a)example.com)<24104><hyaFXqutnqUAAAAAAAAAAAAAAAAAAAAB>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f0faeaeb62b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f0faeaeb6c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f0faea5a149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac) [0x7f0faea574ac] -> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104) [0x7f0faead3844] -> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7f0faead5df8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7f0faec6e89e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45) [0x7f0faebf0445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774) [0x7f0faec6f774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68) [0x7f0faec70a68] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61) [0x7f0faec710e1] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28) [0x7f0faebf9e58] -> dovecot/imap(+0x2691f) [0x55a43cada91f] -> dovecot/imap(command_exec+0x70) [0x55a43cad3d80] -> dovecot/imap(+0x25ed2) [0x55a43cad9ed2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111) [0x7f0faeb018f1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0) [0x7f0faeb03070] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f0faeb01b7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f0faeb01ce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f0faea820d3] -> dovecot/imap(main+0x325) [0x55a43cac4bf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f0fae86809b] -> dovecot/imap(_start+0x2a) [0x55a43cac4d8a] Aug 25 00:33:45 server01 dovecot: imap(username(a)example.com)<24104><hyaFXqutnqUAAAAAAAAAAAAAAAAAAAAB>: Fatal: master: service(imap): child 24104 killed with signal 6 (core dumped) The package versions are: ii dovecot-core 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - LMTP server ii dovecot-lucene 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - Lucene support ii dovecot-mysql 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - Sieve filters support ii dovecot-solr 1:2.3.4.1-5+deb10u3 amd64 secure POP3/IMAP server - Solr support Emails are accessed via roundcube webmail. I am attaching information for a better analysis of the problem. -- Claudio Junior

1 1

Strange index error on NFS after upgrade to CentOS 7 from 6
by Alessio Cecchi 25 Aug '20

25 Aug '20

Hi, I'm running 3 Dovecot director and 6 Dovecot backend on CentOS 6 and Dovecot 2.3.10, with Maildir shared on NFSv3 (on NetApp). Since CentOS 6 will be EOL on November I started to upgrade to CentOS 7 the first Dovecot backend. But after Director start to direct users on new CentOS 7 server some errors, for any users, come up, an example: Aug 21 14:56:41 Error: imap(alessio(a)cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken or unexpectedly changed file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: - re-reading from beginning Aug 21 14:56:41 Error: imap(alessio(a)cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: Consequently to the error the user see the synchronization of his mailbox again. The Dovecot version and configuration is the same that in CentOS 6, also the mount parameters are the same, so I suspect that could be some difference in the NFS client implementation on CentOS 7. This the entry on fstab: 192.168.1.2:/vmail0 /mnt/vmail0 nfs rw,nfsvers=3,noatime,nodiratime,_netdev,nordirplus 0 0 # Bind for vmail0 /mnt/vmail0/domains /home/vmail/domains none x-systemd.requires=/mnt/vmail0,x-systemd.automount,bind 0 0 In the archive of this list I found a similar issue but without a solutions: https://dovecot.org/pipermail/dovecot/2018-October/113207.html Do you have any suggestions? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 2

unsupported auth mechanism
by absolutely_free＠libero.it 25 Aug '20

25 Aug '20

Hi, last friday I upgraded from dovecot-2.3.10.1_2 to dovecot-2.3.11.3 (FreeBSD). Since then, I started having some issues with some customers. The log I see is like: pop3-login: Disconnected (tried to use unsupported auth mechanism): user=<username(a)domain.it>, method=USER, rip=x,y,x,z, lip=x,y,w,z, session=<e5KkR5qto8hPAL9q> While, before upgrade, same user logged succesfully: pop3-login: Login: user=<username(a)domain.it>, method=PLAIN, rip=x,y,x,z, lip=x,y,w,z, mpid=62876, session=<dMRmGWCtFtJtdcy6> This is my conf (unchanged since months): # dovecot -n # 2.3.11.3 (502c39af9): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 12.1-RELEASE-p8 amd64 zfs # Hostname: server doveconf: Warning: please set ssl_dh=</usr/local/etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/db/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /usr/local/etc/dovecot/dh.pem auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes auth_verbose_passwords = yes default_client_limit = 2000 default_process_limit = 500 default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_gid = 125 first_valid_uid = 125 imap_id_log = * mail_gid = 1003 mail_location = maildir:/mail/domains mail_privileged_group = postfix mail_uid = 1003 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 = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-crypt.conf.ext driver = sql } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = postfix } } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/ssl/wildcard.domain.net_bundle.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { mail_max_userip_connections = 100 } any help? Thank you!

2 2

Panic with namespace
by Kostya Vasilyev 25 Aug '20

25 Aug '20

Hi, I was trying to configure a namespace like this: 10-mail.conf namespace inbox { prefix = "iNBox." inbox = yes } And when a client connected, I got the panic below. Dovecot version is 2.3.4.1 (f79e8e7e4) on Debian 10. Aug 25 16:18:27 kman dovecot: imap(kman@...)<20082><XOXiibOtpq2y2nhZ>: Panic: file mailbox-list-maildir-iter.c: line 511 (maildir_list_iter_next ): assertion failed: ((ctx->info.flags & MAILBOX_NOCHILDREN) != 0) Aug 25 16:18:27 kman dovecot: imap(kman@...)<20082><XOXiibOtpq2y2nhZ>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f659 9d9962b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f6599d996c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f6599d08149] -> /usr/lib/dov ecot/libdovecot-storage.so.0(+0x45b6e) [0x7f6599e92b6e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_sync+0x1dc) [0x7f6599f08c6c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_refresh_force+0xfb) [0x7f6599f0ac3b] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb9274 ) [0x7f6599f06274] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb9467) [0x7f6599f06467] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_exists+0 x68) [0x7f6599ea70e8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_mailbox+0x1f6) [0x7f6599eb6126] -> /usr/lib/dovecot/libdovecot-storage. so.0(mailbox_list_iter_init_namespaces+0x208) [0x7f6599f0be08] -> dovecot/imap(cmd_list_full+0x60e) [0x5654c07d02de] -> dovecot/imap(command_exec+0x70 ) [0x5654c07d9d80] -> dovecot/imap(+0x1e3f2) [0x5654c07d83f2] -> dovecot/imap(+0x1e494) [0x5654c07d8494] -> dovecot/imap(client_handle_input+0x1b5) [0 x5654c07d8845] -> dovecot/imap(client_input+0x7e) [0x5654c07d8d6e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6f) [0x7f6599dafadf] -> /usr/ lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7f6599db10d6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f65 99dafb7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f6599dafce0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f659 9d300d3] -> dovecot/imap(main+0x325) [0x5654c07cabf5] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f6599b1b09b] -> dovecot/imap(_sta rt+0x2a) [0x5654c07cad8a] -- K

1 0

doveadm/doveconf as user tries and fails to read host key
by jimc 25 Aug '20

25 Aug '20

Distro: OpenSuSE Tumbleweed for x86_64 Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd doveadm who #The simplest possible command, for testing It says: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file /etc/ssl/hostcerts/hostw.cia: Permission denied The actual EPERM occurs trying to traverse a directory in /etc/letsencrypt, but the next configuration item to be read (in the SSL section) is the host's private key, and the user is surely not ever going to get permission to read that. (I did test giving the user permission to the 750 directory and it did attempt to read the private key, failing.) If you run it as root, of course it works because root has read permission. The initial failure was seen running as the user from cron. Behavior seen in strace: doveadm execs doveconf; doveconf reads the configuration and saves it somewhere (shared memory?); doveconf execs the next program which in this case is doveadm with its original command line; and doveadm now knows its configuration. I can re-do and post the strace if needed. I don't know why doveconf is reading the SSL keys in 2.3.11.3 when it didn't in 2.3.10.1, but if the idea is to read the complete configuration in case it might be needed in obscure situations, a possible workaround is to not die on unreadable secrets and to report those either as unset or as a new "error" symbol, letting the consumer (doveadm) deal with the fallout, or in this case ignore it. Attached: sysreport.gz ; doveconf-n.out Dovecot's working files and user mailboxes are on ext4 filesystems; NFS is not involved. The mail reader is Roundcube webmail. -- James F. Carter Email: jimc(a)jfcarter.net Web: http://www.math.ucla.edu/~jimc (q.v. for PGP key)

2 2

2 factor authentication
by The Doctor 24 Aug '20

24 Aug '20

Is 2 factor authentication possible on dovecot? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b New Brunswick Save The PRovince Vote Liberal 14 Sept!!

3 2

2.3.11.3 on 32bit platforms
by Michael Ströder 22 Aug '20

22 Aug '20

HI! I'm trying to update openSUSE package on OBS [1] which builds for various OS versions and hardware platforms. To me it seems that a test fails on 32bit platforms: Info: invalid token 3: structure length disagrees with data size test rpa ..................................... : ok Info: invalid NTLM response: buffer length out of bounds test ntlm ............................: ok 1 / 86 tests failed [1] https://build.opensuse.org/package/show/home:stroeder:branches:server:mail/… Ciao, Michael.

4 6

Dovecot on Ubuntu 20.04
by spamvoll＠googlemail.com 22 Aug '20

22 Aug '20

Hi, is anyone using the "Bionic (18.04 LTS)" packages on Focal Fossa (20.04 LTS) ? I'm not sure if its working after the upgrade Hans

5 7

RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
by Thomas Scheunemann 22 Aug '20

22 Aug '20

Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory We use tcpwrap support in dovecot, which worked flawlessly in the older version. I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. And comparing with RPMs, the new one seems to be missing the file: /usr/libexec/dovecot/tcpwrap which leads me to conclusion that the new version is just not compiled with tcpwrap support. Thomas Scheunemann

5 6

dovecot-SASL for Postfix: EXTERNAL does not work.
by Steffen Nurpmeso 21 Aug '20

21 Aug '20

Hello. I am not subscribed and new here, so first of all i want to thank you for dovecot. I personally do not use it in "production" (yet), but it is my sole point of interaction for testing the little MUA i maintain for quite some years. I also have used its code for affirmation purposes. (Interesting that OAUTHBEARER treats hostname and port as optional. I currently do OAUTHBEARER.) So then i stumbled over GSSAPI not being usable anymore with the latest release, but it seems there is an ML thread with a fix. I have not tried it, i reverted to the last release here, though. When i implemented EXTERNAL authentication last year i could not figure out how to make postfix+dovecot-SASL work with it. First of all i had to switch configs back and forth, but in the meantime i learned a very nice trick: if i use two password databases passdb { driver = passwd-file mechanisms = external args = /etc/dovecot/pass-external.db override_fields = nopassword } passdb { driver = passwd-file args = /etc/dovecot/pass.db } userdb { driver = passwd } which are effectively the same except that one does not have passwords while the other has, i can use EXTERNAL (with and without additional user-via-protocol in combination with auth_ssl_username_from_cert=yes and it just works! Whereas EXTERNAL works just fine for IMAP and POP3 it does not for SMTP. Last year when i did it i saw a postfix ML thread in action, so i have not looked further into that. Looking again with things unchanged in the postfix 3.5 that they mentioned by then i think, i now posted to the postfix list myself yesterday [1], and it turned out that postfix seems incapable to do something about it, because the dovecot auth protocol does not offer the possibility to specify a valid-user-certificate-seen flag as well as pass the username from the certificate. (Or even pass the entire certificate as a base64 string, less postfix CA, .. or whatever.) [1] https://marc.info/?l=postfix-users&m=159785887710910&w=2 What is really terrible with the current situation is that postfix announces the EXTERNAL, with Wietse Venema saying Short summary: Postfix does not implement a single iota of SASL AUTH support. Postfix simply propagates the names of mechanisms that the backend (Cyrus or Dovecot) claims to support, and Postfix proxies requests and responses between the remote SMTP client and the SASL backend. Postfix has no idea what SASL mechanisms are, including EXTERNAL. It just proxies stuff. If Dovecot claims to support SASL EXTERNAL but does not handle it, that that is a bit of a WTF. It would be tremendous to have true EXTERNAL support all through, i personally really like EXTERNAL, i would rather have some password-protected crytographically secured certificates in my local store, and have client certificates in all the IoT devices, than have to mess around with the OAUTH that the major players press forward, for example. Thanks, and Ciao from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

3 9

zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
by Robert Nowotny 21 Aug '20

21 Aug '20

I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Thunderbird reports some error when try to save/open a bigger attachment. Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63871><9A0...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:11 lxc-imap dovecot: imap(cpotzinger)<63889><Ig6...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:17 lxc-imap dovecot: imap(cpotzinger)<64169><GXe...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug anything I can tweak or do ? Robert

1 0

Adjusting logging with the "remote" syntax
by Jason Young 21 Aug '20

21 Aug '20

According to the docs, we can use ‘local’ and ‘remote’ blocks to change configuration directives. In my current setup (Mail-in-a-box using Nextcloud, which is configured for IMAP authentication), my mail logs are spammed with local logins. I really don't need these reports, but still want to retain login logs for remote IPs. So I set the following in my configuration: remote 127.0.0.1 { info_log_path = /dev/null } When I run "doveadm -n -f remote=127.0.0.1”, it does seem to understand it: --- # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) ... info_log_path = /dev/null ... remote 127.0.0.1 { info_log_path = /dev/null } --- However, I’m still getting spammed with local login reports: Aug 12 12:17:13 imap-login: Info: Login: user=<user(a)domain.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=29798, TLS, session=<FGVJhbCsstt/AAAB> Aug 12 12:17:13 imap(user(a)domain.tld): Info: Logged out in=305 out=2277 I've also tried logging to a specific file, instead of /dev/null, but no file was created. So there must be an issue with my understanding. How can I prevent logins from localhost from being logged without sacrificing logs for all logins? -Jason Young

1 1

OT: SASL questions
by Richard Hector 21 Aug '20

21 Aug '20

Hi all, Apologies for the somewhat off-topic questions - I'm trying to get my head around SASL, and what it is/does. I can see that a (SMTP, IMAP etc) server can offer various authentication methods, which are pre-defined and which the client can choose from. SASL then seems to define how those work. But dovecot and cyrus-sasl both seem to offer a client-server interface, usable by eg postfix, which I don't see any reference to in SASL summaries online. Is that a standard interface? ie can a client like postfix talk to either dovecot or cyrus without knowing the difference? Are there others? Is there a good reference to this somewhere, short of reading the RFCs? And is there any option (current or proposed) to let dovecot act as a client, rather than a server? Thanks, Richard

2 2

Rootless wiki page is not up to date?
by Marc Roos 20 Aug '20

20 Aug '20

If I run a docker image with the mesos containerizer and altering the dovecot config mentioned here[1] I think the root detection is incorrect because it looks like dovecot is still thinking it is root. I still get errors like: >> log(829825): Fatal: We couldn't drop root group privileges (wanted=10053(dovecot), gid=0(root), egid=0(root)) Why does it want to drop to root, if we are not even running as root? >> Error: service(ipc): chown(/var/dovecot/login/ipc-proxy, 91, 4294967295) failed: Operation not permitted Why does it want to chown, when it is not root? pop3-login: Fatal: setgid(101(dovenull)) failed with euid=10053(dovecot), gid=10053(dovecot), egid=10053(dovecot): Operation not permitted (This binary should probably be called with process group set to 101(dovenull) instead of 10053(dovecot)) [1] https://wiki.dovecot.org/HowTo/Rootless?action=edit&editor=text

2 2

INBOX sharing does not work
by Torsten 19 Aug '20

19 Aug '20

Hello! INBOX sharing does not seem to work, although all other mailboxes work. User bar(a)example.de has shared a few mailboxes: # doveadm acl get -u bar(a)example.de INBOX ID Global Rights user=foo(a)example.de lookup read write-seen # doveadm acl get -u bar(a)example.de Sent ID Global Rights user=foo(a)example.de lookup read write-seen # doveadm acl get -u bar(a)example.de Drafts ID Global Rights user=foo(a)example.de lookup read write-seen But user foo(a)example.de can't see the shared INBOX: # doveadm mailbox list -u foo(a)example.de Trash Sent Drafts Junk shared shared/bar(a)example.de shared/bar(a)example.de/Sent shared/bar(a)example.de/Drafts INBOX A review of the ACL does not explain the behaviour: # doveadm acl debug -u foo(a)example.de shared/bar(a)example.de/INBOX doveadm(foo(a)example.de): Info: Mailbox 'INBOX' is in namespace 'shared/bar(a)example.de/' doveadm(foo(a)example.de): Info: Mailbox path: /srv/mail-storage/mailhome/example.de/bar/Maildir doveadm(foo(a)example.de): Info: Per-user private flags in mailbox: \Seen doveadm(foo(a)example.de): Info: User foo(a)example.de has rights: lookup read write-seen doveadm(foo(a)example.de): Info: Mailbox found from dovecot-acl-list doveadm(foo(a)example.de): Info: User bar(a)example.de found from ACL shared dict doveadm(foo(a)example.de): Info: Mailbox shared/bar(a)example.de/INBOX is visible in LIST ---------- doveconf -n ---------- # 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.5 # Hostname: XXX.YYYY.de auth_master_user_separator = * auth_verbose = yes first_valid_gid = 401 first_valid_uid = 401 last_valid_gid = 401 last_valid_uid = 401 mail_gid = vmail mail_home = /srv/mail-storage/mailhome/%d/%n mail_location = maildir:~/Maildir mail_plugins = " acl listescape zlib" 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace shared { list = children location = maildir:/srv/mail-storage/mailhome/%%d/%%n/Maildir:INDEXPVT=~/Maildir/shared/%%d/%%n prefix = shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/srv/mail-storage/mailhome/shared-mailboxes.db sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } protocols = " imap lmtp sieve" service auth { unix_listener auth-userdb { mode = 0777 } } ssl = required ssl_cert = </var/lib/dehydrated/certs/XXX.YYYY.de/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = static } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { mail_plugins = " acl listescape zlib sieve" } protocol imap { mail_max_userip_connections = 20 mail_plugins = " acl listescape zlib imap_acl" } ------------------------------ I don't think it is relevant, but I don't want to forget to mention that /srv/mail-storage/ is an NFS share. It would bee nice if someone has a hint. I hope it isn't a bug. Regards Torsten

2 2

pop3_migration plugin
by Andrea Gabellini 19 Aug '20

19 Aug '20

Hello, I'm trying to migrate from an old courier-IMAP server on which I made a plugin to access the individual mailboxes with a master password Emails are used in both POP3 and IMAP. I followed this guide https://wiki.dovecot.org/Migration/Dsync In the log I find these messages, which are generated by the server independently without issuing the command "doveadm backup ..." dsync-local (xxxxxxx) <yIAgHZtVPF85HwAA9osHUQ>: Error: pop3_migration: 8044 POP3 messages have no matching IMAP messages (first POP3 msg 1 UIDL UID33550-1353000352) - all IMAP messages were found (POP3 may contain more than IMAP to INBOX - you may want set pop3_migration_all_mailboxes = yes) - set pop3_migration_ignore_missing_uidls = yes or pop3_migration_ignore_extra_uidls = yes to continue anyway The mailboxes obviously have at least the "Sent", "Trash" and "Drafts" mailboxes. What should I do? Where can I find documentation of the pop3_migration plugin? Thanks, Andrea -- __________________________ Seen it all, done it all, can't remember most of it __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

1 0

Sieve scripts replication not working
by Piotr Auksztulewicz 18 Aug '20

18 Aug '20

Hi all! I am a long-time dovecot user/admin on my home server, but only recently tried to configure replication. Everything seems to work except sieve scripts replication. When I upload new one on the server A, it does not replicate to server B, even if it seemingly tries to, according to debug logs. The log antry says: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 on server A, but nothing like that on server B. Server B logs show that server A is connecting to doveadm service but little else. Any ideas what could be wrong? Please see the logs below. Users and domains have been anonymized. ----- Upload ------------- $ sieve-connect -s serverA.mydomain.example -p sieve -u user(a)mydomain.example --notlsverify Sieve/IMAP Password: ReadLine support enabled. > put lists > put autosave ----- Server A log ------- Aug 18 16:05:49 serverA dovecot[60776]: managesieve-login: Login: user=<user(a)mydomain.example>, method=PLAIN, rip=<redacted>, lip=<redacted>, mpid=35651, TLS, session=<Qw4fYiet/uEKKCgK> Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Loading modules from directory: /usr/lib/dovecot/modules Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: Pigeonhole version 0.5.4 () initializing Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using active Sieve script path: /var/vmail/user(a)mydomain.example/.sieve Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using script storage path: /var/vmail/user(a)mydomain.example/sieve Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using permissions from /var/vmail/user(a)mydomain.example/sieve: mode=0700 gid=-1 Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: sync: Synchronization active Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using Sieve script path: /var/vmail/user@mydomain.example/sieve/tmp/lists_1597759554.M792097P35651.serverA.mydomain.example.sieve Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file script: Opened script `lists' from `/var/vmail/user@mydomain.example/sieve/tmp/lists_1597759554.M792097P35651.serverA.mydomain.example.sieve' Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: replication: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example)<35652><>: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using Sieve script path: /var/vmail/user@mydomain.example/sieve/tmp/autosave_1597759558.M923011P35651.serverA.mydomain.example.sieve Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file script: Opened script `autosave' from `/var/vmail/user@mydomain.example/sieve/tmp/autosave_1597759558.M923011P35651.serverA.mydomain.example.sieve' Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: replication: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example)<35653><>: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:06:00 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Disconnected: Logged out bytes=3748/95 ----- Server B log ------- Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default ----- doveconf -n ------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-8-amd64 x86_64 Debian 10.4 # Hostname: serverA.mydomain.example 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_debug = yes mail_location = maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 mail_plugins = " notify replication" mail_privileged_group = 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 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:serverB.mydomain.example 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 = serverA.mydomain.example 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 = serverA.mydomain.example port = 4551 } } service imap-hibernate { protocol = none } service imap-login { inet_listener imap { address = serverA.mydomain.example port = 143 } process_limit = 25 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 = 25 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 = serverA.mydomain.example port = 2306 } process_limit = 5 user = vmail } service log { user = $default_internal_user } service managesieve-login { inet_listener sieve { address = serverA.mydomain.example 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 = 3 service_count = 1 } service pop3 { chroot = /var/vmail process_limit = 3 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

4 3

Sieve scripts replication not working
by Piotr Auksztulewicz 18 Aug '20

18 Aug '20

Hi all! I am a long-time dovecot user/admin on my home server, but only recently tried to configure replication. Everything seems to work except sieve scripts replication. When I upload new one on the server A, it does not replicate to server B, even if it seemingly tries to, according to debug logs. The log antry says: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 on server A, but nothing like that on server B. Server B logs show that server A is connecting to doveadm service but little else. Any ideas what could be wrong? Please see the logs below. Users and domains have been anonymized. ----- Upload ------------- $ sieve-connect -s serverA.mydomain.example -p sieve -u user(a)mydomain.example --notlsverify Sieve/IMAP Password: ReadLine support enabled. > put lists > put autosave ----- Server A log ------- Aug 18 16:05:49 serverA dovecot[60776]: managesieve-login: Login: user=<user(a)mydomain.example>, method=PLAIN, rip=<redacted>, lip=<redacted>, mpid=35651, TLS, session=<Qw4fYiet/uEKKCgK> Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Loading modules from directory: /usr/lib/dovecot/modules Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: Pigeonhole version 0.5.4 () initializing Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using active Sieve script path: /var/vmail/user(a)mydomain.example/.sieve Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using script storage path: /var/vmail/user(a)mydomain.example/sieve Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using permissions from /var/vmail/user(a)mydomain.example/sieve: mode=0700 gid=-1 Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ Aug 18 16:05:49 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: sync: Synchronization active Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using Sieve script path: /var/vmail/user@mydomain.example/sieve/tmp/lists_1597759554.M792097P35651.serverA.mydomain.example.sieve Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file script: Opened script `lists' from `/var/vmail/user@mydomain.example/sieve/tmp/lists_1597759554.M792097P35651.serverA.mydomain.example.sieve' Aug 18 16:05:54 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: replication: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example)<35652><>: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file storage: Using Sieve script path: /var/vmail/user@mydomain.example/sieve/tmp/autosave_1597759558.M923011P35651.serverA.mydomain.example.sieve Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: sieve: file script: Opened script `autosave' from `/var/vmail/user@mydomain.example/sieve/tmp/autosave_1597759558.M923011P35651.serverA.mydomain.example.sieve' Aug 18 16:05:58 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Debug: replication: Replication requested by 'sieve_storage_sync_transaction_begin', priority=1 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example)<35653><>: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: remote(serverB.mydomain.example): fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverA dovecot[60776]: doveadm(user(a)mydomain.example): Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:06:00 serverA dovecot[60776]: managesieve(user(a)mydomain.example)<35651><Qw4fYiet/uEKKCgK>: Disconnected: Logged out bytes=3748/95 ----- Server B log ------- Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:55 serverB dovecot[30215]: doveadm: Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: auth PASS input: user=user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: auth USER input: user(a)mydomain.example uid=113 gid=122 home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Effective uid=113, gid=122, home=/var/vmail/user(a)mydomain.example Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: fs: root=/var/vmail/user(a)mydomain.example/mail, index=, indexpvt=, control=, inbox=, alt= Aug 18 16:05:59 serverB dovecot[30215]: doveadm: Debug: Namespace : Using permissions from /var/vmail/user(a)mydomain.example/mail: mode=0700 gid=default ----- doveconf -n ------- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-8-amd64 x86_64 Debian 10.4 # Hostname: serverA.mydomain.example 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_debug = yes mail_location = maildir:~/mail:LAYOUT=fs:DIRNAME=.MailDir:UTF-8 mail_plugins = " notify replication" mail_privileged_group = 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 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:serverB.mydomain.example 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 = serverA.mydomain.example 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 = serverA.mydomain.example port = 4551 } } service imap-hibernate { protocol = none } service imap-login { inet_listener imap { address = serverA.mydomain.example port = 143 } process_limit = 25 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 = 25 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 = serverA.mydomain.example port = 2306 } process_limit = 5 user = vmail } service log { user = $default_internal_user } service managesieve-login { inet_listener sieve { address = serverA.mydomain.example 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 = 3 service_count = 1 } service pop3 { chroot = /var/vmail process_limit = 3 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

1 0

solr and dovecot 2.2.36
by Maciej Milaszewski 18 Aug '20

18 Aug '20

Hi I have dovecot-2.2.36.4 (director) + 5 nodes dovecot (dovecot-2.2.36.4) What version of Solr do you recommend ? -- Maciej Miłaszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obsługi Klienta: e-mail: bok(a)iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 0000007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853

3 3

Indexer error after upgrade to 2.3.11.3
by Alessio Cecchi 18 Aug '20

18 Aug '20

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x2f) [0x7f0ee3c828bf] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x26) [0x7f0ee3c829d6] -> /usr/lib64/dovecot/libdovecot.so.0(+0xeb7ba) [0x7f0ee3c8d7ba] -> /usr/lib64/dovecot/libdovecot.so.0(+0xeb801) [0x7f0ee3c8d801] -> /usr/lib64/dovecot/libdovecot.so.0(+0x42ff1) [0x7f0ee3be4ff1] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_send_more+0x415) [0x7f0ee3c2ba25] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_connection_output+0x114) [0x7f0ee3c30994] -> /usr/lib64/dovecot/libdovecot.so.0(+0x115470) [0x7f0ee3cb7470] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f0ee3ca4eb5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x7f0ee3ca6ebc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f0ee3ca4fac] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ee3ca51f8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8a955) [0x7f0ee3c2c955] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_finish_payload+0x21) [0x7f0ee3c2cbd1] -> /usr/lib64/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_end+0x45) [0x7f0ee1c85d15] -> /usr/lib64/dovecot/lib21_fts_solr_plugin.so(+0x3fa0) [0x7f0ee1c81fa0] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x86cc) [0x7f0ee297f6cc] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_backend_update_deinit+0x2c) [0x7f0ee297f74c] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xfd04) [0x7f0ee2986d04] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xff3f) [0x7f0ee2986f3f] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xf64b) [0x7f0ee2dc764b] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xde43) [0x7f0ee2fdce43] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x54) [0x7f0ee3f91db4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0x16) [0x7f0ee3f91e76] -> dovecot/indexer-worker [info(a)domain.com INBOX](+0x291c) [0x557584acb91c] -> dovecot/indexer-worker [info(a)domain.com INBOX](+0x2e54) [0x557584acbe54] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x55) [0x7f0ee3ca4eb5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x7f0ee3ca6ebc] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f0ee3ca4fac] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f0ee3ca51f8] Aug 18 11:02:35 Error: indexer: Indexer worker disconnected, discarding 1 requests for info(a)domain.com Aug 18 11:02:35 Error: imap(info(a)domain.com) session=<g71KISOttvS5LNVj>: indexer failed to index mailbox INBOX Aug 18 11:02:35 Fatal: indexer-worker(info(a)domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: master: service(indexer-worker): child 24604 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) I'm using FTS with Solr 6.6.5. What is it? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 0

Tests failing on CentOS 6
by Peter 18 Aug '20

18 Aug '20

Getting this when attempting to build 2.3.11.3 on CentOS 6: test-mail-cache.c:176: Assert failed: strcmp(str_c(str),"123\nfoo\n456\nbar\n") "" != "123 foo 456 bar " test-mail-cache.c:176: Assert failed: strcmp(str_c(str),"123\nfoo\n456\nbar\n") "" != "123 foo 456 bar " mail cache uncommitted lookups ....................................... : FAILED Full make check output is at https://paste.centos.org/view/b48d38a9 I can provide full build logs if you want, but that's a 4M file so I'll provide it upon request. For now I'm going ot have to bypass the make check stage of the build for CentOS 6, but I worry that the failed check could be indicative of something critical. Peter

2 2

Apple Mail Since upgrade to dovecot 2.3.x unable to connect
by Johannes Rohr 18 Aug '20

18 Aug '20

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument| || |Unfortunately, it doesn't reveal the name of the unsupported protocol. Also, what about the failed syscall? Does dovecot try and fail to open some file?| |Here are the contents of /etc/dovecot/conf.d/10-ssl.conf:| | ssl = yes ssl_cert = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/fullchain.pem ssl_key = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/key.pem ssl_ca = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/ca.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = </etc/dovecot/dh.pem | |I would greatly appreciate any hints! | |Cheers,| |Johannes | | | ||

6 6

MDBOX DSYNC error: Broken physical size in mailbox
by paul-dovecotlist＠trainor.nz 18 Aug '20

18 Aug '20

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no issues for a couple of years. I'm running this command on Server A: doveadm sync -u #user# tcp:#newservername#:24245 Small mailboxes with few items are syncing OK.. but most mailboxes fail (sycn stops) with the following type of error: (Mailbox name, storage file, UID and sizes vary). dsync-local(#username#)<b2vTDKerOV/fAQAAZMK/0g>: Error: Mailbox INBOX: Cache /#usershomedirectory#/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: Deleting corrupted cache record uid=9: UID 9: Broken physical size in mailbox INBOX: read(/#usershomedirectory#/mdbox/storage/m.1) failed: Cached message size larger than expected (60616 > 8688, box=INBOX, UID=9) If I run it again, I'll get the same error, but with a new UID. If I do a local migration instead of server to server, I still get the errors. e.g. doveadm sync -u #user# maildir:~/Maildir-test/ I tried running a force resync (doveadm force-resync -u #user# -f "*) but it didn't help. There's no issues from an imap client accessing any emails. Using imapsync to sync affected mailboxes works fine for example. But... if I then run a dsync on Server B (doveadm sync -u #user# maildir:~/Maildir-test/) on an account that was successfully migrated with imapsync, I get the issue again. How worried should I be about these corrupted cache records, and any ideas how to resolve? Thanks in advance for your help! Paul. --- output of doveconf -n --- # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (6c69c917) # OS: Linux 5.3.0-1032-aws x86_64 Ubuntu 18.04.5 LTS hostname = ### lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_trusted_networks = ### mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " acl notify replication" 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 mmap_disable = yes 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 = separator = / type = private } namespace shared { list = children location = mdbox:/mailhomes/%%d/%%n/mdbox:INDEXPVT=/mailhomes/%d/%n/shared prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/tmp/global-acls:cache_secs=5 mail_plugins = " acl notify replication" sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /mailhomes/sieve/global/SpamToJunk.sieve sieve_max_actions = 32 sieve_max_redirects = 4 sieve_max_script_size = 1M sieve_quota_max_scripts = 20 sieve_quota_max_storage = 10M sieve_redirect_envelope_from = sender zlib_save = bz2 zlib_save_level = 6 } protocols = " imap lmtp sieve submission sieve" recipient_delimiter = - service doveadm { inet_listener { port = 24245 } } service imap-login { process_min_avail = 2 } service imap { process_limit = 4096 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 2 service_count = 1 } service managesieve { process_limit = 1024 } service submission-login { inet_listener submission { port = 587 } } ssl = required ssl_cert = </etc/dovecot/dovecot-backend.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it submission_client_workarounds = whitespace-before-path submission_host = ### submission_relay_host = ### submission_relay_ssl = starttls submission_relay_trusted = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lda { mail_plugins = " acl notify replication zlib" } protocol imap { mail_max_userip_connections = 100 mail_plugins = " acl notify replication zlib imap_acl" } protocol lmtp { mail_plugins = " acl notify replication zlib sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k } protocol submission { mail_plugins = " acl notify replication" } local ### { doveadm_password = # hidden, use -P to show it } local ### { doveadm_password = # hidden, use -P to show it }

2 1

Apple Mail Since upgrade to dovecot 2.3.x unable to connect
by Johannes Rohr 17 Aug '20

17 Aug '20

|Dear all,| |a couple of days ago I upgraded our server from Ubuntu 18.04 to 20.04, thereby upgrading dovecot from 2.2.x to 2.3.x. | |Since then, some older versions of apple's mail.app (bundled with el Capitano, released in 2016) no longer connect. When I turn on SSL debugging, I see:| |Debug: SSL error: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol imap-login: Debug: SSL error: SSL_accept() syscall failed: Invalid argument| || |Unfortunately, it doesn't reveal the name of the unsupported protocol. Also, what about the failed syscall? Does dovecot try and fail to open some file?| |Here are the contents of /etc/dovecot/conf.d/10-ssl.conf:| | ssl = yes ssl_cert = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/fullchain.pem ssl_key = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/key.pem ssl_ca = </etc/ssl/letsencrypt/idaweb-mail.rooot.de/ca.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = </etc/dovecot/dh.pem | |I would greatly appreciate any hints! | |Cheers,| |Johannes | | | ||

2 1

generating secure ARGON2ID passwords
by Felix Zielcke 16 Aug '20

16 Aug '20

Hello, I'm using dovecot 2.3.4.1 on a Debian buster system. with Argon2ID password scheme, it's only possible to configure the parameters used for it via the generic -r option to "doveadm pw". A higher -r will increase time and memory comsumption. But on my dual core VM it always uses p=1. So it seems the needed threads can only be changed on compile time? Will there be in future a way to explicitly specify memory, time and threads needed for Argon2ID?

2 2

Bug: GSSAPI: Unexpected NUL in auth data
by Paul Banks 16 Aug '20

16 Aug '20

Hi, After upgrading server to v2.3.11.3 (Arch linux). I can no longer connect from Evolution client to the server via GSSAPI (Kerberos). I get the following message in the log: auth: Debug: gssapi(?,x.x.x.x,<XXX>): Unexpected NUL in auth data The bug appears to have been introduced by this patch: https://github.com/dovecot/core/commit/d196f4c83c7383c17440d39eb994b4cd9ff5… Should mech_gssapi also have the MECH_SEC_ALLOW_NULS flag set? Kind regards, Paul

2 2

2.3.11.3: dsync failure
by Alexander Tsoy 16 Aug '20

16 Aug '20

Hello! dovecot 2.3.11.3 fails to backup/sync my mailbox. The mailbox is currently in mdbox format and is (mostly) lz4-compressed. See the trace below (I've added newlines to the output): # doveadm -v backup -u username mdbox:/var/vmail/username_new/mdbox dsync(username): Panic: file istream.c: line 332 (i_stream_read_memarea): assertion failed: (!stream->blocking) dsync(username): Error: Raw backtrace: #0 default_fatal_finish[0x7f1179173b29] -> #1 fatal_handler_real[0x7f1179173be0] -> #2 default_fatal_handler[0x7f1179173c3d] -> #3 i_panic[0x7f1179173e27] -> #4 i_stream_read_memarea[0x7f1179187b29] -> #5 read_more[0x7f117919519b] -> #6 read_from_buffer[0x7f117919535a] -> #7 i_stream_seekable_read[0x7f117919582e] -> #8 i_stream_seekable_stat[0x7f1179195cdf] -> #9 i_stream_stat[0x7f1179188764] -> #10 i_stream_limit_stat[0x7f1179192380] -> #11 i_stream_stat[0x7f1179188764] -> #12 i_stream_default_stat[0x7f117918a0a3] -> #13 i_stream_default_get_size[0x7f117918a282] -> #14 i_stream_get_size[0x7f1179188811] -> #15 mdbox_save_begin[0x7f11792edb85] -> #16 zlib_mail_save_compress_begin[0x7f117891b2ad] -> #17 mailbox_save_begin[0x7f11792c8f22] -> #18 mail_storage_try_copy[0x7f11792b2443] -> #19 mail_storage_copy[0x7f11792b2604] -> #20 mdbox_copy[0x7f11792ee96f] -> #21 mailbox_copy_int[0x7f11792c9611] -> #22 mailbox_copy[0x7f11792c98c2] -> #23 dsync_mailbox_save_body[0x5629fd7936a5] -> #24 dsync_mailbox_save_newmails[0x5629fd793dc3] -> #25 dsync_mailbox_import_mail[0x5629fd793eb0] -> #26 dsync_brain_recv_mail[0x5629fd78b982] -> #27 dsync_brain_sync_mails[0x5629fd78bd79] -> #28 dsync_brain_run_real[0x5629fd78576c] -> #29 dsync_brain_run[0x5629fd7859a5] -> #30 cmd_dsync_run_local[0x5629fd75e8d3] -> #31 cmd_dsync_run[0x5629fd75f3a8] -> #32 doveadm_mail_next_user[0x5629fd762f81] -> #33 doveadm_mail_single_user[0x5629fd763311] -> #34 doveadm_mail_cmd_exec[0x5629fd763963] -> #35 doveadm_mail_cmd[0x5629fd763c22] -> #36 doveadm_mail_try_run[0x5629fd7641e1] -> #37 main[0x5629fd78051d] -> #38 __libc_start_main[0x7f1178d56c00] -> #39 _start[0x5629fd74cb20] Aborted Tried different output compression types: gz, xz, zstd. dovecot 2.3.10.1 doesn't seem to have such problem. But since I already have some messages compressed with zstd, I would like to do migration using 2.3.11.x. Please let me know if I can provide any further information. I'm not on the list, so please CC me on reply. $ sudo dovecot -n # 2.3.11.3 (502c39af9): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.11 (d71e0372) # OS: Linux 5.4.58-gentoo x86_64 Gentoo Base System release 2.6 # Hostname: xxxxxxxx.xx auth_mechanisms = plain login default_client_limit = 50 default_process_limit = 10 imap_idle_notify_interval = 29 mins mail_fsync = always mail_location = mdbox:~/mdbox mail_plugins = " zlib" 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 mdbox_preallocate_space = yes 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 = separator = / subscriptions = yes } passdb { args = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = xz zlib_save_level = 9 } protocols = imap lmtp service auth-worker { user = $default_internal_user } service auth { unix_listener auth-client { mode = 0660 user = mail } user = $default_internal_user } service imap-login { inet_listener imaps { port = 0 } } ssl = required ssl_cert = </etc/ssl/dovecot/server.crt ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%n /etc/dovecot/users driver = passwd-file } protocol lmtp { mail_plugins = " zlib sieve" } protocol lda { mail_plugins = " zlib sieve" } local_name imap.xxxx.xx { ssl_cert = </etc/ssl/dovecot/imap.xxxx.xx.crt ssl_key = # hidden, use -P to show it } local_name imap.xxxxxxxx.xx { ssl_cert = </etc/ssl/dovecot/imap.xxxxxxxx.xx.crt ssl_key = # hidden, use -P to show it }

1 0

Doveadm error since 2.3.11.3 when run as unprivileged user
by Arjen de Korte 15 Aug '20

15 Aug '20

I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_key: Can't open file /etc/ssl/private/de-korte.org.key: Permission denied This is no surprise, as non-privileged users are not allowed to read the private keys of the server. Question is, why is doveadm trying to read this key in the first place (it is not needed for mailbox maintenance) and why is it failing now? Regards, Arjen

4 6

User doesn't exist
by Bruno Kiste 15 Aug '20

15 Aug '20

I try to use dovecot as a MTA with postfix. But it does not accept incoming mails. Why does it not work? [root@localhost bruno]# dovecot --version 2.3.8 (9df20d2db) /var/log/maillog Aug 14 11:03:32 localhost dovecot[566097]: lmtp(566373): Connect from local Aug 14 11:03:32 localhost dovecot[566097]: lmtp(bruno(a)2c2axxx.online-server.cloud)<566373><0O+4HWRTNl9lpAgA0J78UA>: Debug: auth-master: userdb lookup(bruno(a)2c2axxx.online-server.cloud): Started userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: lmtp(bruno(a)2c2axxx.online-server.cloud)<566373><0O+4HWRTNl9lpAgA0J78UA>: Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting Aug 14 11:03:32 localhost dovecot[566097]: lmtp(bruno(a)2c2axxx.online-server.cloud)<566373><0O+4HWRTNl9lpAgA0J78UA>: Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Client connected (fd=16) Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: master in: USER#0111#011bruno(a)2c2axxx.online-server.cloud#011service=lmtp Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: passwd(bruno(a)2c2axxx.online-server.cloud): Performing userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: Loading modules from directory: /usr/lib64/dovecot/auth Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: passwd-file /etc/dovecot/users: Read 4 users in 0 secs Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: conn unix:auth-worker (pid=566367,uid=97): Server accepted connection (fd=14) Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: conn unix:auth-worker (pid=566367,uid=97): Sending version handshake Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: conn unix:auth-worker (pid=566367,uid=97): auth-worker<1>: Handling USER request Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: passwd(bruno(a)2c2axxx.online-server.cloud): Performing userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: passwd(bruno(a)2c2axxx.online-server.cloud): lookup Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): passwd(bruno(a)2c2axxx.online-server.cloud): unknown user - trying the next userdb Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: passwd(bruno(a)2c2axxx.online-server.cloud): Finished userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth-worker(566374): Debug: conn unix:auth-worker (pid=566367,uid=97): auth-worker<1>: Finished Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: passwd(bruno(a)2c2axxx.online-server.cloud): Finished userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: passwd-file(bruno(a)2c2axxx.online-server.cloud): Performing userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: passwd-file(bruno(a)2c2axxx.online-server.cloud): lookup: user=bruno(a)2c2axxx.online-server.cloud file=/etc/dovecot/users Aug 14 11:03:32 localhost dovecot[566097]: auth: passwd-file(bruno(a)2c2axxx.online-server.cloud): unknown user Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: passwd-file(bruno(a)2c2axxx.online-server.cloud): Finished userdb lookup Aug 14 11:03:32 localhost dovecot[566097]: auth: Debug: userdb out: NOTFOUND#0111 Aug 14 11:03:32 localhost dovecot[566097]: lmtp(bruno(a)2c2axxx.online-server.cloud)<566373><0O+4HWRTNl9lpAgA0J78UA>: Debug: auth-master: userdb lookup(bruno(a)2c2axxx.online-server.cloud): auth USER input: Aug 14 11:03:32 localhost dovecot[566097]: lmtp(bruno(a)2c2axxx.online-server.cloud)<566373><0O+4HWRTNl9lpAgA0J78UA>: Debug: auth-master: userdb lookup(bruno(a)2c2axxx.online-server.cloud): Userdb lookup failed Aug 14 11:03:32 localhost postfix/lmtp[566372]: 4E2127802973: to=<bruno(a)2c2axxx.online-server.cloud>, relay=2c2axxx.online-server.cloud[private/dovecot-lmtp], delay=0.26, delays=0.19/0.02/0.02/0.02, dsn=5.1.1, status=bounced (host 2c2axxx.online-server.cloud[private/dovecot-lmtp] said: 550 5.1.1 <bruno(a)2c2axxx.online-server.cloud> User doesn't exist: bruno(a)2c2axxx.online-server.cloud (in reply to RCPT TO command)) [root@localhost bruno]# cat /etc/dovecot/users #user:password:uid:gid:(gecos):home:(shell):extra_fields bruno:{CRAM-MD5}88XXXee:5001:5001::/home/bruno:: mail:{CRAM-MD5}88XXXee:5001:5001::/home/mail:: nas:{CRAM-MD5}8eXXX40:5001:5001::/home/nas asys:{CRAM-MD5}99XXX09:5001:5001::/home/asys

3 3

CentOS 8 packages available
by Aki Tuomi 14 Aug '20

14 Aug '20

We are happy to announce that we have CentOS 8 packages available starting from v2.3.11.3. You can find these packages at https://repo.dovecot.org/ Regards, Aki Tuomi Open-Xchange oy

2 1

2.3.11.3 on 32bit platforms
by Christian Göttsche 14 Aug '20

14 Aug '20

See also the 32bit build failures on Debian: https://buildd.debian.org/status/package.php?p=dovecot There are some compiler warnings on 32bit architectures in test-mech.c test-mech.c: In function ‘test_mechs’: test-mech.c:326:61: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’ [-Wformat=] 326 | const char *testname = t_strdup_printf("auth mech %s %d/%lu", | ~~^ | | | long unsigned int | %u test-mech.c:338:12: warning: passing argument 2 of ‘test_mech_construct_apop_challenge’ from incompatible pointer type [-Wincompatible-pointer-types] 338 | &test_case->len); | ^~~~~~~~~~~~~~~ | | | size_t * {aka unsigned int *} test-mech.c:195:77: note: expected ‘long unsigned int *’ but argument is of type ‘size_t *’ {aka ‘unsigned int *’} 195 | test_mech_construct_apop_challenge(unsigned int connect_uid, unsigned long *len_r) | ~~~~~~~~~~~~~~~^~~~~ But the unit test still fails after a commit like: diff --git a/src/auth/test-mech.c b/src/auth/test-mech.c index cf05370..90c2215 100644 --- a/src/auth/test-mech.c +++ b/src/auth/test-mech.c @@ -192,7 +192,7 @@ static void test_mech_handle_challenge(struct auth_request *request, } static inline const unsigned char * -test_mech_construct_apop_challenge(unsigned int connect_uid, unsigned long *len_r) +test_mech_construct_apop_challenge(unsigned int connect_uid, size_t *len_r) { string_t *apop_challenge = t_str_new(128); @@ -323,7 +323,7 @@ static void test_mechs(void) struct test_case *test_case = &tests[running_test]; const struct mech_module *mech = test_case->mech; struct auth_request *request; - const char *testname = t_strdup_printf("auth mech %s %d/%lu", + const char *testname = t_strdup_printf("auth mech %s %d/%zu", mech->mech_name, running_test+1, N_ELEMENTS(tests));

1 0

About the changing namespace handling from v2.0 to v2.1 or later
by mizuta.takeshi＠fujitsu.com 14 Aug '20

14 Aug '20

Hi, all, Please tell me about the patch and description below. https://github.com/dovecot/core/commit/5f46b863383fc94afcd2693ecae8788cb5fd… example-config: Use a default uncommented "namespace inbox". https://doc.dovecot.org/configuration_manual/namespace/ There's a default inbox namespace added in 10-mail.conf. If the configuration doesn't explicitly specify a namespace (as was in v2.0 and older) a default namespace is created automatically. Since v2.1, namespace is enabled by default in 10-mail.conf, and "inbox" is added as a sectionname of namespace. I checked the dovecot's mail archive, but I didn't understand the reason for the change. Please tell me about followings. - Why "inbox" was added as a sectionname? - Why was namespace changed to be enabled by default? Best regards, MIZUTA Takeshi

1 0

2.3.11.3 mail_cache_open_or_create_path called with null path
by Stuart Henderson 13 Aug '20

13 Aug '20

Originally reported here - https://marc.info/?l=openbsd-ports&m=159731598419071&w=2 OpenBSD's printf functions have a (mostly annoying but occasionally useful) feature where they generate a syslog entry if printf %s format is called with a null pointer. It is tripped in lmtp/lda deliveries with 2.3.11.3: lmtp: vfprintf %s NULL in "Cache %s: " dovecot-lda: vfprintf %s NULL in "Cache %s: " src/lib-index/mail-cache.c: .. 557 struct mail_cache * 558 mail_cache_open_or_create_path(struct mail_index *index, const char *path) 559 { .. 565 cache->filepath = i_strdup(path); .. 572 event_set_append_log_prefix(cache->event, 573 t_strdup_printf("Cache %s: ", cache->filepath); .. Seems something is wrong to have this function called with no cache path?

2 1

Fix for pigeonhole 0.5.11
by Aki Tuomi 13 Aug '20

13 Aug '20

Hi! We have made a small fix to the Pigeonhole 0.5.11 tarball, please find the new tarball at https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.t… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.t… The original released tarball is still available. The only change here is that the configure.ac file has correctly formatted version number. Regards, Aki Tuomi Open-Xchange oy

1 0

CentOS 6 packages dropped
by Aki Tuomi 13 Aug '20

13 Aug '20

Hi! We are dropping CentOS 6 packages now that we have CentOS 8 packages available. 2.3.11.3 will be last version for which CentOS 6 packages are built for https://repo.dovecot.org. Regards, Aki Tuomi Open-Xchange oy

1 0

Correcting Mail Home, Maildir and Sieve folder locations
by David White 13 Aug '20

13 Aug '20

I have Dovecot 2.3.7.2 on Ubuntu 20.04. I just migrated the server from CentOS 8, and only migrated to the CentOS 8 machine a few months ago off of CentOS 7. I am pasting `doveconf -n` at the bottom of this email. Everything is working. However, I'm trying to clean up warnings in the logs, and just discovered that I'm not managing home directories properly. (c/f https://wiki.dovecot.org/VirtualUsers/Home) This is in the logs: > Jun 28 06:09:50 mail.example.com dovecot: imap(email(a)example.com)<3786><fICEJCKpbfatQHg1>: Error: stat(/var/vmail/example.com/email@example.com/.dovecot.sieve/tmp) failed: Not a directory Can I please get a sanity check? To resolve, I've come up with a bash loop to create a home folder, and fix the existing structure for each mailbox on the system. I ran this for 1 of the domains on the system. > for i in */ ; do mv "$i" mail; mkdir "$i"; mv mail "$i"; mv "$i"/.dovecot* "$i"; done Then, I would simply edit /etc/dovecot/conf.d/10-mail.conf so that it looks like this: > mail_home = /var/vmail/%d/%u > mail_location = maildir:/var/vmail/%d/%u/mail To confirm, should all of the 'hidden' dovecot files be moved to the user's new home folder like I'm trying to do in the above script? Or are there other files that I will need to move? After running that loop above on a test server (don't worry, I would never do this in production without testing), one of the mailbox's home folder on the server looks like this: > total 56 > drwxr-xr-x 4 vmail vmail 4096 Jun 28 06:19 . > drwx------ 6 vmail vmail 4096 Jun 28 06:09 .. > -rw------- 1 vmail vmail 54 Jul 4 2019 .dovecot.lda-dupes > lrwxrwxrwx 1 vmail vmail 21 May 26 2016 .dovecot.sieve -> sieve/roundcube.sieve > -rw------- 1 vmail vmail 0 Oct 17 2016 .dovecot.sieve.log > -rw------- 1 vmail vmail 218 Jul 6 2019 .dovecot.svbin > drwx------ 277 vmail vmail 32768 Jun 28 06:19 mail > drwx------ 3 vmail vmail 4096 Feb 2 17:31 sieve ... and connecting to that mailbox over Thunderbird seems to be working fine. But I want to make sure I'm not missing anything. Here is my doveconf -n, with identifying information snipped out: > root@mail:# doveconf -n > # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.7.2 () > # OS: Linux 5.4.0-39-generic x86_64 Ubuntu 20.04 LTS ext4 > # Hostname: {snip} > auth_mechanisms = plain login > mail_location = maildir:/var/vmail/%d/%u > 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 { > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > 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:~/sieve;active=~/.dovecot.sieve > } > protocols = imap pop3 lmtp sieve > service auth-worker { > user = $default_internal_user > } > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0666 > user = postfix > } > unix_listener auth-userdb { > group = postfix > mode = 0666 > user = vmail > } > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0666 > user = postfix > } > } > ssl = required > ssl_ca = </etc/ssl/certs/snip.ca-bundle > ssl_cert = </etc/ssl/certs/snip.crt > ssl_cipher_list = ALL:!LOW:!SSLv3:!EXP:!aNULL:!MD5 > ssl_key = # hidden, use -P to show it > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%d/%u > driver = static > } Sent with ProtonMail Secure Email.

1 1

Pigeonhole 0.5.11 released
by Aki Tuomi 13 Aug '20

13 Aug '20

We are pleased to release pigeonhole 0.5.11. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.1… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.1… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * managesieve: managesieve_max_line_length setting is now a "size" type instead of just number of bytes. This allows using e.g. "64k" as the value. - lib-sieve: When folding white space is used in the Message-ID header, it is not stripped away correctly before the message ID value is used, causing e.g. garbled log lines at delivery.

5 9

Problems, virtual and alias, Dovecot, Neomutt, OpenSMTPD on OpenBSD
by Chris Bennett 12 Aug '20

12 Aug '20

I'm having some problems. I'm using virtual users with real domains. That is working, but the folders are not showing up properly in neomutt, for both virtual users and system users. When I use K9 on Android, the folders show up correctly. Sending is working, but I don't have auth setup right on OpenSMTPD, so I'm sending locally, not remotely (including from K9, which can't login to send). That's really probably not relevant here, but I thought I'd mention it. I'm a bit embarrassed to admit that after having to move everything off of one server super rapidly to another already working to save money, I realized that I had made some wrong assumptions. Oops but +1 for me. So now I know what to fix there and why. If anyone has a good .neomuttrc or hints, I would appreciate that help. But I can save that problem for the neomutt mailing list. Here are copies of my doveconf -n, dovecot/passwd, vaddr, vdomains and vusers. Obscured of course. Plus the DNS IP's of this server and the one other server, which isn't running dovecot yet. Everything is using maildir on both servers. DNSSEC on all but bennettconstruction.us and mail.bennettconstruction.us Is there anything wrong, missing or screwed up here? I do intend to use encrypted passwds once I get submission to OpenSMTPD working and add the right ports for that. So far, I really haven't found the three different dovecot logs to be particularly helpful, but I can send excerpts of those if helpful. Thanks. I appreciate any help. This is my first go at IMAP and someone sent me some config info a while ago, which really helped a ton. I really like this software, I used it previously a few years ago for POP3. I do find the documentation missing some sample configs with some explanations for why and how. At some point I would like to add some more complicated things, but I don't understand what some config options really do. I also understand that documentation vs. code work are always in conflict. 28 hour days would really help! :-} doveconf -n: # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: OpenBSD 6.7 amd64 ffs # Hostname: cowboyup.xyz auth_debug = yes auth_debug_passwords = yes auth_socket_path = /var/dovecot/auth-userdb auth_verbose = yes auth_verbose_passwords = sha1 debug_log_path = /var/log/dovecot-debug.log first_valid_uid = 1000 hostname = consulting-diy-construction.com imap_id_log = * imap_id_send = * info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_client_workarounds = whitespace-before-path mailbox-for-path log_path = /var/log/dovecot.log login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_debug = yes mail_location = maildir:/home/vmail/%n@%d/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 mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes } passdb { driver = bsdauth } passdb { args = /etc/dovecot/passwd driver = passwd-file } plugin { mail_log_fields = uid box msgid size sieve = file:~/sieve;active=~/.dovecot.sieve } postmaster_address = postmaster(a)consulting-diy-construction.com protocols = imap lmtp sieve service auth-worker { user = root } service auth { unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 1 } service imap { process_limit = 1024 } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl_dh = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/home/vmail/%n@%d driver = static } verbose_ssl = yes protocol lmtp { mail_plugins = } protocol imap { mail_max_userip_connections = 10 mail_plugins = } protocol lda { mail_plugins = } local 172.107.198.230 { ssl_cert = </etc/ssl/mx.no-seas-necio.ninja.fullchain.pem ssl_key = # hidden, use -P to show it } local 172.107.198.231 { ssl_cert = </etc/ssl/mail.freedomforlife.rocks.fullchain.pem ssl_key = # hidden, use -P to show it } local 172.107.198.229 { ssl_cert = </etc/ssl/mail.consulting-diy-construction.com.fullchain.pem ssl_key = # hidden, use -P to show it } vaddr: #root(a)consulting-diy-construction.com #abuse(a)consulting-diy-construction.com #security(a)consulting-diy-construction.com #hostmaster(a)consulting-diy-construction.com webmaster(a)consulting-diy-construction.com postmaster(a)consulting-diy-construction.com ch(a)consulting-diy-construction.com fr(a)consulting-diy-construction.com ro(a)consulting-diy-construction.com di(a)no-seas-necio.ninja kl(a)no-seas-necio.ninja ff(a)freedomforlife.rocks ff6(a)freedomforlife.rocks chris-dvcot(a)freedomforlife.rocks postmaster(a)freedomforlife.rocks postmaster(a)consulting-diy-construction.com vdomains: consulting-diy-construction.com no-seas-necio.ninja freedomforlife.rocks bennettconstruction.us vusers: root(a)consulting-diy-construction.com ro(a)consulting-diy-construction.com root(a)cowboyup.xyz ro(a)consulting-diy-construction.com root(a)freedomforlife.rocks ro(a)consulting-diy-construction.com webmaster(a)consulting-diy-construction.com ro(a)consulting-diy-construction.com chris(a)cowboyup.xyz ro(a)consulting-diy-construction.com chris(a)consulting-diy-construction.com ro(a)consulting-diy-construction.com fr(a)cowboyup.xyz vmail fr fr(a)consulting-diy-construction.com ro ro(a)consulting-diy-construction.com fr(a)consulting-diy-construction.com vmail ro(a)consulting-diy-construction.com vmail di dirkly(a)no-seas-necio.ninja kl(a)no-seas-necio.ninja vmail di(a)no-seas-necio.ninja vmail chris-dvcot(a)freedomforlife.rocks vmail postmaster(a)freedomforlife.rocks vmail postmaster(a)consulting-diy-construction.com vmail dovecot/passwd: #ro@consulting-diy-construction.com:{BLF-CRYPT}$2b$MEe:::::: #ro@cowboyup.xyz:{BLF-CRYPT}$2b$MEe:::::: #ch@consulting-diy-construction.com:{BLF-CRYPT}$2b$MEe:::::: #ch@cowboyup.xyz:{BLF-CRYPT}$2b$MEe:::::: #di@no-seas-necio.ninja:{BLF-CRYPT}$2b$9QZ. #vmail:{BLF-CRYPT}$2b$fG6:::::: ro@consulting-diy-construction.com:{PLAIN}46:::::: ro@cowboyup.xyz:{PLAIN}46:::::: ro:{PLAIN}46:::::: fr@consulting-diy-construction.com:{PLAIN}46:::::: fr@cowboyup.xyz:{PLAIN}46y:::::: fr:{PLAIN}Xella#%46:::::: di:{PLAIN}Xella#%46:::::: di@no-seas-necio.ninja:{PLAIN}46:::::: di@consulting-diy-construction.com:{PLAIN}46:::::: di@cowboyup.xyz:{PLAIN}46:::::: kl@no-seas-necio.ninja:{PLAIN}46:::::: chris-dvcot@freedomforlife.rocks:{PLAIN}68:::::: postmaster@freedomforlife.rocks:{PLAIN}68:::::: postmaster@consulting-diy-construction.com:{PLAIN}68:::::: This server: OpenBSD 6.7-current (GENERIC.MP) #22: Tue Aug 11 21:29:51 MDT 2020 172.107.198.226 cowboyup.xyz 172.107.198.227 no-seas-necio.ninja 172.107.198.228 consulting-diy-construction.com 172.107.198.229 mail.consulting-diy-construction.com 172.107.198.230 mx.no-seas-necio.ninja 172.107.198.231 mail.freedomforlife.rocks 172.107.198.232 mail.bennettconstruction.us 172.107.198.233 bennettconstruction.us 172.107.198.234 capuchado.com 172.107.198.235 strengthcouragewisdom.rocks Other server: OpenBSD 6.7-current (GENERIC.MP) #22: Tue Aug 11 21:29:51 MDT 2020 172.107.202.138 freedomforlife.rocks 172.107.202.139 mail.no-seas-necio.ninja 172.107.202.140 mail.cowboyup.xyz 172.107.202.141 mail.strengthcouragewisdom.rocks 172.107.202.142 mail.capuchado.com

1 0

Can't move/delete folder "Renaming not supported across conflicting directory permissions"
by Johannes Rohr 12 Aug '20

12 Aug '20

Dear all, several users have reported that they were unable to move/delete folders using Thunderbird and they got the message "Renaming not supported across conflicting directory permissions". When I google for this message, I see hints like "your mail may not be all on the same volume", but here this is definitely not the case. All mail is in /var/mail/virtual and owned by mail:mail Curiously, when I tried the same operation in Roundcube, there was no error reported, so something about the combination of Thunderbird and Dovecot seems to be causing the error. Does anyone have advise on how I should go about tracking down the cause of the error? Thanks a lot in advance! Johannes

3 2

Replication: Mails deleted over POP3 aren't deleted at the same time from the second server
by Lukas 12 Aug '20

12 Aug '20

Hi, I have two Dovecot 2.3.8 (on RHEL 8.2) servers. Replication works great except in one situation. What works: * If one server receives an email, it is immediately available on the other server. * If an email is deleted via IMAP from one server, it is immediately deleted from the other server. What doesn't work: If a user retrieves (download + delete) an email via POP3 (Thunderbird), then the mail is only deleted from the server from which it was downloaded but not from the other server. The email is only deleted from the other server in the following situations: * If a new email arrives (triggers a sync action) * When the next full sync happens (I temporarily set replication_full_sync_interval to "1 hour") * When forcing a manual full sync (doveadm replicator replicate user_name) If I activate debug logging (mail_debug = yes), I can immediately see a replication action when an email is deleted via IMAP. However, when an email is deleted via POP3, nothing is logged (because no replication happens). Does anyone have an idea why deleting an email via POP3 isn't replicated and how to configure this? Thanks for your help. Lukas My config (it is identical on on both servers, except of the "mail_replica" and "address" parameters): auth_mechanisms = plain login auth_username_format = %n doveadm_password = # hidden, use -P to show it doveadm_port = 12345 login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_gid = vmail mail_home = /var/spool/dovecot/%u mail_location = sdbox:/var/spool/dovecot/%u mail_plugins = " notify replication" 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 namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/deny.%s deny = yes driver = passwd-file } passdb { args = scheme=SSHA512 username_format=%n /etc/dovecot/passwd driver = passwd-file } plugin { mail_replica = tcps:server2.example.com:12345 sieve = ~/sieve/.dovecot.sieve } protocols = imap pop3 lmtp sieve replication_full_sync_interval = 1 hours service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = $default_internal_user } service doveadm { inet_listener { address = ... port = 12345 ssl = yes } user = vmail } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = ... port = 993 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { address = ... port = 4190 } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = ... port = 995 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/server1.example.com/fullchain.pem ssl_client_ca_file = /etc/pki/tls/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_options = no_compression syslog_facility = local5 userdb { args = username_format=%n /etc/dovecot/passwd driver = passwd-file result_failure = return-fail result_internalfail = return-fail } protocol sieve { ssl = required } protocol lmtp { mail_plugins = " notify replication sieve" }

1 0

auth debug log entry incorrect
by Tomas Habarta 12 Aug '20

12 Aug '20

Hello, just want to report a slightly confusing log entry on auth-debug level I have encountered while setting up Kerberos auth. Users are stored in ldap, Kerberos makes use of the same ldap as its backend, goal was to enable users to use their principals in addition to simple login with mailAddress/userPassword combination. Sample entry relevant attrs: --- mailAddress: sn.gn(a)example.com mailDeliveryAddress: 123456(a)example.com uid: u123456 krbPrincipalName: u123456@REALM krbPrincipalName: user123456@REALM krbPrincipalName: alias@REALM --- with pass_attrs = =user=%{ldap:mailDeliveryAddress},=password=%{ldap:userPassword},=k5principals=%{ldap:krbPrincipalName} I can see incorrectly logged ldap search result for krbPrincipalName attr as it is written 3 times with the same value -- number is correct, values should differ. All is working ok as expected, but was a bit confusing while tuning /etc/krb5.conf on non-working remote client whilst local client had no issues (mutt). Anyway, to eventually save someone's time, this seems to be easy enough to be fixed. Thanks for this great software, Tomas dovecot[13337]: auth: Debug: ldap(sn.gn(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): result: mailDeliveryAddress=123456(a)example.com krbPrincipalName=u123456@REALM,u123456@REALM,u123456@REALM; krbPrincipalName,mailDeliveryAddress unused dovecot[13337]: auth: Debug: ldap(sn.gn(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): username changed sn.gn(a)example.com -> 123456(a)example.com dovecot[13337]: auth: Warning: ldap(123456(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): Multiple values found for 'krbPrincipalName', using value 'u123456@REALM' dovecot[13337]: auth: Debug: ldap(123456(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): Finished passdb lookup dovecot[13337]: auth: Debug: gssapi(123456(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): authorized by k5principals field: u123456@REALM dovecot[13337]: auth: Debug: auth(123456(a)example.com,10.0.9.14,<6xHsI62sJoWT+2C4>): Auth request finished dovecot[13337]: auth: Debug: client passdb out: OK 1 user=123456(a)example.com k5principals=u123456@REALM original_user=u123456@REALM dovecot[13337]: auth: Debug: master in: REQUEST 3251372033 13340 1 3bbd5f6931fe4e949e7822657da9e33b session_pid=13343 request_auth_token # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-193.14.2.el8_2.x86_64 x86_64 CentOS Linux release 8.2.2004 (Core)

1 0

CVE-2020-12674: Specially crafted RPA authentication message crashes auth
by Aki Tuomi 12 Aug '20

12 Aug '20

Open-Xchange Security Advisory 2020-08-12 Affected product: Dovecot IMAP server Internal reference: DOP-1869 (Bug ID) Vulnerability type: CWE-126 (Buffer over-read) Vulnerable version: 2.2 Vulnerable component: auth Fixed version: 2.3.11.3 Report confidence: Confirmed Solution status: Fix available Vendor notification: 2020-05-03 Researcher credit: Orange from DEVCORE team CVE reference: CVE-2020-12674 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vulnerability Details: Dovecot's RPA mechanism implementation accepts zero-length message, which leads to assert-crash later on Risk: An adversary can use this vulnerability to crash dovecot auth process repeatedly, preventing login. Steps to reproduce: (echo 'AUTH RPA'; echo -ne '\x60\x11\x06\x09\x60\x86\x48\x01\x86\xf8\x73\x01\x01\x01\x00\x04\x00\x00\x01' | base64 -w 0; echo ; echo -ne '\x60\x11\x06\x09\x60\x86\x48\x01\x86\xf8\x73\x01\x01\x00\x03A@A\x00' | base64 -w 0; echo ; echo QUIT) | nc 127.0.0.1 110 Workaround: Disable RPA authentication. Solution: Upgrade to fixed version. Best regards, Aki Tuomi Open-Xchange oy

1 0

CVE-2020-12673: Specially crafted NTML package can crash auth service
by Aki Tuomi 12 Aug '20

12 Aug '20

Open-Xchange Security Advisory 2020-08-12 Affected product: Dovecot IMAP server Internal reference: DOP-1870 (Bug ID) Vulnerability type: CWE-789 (Uncontrolled Memory Allocation) Vulnerable version: 2.2 Vulnerable component: auth Fixed version: 2.3.11.3 Report confidence: Confirmed Solution status: Fix available Vendor notification: 2020-05-03 CVE reference: CVE-2020-12673 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vulnerability Details: Dovecot's NTLM implementation does not correctly check message buffer size, which leads to reading past allocation which can lead to crash. Risk: An adversary can use this vulnerability to crash dovecot auth process repeatedly, preventing login. Steps to reproduce: (echo 'AUTH NTLM'; echo -ne 'NTLMSSP\x00\x01\x00\x00\x00\x00\x02\x00\x00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA' | \ base64 -w0 ;echo ;echo -ne 'NTLMSSP\x00\x03\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00AA\x00\x00\x41\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00orange\x00'| \ base64 -w0;echo ; echo QUIT) | nc 127.0.0.1 110 Workaround: Disable NTLM authentication. Solution: Upgrade to fixed version. Best regards, Aki Tuomi Open-Xchange oy

1 0

CVE-2020-12100: Receiving mail with deeply nested MIME parts leads to resource exhaustion.
by Aki Tuomi 12 Aug '20

12 Aug '20

Open-Xchange Security Advisory 2020-08-12 Affected product: Dovecot IMAP server Internal reference: DOP-1849 (Bug ID) Vulnerability type: Uncontrolled recursion (CWE-674) Vulnerable version: 2.0 Vulnerable component: submission, lmtp, lda Fixed version: 2.3.11.3 Report confidence: Confirmed Solution status: Fix available Vendor notification: 2020-04-23 CVE reference: CVE-2020-12100 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vulnerability Details: Receiving mail with deeply nested MIME parts leads to resource exhaustion as Dovecot attempts to parse it. Risk: Malicious actor can cause denial of service to mail delivery by repeatedly sending mails with bad content. Workaround: Limit MIME structures in MTA. Solution: Upgrade to fixed version. Best regards, Aki Tuomi Open-Xchange oy

1 0

Dovecot v2.3.11.3 released
by Aki Tuomi 12 Aug '20

12 Aug '20

We are pleased to release v2.3.11.3. Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.11.3.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.11.3.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- * CVE-2020-12100: Parsing mails with a large number of MIME parts could have resulted in excessive CPU usage or a crash due to running out of stack memory. * CVE-2020-12673: Dovecot's NTLM implementation does not correctly check message buffer size, which leads to reading past allocation which can lead to crash. * CVE-2020-10967: lmtp/submission: Issuing the RCPT command with an address that has the empty quoted string as local-part causes the lmtp service to crash. * CVE-2020-12674: Dovecot's RPA mechanism implementation accepts zero-length message, which leads to assert-crash later on. * Events: Fix inconsistency in events. See event documentation in https://doc.dovecot.org. * imap_command_finished event's cmd_name field now contains "unknown" for unknown commands. A new "cmd_input_name" field contains the command name exactly as it was sent. * lib-index: Renamed mail_cache_compress_* settings to mail_cache_purge_*. Note that these settings are mainly intended for testing and usually shouldn't be changed. * events: Renamed "index" event category to "mail-index". * events: service:<name> category is now using the name from configuration file. * dns-client: service dns_client was renamed to dns-client. * log: Prefixes generally use the service name from configuration file. For example dict-async service will now use "dict-async(pid): " log prefix instead of "dict(pid): " * *-login: Changed logging done by proxying to use a consistent prefix containing the IP address and port. * *-login: Changed disconnection log messages to be slightly clearer. + dict: Add events for dictionaries. + lib-index: Finish logging with events. + oauth2: Support local validation of JWT tokens. + stats: Add support for dynamic histograms and grouping. See https://doc.dovecot.org/configuration_manual/stats/. + imap: Implement RFC 8514: IMAP SAVEDATE + lib-index: If a long-running transaction (e.g. SORT/FETCH on a huge folder) adds a lot of data to dovecot.index.cache file, commit those changes periodically to make them visible to other concurrent sessions as well. + stats: Add OpenMetrics exporter for statistics. See https://doc.dovecot.org/configuration_manual/stats/openmetrics/. + stats: Support disabling stats-writer socket by setting stats_writer_socket_path="". - auth-worker: Process keeps slowly increasing its memory usage and eventually dies with "out of memory" due to reaching vsz_limit. - auth: Prevent potential timing attacks in authentication secret comparisons: OAUTH2 JWT-token HMAC, imap-urlauth token, crypt() result. - auth: Several auth-mechanisms allowed input to be truncated by NUL which can potentially lead to unintentional issues or even successful logins which should have failed. - auth: When auth policy returned a delay, auth_request_finished event had policy_result=ok field instead of policy_result=delayed. - auth: auth process crash when auth_policy_server_url is set to an invalid URL. - auth: Lua passdb/userdb leaks stack elements per call, eventually causing the stack to become too deep and crashing the auth or auth-worker process. - dict-ldap: Crash occurs if var_expand template expansion fails. - dict: If dict client disconnected while iteration was still running, dict process could have started using 100% CPU, although it was still handling clients. - doveadm: Running doveadm commands via proxying may hang, especially when doveadm is printing a lot of output. - imap: "MOVE * destfolder" goes to a loop copying the last mail to the destination until the imap process dies due to running out of memory. - imap: Running "UID MOVE 1:* Trash" on an empty folder goes to infinite loop. - imap: SEARCH doesn't support $. - lib-compress: Buffer over-read in zlib stream read. - lib-dns: If DNS lookup times out, lib-dns can cause crash in calling process. - lib-index: Fixed several bugs in dovecot.index.cache handling that could have caused cached data to be lost. - lib-index: Writing to >=1 GB dovecot.index.cache files may cause assert-crashes: Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) - lib-mail: v2.3.11 regression: MIME parts not returned correctly by Dovecot MIME parser. - lib-ssl-iostream: Fix buggy OpenSSL error handling without assert-crashing. If there is no error available, log it as an error instead of crashing: Panic: file iostream-openssl.c: line 599 (openssl_iostream_handle_error): assertion failed: (errno != 0) - lib-ssl-iostream: ssl_key_password setting did not work. - pop3-login: Login didn't handle commands in multiple IP packets properly. This mainly affected large XCLIENT commands or a large SASL initial response parameter in the AUTH command. - pop3: pop3_deleted_flag setting was broken, causing: Panic: file seq-range-array.c: line 472 (seq_range_array_invert): assertion failed: (range[count-1].seq2 <= max_seq) - pop3-login: Login would fail with "Input buffer full" if the initial response for SASL was too long. - submission: A segfault crash may occur when the client or server disconnects while a non-transaction command like NOOP or VRFY is still being processed. - virtual: Copying/moving mails with IMAP into a virtual folder assert-crashes: Panic: file cmd-copy.c: line 152 (fetch_and_copy): assertion failed: (copy_ctx->copy_count == seq_range_count(&copy_ctx->saved_uids))

1 0

Client shows incorrect message counts
by Antonio Leding 11 Aug '20

11 Aug '20

Hello all… First, a disclaimer…I am aware that this is very likely not a Dovecot related issue but I am truly pulling whatever hair I have left out of my head and given the brain-power of this mailer, I thought someone might know what is going in here. The issues is this… I check the message counts for a given account using doveadm and get a given number. I then configure the same account in 3 mail clients: Apple Mail, Mailmate, and Thunderbird. Both the Mailmate and Thunderbird message counts match exactly with the doveadm numbers. Apple Mail is low in almost all cases. I have tried every idea I have found including: — Delete and recreate the mail account — Rebuild mailbox — Resync mailbox — Reindex Spotlight — Removing the "~/Library/Mail/V*/Envelope*” files; restart Mail — Remove the entire "~/Library/Mail/V*” directory; restart Mail So, at wit’s end and again, apologies for this not being a Dovecot-centric issue but I know you are all on top of this stuff and may have an idea… Thanks in advance...

2 7

Thanks, got replys
by Chris Bennett 11 Aug '20

11 Aug '20

I've got a mix of some receive only, some send only. I tried to slam together two different configs really fast. This helped. I'll look things over and post some configs after a bit. Thanks again! Chris Bennett

1 0

Test on sending only
by Chris Bennett 10 Aug '20

10 Aug '20

I had to move off of a server to this one too fast. Having problems If this goes through, if someone could reply to chris(a)bennettconstruction.us instead of on-list. Thanks, Chris Bennett

1 0

IMAP Permissions per IP
by Jorge Bastos 10 Aug '20

10 Aug '20

Howdy, Is it possible to define IMAP permissions per IT? What i would like to do is: * IP 1.1.1.1 IS THE ONLY ONE that has permission for EXPUNGE Is it possible? Thanks in advanced,

2 1

is there a way to run doveadm expunge with exception?
by teacup 09 Aug '20

09 Aug '20

is there a way to run this command but with exception to not delete the FLAGGED email? doveadm expunge -u user(a)email.com mailbox Inbox SENTBEFORE 90d -- Sent from: http://dovecot.2317879.n4.nabble.com/

2 2

IPv6 auth failed
by Lefteris Tsintjelis 09 Aug '20

09 Aug '20

I am using latest Windows Thunderbird 68.11.0 and dovecot 2.3.10.1_2 with FreeBSD 12.1-RELEASE-p8. Whenever I enable dovecot IPv6 and I try to login I get auth failed. Aug 09 08:36:11 imap-login: Info: Disconnected: Inactivity (auth failed, 2 attempts in 180 secs): user=<user(a)domain.com>, method=CRAM-MD5, rip=1:2:3:4::5, lip=1:2:3:6::7, TLS, session=<HZeFLGusb8IgAQZ8LNQAEgAAAAAAAAAC> Switching dovecot back to IPv4 only (listen = *) starts to work as expected. Roundcube seems to also have the same problem whenever dovecot IPv6 is enabled.

2 4

Re: [EXT] Re: mail_crypt folder keys without sql database
by Aki Tuomi 06 Aug '20

06 Aug '20

> On 06/08/2020 13:52 secure.light.0417.road <secure.light.0417.road(a)protonmail.com> wrote: > > > Ah, right. The hashed password can't be used to encrypt. > > I want to remove possibility to decrypt mails using materials in mail servers in VPS. I've thought about below scenario: > > 1. The client generates asymmetric keys in local. > 2. The client sends the public key to the dovecot in the mail server. > 3. The dovecot generates a symmetric key. > 4. The dovecot encrypts a received mail with the symmetric key. > 5. The dovecot also encrypts the symmetric key with the public key. > 6. The client get the mail and encrypted symmetric key from server into local and decrypts it using local private key. > You probably want to use PGP then. > Instead of 1 and 2, the way like "the dovecot generates all 3 and removes only private key", can be considered with docker image deployment. mail_crypt plugin is primarily intended to protect storage medium, and not end user as such. While it does support this, it's not perfect tool for it, and can be bit difficult to set up. Dovecot does not support client-supplied private keys. > > Is it possible with mail_crypt? > > narangd > Aki p.s. please keep responses on the list.

1 0

Re: [EXT] Re: mail_crypt folder keys without sql database
by Aki Tuomi 06 Aug '20

06 Aug '20

mail_crypt_private_password cannot be hashed, as it's used to encrypt the key. Aki > On 06/08/2020 10:06 secure.light.0417.road <secure.light.0417.road(a)protonmail.com> wrote: > > > I've tried to append the field "userdb_mail_crypt_private_password=<same-hashed-password-in-passwd-file>" to the end of each user line in userdb as passwd-file. And use the command below to generate keys. > > doveadm -o plugin/mail_crypt_private_password=<not-hashed-user-password> mailbox cryptokey generate -u <username> -U > > I confirmed mail encryption work properly. > > Also I've compared two "dovecot-attribute" files with and without "mail_crypt_require_encrypted_user_key = yes". Seemingly they have no difference. How to check that the private key in dovecot-attribute be encrypted properly? > > narangd > > Sent with ProtonMail Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Thursday, August 6, 2020 1:03 AM, Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: > > > > On 05/08/2020 18:45 secure.light.0417.road secure.light.0417.road(a)protonmail.com wrote: > > > Hello, > > > Can the mail_crypt "folder keys" feature be used with encrypted user keys in passwd-file without sql database? It seems that there is no guide in the docs. > > > Best regards, > > > narangd > > > > Dovecot stores folder and user keys into mail_attribute_dict. This does not have to be SQL database. > > > > You can also add `userdb_mail_crypt_private_password` into passwd-file to provide it if you use passwd-file as userdb. > > > > Aki

1 0

director backend failover?
by Markus Raps 06 Aug '20

06 Aug '20

Hi, i have short question for automatic failover, directors <-> backends is this still the way to go? -> https://dovecot.org/pipermail/dovecot/2012-October/138816.html https://github.com/brandond/poolmon -- Mit freundlichen Grüßen / best regards Markus Raps

1 0

mail_crypt folder keys without sql database
by secure.light.0417.road 05 Aug '20

05 Aug '20

Hello, Can the mail_crypt "folder keys" feature be used with encrypted user keys in passwd-file without sql database? It seems that there is no guide in the docs. Best regards, narangd

2 1

Migration issue
by Kishore Potnuru 05 Aug '20

05 Aug '20

Hi All, I have tried the below command to migrate the data from the old server(dovecot version: 2.0.9) to new servers(dovecot version: 2.2.36 (1f10bfa63)). But it's throwing an error. old server name: production1 new server1 name: production2 (for HA/Replication) new server2 name: production3 (for HA/Replication) I have configured replication between production2 and production3, which is working fine. The issue is, the below command I am trying is from production2 server and trying to take the data from production1 server. ------------- [root@production2 log]# doveadm backup -a All -R -u kishore(a)test.testorg.com imapc: dsync(kishore(a)test.testorg.com): Info: imapc(production1.testorg.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore(a)test.testorg.com): Warning: imapc(production1.testorg.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore(a)test.testorg.com): Info: imapc(production1.testorg.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014) dsync(kishore(a)test.testorg.com): Error: imapc(production1.testorg.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting dsync(kishore(a)test.testorg.com): Error: User initialization failed: imapc: Login to production1.testorg.com failed: Disconnected from server [root@production2 log]# -------------- I looked into the production1 (old server) logs. I see the below error. =============== Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are no passdbs Jul 28 11:14:23 master: Error: service(auth): command startup failed, throttling =============== after the above error, I have commented "pass=yes" in production1 (old server) server, then I see the below error. ================ Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one Jul 28 11:17:10 master: Error: service(auth): command startup failed, throttling =============== Please suggest me on fixing the issue. Adding the dovecot.conf configuration from old and new servers: ========================================= My old server dovecot.conf (production1): ========================================= disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/z1dev/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file master = yes pass = yes } pop3_uidl_format = %g protocols = pop3 imap ssl = yes ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/z1dev/mail/virtual/%d/%n driver = static } mail_debug = no verbose_ssl = no ========================================= My New server dovecot.conf(production2): ========================================= disable_plaintext_auth = no listen = * log_path = /var/log/dovecot.log mail_location = maildir:/z1devenv/mail/virtual/%d/%n/Maildir/ passdb { args = /etc/dovecot/passwd driver = passwd-file } pop3_uidl_format = %g protocols = pop3 imap ssl = yes ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = uid=vmail gid=vmail home=/z1devenv/mail/virtual/%d/%n driver = static } mail_debug = yes verbose_ssl = no # Enable the replication plugin globally mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 } dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u plugin { mail_replica = remote:vmail@production3.testorg.com } service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service replicator { unix_listener replicator-doveadm { mode = 0600 user = vmail } } replication_max_conns = 10 imapc_host = production1.testorg.com imapc_password = vmail imapc_master_user = vmail imapc_user = %u =================================== Please let me know if you need any other details. Thanks, Kishore Potnuru

3 8

How to access mailbox metadata in Lua push driver
by Ralf Becker 04 Aug '20

04 Aug '20

We're currently using the OX push driver, which is straight forward (simple web hook) and allows to store (multiple) push tokens of our webmailer direct in mailbox metadata. Only drawback is that it only supports new arriving mails in the INBOX, even mails moved via Sieve to other folders are NOT reported. Therefore we updated now to Dovecot 2.3(.10.1) to also get mails moved by user or Sieve scripts, deleted mails or flag changes. As far as I read the example Lua scripts and (a little) the Dovecot C code, the nice indirection of using mailbox metadata to a) enable push and b) store push tokens (modify reported user attribute with them) does NOT exist in the Lua driver by default. So my questions is: how can I access mailbox metadata from within the Lua script, to make eg. the example script behave like the OX driver with user_from_metadata set? I'm happy to update the Lua examples, if that's any help ... Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 7

Question about migration 2.2 - 2.3 with replication
by Ralf Becker 03 Aug '20

03 Aug '20

Do both replication nodes need to be updated at the same time? Or can a 2.2(.36.4) node replicate with a 2.3(.10.1)? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 1

Trying to use solr
by Francis Augusto Medeiros-Logeay 02 Aug '20

02 Aug '20

Hi, I am finally trying to use an fts engine with dovecot. My version is 2.3.7.2 under Ubuntu 20.04. I installed solr 7.7.3 and then 8.6.0 to see if this was a version-related error. I copied the schema from 7.7.0 as many people said this was fine. I get the following error when trying to reindex a user's mailbox: doveadm(francis(a)francisaugusto.com): Error: fts_solr: Indexing failed: 400 Bad Request doveadm(francis(a)francisaugusto.com): Error: Mailbox INBOX: Transaction commit failed: FTS transaction commit failed: backend deinit doveadm(francis(a)francisaugusto.com): Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Disconnected: Connection closed (fd=10) On Solr I get this error: org.apache.solr.common.SolrException: Exception writing document id 210/9fd7941e8297d25d91600000c3fdd3da/francis(a)francisaugusto.com to the index; possible analysis error: cannot change field "box" from index options=DOCS_AND_FREQS_AND_POSITIONS to inconsistent index options=DOCS at org.apache.solr.update.DirectUpdateHandler2.addDoc(DirectUpdateHandler2.java:246) Parallel to this, I got some log messages on Solr before attempting to reindex the user (sorry for the garbadged text: TIME (LOCAL) LEVEL CORE LOGGER MESSAGE 7/21/2020, 6:38:47 PM WARN false x:dovecot SolrResourceLoader Solr loaded a deprecated plugin/analysis class [solr.TrieLongField]. Please consult documentation how to replace it accordingly. 7/21/2020, 6:38:47 PM WARN false x:dovecot SolrResourceLoader Solr loaded a deprecated plugin/analysis class [solr.SynonymFilterFactory]. Please consult documentation how to replace it accordingly. 7/21/2020, 6:38:47 PM WARN false x:dovecot SolrResourceLoader Solr loaded a deprecated plugin/analysis class [solr.WordDelimiterFilterFactory]. Please consult documentation how to replace it accordingly. 7/22/2020, 6:43:46 PM ERROR false x:dovecot RequestHandlerBase java.lang.IllegalStateException: Type mismatch: uid was indexed as SORTED_NUMERIC 7/22/2020, 6:43:46 PM ERROR false x:dovecot HttpSolrCall null:java.lang.IllegalStateException: Type mismatch: uid was indexed as SORTED_NUMERIC 7/22/2020, 6:43:49 PM ERROR false x:dovecot RequestHandlerBase java.lang.IllegalStateException: Type mismatch: uid was indexed as SORTED_NUMERIC 7/22/2020, 6:43:49 PM ERROR false x:dovecot HttpSolrCall null:java.lang.IllegalStateException: Type mismatch: uid was indexed as SORTED_NUMERIC 7/22/2020, 6:43:56 PM ERROR false x:dovecot RequestHandlerBase java.lang.IllegalStateException: Type mismatch: uid was indexed as SORTED_NUMERIC 7/22/2020, 6:43:56 PM ERROR false x:dovecot HttpSolrCall null:java.lang.IllegalSta Could anyone point me the right direction to make this work? Best,

3 5

Warning: Expunged message reappeared, giving a new UID with FTS enabled
by symphorien_dovecot＠xlumurb.eu 01 Aug '20

01 Aug '20

Hello, In some conditions with FTS enabled I get this warning: Warning: Expunged message reappeared, giving a new UID Here is how I can reproduce it: I have a test setup with a (postfix) virtual alias multi-alias(a)example.com which delivers emails to user1@ and user2@ If * I send an email to multi-alias@ * expunge user1@ mailbox with doveadm expunge -u user1(a)example.com mailbox Inbox ALL then the warning fires. If * FTS plugin is disabled (I tried with squat and xapian), or * multi-alias@ redirects to only user1@ * I send the email directly to user1@ then no warning. Can I just ignore the warning ? dovecot -n: # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: Linux 5.4.51 x86_64 ext4 # Hostname: server auth_debug = yes auth_mechanisms = plain login base_dir = /run/dovecot2 default_internal_group = dovecot2 default_internal_user = dovecot2 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_access_groups = virtualMail mail_debug = yes mail_gid = virtualMail mail_location = maildir:/var/vmail/%d/%n:INDEX=/var/mailindex mail_plugins = " fts fts_squat quota" mail_uid = virtualMail 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 = prefix = separator = . } passdb { args = /run/dovecot2/passwd driver = passwd-file } plugin { fts = squat fts_autoindex = yes fts_autoindex_exclude = Junk fts_enforced = yes fts_squat = partial=4 full=10 imapsieve_mailbox1_before = file:/var/lib/dovecot/imap_sieve/report- spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/var/lib/dovecot/imap_sieve/report- ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * plugin = fts fts_squat quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=100G quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve = file:/var/sieve/%u/scripts;active=/var/sieve/%u/active.sieve sieve_after = /var/lib/dovecot/sieve/after sieve_default = file:/var/sieve/%u/default.sieve sieve_default_name = default sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /nix/store/7cdslbbivi1b3yagvw18k8m4nfs2n4ym- pipe_bin/pipe/bin sieve_plugins = sieve_imapsieve sieve_extprograms } pop3_uidl_format = %08Xv%08Xu protocols = sieve imap lmtp sendmail_path = /run/wrappers/bin/sendmail service auth { unix_listener auth { group = postfix mode = 0660 user = postfix } user = root } service lmtp { unix_listener dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service quota-status { client_limit = 1 executable = /nix/store/5b9lp6w8jzca86djawnk6aqc3n4p2mh0-dovecot- 2.3.10.1/libexec/dovecot/quota-status -p postfix inet_listener { port = 12340 } } ssl = required ssl_cert = </var/certs/cert-mail.example.com.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /run/dovecot2/passwd driver = passwd-file } verbose_ssl = yes protocol imap { mail_max_userip_connections = 100 mail_plugins = " fts fts_squat quota imap_quota imap_sieve" 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 Trash { auto = no special_use = \Trash } prefix = } } protocol pop3 { mail_max_userip_connections = 100 } protocol lmtp { mail_plugins = " fts fts_squat quota sieve" }

1 0

Migrating from qmail server, invalid option "o" in dsync
by Justin Coleman 01 Aug '20

01 Aug '20

Hi folks, I have an old server running qmail with several years of mails in maildir format I want to migrate to a new server, without requiring fresh client download of everything. Old server is debian 6(?). Local IP is 192.168.0.1. New server is Debian 10, local IP is 192.168.0.25. I have dovecot 2.3.4.1 (latest from apt stable) installed and apparently working - if I manually copy the home directory for my account, I can connect (using thunderbird) and I get all the emails appearing as new, forcing redownload. Seems like the new config is at least functional. I'm trying to follow the migration guide at https://wiki2.dovecot.org/Migration/Dsync, but I am getting an error message: root@newserver:~# doveadm backup -R -u _user_ -o pop3c_user=_user_ -o pop3c_password=_password_ backup: invalid option -- 'o' doveadm backup [-u <user>|-A] [-S <socket_path>] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest> Have tried this a couple different ways and according to everything i can find -o should be valid. Can anyone tell me what I'm doing wrong here? Thanks! # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: newserver.domain.com disable_plaintext_auth = no mail_location = maildir:~/Maildir mail_privileged_group = mail namespace { hidden = yes list = no location = pop3c: prefix = POP3-MIGRATION-NS/ } 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 { driver = pam } plugin { pop3_migration_mailbox = POP3-MIGRATION-NS/INBOX } pop3_uidl_format = %f pop3c_host = 192.168.0.1 protocols = " imap pop3" ssl = no 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 { driver = passwd } protocol doveadm { mail_plugins = " pop3_migration" }

4 6

imap doesn't like my passwd
by James 31 Jul '20

31 Jul '20

I spent days on this problem. I have dovecot setup to use SSL and IMAP. I also have a pop account that I had no trouble getting working. Both use PAM authentication on Linux. openssl s_client -connect localhost:993 a login test_user test_secure_password The response I got back was: a BAD Invalid characters in atom I changed the password to "abc" and it worked. The secure password used to work but it was a different architecture (x86_64 I think). The current architecture is armhf. It may be different versions of the software too. Dovecot v2.1.7

5 7

dovecot replication and pop3 deletion
by Nigel Metheringham 30 Jul '20

30 Jul '20

Hi, I am investigating the use of dovecot for a voicemail storage system (which is effectively a SMTP/POP3 system), which we want to use replication to give us some resilience. Tests have mostly been on dovecot 2.3.8 (9df20d2db) - as packaged on Centos 8 - but I have also used a couple of similar versions on different platforms, so this is not a specific build problem. The platform has replication working, over an SSL TCP link, for delivery. With the pop3 configuration as default as is possible (although the mail_plugins are explicitly included into the protocol sections to ensure notify and replication is called for), any pop3 delete operation does not cause a notify or replication operation. The two servers show the mailboxes in a different state up until something else prods a replication into progress. I would suggest that a pop3 delete/expunge of a message should be flagged as a mailbox change can cause a notify/replication, and that the current behaviour is a bug. There are workarounds to this, and I am considering adding a note to the wiki page https://wiki.dovecot.org/Replication to flag this - not sure what your wiki editing policy is. # Workaround 1 - Change pop3 deletion to set a flag If the setting pop3_deleted_flag = '$POP3Deleted' is added, then rather than the mail being deleted, it is flagged, and this change causes a notification and replication to the other server. However since the mail is not actually deleted, you additionally need another (cron?) task to periodically remove flagged mail, for example:- doveadm expunge -A MAILBOX inbox KEYWORD '$POP3Deleted' # Workaround 2 - Use Lazy Expunge You can use the lazy_expunge plugin - this has the same effect, and automates the removal of the messages after a period of time. https://doc.dovecot.org/configuration_manual/lazy_expunge_plugin/ For example, you can set the following changed config fragments:- mail_plugins = $mail_plugins notify replication lazy_expunge namespace inbox { separator = / prefix = inbox = yes # automatic lazy expunge mailbox mailbox .EXPUNGED { autoexpunge = 3 days autoexpunge_max_mails = 1000 } } plugin { # Move messages to an .EXPUNGED mailbox lazy_expunge = .EXPUNGED } Nigel. -- [ Nigel Metheringham --------------------------- nigel(a)dotdot.cloud ] [ Ellipsis Intangible Cloudy Technologies ]

1 0

Migration issue
by Kishore Potnuru 29 Jul '20

29 Jul '20

Hi Aki & Dovecot team, Just continuing with the previous discussion "Migration from one server to 2 new servers". Hi, I have tried the same way as per your suggestion. But it's throwing an error. ------------- [root@production2 log]# doveadm backup -a All -R -u kishore(a)test.ba.com imapc: dsync(kishore(a)test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:45992) dsync(kishore(a)test.ba.com): Warning: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - reconnecting (delay 0 ms) dsync(kishore(a)test.ba.com): Info: imapc(production1.baplc.com:143): Connected to xxx.xxx.xxx.xxx:143 (local yyy.yyy.yyy.yyy:46014) dsync(kishore(a)test.ba.com): Error: imapc(production1.baplc.com:143): connect(xxx.xxx.xxx.xxx, 143) timed out after 30 seconds - disconnecting dsync(kishore(a)test.ba.com): Error: User initialization failed: imapc: Login to production1.baplc.com failed: Disconnected from server [root@production2 log]# -------------- I looked into the production1 (old server) logs. I see the below error. =============== Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there are no passdbs Jul 28 11:14:23 master: Error: service(auth): command startup failed, throttling =============== after the above error, I have commented "pass=yes" in production1 (old server) server, then I see the below error. ================ Jul 28 11:17:10 auth: Fatal: No passdbs specified in configuration file. PLAIN mechanism needs one Jul 28 11:17:10 master: Error: service(auth): command startup failed, throttling =============== Please suggest me on fixing the issue.

2 3

Migration from one server to 2 new servers
by Kishore Potnuru 28 Jul '20

28 Jul '20

Hi I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions. My Current Production Server details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9 Postfix version - 2.6.6 ======================== New Servers: ========================== Linux OS - Red Hat Enterprise Linux Server release 7.7 (Maipo) Dovecot version - 2.2.36 (1f10bfa63) Postfix version - 2.10.1 ========================== What is the best way to stop/copy/migrate the current production data to the new servers? I am planning the following steps. Not sure if it is correct or not. 1. Stop the Postfix services on the old server and wait for few mins. So that no new emails will be coming to the old servers. Existing emails will be delivered to the receipients. 2. copy/migrate the data from old server to new servers. Please suggest what is the best way? 3. I see that dovecot version(2.0.9) in old production server, I do not know the which is the best option? see the options in the current version. ================================= [root@prodcution ~]# doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] [-S <socket_path>] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] config [doveconf parameters] director add|flush|map|remove|status dump [-t <type>] <path> expunge [-u <user>|-A] [-S <socket_path>] <search query> fetch [-u <user>|-A] [-S <socket_path>] <fields> <search query> force-resync [-u <user>|-A] [-S <socket_path>] <mailbox> help <cmd> import [-u <user>|-A] [-S <socket_path>] <source mail location> <dest parent mailbox> <search query> kick [-a <anvil socket path>] [-f] <user mask>[|]<ip/bits> log find|reopen|test mailbox create|delete|list|mutf7|rename|status|subscribe|unsubscribe penalty [-a <anvil socket path>] [<ip/bits>] purge [-u <user>|-A] [-S <socket_path>] pw [-l] [-p plaintext] [-r rounds] [-s scheme] [-u user] [-V] reload search [-u <user>|-A] [-S <socket_path>] <search query> sis deduplicate|find stop user [-a <userdb socket path>] [-x <auth info>] <user mask> [...] ================================= Please suggest me. Thanks, Kishore Potnuru

5 24