- dovecot - dovecot.org

Dovecot - Xoauth2 - keycloak
by la.jolie＠paquerette 09 Jul '20

09 Jul '20

Hello, Still trying to make roundcube / Dovecot works with Keycloak. Dovecot can't seem to validate the access_token that Roundcube gave. ----- Jul 08 20:48:05 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] Sent header Jul 08 20:48:05 auth: Debug: http-client[1]: peer 11.22.33.44:443: No more requests to service for this peer (1 connections exist, 0 pending) Jul 08 20:48:05 auth: Debug: http-client[1]: conn 11.22.33.44:443 [0]: Got 404 response for request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…] (took 11 ms + 19 ms in queue) Jul 08 20:48:05 auth: Debug: oauth2(my.mail@whatever,::1,<Z2mDOfSpJJ8AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(0, Invalid token) ---- The access_token used by Dovecot is the right one. Dovecot also has the right login (my.mail@whatever) The Nginx and Keycloak logs show this: ---- - - [08/Jul/2020:23:25:18 +0200] "POST /auth/realms/test_saml/protocol/openid-connect/token HTTP/1.1" 200 3171 "-" "Guzzle/5.3.1 curl/7.64.0 PHP/7.3.14-1~deb10u1" - - [08/Jul/2020:23:42:05 +0200] "GET /auth/realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDE0NjUsImlhdCI6MTU5NDI0MTI4NSwiYXV0aF90aW1lIjoxNTk0MjM0ODI3LCJqdGkiOiI0NjRlZjc5NS0yZDYzLTQzYjktYjU4My1iYTY2MmFkMWRhYzUiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhNC1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmOTYyNWM3OS02OTM5LTRkZjEtOGM2Yi1hYWM5Y2EzYWJkY2YiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6eyJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWlkIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iXSwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHeNRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg HTTP/1.1" 404 1465 "-" "dovecot-oauth2-passdb/2.3.4.1" DEBUG [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002315: PathInfo: /realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFUzI1N iIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJEZzR2aWtndzN2MWVpQVgxMU10YkFIaXRaUnM2R2RlVzN3b3hGTTBpd1NnIn0.eyJleHAiOjE1OTQyNDQ3MDQsImlhdCI6MTU5NDI0NDUyNCwiYXV0aF90aW1lIjoxNTk0MjQ0MzQ3LCJqdGk iOiIyYTg3MjQ3NS0zMGMxLTRmMDctODg5Ny04YmQ4OTJjMGI1MjEiLCJpc3MiOiJodHRwczovL3Nzby5udWJvLmNvb3AvYXV0aC9yZWFsbXMvdGVzdF9zYW1sIiwiYXVkIjoiYWNjb3VudCIsInN1YiI6IjhlZWNiODVjLTZlMDYtNGZhN C1iYTAwLTdlMGRlM2MyMWYxNCIsInR5cCI6IkJlYXJlciIsImF6cCI6InJvdW5kY3ViZSIsInNlc3Npb25fc3RhdGUiOiJmMjY0OTQyMy0xNmZkLTQzMTgtYTVkYy04NWJhNmU3YTQ4MWYiLCJhY3IiOiIwIiwiYWxsb3dlZC1vcmlnaW5 zIjpbImh0dHA6Ly9yYy5udWJvLmRvbWFpbmVwdWJsaWMubmV0Il0sInJlYWxtX2FjY2VzcyI6eyJyb2xlcyI6WyJvZmZsaW5lX2FjY2VzcyIsInVtYV9hdXRob3JpemF0aW9uIl19LCJyZXNvdXJjZV9hY2Nlc3MiOnsiYWNjb3VudCI6e yJyb2xlcyI6WyJtYW5hZ2UtYWNjb3VudCIsIm1hbmFnZS1hY2NvdW50LWxpbmtzIiwidmlldy1wcm9maWxlIl19fSwic2NvcGUiOiJvcGVuaWQgbWljcm9wcm9maWxlLWp3dCBwcm9maWxlIGVtYWlsIG9mZmxpbmVfYWNjZXNzIiwidWl kIjoicXVlbmVubmkiLCJ1cG4iOiJxdWVuZW5uaSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwibmFtZSI6Iktlbm55IExvdXZlYXV4IExvdXZlYXV4IiwiZ3JvdXBzIjpbIm9mZmxpbmVfYWNjZXNzIiwidW1hX2F1dGhvcml6YXRpb24iX SwicHJlZmVycmVkX3VzZXJuYW1lIjoicXVlbmVubmkiLCJnaXZlbl9uYW1lIjoiS2VubnkgTG91dmVhdXgiLCJmYW1pbHlfbmFtZSI6IkxvdXZlYXV4IiwiZW1haWwiOiJrZW5ueUBudWJvLnNpdGUifQ.TsUBiZ5nSTuA9ojr6bao5NQUHe NRmcYQZsC95rrhYca9FsFG4xG8mT53X9eOSNEqzRMJiPHaDuAh-3Bq8Rjdlg --- Dovecot does a GET request where the access_token is directly attached to the 'tokeninfo_url' option. Is that the correct/normal way? Shouldn't it be a POST with data passed as params? Or is it Keycloak that should accept that request? Thanks Kenny

2 1

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Hi, Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also. This is my current situation: 1) I have 2 test servers which are loaded with the following configuration. ============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago) [root@devap01 ~]# dovecot --version 2.0.9 [root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6 =============== So, I would like to install the max possible dovecot version on the above servers for the testing purpose. I would like to implement the HA/Resilience with those 2 servers. I have shared storage and individual storage in this environment. But I am seeing some issues with both of them ( I explained details in my first email thread). please see if you can help. 2) If it is successful, I will get two RHEL 7.7 servers to implement the same in LIVE environment for HA/Resilience. First I am going with compatibility issues to resolve in my environment. Once that is resolved, I will go with HA/Resilience implementation. Please let me know if you need any more details. Thanks & Regards, Kishore Potnuru On Wed, Jul 8, 2020 at 8:57 PM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > >>> with broken or vulnerable software is there really a benefit? > >> > >> LTS distributions back port necessary patches > > >Then the OP should be able to update to a dovecot that doesn't have the > issue, right? > > I have no idea what his issue is, and why he is stuck even in specific > releases. I have been running dovecot on el6 and el7 for years and years > without issues. > > > > > > > >

2 1

RE: Urgent Help required
by Marc Roos 08 Jul '20

08 Jul '20

>>The other side of the question is, Why is the software always so "vulnerable" and "broken" in the first >>place as to be unsuitable for Long Term Support? >> >>If the software code worked when it was released some number of years ago, then why doesn't it still work >>the same way today as it it did when it was released? Whenever I hear people complain about computers and/or software. I always suggest them to use something like the abacus of 2000 bc. You should be glad for what they do for you ;) And since humans operate them, you will find annoyances as with doctors amputating the wrong limb.

1 0

Re: Urgent Help required
by Kishore Potnuru 08 Jul '20

08 Jul '20

Thank you for your reply. 1. Am i able to upgrade directly from 2.0 to 2.3? or I should go periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3....? 2. could you please suggest me steps to pick the correct package to upgrade in the above version (2.1, 2.2, 2.3)? 3. which location i need to download the packages? 4. I am using redhat servers. Am i able to directly download and upgrade the software from my redhat linux server? please advise step-by-step instructions for this? Thanks, Kishore Potnuru On Wed, Jul 8, 2020 at 11:00 AM Apostolis Hardalias <a.hardalias(a)skroutz.gr> wrote: > > On 7/8/20 12:53 PM, Kishore Potnuru wrote: > > Hi All, > > > > I request your help on this. > > > > I have 2 dovecot test servers (IMAP protocol) installed with the > > following configuration. > > ============= > > [root@devap01 ~]# cat /etc/redhat-* > > Red Hat Enterprise Linux Server release 6.10 (Santiago) > > > > [root@devap01 ~]# dovecot --version > > 2.0.9 > > > > [root@devap01 ~]# postconf | grep mail_version > > mail_version = 2.6.6 > > =============== > > > > I have another server also "devap02" with the same configuration. > > > > Couple of points/questions/queries here. > > > > 1. I know these servers are having old dovecot versions. I would like > > to upgrade to the latest versions. Could you please suggest the steps > > for upgrading to the latest version in redhat (step by step details > > are helpful please) . If I upgrade to the latest version, will there > > be any impact on the existing configuration/setup? > > Check the documents posted here: > > https://doc.dovecot.org/installation_guide/upgrading/from-2.0-to-2.1/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.1-to-2.2/ > > https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/ > > Depending on your setup, you may also need to check for changes to > additional software (e.g. amavis) > > > > > 2. Now I have added these 2 servers behind the Load Balancer. Enabled > > 110/143 ports on the Load Balancer FQDN (test.pop3.testing.com > > <http://test.pop3.testing.com>) and opened the firewall ports. Here I > > configured IMAP settings from microsoft outlook to see the emails. I > > gave the Incoming Mail Server & Outgoing mail server as > > "test.pop3.testing.com <http://test.pop3.testing.com>". It is > > configured without errors in Outlook. But I see these 2 types issues > > (shared storage & individual storage) > > > > a) individual separate storage - When I send 10 emails to LB FQDN > > (test.pop3.testing.com <http://test.pop3.testing.com>), the emails are > > going to 2 backend servers. But when i see the emails from Outlook > > inbox, it shows 5 emails from one server for some time. After sometime > > it shows other 5 emails in the inbox. But, I am not able to see all 10 > > emails at same time in my inbox. Please suggest how to fix this issue? > > In this scenario, I have separate individual storage in both the servers. > > I'm not sure if you've set it up already because it's unclear from the > configuration you posted but, you may wanna have a look at: > https://wiki.dovecot.org/Replication > > I suggest using replication after you've upgraded since earlier versions > of dovecot had a few issues. > > > > b) common shared storage - I have tried a different scenario also. > > I also have one common NFS storage. So, I have configured that storage > > in both the servers. So when I sent 10 emails, I see all the 10 emails > > from both the servers as it is common shared storage. But, I am not > > getting those 10 emails delivered into my Outlook. I have made all the > > configuration correctly. Please suggest what is the mistake here. > > > > Dovecot.conf > > ========================================================= > > > > [root@devap01 ~]# cat /etc/dovecot/dovecot.conf > > disable_plaintext_auth = no > > > > listen = * > > log_path = /var/log/dovecot.log > > mail_location = maildir:/r3/mail/virtual/%d/%n/Maildir/ > > passdb { > > args = /etc/dovecot/passwd > > driver = passwd-file > > } > > pop3_uidl_format = %g > > protocols = imap pop3 > > 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=/r3/mail/virtual/%d/%n > > driver = static > > } > > mail_debug = no > > verbose_ssl = no > > ========================================================= > > > > Please help me here. > > > > Thanks, > > Kishore Potnuru >

1 1

Dovecot Maildirs multi language
by Luca Müller 07 Jul '20

07 Jul '20

Hello, I'm hosting a few customers on a dovecot Server. Most users speak german and have german as their main language. I configured the IMAP Foldernames in a Dovecot configuration file like this: ##### root@srv04:~# cat /etc/dovecot/conf.d/105-mailboxes.conf imap_capability = +XLIST namespace inbox { inbox = yes location = separator = / mailbox "Entwürfe" { auto = subscribe special_use = \Drafts auto=subscribe } mailbox Junk-E-Mail { special_use = \Junk auto=subscribe } mailbox "Gelöschte Elemente" { special_use = \Trash auto=subscribe } mailbox "Gesendete Elemente" { special_use = \Sent auto=subscribe } mailbox Archive { special_use = \Archive auto=subscribe } } ##### Dovecot Version: 2.3.10 (0da0eff44) ##### Is it possible to change this configuration for specific users or to provide multi language support somehow? Thanks in advance. Best regards, Luca

4 4

dovecot oauth
by la.jolie＠paquerette 06 Jul '20

06 Jul '20

Hello, I'm trying to configure roundcube / dovecot to work with keycloak. I activated xoauth2 oauthbearer in dovecot. But a problem occurs when dovecot tries to contact the keycloak server (logs are below). My problem looks like this one: https://dovecot.org/pipermail/dovecot/2019-December/117768.html The response to this problem was about a bug in oauth driver (https://dovecot.org/pipermail/dovecot/2019-December/117787.html) Mizuki was using Dovecot v2.2.36 (1f10bfa63) I have Dovecot Dovecot v2.3.4.1 (f79e8e7e4) I'm wondering if this bug is still present in my version or if I have another problem. Both my servers (dovecot and keycloak) are using let's encrypt certificates. I tried to configure Keycloak with nginx proxy and without it (access via port 8443) (in case the problem came from the ssl config on the keycloak server), but still the same error. If the bug is fixed, then could someone tell me what do I have to put in the option tls_ca_cert_file? I tried with /etc/letsencrypt/live/my.host/chain.pem and also certs I got from let's encrypt website (https://letsencrypt.org/certificates/ / tried ISRG Root X1 (self-signed) & Let’s Encrypt Authority X3 (IdenTrust cross-signed) & Let’s Encrypt Authority X3 (Signed by ISRG Root X1)) But I always have the same error. Thanks, Kenny My configs: - I'm on a Debian Buster with Dovecot / postfix / roundcube - dovecot -n : --- # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-5-cloud-amd64 x86_64 Debian 10.4 auth_debug = yes auth_mechanisms = xoauth2 oauthbearer login auth_verbose = yes debug_log_path = /var/log/dovecot-debug.log first_valid_gid = 10000 first_valid_uid = 10000 info_log_path = /var/log/dovecot.log last_valid_gid = 20000 last_valid_uid = 20000 lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = mail mail_location = maildir:~/Maildir 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 { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix } unix_listener auth-master { mode = 0600 user = mail } unix_listener auth-userdb { mode = 0600 user = mail } } service stats { unix_listener stats-reader { mode = 0600 user = mail } unix_listener stats-writer { mode = 0600 user = mail } } ssl_cert = </etc/letsencrypt/live/my.host/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 ssl_prefer_server_ciphers = yes ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = gid=mail home=/var/mail/%u driver = static } verbose_ssl = yes protocol lda { info_log_path = /var/log/dovecot-deliver.log log_path = /var/log/dovecot-deliver-errors.log } ------ - dovecot-oauth2.conf.ext ----- tokeninfo_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token introspection_mode = post introspection_url = https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke… username_attribute = email tls_ca_cert_file = /etc/letsencrypt/live/my.host/chain.pem #tls_ca_cert_file = /etc/ssl/certs/letsencrypt.pem #active_attribute = enableMail #active_value = TRUE debug = yes rawlog_dir = /tmp/oauth2 ----- * Logs: ------- Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: Making token validation lookup to https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/token Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Host session created Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: IPs have expired; need to refresh DNS lookup Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: Performing asynchronous DNS lookup Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Submitted (requests left=1) Jul 04 17:00:12 auth: Debug: http-client: host my.keycloak.host: DNS lookup successful; got 1 IPs Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14 (shared): Peer created Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Peer pool created Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Peer created Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Setting up connection to 151.62.56.14 (SSL=my.keycloak.host) (1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Linked queue https://my.keycloak.host (1 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Started new connection to 151.62.56.14 (SSL=my.keycloak.host) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Creating 1 new connections to handle requests (already 0 usable, connecting to 0, closing 0) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Making new connection 1 of 1 (0 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Connecting Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Waiting for connect (fd=22) to finish for max 0 msecs Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: HTTPS connection created (1 parallel connections exist) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Client connected (fd=22) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connected Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Starting SSL handshake Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x10, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: before SSL initialization Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server hello Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server certificate Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read server done Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write client key exchange Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished ==> dovecot.log <== Jul 04 17:00:12 auth: Info: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=-1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS write finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read change cipher spec Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1001, ret=1: SSLv3/TLS read finished Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x20, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL: where=0x1002, ret=1: SSL negotiation finished successfully Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Connection failed (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client: peer 151.62.56.14: Failed to make connection (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Failed to establish any connection within our peer pool: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 connections exist, 0 pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up connection to 151.62.56.14 (SSL=my.keycloak.host): SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (1 peers pending, 1 requests pending) Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Failed to set up any connection; failing all queued requests Jul 04 17:00:12 auth: Debug: http-client[1]: peer 151.62.56.14: Unlinked queue https://my.keycloak.host (0 queues linked) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Error: 9003 SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: queue https://my.keycloak.host: Dropping request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)] Jul 04 17:00:12 auth: Debug: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2: callback(-1, SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3) ==> dovecot.log <== Jul 04 17:00:12 auth: Error: oauth2(my.mail@whatever,::1,<fG8uk6CpBJ0AAAAAAAAAAAAAAAAAAAAB>): oauth2 failed: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 ==> dovecot-debug.log <== Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Destroy (requests left=1) Jul 04 17:00:12 auth: Debug: http-client[1]: request [Req1: GET https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/toke…... (long token)]: Free (requests left=0) Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: SSL handshaking with 151.62.56.14 failed: read(SSL 151.62.56.14) failed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection close Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection disconnect Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: (151.62.56.14): Disconnected: Connection closed: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 (fd=22) Jul 04 17:00:12 auth: Debug: my.keycloak.host: SSL error: Received invalid SSL certificate: unable to get issuer certificate: /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Detached peer Jul 04 17:00:12 auth: Debug: http-client[1]: conn 151.62.56.14 [0]: Connection destroy -------

2 4

export of information about mail into csv
by Marcel Blenkers 05 Jul '20

05 Jul '20

3 3

Quota: How/where to set/change
by Frank Elsner 03 Jul '20

03 Jul '20

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So 21.52 % full Host2 is under my control and running dovecot-2.3.10.1. I need to increase the quota above 2 GB but don't know where it comes from and therefor don't know what to do. This is the doveconf -a: | # 2.3.10.1 (a3d0e1171): /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 5.7.6-201.fc32.x86_64 x86_64 Fedora release 32 (Thirty Two) ext3 | # Hostname: christo.fritz.box | # NOTE: Send doveconf -n output instead when asking for help. | auth_anonymous_username = anonymous | auth_cache_negative_ttl = 1 hours | auth_cache_size = 0 | auth_cache_ttl = 1 hours | auth_cache_verify_password_with_worker = no | auth_debug = no | auth_debug_passwords = no | auth_default_realm = | auth_failure_delay = 2 secs | auth_gssapi_hostname = | auth_krb5_keytab = | auth_master_user_separator = | auth_mechanisms = plain login | auth_policy_check_after_auth = yes | auth_policy_check_before_auth = yes | auth_policy_hash_mech = sha256 | auth_policy_hash_nonce = | auth_policy_hash_truncate = 12 | auth_policy_log_only = no | auth_policy_reject_on_fail = no | auth_policy_report_after_auth = yes | auth_policy_request_attributes = login=%{requested_username} pwhash=%{hashed_password} remote=%{rip} device_id=%{client_id} protocol=%s | auth_policy_server_api_header = | auth_policy_server_timeout_msecs = 2000 | auth_policy_server_url = | auth_proxy_self = | auth_realms = | auth_socket_path = auth-userdb | auth_ssl_require_client_cert = no | auth_ssl_username_from_cert = no | auth_stats = no | auth_use_winbind = no | auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ | auth_username_format = %Lu | auth_username_translation = | auth_verbose = no | auth_verbose_passwords = no | auth_winbind_helper_path = /usr/bin/ntlm_auth | auth_worker_max_count = 30 | base_dir = /var/run/dovecot | config_cache_size = 1 M | debug_log_path = | default_client_limit = 1024 | default_idle_kill = 1 mins | default_internal_group = dovecot | default_internal_user = dovecot | default_login_user = dovenull | default_process_limit = 256 | default_vsz_limit = 512 M | deliver_log_format = msgid=%m: %$ | dict_db_config = | director_flush_socket = | director_mail_servers = | director_max_parallel_kicks = 100 | director_max_parallel_moves = 100 | director_output_buffer_size = 10 M | director_ping_idle_timeout = 30 secs | director_ping_max_timeout = 1 mins | director_servers = | director_user_expire = 15 mins | director_user_kick_delay = 2 secs | director_username_hash = %Lu | disable_plaintext_auth = yes | dotlock_use_excl = yes | doveadm_allowed_commands = | doveadm_api_key = | doveadm_http_rawlog_dir = | doveadm_password = | doveadm_port = 0 | doveadm_socket_path = doveadm-server | doveadm_ssl = no | doveadm_username = doveadm | doveadm_worker_count = 0 | dsync_alt_char = _ | dsync_commit_msgs_interval = 100 | dsync_features = | dsync_hashed_headers = Date Message-ID | dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U | first_valid_gid = 1 | first_valid_uid = 200 | haproxy_timeout = 3 secs | haproxy_trusted_networks = | hostname = | imap_capability = | imap_client_workarounds = | imap_fetch_failure = disconnect-immediately | imap_hibernate_timeout = 0 | imap_id_log = | imap_id_retain = no | imap_id_send = name * | imap_idle_notify_interval = 2 mins | imap_literal_minus = no | imap_logout_format = in=%i out=%o deleted=%{deleted} expunged=%{expunged} trashed=%{trashed} hdr_count=%{fetch_hdr_count} hdr_bytes=%{fetch_hdr_bytes} body_count=%{fetch_body_count} body_bytes=%{fetch_body_bytes} | imap_max_line_length = 64 k | imap_metadata = no | imap_urlauth_host = | imap_urlauth_logout_format = in=%i out=%o | imap_urlauth_port = 143 | imapc_cmd_timeout = 5 mins | imapc_connection_retry_count = 1 | imapc_connection_retry_interval = 1 secs | imapc_features = | imapc_host = | imapc_list_prefix = | imapc_master_user = | imapc_max_idle_time = 29 mins | imapc_max_line_length = 0 | imapc_password = | imapc_port = 143 | imapc_rawlog_dir = | imapc_sasl_mechanisms = | imapc_ssl = no | imapc_ssl_verify = yes | imapc_user = | import_environment = TZ CORE_OUTOFMEM CORE_ERROR | info_log_path = | instance_name = dovecot | last_valid_gid = 0 | last_valid_uid = 65534 | lda_mailbox_autocreate = no | lda_mailbox_autosubscribe = no | lda_original_recipient_header = | libexec_dir = /usr/local/dovecot/libexec/dovecot | listen = * | lmtp_add_received_header = yes | lmtp_client_workarounds = | lmtp_hdr_delivery_address = final | lmtp_proxy = no | lmtp_proxy_rawlog_dir = | lmtp_rawlog_dir = | lmtp_rcpt_check_quota = no | lmtp_save_to_detail_mailbox = yes | lmtp_user_concurrency_limit = 0 | lock_method = fcntl | log_core_filter = | log_debug = | log_path = syslog | log_timestamp = "%b %d %H:%M:%S " | login_access_sockets = | login_greeting = m28a.ddns.net - IMAPs Service (dovecot) ready. | login_log_format = %$: %s | login_log_format_elements = %u %r %c | login_plugin_dir = /usr/local/dovecot/lib/dovecot/login | login_plugins = | login_proxy_max_disconnect_delay = 0 | login_proxy_notify_path = proxy-notify | login_source_ips = | login_trusted_networks = | mail_access_groups = | mail_always_cache_fields = | mail_attachment_detection_options = | mail_attachment_dir = | mail_attachment_fs = sis posix | mail_attachment_hash = %{sha1} | mail_attachment_min_size = 128 k | mail_attribute_dict = | mail_cache_compress_continued_percentage = 200 | mail_cache_compress_delete_percentage = 20 | mail_cache_compress_header_continue_count = 4 | mail_cache_compress_min_size = 32 k | mail_cache_fields = flags | mail_cache_min_mail_count = 0 | mail_cache_record_max_size = 64 k | mail_cache_unaccessed_field_drop = 30 days | mail_chroot = | mail_debug = no | mail_fsync = optimized | mail_full_filesystem_access = no | mail_gid = | mail_home = | mail_index_log2_max_age = 2 days | mail_index_log_rotate_max_size = 1 M | mail_index_log_rotate_min_age = 5 mins | mail_index_log_rotate_min_size = 32 k | mail_index_rewrite_max_log_bytes = 128 k | mail_index_rewrite_min_log_bytes = 8 k | mail_location = maildir:/var/spool/mail/%u:LAYOUT=fs | mail_log_prefix = "%Us(%u,%r): " | mail_max_keyword_length = 50 | mail_max_lock_timeout = 0 | mail_max_userip_connections = 10 | mail_never_cache_fields = imap.envelope | mail_nfs_index = no | mail_nfs_storage = no | mail_plugin_dir = /usr/dovecot/lib/dovecot/ | mail_plugins = notify quota fts fts_squat acl | mail_prefetch_count = 0 | mail_privileged_group = | mail_save_crlf = no | mail_server_admin = | mail_server_comment = | mail_shared_explicit_inbox = no | mail_sort_max_read_count = 0 | mail_temp_dir = /tmp | mail_temp_scan_interval = 1 weeks | mail_uid = | mail_vsize_bg_after_count = 0 | mailbox_idle_check_interval = 30 secs | mailbox_list_index = yes | mailbox_list_index_include_inbox = no | mailbox_list_index_very_dirty_syncs = no | maildir_broken_filename_sizes = no | maildir_copy_with_hardlinks = yes | maildir_empty_new = no | maildir_stat_dirs = no | maildir_very_dirty_syncs = no | master_user_separator = | mbox_dirty_syncs = yes | mbox_dotlock_change_timeout = 2 mins | mbox_lazy_writes = yes | mbox_lock_timeout = 5 mins | mbox_md5 = apop3d | mbox_min_index_size = 0 | mbox_read_locks = fcntl | mbox_very_dirty_syncs = no | mbox_write_locks = dotlock fcntl | mdbox_preallocate_space = no | mdbox_rotate_interval = 0 | mdbox_rotate_size = 10 M | mmap_disable = no | namespace inbox { | disabled = no | hidden = no | ignore_on_failure = no | inbox = yes | list = yes | location = | mailbox Drafts { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Drafts | } | mailbox Gesendet { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox SPAM { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Junk | } | mailbox Sent { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Sent | } | mailbox Trash { | auto = no | autoexpunge = 0 | autoexpunge_max_mails = 0 | comment = | driver = | special_use = \Trash | } | order = 0 | prefix = | separator = | subscriptions = yes | type = private | } | old_stats_carbon_interval = 30 secs | old_stats_carbon_name = | old_stats_carbon_server = | old_stats_command_min_time = 1 mins | old_stats_domain_min_time = 12 hours | old_stats_ip_min_time = 12 hours | old_stats_memory_limit = 16 M | old_stats_session_min_time = 15 mins | old_stats_user_min_time = 1 hours | passdb { | args = dovecot | auth_verbose = default | default_fields = | deny = no | driver = pam | master = no | mechanisms = | name = | override_fields = | pass = no | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | username_filter = | } | plugin { | fts = squat | fts_squat = partial=4 full=10 | mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append | mail_log_fields = uid box from subject msgid size flags | mail_log_group_events = yes | quota = maildir:User quota | quota_rule = ?:storage=5G | quota_rule2 = Trash:storage=+100M | } | pop3_client_workarounds = | pop3_delete_type = default | pop3_deleted_flag = | pop3_enable_last = no | pop3_fast_size_lookups = no | pop3_lock_session = no | pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s | pop3_no_flag_updates = no | pop3_reuse_xuidl = no | pop3_save_uidl = no | pop3_uidl_duplicates = allow | pop3_uidl_format = %08Xu%08Xv | pop3c_features = | pop3c_host = | pop3c_master_user = | pop3c_password = | pop3c_port = 110 | pop3c_quick_received_date = no | pop3c_rawlog_dir = | pop3c_ssl = no | pop3c_ssl_verify = yes | pop3c_user = %u | postmaster_address = mailonator(a)mailbox.org | protocols = imap | quota_full_tempfail = no | rawlog_dir = | recipient_delimiter = + | rejection_reason = Your message to <%t> was automatically rejected:%n%r | rejection_subject = Rejected: %s | replication_dsync_parameters = -d -N -l 30 -U | replication_full_sync_interval = 1 days | replication_max_conns = 10 | replicator_host = replicator | replicator_port = 0 | sendmail_path = /usr/sbin/sendmail | service aggregator { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = aggregator | extra_groups = | fifo_listener replication-notify-fifo { | group = | mode = 0600 | user = | } | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replication-notify { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service anvil { | chroot = empty | client_limit = 1024 | drop_priv_before_exec = no | executable = anvil | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 1 | protocol = | service_count = 0 | type = anvil | unix_listener anvil-auth-penalty { | group = | mode = 0600 | user = | } | unix_listener anvil { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service auth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = auth -w | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener auth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service auth { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = auth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener auth-client { | group = exim | mode = 0660 | user = exim | } | 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 = 0666 | 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 | } | service config { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = config | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = config | unix_listener config { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service dict-async { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict-async { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dict { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dict | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dict { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service director { | chroot = . | client_limit = 0 | drop_priv_before_exec = no | executable = director | extra_groups = | fifo_listener login/proxy-notify { | group = | mode = 00 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener director-admin { | group = | mode = 0600 | user = | } | unix_listener login/director { | group = | mode = 00 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service dns_client { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = dns-client | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener dns-client { | group = | mode = 0666 | user = | } | unix_listener login/dns-client { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service doveadm { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = doveadm-server | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 1 | type = | unix_listener doveadm-server { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service health-check { | chroot = | client_limit = 1 | drop_priv_before_exec = yes | executable = script -p health-check.sh | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-hibernate { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = imap-hibernate | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 0 | type = | unix_listener imap-hibernate { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-login | extra_groups = | group = | idle_kill = 0 | inet_listener imap { | address = | haproxy = no | port = 143 | reuse_port = no | ssl = no | } | inet_listener imaps { | address = | haproxy = no | port = 993 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 512 | process_min_avail = 3 | protocol = imap | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-postlogin { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = script-login /usr/local/sbin/dovecot-imap-post-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = | service_count = 0 | type = | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-login { | chroot = token-login | client_limit = 0 | drop_priv_before_exec = no | executable = imap-urlauth-login | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = login | unix_listener imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service imap-urlauth-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-urlauth-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service imap-urlauth { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap-urlauth | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener token-login/imap-urlauth { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service imap { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = imap | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = imap | service_count = 1 | type = | unix_listener imap-master { | group = | mode = 0600 | user = | } | unix_listener login/imap { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer-worker { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = indexer-worker | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 10 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer-worker { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service indexer { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = indexer | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener indexer { | group = | mode = 0666 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service ipc { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = ipc | extra_groups = | group = | idle_kill = 0 | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener ipc { | group = | mode = 0600 | user = $default_internal_user | } | unix_listener login/ipc-proxy { | group = | mode = 0600 | user = $default_login_user | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service lmtp { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = lmtp | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = lmtp | service_count = 0 | type = | unix_listener lmtp { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service log { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = log | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = log | unix_listener log-errors { | group = | mode = 0600 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service old-stats { | chroot = empty | client_limit = 0 | drop_priv_before_exec = no | executable = old-stats | extra_groups = | fifo_listener old-stats-mail { | group = | mode = 0600 | user = | } | fifo_listener old-stats-user { | group = | mode = 0600 | user = | } | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener old-stats { | group = | mode = 0600 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service pop3-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = pop3-login | extra_groups = | group = | idle_kill = 0 | inet_listener pop3 { | address = | haproxy = no | port = 110 | reuse_port = no | ssl = no | } | inet_listener pop3s { | address = | haproxy = no | port = 995 | reuse_port = no | ssl = yes | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service pop3 { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = pop3 | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 128 | process_min_avail = 0 | protocol = pop3 | service_count = 1 | type = | unix_listener login/pop3 { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | service replicator { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = replicator | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener replicator-doveadm { | group = | mode = 00 | user = $default_internal_user | } | unix_listener replicator { | group = | mode = 0600 | user = $default_internal_user | } | user = | vsz_limit = 18446744073709551615 B | } | service stats { | chroot = | client_limit = 0 | drop_priv_before_exec = no | executable = stats | extra_groups = | group = | idle_kill = 4294967295 secs | privileged_group = | process_limit = 1 | process_min_avail = 0 | protocol = | service_count = 0 | type = | unix_listener stats-reader { | group = | mode = 0600 | user = | } | unix_listener stats-writer { | group = $default_internal_group | mode = 0660 | user = | } | user = $default_internal_user | vsz_limit = 18446744073709551615 B | } | service submission-login { | chroot = login | client_limit = 0 | drop_priv_before_exec = no | executable = submission-login | extra_groups = | group = | idle_kill = 0 | inet_listener submission { | address = | haproxy = no | port = 587 | reuse_port = no | ssl = no | } | privileged_group = | process_limit = 0 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = login | user = $default_login_user | vsz_limit = 18446744073709551615 B | } | service submission { | chroot = | client_limit = 1 | drop_priv_before_exec = no | executable = submission | extra_groups = $default_internal_group | group = | idle_kill = 0 | privileged_group = | process_limit = 1024 | process_min_avail = 0 | protocol = submission | service_count = 1 | type = | unix_listener login/submission { | group = | mode = 0666 | user = | } | user = | vsz_limit = 18446744073709551615 B | } | shutdown_clients = yes | ssl = yes | ssl_alt_cert = | ssl_alt_key = | ssl_ca = | ssl_cert = </usr/local/etc/Certs/m28a.crt | ssl_cert_username_field = commonName | ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH | ssl_client_ca_dir = | ssl_client_ca_file = | ssl_client_cert = | ssl_client_key = | ssl_client_require_valid_cert = yes | ssl_crypto_device = | ssl_curve_list = | ssl_dh = # hidden, use -P to show it | ssl_key = # hidden, use -P to show it | ssl_key_password = | ssl_min_protocol = TLSv1 | ssl_options = | ssl_prefer_server_ciphers = no | ssl_require_crl = yes | ssl_verify_client_cert = no | state_dir = /var/lib/dovecot | stats_writer_socket_path = stats-writer | submission_client_workarounds = | submission_host = | submission_logout_format = in=%i out=%o | submission_max_mail_size = 0 | submission_max_recipients = 0 | submission_relay_command_timeout = 5 mins | submission_relay_connect_timeout = 30 secs | submission_relay_host = | submission_relay_master_user = | submission_relay_max_idle_time = 29 mins | submission_relay_password = | submission_relay_port = 25 | submission_relay_rawlog_dir = | submission_relay_ssl = no | submission_relay_ssl_verify = yes | submission_relay_trusted = no | submission_relay_user = | submission_ssl = no | submission_timeout = 30 secs | syslog_facility = mail | userdb { | args = | auth_verbose = default | default_fields = | driver = passwd | name = | override_fields = | result_failure = continue | result_internalfail = continue | result_success = return-ok | skip = never | } | valid_chroot_dirs = | verbose_proctitle = yes | verbose_ssl = no | version_ignore = no | protocol lmtp { | mail_plugins = notify quota fts fts_squat acl | } | protocol lda { | mail_plugins = notify quota fts fts_squat acl | } | protocol imap { | imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags | imap_id_log = * | imap_logout_format = [%i/%o] | mail_max_userip_connections = 0 | mail_plugins = notify quota fts fts_squat acl quota imap_quota listescape fts fts_squat | } The config may be sub-optimal. Please concentrate on my quota problem. Stay healthy, Frank Elsner

1 0

Mail replication fails between v2.2.27 and v2.3.4.1
by Apostolis Hardalias 03 Jul '20

03 Jul '20

Hello, I have two installations of dovecot configured to replicate mailboxes between them. recently, i upgraded the operating system on one of them (mx2.example.com) and now i'm running one installation on version 2.2.27 (debian stretch) and another on version 2.3.4.1 (mx1.example.com debian buster). My setup includes 3 shared namespaces that point to the mailboxes of 3 accounts. these accounts are setup to use maildir format. After upgrading one of the hosts, i started having issues with failed replications on those mailboxes. I tried running the replication manually and repeatedly by issuing the following on mx1.example.com: doveadv -d sync -u exception_bucket(a)example.com -d -l 30 -n -u and the logs on mx2.example.com included the following lines consistently: Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: Change during sync: Mailbox GUID 2d32711ddfd27250390e0000a712b6e3 was lost Jul 02 14:21:58 dsync-server(exception_bucket(a)example.com): Debug: brain S: We don't have mailbox 2d32711ddfd27250390e0000a712b6e3 I double checked for the existance of the mailbox with that guid (that guid points to the inbox) and the mailbox existed on both servers but, the contents of the mailbox on the two servers where different (missing e-mails on both servers). I attempted running a force-resync command as follows but with no luck. doveadm -d force-resync -u exception_bucket(a)example.com inbox but the issue persisted. admittedly, i didn't run the command on both servers because i read it doesn't replicate after figuring a workaround. The next thing i tried was attempting replication without the -n flag, given that you mention that there are some issues replicating shared namespaces. That didn't fix the replication status either. After looking around, i came onto the solution on this thread: https://dovecot.org/pipermail/dovecot/2017-october/109620.html which proposed setting mailbox_list_index = no. This was the default setting on version 2.2.27, so i changed that setting on mx2.example.com which was running version 2.3.4.1. This allowed the replication to work but i don't think it is a setting i want in my configuration. Is there something i can do to re-enable dovecot to check index files instead of mailboxes? Could that be an issue when replicating between those two different versions? I'm attaching the configuration files for both the mailservers, a separate configuration file is included since mail_replica settings are set from there, and a link to the compressed log file i pulled during the operation. https://filebin.net/d9yygnq8jg74unwb/replication_debug.log.bz2?t=vv2o81ka Thank you in advance, Apostolis Hardalias

1 0

local stanza only generated for IPv6
by Jeremy Ardley 02 Jul '20

02 Jul '20

I have a mail server with multiple IP addresses and associated DNS names In the dovecot configuration I have a listen directive: listen = mail.example.com.com,mail.otherexample.com,localhost Multiple local stanzas are of the form: local mail.example.com { protocol imap { ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ssl_key = </etc/letsencrypt/live/mail.example.com/privkey.pem service imaps_login { inet_listener imaps { address=mail.example.com } inet_listener imap { address=mail.example.com } } } } mail.example.com has IPv4 and IPv6 addresses in DNS When I run doveconf -n the local configuration is only generated for the IPv6 address. I can test the operation on IPv6 using openSSL and see different server certificates on different IP addresses as expected. How do I force local generation for both IPv4 and IPv6 ?

3 4

dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory
by Brent Clark 30 Jun '20

30 Jun '20

Good day Guys Currently on Debian Stretch (2.2.27). This morning we enabled SNI for our clients (file per domain). On going live with the new server configuration, we started getting the following on our shared hosting servers. Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: doveconf: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: block_alloc(134217728): Out of memory Jun 30 07:25:04 REMOVED_HOSTNAME dovecot: config: Fatal: master: service(config): child 64008 returned error 83 (Out of memory (service config { vsz_limit=512 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) Jun 30 07:25:34 REMOVED_HOSTNAME dovecot: doveconf: Panic: data stack: Out of memory when allocating 2147483688 bytes Jun 30 07:25:37 REMOVED_HOSTNAME dovecot: config: Panic: data stack: Out of memory when allocating 2147483688 bytes This is a server with 2414 domains. On a few of our servers, to buy time, we had to set: default_vsz_limit =10096M A question I would like to ask is. Based on the following change notice, could the following be the problem. https://dovecot.org/pipermail/dovecot-news/2019-July/000412.html - config: Memory leak in config process when ssl_dh setting wasn't set and there was no ssl-parameters.dat file. This caused config process to die once in a while with "out of memory". If anyone could provide any assistance or share a tip on where we can look it would be appreciated. This one has my team and I stumped. Kind regards Brent Clark

1 0

POP3Deleted flag issues
by Justina Colmena ~biz 29 Jun '20

29 Jun '20

Hello, I have been running my own mail server with Dovecot, Postfix, and Cyrus-SASL for authentication. = dovecot22u.x86_64 1:2.2.36.4-1.el7.ius @ius I am basically trying to tune the system for better performance. The flat files "/var/mail/justina" etc exhibit locking issues and conflicts when fetching mail at the same time new mail is being delivered by Postfix. Other mail is stored in "Maildir" type folders accessible via IMAP. These exhibit better performance with finer grained locking. There's an "idea" that was posted to the list 7 years ago, shows up top rank on Google. https://dovecot.org/pipermail/dovecot/2013-May/090114.html I fear either an incomplete implementation of the feature or "here-be-dragons" code that may or may not be completely documented. I would like all the "$POP3Deleted" mail to be moved to an "Archive" Maildir folder accessible via IMAP. How do I accomplish this? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

layout:fs info
by Stefano Gatto - Fly2Net sas 29 Jun '20

29 Jun '20

Hi all, my dovecot version is 2.2.13, quite standard configuration. Can I add directive LAYOUT=fs in dovecot configuration without losing all my archived messages? This should modify the separator of email folders from dots to slashes, correct? BR Stefano

2 2

Plugin ABI compat between v2.3.8 and v2.3.9
by Alexander Strasser 24 Jun '20

24 Jun '20

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that the crash happened in an external plugin fetchmail_wakeup[1]. After recompiling that plugin with up to date dovecot headers, I didn't get crashes anymore. So I suspect there were ABI incompatible changes and it was forgotten to bump the minimum Plugin-ABI version supported. I could try to follow up some more details, but it would be quite a burden because of rebuilding the plugin with debug symbols against version 2.3.8 of dovecot and triggering the crash etc. Despite that I think it should be possible to detect changes that are ABI incompatible, as otherwise plugin users would always have to find out first hand with unknown consequences. That said there could be a possibility of the plugin using the API/ABI in an invalid way. If that was the cause, then the plugin should be changed. Hope this report turns out to help improve the situation. I don't have problems currently and will in future be sensitive to this specific possible cause of problems, but not having such crashes in the first place, would be worth it and maybe could still help others. Best regards, Alexander 1: slightly reduced version of: https://github.com/marschap/fetchmail_wakeup

2 4

Converting dot-namespaced Maildir to /-namespaced
by Guido Goluke, MajorLabel 24 Jun '20

24 Jun '20

I have a couple of domains on my server, all of them namespaced with a dot. It's 10-15 mailboxes at the most. Is there good way to convert them to / (slash) namespaced folders? Maybe some bash script lying around somewhere?

1 0

dovecot fts configuration without solr
by Danilo Tomasoni 24 Jun '20

24 Jun '20

Hello All, I always used dovecot and I'm pretty happy with it, but recently I changed OS (to ubuntu 18) and to get dovecot LTS with lucene (the default I was using on my previous arch installation) I needed to build from source the version 2.3.10 (the one that came with the repos was older and clucene was not actually supported) The problem is that the Clucene is not behaving well, It indexes only some mails but definitely not all according to my tests (there are also strange assertion errors in the logs) I also tried xapian fts index but is very slow indexing and definitely doesn't seem to work. The problem with solr fts is that solr doesn't even start on my tiny system (odroid C2 with 2GB RAM) and anyway I don't want to bloat all the system for the indexing if possible.. Anyone can suggest me a proper minimal and working configuration? Thank you Danilo

2 2

JMAP support
by Martynas Bendorius 23 Jun '20

23 Jun '20

Hello, Is there any ETA set for JMAP support? Thank you! >> On 11/27/2016 5:28 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> Hi! >> We are working on including JMAP support to Dovecot. At this moment I cannot give any promise for exact version, but hopefully it will be part of v2.3 >> >> Aki Tuomi >> Dovecot Oy -- Best regards, Martynas Bendorius

3 2

Apple mail works but thunderbird unable to connect
by Dshah 23 Jun '20

23 Jun '20

Dear all, I am stuck on this issue for days, I am able to connect on my IMAP server using Apple mail client but thunderbird shows me this error: "improper command pipelining after EHLO" I have tried all the ports in manual config but it just is not working while Apple Mail is able to connect perfectly, here are my configuration details of "postconf -n" , "doveconf -n" and " master.cf" https://pastebin.com/M3XG9DXA Thanks in advance.

6 12

problem with warnings
by Maciej Milaszewski 23 Jun '20

23 Jun '20

Hi I have a problem with warrnings in log Yesterday "big gays" change datastore and After this time i get warrnings in dovecot like: Warning: Created dotlock file's timestamp is different than current time (1592878268 vs 1592871191): /vmail/us/username/Maildir/dovecot-uidlist Before that there was no problem with warnnings I have dovecot director with 5 dovecot-nodes and storage always was mounted via nfs /vmail on /vmail type nfs (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.100.41,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=xxx.xxx.xxx.xxx) # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-10-amd64 x86_64 Debian 8.11

1 0

from field encoding
by Jan Jurko 23 Jun '20

23 Jun '20

Good day. I have a dovecot 2.3.4.1 on debian 10 as an imap server. I found there are emails where the header field From has no encoding even if there is a name with special characters like Žlutý Kůň. The header looks like: From: "Žlutý Kůň" <zluty.kun(a)domain.tld> In this case the email client - roundcube, outlook etc. will show the From with wrong characters. This behaviour is typical only for dovecot, not for courier-imap - it was installed before dovecot with no problems. If there is corretly encoded From filed, the client shows the From correctly. Is there a way to set up the dovecot to show the field correctly even without encoding stuff? Some default/fallback settings? Thank you very much for your help Jan Jurko

2 3

nodelay passdb extra field does not work?
by Joe Wong 23 Jun '20

23 Jun '20

Hello, I have added 'y' as nodelay in my passdb query and I see the following in log: dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay does it mean this option is no longer supported in 2.3.10 ? - Joe

2 4

AW: replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 23 Jun '20

23 Jun '20

I managed to convince the System that I really want a core dump 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: 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)

1 0

Updating wiki content
by Dan 22 Jun '20

22 Jun '20

Greetings, I'd like to contribute to the Dovecot wiki in regards to clients that lack the ability to support SNI. However the captcha doesn't make sense, I get a question "What do you do to prevent spam?". This is a loaded question which I'm uncertain what the answer should be. Thanks.

2 1

Bug[?]report: duplicate response
by Johannes Schilling 21 Jun '20

21 Jun '20

hi, i'm not sure if i've discovered a bug or if i'm not following the IMAP specs correctly. observations: { echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993 produces the following output (aside from the openssl s_client cert-inspection stuff): 2020-06-21 12:26:02 * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. 2020-06-21 12:26:02 a1 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 LITERAL+ NOTIFY SPECIAL-USE] Logged in 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.005 + 0.000 + 0.004 secs). 2020-06-21 12:26:02 a2 OK NOTIFY completed (0.002 + 0.000 + 0.001 secs). the first line is the pre-login welcome prompt, the second one the result of the "a1 login .." command and the third and fourth seem to be the answer to the "a2 notify set .." command, twice. from the different timings given, it seems the a2 command is actually executed twice. is this a case of "you're not allowed to pipeline commands like this" or a bug in dovecot (or both)? i attached the output of `dovecot -n`. best, dario

1 0

Mailfiles gets duplicated
by Jacques Schreiber 19 Jun '20

19 Jun '20

Hello, With my configuration Dovecot creates multiple duplicates (sometimes 2, sometimes 3, sometimes a plenty) of mailfiles when moving them into the Sent or the Trash folders. This does not affect the Inbox folder. I observed this while using Thunderbird on Ubuntu as a client as well as K9-Mail on Android, therefore I expect this comes from the Dovecot server and not from the client itself. It also appears that the duplicates does not have the size S= and vsize W= flags. Here is a short example of the last emails from my folder /.Sent/cur: -rw------- 1 pi pi 1,6M mars 24 22:18 1585084691.M834293P16489.raspberry-pi,S=1658182,W=1679758:2,S -rwx------ 1 pi pi 34M mars 24 22:20 1585084841.M415421P17104Q0Rc311b18de2edf536.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:22 1585084954.M254398P17175Q0R6c5a66e22ac3a3d2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:46 1585086411.M317404P18117Q0R61ba34fb281e8eb5.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:51 1585086659.M435086P18251Q0R7e118d3bd7784c6d.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:53 1585086799.M821376P18319Q0R6b838db7f14a2302.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 22:54 1585086861.M788796P18398Q0Raaa98233db1f9b6a.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:00 1585087244.M616219P18629Q0R4d5856ac0d1b1337.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087278.M581756P18651Q0R6a75f871d9e8f0aa.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:01 1585087296.M954701P18666Q0R0cce469807cb0aa8.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:05 1585087552.M557221P18793Q0R541dece72da12039.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:09 1585087759.M768686P18927Q0Rbc1c813e1b124702.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087823.M232119P19026Q0R4086d52491835470.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:10 1585087855.M951407P19035Q0R4edd76369b804f54.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:22 1585088561.M364587P19476Q0Rdc0ac3a664f1a80f.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:24 1585088639.M90555P19512Q0R6214b0e915c88908.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:27 1585088859.M192671P19663Q0Re4562fb440f7a4be.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:28 1585088927.M926251P19699Q0Rbe7523140efc06e2.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:29 1585088962.M120826P19721Q0Rd66b5d585c41123b.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:31 1585089111.M427988P19799Q0R5b8e8a032adc33c8.raspberry-pi:2, -rwx------ 1 pi pi 1,6M mars 24 23:32 1585089138.M910049P19827Q1R1b4d834fadfb0fd6.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:33 1585089180.M811880P19839Q0R8c415b8fbf638018.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089252.M333476P19878Q0R3b809c0f458a90e0.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:34 1585089293.M103544P19918Q0Rd9acc8d53f5c8b32.raspberry-pi:2, -rwx------ 1 pi pi 34M mars 24 23:35 1585089314.M270143P19948Q0R1202a6fe81862880.raspberry-pi:2, -rw------- 1 pi pi 2,0M mars 29 13:01 1585479708.M437415P11486.raspberry-pi,S=2076767,W=2105374:2,S -rwx------ 1 pi pi 2,0M mars 29 13:02 1585479733.M94224P13150Q0R974361f29d7d9cdb.raspberry-pi:2, -rw------- 1 pi pi 2,5K mars 31 09:10 1585638623.M921769P12803.raspberry-pi,S=2511,W=2585:2,S -rwx------ 1 pi pi 3,0K mars 31 09:11 1585638671.M552885P12861Q0R878fb6aa8485b5c0.raspberry-pi:2, -rw------- 1 pi pi 19M avril 3 09:38 1585899475.M669440P24679.raspberry-pi,S=19757959,W=20028662:2,S -rwx------ 1 pi pi 19M avril 3 09:38 1585899531.M744009P25082Q0R0b61c7e8e7b723b4.raspberry-pi:2, -rw------- 1 pi pi 421 avril 3 14:52 1585918350.M591326P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918360.M206900P1027.raspberry-pi,S=421,W=434:2,S -rw------- 1 pi pi 421 avril 3 14:52 1585918372.M255849P1032.raspberry-pi,S=421,W=434:2,S -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918394.M224204P1071Q0R7e9bc28b2d8e7fc4.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918395.M884727P1073Q1Ra4a111c1e0f5a399.raspberry-pi:2, -rwx------ 1 pi pi 1,1K avril 3 14:53 1585918398.M36019P1077Q2R10960cdc588b3ede.raspberry-pi:2, Below are details about my configuration pi@raspberry-pi:~$ sudo uname --all Linux raspberry-pi 4.4.38+ #938 Thu Dec 15 15:17:54 GMT 2016 armv6l GNU/Linux pi@raspberry-pi:~$ mount [...] /dev/sda1 on /home/pi type ext4 (rw,noatime,nodiratime,data=ordered) [...] pi@raspberry-pi:/var/log$ sudo dovecot --version 2.2.13 pi@raspberry-pi:/var/log$ sudo dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.4.38+ armv6l Debian 8.0 ext4 disable_plaintext_auth = no mail_location = maildir:/home/pi/Mails/%u namespace { inbox = yes location = mailbox { auto = subscribe special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { auto = subscribe special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = separator = / type = private name = inbox } passdb { driver = pam } passdb { args = /home/pi/Mails/dovecot_passwords driver = passwd-file } protocols = " imap" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service { inet_listener { address = * port = 4143 name = imap } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </home/pi/Mails/imap_ssl_certificate.crt ssl_key = </home/pi/Mails/imap_ssl_private.key userdb { driver = passwd } userdb { args = uid=1000 gid=1000 home=/var/mail/%u driver = static } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } }

1 1

replicator: Panic: data stack: Out of memory
by Thomas Tsiakalakis 18 Jun '20

18 Jun '20

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) 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.

1 0

Sieve-scripts won't replicate
by Niels Kobschätzki 18 Jun '20

18 Jun '20

Hi, I am trying to use dovecot replication for a two-way sync. And whatever I do, sieve-scripts won’t replicate. Mails replicate near instantaneous. When I disable the sieve-script in roundcube, the other server will create in the home of the user on the other side a folder sieve/tmp but enabling won’t create the roundcube.sieve and the symlink .dovecot.sieve -> sieve/roundcube.sieve The home of a virtual mail user on server1 looks like this: drwx------ 4 vexim vexim 4096 Jun 18 08:02 . drwx------ 8 vexim vexim 4096 Jun 18 07:59 .. lrwxrwxrwx 1 vexim vexim 21 Jun 18 07:59 .dovecot.sieve -> sieve/roundcube.sieve drwx------ 5 vexim vexim 4096 Jun 18 08:14 Maildir drwx------ 3 vexim vexim 4096 Jun 18 08:02 sieve A ps auxwww|grep dove looks like this (maybe some user is wrong?): ps auxwww |grep dove root 847 0.0 0.0 4200 3044 ? Ss 07:54 0:00 /usr/sbin/dovecot -F root 849 0.0 0.0 4060 2544 ? S 07:54 0:00 dovecot-team1/replicator dovecot 850 0.0 0.0 3912 1092 ? S 07:54 0:00 dovecot-team1/anvil root 851 0.0 0.0 4048 2464 ? S 07:54 0:00 dovecot-team1/log dovecot 852 0.0 0.0 4048 2692 ? S 07:54 0:00 dovecot-team1/stats root 853 0.0 0.0 6072 4368 ? S 07:54 0:00 dovecot-team1/config dovecot 855 0.0 0.0 17412 6620 ? S 07:54 0:00 dovecot-team1/auth dovenull 856 0.0 0.0 8200 6344 ? S 07:54 0:00 dovecot-team1/imap-login vexim 858 0.0 0.0 7092 5300 ? S 07:54 0:00 dovecot-team1/imap dovecot 902 0.0 0.0 3912 1096 ? S 07:55 0:00 dovecot-team1/aggregator dovenull 1929 0.0 0.0 8200 6256 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1930 0.0 0.0 6984 5284 ? S 08:15 0:00 dovecot-team1/imap dovenull 1931 0.0 0.0 8200 6248 ? S 08:15 0:00 dovecot-team1/imap-login vexim 1932 0.0 0.0 6964 5140 ? S 08:15 0:00 dovecot-team1/imap root 2210 0.0 0.0 6048 892 pts/0 S+ 08:21 0:00 grep dove I do not see any errors in the log. Here is the doveconf -n output. The partner looks identical except the replication target. # 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: team.snafu.de auth_mechanisms = plain login auth_verbose = yes doveadm_password = # hidden, use -P to show it doveadm_port = 12345 instance_name = team1 mail_location = maildir:~/mail:INBOX=/var/vmail/%d/%u mail_plugins = " notify replication" mail_privileged_group = mail 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 spamtest spamtestplus virustest editheader servermetadata imapflags notify 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 = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * mail_replica = tcps:server2.domain.de:12345 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags +editheader +regex +spamtest +spamtestplus +virustest +servermetadata sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve sieve" replication_dsync_parameters = -D -d -N -l 30 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vexim } unix_listener replication-notify { mode = 0666 user = vexim } } service auth { unix_listener auth-client { group = vexim mode = 0660 user = Debian-exim } unix_listener auth-userdb { group = vexim mode = 0666 user = vexim } } service config { unix_listener config { user = vexim } } service doveadm { inet_listener { port = 12345 ssl = yes } user = vexim } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </etc/ssl/certs/wildcard.domain.de.pem ssl_cipher_list = HIGH:!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_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_plugins = " notify replication imap_sieve" } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log mail_plugins = " notify replication sieve" } protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536 } Any help appreciated. Niels

1 1

Password mismatch after upgrade to Ubuntu Focal
by Jeffrey van Doesburg 16 Jun '20

16 Jun '20

Hi! Today I upgraded one of our Dovecot servers from Ubuntu 18.04 to Ubuntu 20.04. After the upgrade I have login issues because the password didn't match. I also installed Dovecot on a clean Ubuntu 20.04 server with the same configuration files. And here I also got the password match issue. We're using LDAP for managing the login credentials and I'm 100% sure the password is correct. With the debug options on, you will see something like this: CRYPT(<PLAIN_TEXT_PASSWORD>) != '$6$<SECRET_PASSWORD_HASH>' Does somebody know if there are know issues with Dovecot 2.3.7.2- 1ubuntu3.1 on Ubuntu 20.04 and with the LDAP driver? dovecot -n ------------------------- # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-33-generic x86_64 Ubuntu 20.04 LTS ceph # Hostname: server.example.tld auth_verbose = yes disable_plaintext_auth = no listen = *, [::] log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = POP/IMAP Service ready. mail_fsync = always mail_location = maildir:/mail/%u mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile:/etc/dovecot/acls/:cache_secs=30 autosubscribe = Trash autosubscribe2 = Sent autosubscribe3 = Drafts } protocols = imap pop3 service auth { user = root } service imap-create-folder { executable = script-login /usr/local/sbin/dovecot-create-dirs.sh } service imap-login { process_min_avail = 15 service_count = 0 } service imap { executable = imap imap-create-folder } service pop3-login { process_min_avail = 15 service_count = 0 } service pop3 { drop_priv_before_exec = yes } ssl = no userdb { driver = prefetch } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl } protocol pop3 { pop3_uidl_format = %f } ------------------------------ /etc/dovecot/dovecot-ldap.conf ------------------------------ hosts = ldap.server.example.tld dn = <XXXXX> dnpass = <XXXXX> auth_bind = no ldap_version = 3 base = <XXXXX> pass_attrs = <XXXXX> pass_filter = <XXXXX> ----------------- Thanks! Jeffrey

2 5

Send SPF SoftFails to Junk
by Scott A. Wozny 14 Jun '20

14 Jun '20

Hello Dovecot gurus, I've set up SPF checking on my postfix gateway and have confirmed that messages from domains set with hard fails that don't come from a good sender are rejected outright. Messages from domains set with a softfail that come from bad sources are tagged in the message header with "Softfail (domain owner discourages use of this host)", but end up in the user's Inbox, anyway. I suppose I kind of figured DoceCot would see the SPF softfail in the message header and automagically route that message to Junk, but it didn't. I've looked around Google and the Dovecot documentation to see if there are any instructions on how to do this, but I can't find anything. Is there an easy way to do this or do I need something more advanced in the way of a spam filtering system? OR is doing this my mail client's responsibility and I need to look around my Thunderbird settings? I suppose it's also possible that Postfix needed to do something beyond adding the Received-SPF line in the message header, but I didn't see anything about that in the Policy-SPF config. This is my first foray into SPF so I'm open to any suggestions. Thanks, Scott

2 2

Login auth strip domain from username
by David Pottage 14 Jun '20

14 Jun '20

Hi, I have just discovered that the IMAP account setup wizard in outlook 2019 assumes that the email address for a user is the same as their username, and there is no easy way to separately enter different user. (It can be done via hidden dialog boxes, command line switches and registry hacking, but it is far from easy [1]) Like many small setups, the dovecot accounts on my mail server map directly to unix accounts on the machine, and the IMAP password for each account is the same as the unix login password. I have now got outlook sorted and talking to my IMAP server, but seeing as this issue will almost certainly arise again, with out over-simplified MUA software, is there a setting in dovecot that if it is given an email address as a login username it strips off the domain part, and tests the user part against the password supplied? If you know how to do that for postfix for sending email, then even better! [1] https://superuser.com/questions/1391960/how-to-enter-username-of-imap-accou… -- David Pottage

4 3

handling spam from gmail.
by Marc Roos 12 Jun '20

12 Jun '20

I am sick of this gmail spam. Does anyone know a solution where I can do something like this: 1. received email from adcpni444(a)gmail.com 2. system recognizes this email address has been 'whitelisted', continue with 7. 3. system recognizes as this email never been seen before 4. auto reply with something like (maybe with a wait time of x hours): Your message did not receive the final recipient. You are sending from a known spam provider network that is why we blocked your message. Please confirm that: - you are not a spammer and - you have permission to use the mail adress you send your message to - you and your provider agree to uphold GDPR legislation - you and your provider are liable for damages when breaching any of the above. Click link to confirm and you agree with the above https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf 5. sender clicks confirm url 6. email address is added to some white list. 7. email is delivered to recipient.

16 27

Read-flag of mails don't update
by Marius Rasch 12 Jun '20

12 Jun '20

Hi, since one or two month I have a problem with Dovecot not updating the read-flag on mails using IMAP. I receive new mails, but when reading, they still unread on other devices (but shown as read on the first device). When I remember correct, this problem doesn't come with an update of dovecot, but just occured at some time. But I've updated dovecot since then a few times. Whenever a client connects to dovecot I get an panic in the log. I therefore added a log file and my dovecot configuration (is this fine or does it need to be in the mail body?). There are system information in the output of dovecot -n; the filesystem dovecot is running on is ext4. I hope I provided all information needed and seeing forward to get a hint what the problem might be. Marius

3 7

executing script on mail arrival from sieve
by Voytek Eymont 12 Jun '20

12 Jun '20

I currently have a basic script to process some mails, it runs from cron every 10 minutes, basically, sieve copies some mails to subfolder on mail arrival, script fetches mails if any from this subfolder then processes these mail, get maybe 1 or 2 or often none but cron runs the script every 10 minutes, most times not needed as nothing is retrieved it's pretty crude - but works getmail fetches mails to local folder, deletes in subfolder munpack mailfile to unMIME links dumps HTML to txt looking at wiki2, 'Pigeonhole Sieve Extprograms Plugin', is this what would allow to execute my script on new mail arrival? I can't quite figure out how to.. if anyone has any sample, I might try to adapt to my need.. thanks (probably I should just leave like it is till I understand the docs...) thanks, V

2 2

Doveadm Backup (other) issues
by Gingko 11 Jun '20

11 Jun '20

Hello, I also have issues using Dovecot Backup. I am trying to Backup (or possibly Sync - one way) a single user IMAP account from a remote server, unknown type, to my own server. For that purpose, I defined the following parameters : imapc_host = <host name> imapc_user = <user name> imapc_password = <password> imapc_features = rfc822.size (<user name> has format: name(a)example.com, and <host name> is the name of the imap remote server that I use for getting mails) … and then I issued the following command: doveadm backup -R -u <user name, format name(a)example.com> imapc: ... but doing this, I get the following answer: dsync(<user name>): Info: imapc(<host name>:143): Connected to <host IP address>:143 (local 192.168.1.2:52940) dsync(<user name>): Error: Failed to initialize user: namespace configuration error: Namespace mail/ can't have alias_for= to a different storage (different root dirs) How can I solve this? If there is something not matching between servers, I may eventually change configuration on my side, but I think I would first have to know which feature(s) I have to know from the remote server in order to create the matching one on my server. Is there a way to list all relevant data coming from the remote server? Also: Doing this, is it necessary that the source user name be the same as the destination user name? Is it possible to backup an IMAP account to a user account having a completely different name? Regards, Gingko

5 7

Dovecot /VMWare Boxer
by Djule Djukic 11 Jun '20

11 Jun '20

Hello all, My name is Djule Djukic and I am working for Hipotekarna Banka from Montenegro. We are using IMAP email server Dovecot version 2.1.17. As a email clients on our corporate workstations we are using Thunderbird or WebMail and everything is working fine. We decided to introduce MDM solution in our environment and we installed VMWare WorkspaceOne (former Airwatch) which use Boxer as a mail client in App per VPN scenario. When we syncronise email with Boxer we have found that the time and date displayed for some messages have been changed to the time at which the file was synchronized. This is not hapening with all messages. It is happening only with messages in subfolders, never with Inbox. It seems when messages is moved by some rule from WebMail or Thunderbird from Inbox to some subfolder, Boxer is not able to read dates correctly, By seraching on Internet we found couple of explanation what might be possibel cause of this behaviour. https://imapsync.lamiral.info/FAQ.d/FAQ.Dates.txt https://serverfault.com/questions/588618/maintain-email-timestamp-when-tran… https://dovecot.org/pipermail/dovecot/2008-July/032165.html Problem with some email clients is that they not look always for "Date:" from email message header. The "Date:" header is usually the date the message was written or sent the first time, at the writer side. This "Date:" header line is never changed by any transfer or copy. If an email client uses the "Date:" header for displaying the date of a message then no problem in synchronization with wrong date should arise. Obviously this is not a case with a Boxer email application. We tried GMail and everything is working fine. We are wondering if someone can explain what APPEND command could have done in our case? Is it relevant at all for our case? Is it used somehow by thunderbird or webmail clients? Also we would like to hear from someone if there are some improvemnents in further release of dovecot or some configuration that we can implement in order to fix this? Thank you in advanced for your suggestions and contribution, Đule Đukić Specijalista za informacionu bezbjednost / ISO ĐuleĐukić Specijalistaza informacionu bezbjednost / ISO http://www.hipotekarnabanka.com/hb-content/uploads/2014/06/slika1.jpg

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Yes tell that to the people that create rhel6, rhel7 and rhel8 and give lts support. Unless google pays you to train your software to mark their messages as spam, you might want to consider yourself not to smart as well ;) My solution would solve the problem others create (see the other mail). Your solution wastes your time and will always be carrying water to the sea. I think if 50% of providers in the world would do this, it would quickly be end of story for the spam originating from the networks like google and amazon. If there is a McDonalds build next to your home, and their clients throw waste into your garden. You hold McDonalds liable for cleaning this up not? Or are you also going to cleanup their mess indefinitely. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 11:09 To: Marc Roos; dominic; dovecot; lists; users Subject: Re: handling spam from gmail. Am 11.06.20 um 11:04 schrieb Marc Roos: > I have got lots of shit coming from *.google.com like these: > > X-Spam-Status: No, score=2.1 required=3.0 tests=BAYES_00 because you are too dumb to train your bayes give me one such message and i am pretty sure it will fire BAYES_80 or BAYES_99 which will burn it with fire and lead to a milter reject here SpamAssassin 3.3.1 is also not very smart in 2020 so instead ask for dumb solutions which making you part of a bigger problem better do your homework

2 1

Pigeonhole-sieve auto-reply
by ＠lbutlr 11 Jun '20

11 Jun '20

Is it possible to have a sieve script reply with a press message to certain emails (and only certain emails) based on sieve matches? I see a lot on vacation replies, but I want something more specific. Something along the lines of procmails formail command? Everything I’ve searched for is about vacation r filing replies into the same folder as the original message.

2 2

Special use folders in mailbox hierarchy
by Scott A. Wozny 11 Jun '20

11 Jun '20

Dear Dovecot Gurus, Setting up my first IMAP server and looking at the folder structure, I had a mailbox I built on a Dovecot server and a mailbox configured by a hosting provider next to each other in Thunderbird and I noticed that the special use folders (Drafts, Trash and Sent) in my default-ish (I did set them to auto = subscribe) Dovecot install make these folders appear parallel to my Inbox folder where my hosting provider’s default configuration has them under the Inbox hierarchically, along with all the folders I built for mail storage over the use of the account. I did some googling, but I cannot find any guidance on which of these is preferred, why, or how they could be controlled in Dovecot. The default Dovecot config is ambiguous (IMHO) in that the mailbox config elements are children to the inbox namespace (implying they go under Inbox in the hierarchy) but their special_use parameter names are \Name which (if you use a UNIX filesystem paradigm) implies they should be at the root of the hierarchy and, therefore, parallel with Inbox, which is how Thunderbird shows them, but I’m not sure if that’s a mail client decision and not anything to do with the server configuration. Since I can’t access the config of my hosting provider, I can’t make any comparisons, so I thought I’d ask on the list if there is any standard guidance on server side configuration of special use folders in Dovecot or if there’s no guidance available because I’m overthinking this. :) Thanks, Scott

3 3

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

>> Yes tell that to the people that create rhel6, rhel7 and rhel8 and give >> lts support. > >as said that has nothing to do with your wrong training and RHEL has >always the same problem: you can't package the latest and greatest shit >over 10 years because it requrires newer versions of dependencies > >so what you get with your lazyness by using a LTS distribution is a >"never change a running system, just fix the worst bugs and don't touch >anything else" > >upstream developers don't hold development for 10 years > >written from a Fedora workstation with kernel 5.6.18-200.fc31.x86_64 >from last night realyed over a datacenter firewall and a mailserver >using the same kernel > >> Unless google pays you to train your software to mark their messages as >> spam, you might want to consider yourself not to smart as well ;) > >unless i make good money from customers paying for a nearly 100% >hitrate of spam combine with a zero-false-positive policy i am likely >smarter than you I would argue it is quite difficult to identify intelligence. I am pretty sure I would not start with your reasoning. I have a favourite German saying I like to quote in matters like these "gegen Dummheit kämpfen Götter selbst vergebens" >> My solution would solve the problem others create (see the other mail). >> Your solution wastes your time and will always be carrying water to the >> sea. I think if 50% of providers in the world would do this, it would >> quickly be end of story for the spam originating from the networks like >> google and amazon. > >they won't give a shit and when i get such idiotic mails as you propose >i take the phone, call the sender and suggest to fire his mailadmin >better sooner than later > >> If there is a McDonalds build next to your home, and their clients throw >> waste into your garden. You hold McDonalds liable for cleaning this up >> not? Or are you also going to cleanup their mess indefinitely. > >what a nonsense

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

Your logics sucks. There is a difference between how email works and how spamassassin works. You are assuming that everyone in the world is using spamassassin by including it in 'how email works'. Maybe you like to post a link to your bayes files???? Am 11.06.20 um 11:13 schrieb Marc Roos: > You do not understand how mail works. Google mail is only getting > through when spf checks and the likes are being passed. unless you don't manage to get rid of BAYES_00 in case of clear spam messages don't tell me you understand how email works

1 0

RE: handling spam from gmail.
by Marc Roos 11 Jun '20

11 Jun '20

You do not understand how mail works. Google mail is only getting through when spf checks and the likes are being passed. I am not creating any problems with this, I am just bouncing them back. Google has enough billions to handle these issues. If everyone would apply this procedures, people with legitimate email accounts would move from a spam network to some other provider. People joining these providers are the problem, because it allows these networks to mix spam with legitimate email. When clients start moving out, spam networks are becoming easier to hard block and these providers start thinking about their infrastructure and their bussines model. If everyone would be doing this, it is solving the spam problem. My below procedure should be applicable for any network generating a lot of spam. -----Original Message----- From: Reindl Harald [mailto:h.reindl@thelounge.net] Sent: donderdag 11 juni 2020 10:25 To: Marc Roos; dovecot; users Subject: Re: handling spam from gmail. Am 11.06.20 um 10:19 schrieb Marc Roos: > I am sick of this gmail spam. Does anyone know a solution where I can > do something like this: > > 1. received email from adcpni444(a)gmail.com 2. system recognizes this > email address has been 'whitelisted', continue with 7. > 3. system recognizes as this email never been seen before 4. auto > reply with something like (maybe with a wait time of x hours): > Your message did not receive the final recipient. You are sending > from a known spam provider > network that is why we blocked your message. Please confirm that: > - you are not a spammer and > - you have permission to use the mail adress you send your message to > - you and your provider agree to uphold GDPR legislation > - you and your provider are liable for damages when breaching any > of the above. > > > Click link to confirm and you agree with the above > https://www.domainwithoutletsencryptcertificate.com/asdfasdfadsfaf > > 5. sender clicks confirm url > 6. email address is added to some white list. > 7. email is delivered to recipient. and i am sick of people not understanding how email works! you don't send unasked mail to a in the most cases forged sender unless you want to be part of the problem backscatters and brainless autoreplies have to be burnt with fire

1 0

Dovecot fs quota reports quota as byte
by Kazim Koybasi 11 Jun '20

11 Jun '20

Hello, My dovecot configuration is like below. My filesystem quota is reported as kb and dovecot quota reported as bytes so dovecot quota becomes wrongly greater than filesystem quota. How can I solve this issue? Any help apretiated. Quota name Type Value Limit % user STORAGE 10428416 3242880 321 # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 CentOS Linux release 8.1.1911 (Core) # Hostname: suretired auth_mechanisms = plain login auth_username_format = %Ln debug_log_path = /var/log/dovecot.log first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_debug = yes mail_location = maildir:~/Maildir:INDEX=/var/no-quotas/index/%u:CONTROL=/var/no-quotas/control/%u mail_plugins = quota 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 spamtest spamtestplus mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { quota = fs:user sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/default.sieve sieve_extensions = +spamtest +spamtestplus sieve_spamtest_max_value = 15 sieve_spamtest_status_header = X-Spam-Score: (-?[[:digit:]]+\.[[:digit:]]).* sieve_spamtest_status_type = score } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-userdb { group = postfix mode = 0600 user = dovecot } } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 2424 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 1024 } service quota-warning { executable = script /usr/bin/quota-warning.sh unix_listener quota-warning { group = dovecot mode = 0600 user = dovecot } user = dovecot } ssl_cert = </etc/pki/dovecot/certs/letsencrypt/fullchain1.pem 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:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !TLSv1 userdb { driver = passwd } protocol lmtp { info_log_path = /var/log/dovecot-lmtp.log log_path = /var/log/dovecot-lmtp-errors.log mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve quota } protocol imap { mail_plugins = quota quota imap_quota } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log managesieve_max_line_length = 65536 } protocol pop3 { mail_plugins = quota pop3_quota quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

1 0

How to unset namespace configuration from dovecot.conf in conf.d/99-cutom.conf?
by Py Retta 09 Jun '20

09 Jun '20

Dear all, my /etc/dovecot/dovecot.conf [0] that is shipped with the Linux distro (Ubuntu 18.04, dovecot 2.3.10) has a namespace section: namespace inbox { ... mailbox Sent { ... } ... } I need to remove this whole section from the configuration, but I need to do this in a file such as /etc/dovecot/conf.d/99-custom.conf because I want this modification to be stable against automatic updates of dovecot.conf shipped by the distro. This raises the question, how do I "unset" an earlier namespace configuration at a later point in the stack of config files? Speaking in terms of `doveconf -n`, snippet [1] below lists the original configuration (including namespace setup) and [2] lists the desired configuration that results from deleting the namespace passage from dovecot.conf. However, I would like to achieve it without deleting it from dovecot.conf but by adding sth to conf.d/99-custom.conf. Thanks a lot, Py [0] original dovecot.conf (only relevant namespace section): # Default private namespace setup compatible with Courier-IMAP. namespace inbox { separator = . prefix = INBOX. inbox = yes mailbox Sent { auto = subscribe # autocreate and autosubscribe the Sent mailbox special_use = \Sent } mailbox Spam { auto = create # autocreate Spam, but don't autosubscribe special_use = \Junk } mailbox Drafts { auto = create special_use = \Drafts } mailbox Trash { auto = create special_use = \Trash } } [1] `doveconf -n` for the original configuration: # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 imapflags notify namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } prefix = INBOX. separator = . } passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" } [2] `doveconf -n` for the desired configuration (with the namespace section in dovecot.conf removed): # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (2248) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (2251) # OS: Linux 4.15.0 x86_64 Ubuntu 18.04.4 LTS ext4 # Hostname: ############ auth_mechanisms = ####################### auth_username_chars = ################ disable_plaintext_auth = #### first_valid_uid = #### imap_client_workarounds = delay-newmail imap_logout_format = rcvd=%i, sent=%o mail_home = ################## mail_location = ##################### mail_log_prefix = "service=%s, user=%u, ip=[%r]. " mail_plugins = " quota" managesieve_logout_format = rcvd=%i, sent=%o 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 imapflags notify passdb { driver = plesk } plugin { quota = maildir:User quota quota_grace = 0 quota_warning = storage=95%% quota-warning %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = rcvd=%i, sent=%o, top=%t/%p, retr=%r/%b, del=%d/%m, size=%s protocols = imap pop3 sieve service auth-worker { group = user = } service auth { group = unix_listener auth-userdb { group = popuser mode = 0600 user = popuser } user = } service imap-login { process_limit = 1024 service_count = 1 } service imap { process_limit = 1024 service_count = 1 } service pop3-login { process_limit = 1024 service_count = 1 } service pop3 { process_limit = 1024 service_count = 1 } service quota-warning { executable = ################ unix_listener quota-warning { user = popuser } user = popuser } service stats { unix_listener stats-writer { user = popuser } } ssl_cert = ################ ssl_cipher_list = ############# ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=popuser gid=popuser driver = static } protocol imap { mail_plugins = " quota imap_quota" } protocol pop3 { pop3_uidl_format = UID%u-%v } protocol lda { mail_plugins = " quota sieve" }

1 0

doveadm protocol bug
by Felipe Gasper 08 Jun '20

08 Jun '20

Hi everyone, On 26th May I emailed this list a few times about an apparent protocol bug in Dovecot’s server-side doveadm implementation. Later that day I sent in a pull request to fix the issue. Thread reference: https://dovecot.org/pipermail/dovecot/2020-May/119066.html Pull request: https://github.com/dovecot/core/pull/129 Thus far neither the mailing list emails nor the PR have garnered any responses. Can someone please weigh in on these? It’s totally understandable if Dovecot’s behavior here is going to say as-is; I’d just like some confirmation so we can note it in our client implementation. (Switching our client to the HTTP API would be out-of-scope for our current project.) Thank you again! cheers, -Felipe Gasper

1 0

Can't share a mailbox
by Maxime DERCHE 08 Jun '20

08 Jun '20

Hello, I have a "notifs@" generic mail account, intended to receive technical monitoring messages. I need to share it with the people of the analyst team. I created a shared namespace, and enabled the modules. doveadm acl creates the dovecot-acl file but not the acl_shared_dict file. I guess something prevents it from doing it, but I fail to see what. It is a LDAP setup, and there is only one vmail (uid/gid 500) UNIX account to read and write the files on the file system. $ > doveadm acl add -u notifs(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" user=maxime.derche(a)test.example.tld :lrw $ > doveadm acl debug -u maxime.derche(a)test.example.tld "shared/notifs(a)test.example.tld/INBOX" doveadm(maxime.derche(a)test.example.tld): Info: Mailbox 'INBOX' is in namespace 'shared/notifs(a)test.example.tld/' doveadm(maxime.derche(a)test.example.tld): Info: Mailbox path: /var/vmail/test.example.tld/notifs/mail doveadm(maxime.derche(a)test.example.tld): Info: Per-user private flags in mailbox: \Seen doveadm(maxime.derche(a)test.example.tld): Info: User maxime.derche(a)test.example.tld has rights: lrw doveadm(maxime.derche(a)test.example.tld): Error: User maxime.derche(a)test.example.tld is missing 'lookup' right doveadm(maxime.derche(a)test.example.tld): Info: Mailbox shared/notifs(a)test.example.tld/INBOX is NOT visible in LIST /var/vmail/test.example.tld/notifs/mail/dovecot-acl: ---------------------------------------- user=maxime.derche(a)test.example.tld :lrw ---------------------------------------- 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 # Hostname: server.example.tld auth_debug = yes auth_mechanisms = plain login auth_verbose = yes lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes mail_access_groups = vmail mail_debug = yes mail_gid = 5000 mail_location = maildir:~/Maildir mail_plugins = quota acl mail_privileged_group = mail mail_server_admin = mailto:postmaster@test.example.tld mail_shared_explicit_inbox = yes mail_uid = 5000 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 { list = children location = maildir:%%h/mail:INDEXPVT=~/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } 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 = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/var/vmail/shared-mailboxes imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /etc/dovecot/sieve-after sieve_before = /etc/dovecot/sieve-before sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = " imap lmtp sieve" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/ssl/certs/cert.pem ssl_cipher_list = HIGH:!ADH:!AECDH:!PSK:!KRB5:!RC4:!DES:!3DES:!MD5 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 { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/vmail/%d/%n } protocol lmtp { mail_plugins = quota acl sieve userdb { args = allow_all_users=yes uid=vmail gid=vmail home=/var/vmail/%d/%n mail=maildir:~/mail driver = static name = } } protocol imap { mail_plugins = quota acl imap_sieve imap_acl } ---------------------------------------- Does anyone see what I'm doing wrong here? Kind regards, -- Maxime DERCHE Information System Consulting France | NVMQVAM SOLVS https://www.mdisc.fr/ OpenPGP Key ID: 0x814E02A25697FD13 OpenPGP Key Fingerprint: 8B7B 60C9 1095 A198 C883 5205 814E 02A2 5697 FD13

1 0

Doveadm Backup issues
by Francis Augusto Medeiros-Logeay 07 Jun '20

07 Jun '20

Hi, I'm trying to use doveadm backup but I'm having a few issues. When trying locally: `doveadm backup -D -A maildir:/usr/local/backup` It results that no mailbox is separated by user - all seems to sync on the same folder, messing up with the folder structure of the original maildir. When trying remotely: `doveadm backup -D -A -N ssh -i mykey root@myremotebackup.com:/backup doveadmin dsync-server -A` I get this error line for each user: dsync-local(theuser(a)thedomain.com)<5DNrEXdG1l5tAgAAqsACHw>: Error: read(remote) failed: EOF (version not received) doveadm(theuser(a)thedomain.com): Fatal: execvp(ssh) failed: No such file or directory I'd be very thankful if someone could help me with this. Best, Francis -- Francis Augusto Medeiros-Logeay Oslo, Norway

3 5

Deliver administrative message ignoring user quota
by Peter Folta 07 Jun '20

07 Jun '20

Hi everyone, I have a separate internal system running on a different host that needs to put an administrative email into a user’s inbox. I’ve been playing around with the “doveadm mailbox save” command via Doveadm’s HTTP API (https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save <https://doc.dovecot.org/admin_manual/doveadm_http_api/#doveadm-mailbox-save>). This works quite well provided the user is within quota limit, however, I would like to be able to deliver these messages even if the email account is over quota. I noticed that it’s possible to override the quota configuration using dovecot-lda by overriding plugin/quota with the “noenforcing” directive as explained in https://wiki.dovecot.org/Quota/Configuration <https://wiki.dovecot.org/Quota/Configuration>. I don’t currently use LDA, SMTP servers based on Postfix deliver mail via LMTP and I need to be able to deliver this message from a different host in the network. The HTTP API doesn’t seem to support overriding the quota config. What would be the best way to go about this? Thanks Peter

2 2

(no subject)
by Stephen Blackwell 07 Jun '20

07 Jun '20

I want to disable the time penalty for dovecot imap authentication. When receiving a valid user-password combo the server responds in .04 seconds. When I send in an invalid comination it will either respond in 1.544 or 2.044 seconds += .002 I am using dovecot to test a program that sends a login request to a server and processes the response. I want to be able to send a series of valid and invalid login attempts. The issue is that with the 2 seconds delay for a bad login attempt, the tests are too slow to run in production I can see that the delay is defined in auth-penalty.h Is there a way, in the config file, to set AUTH_PENALTY_INIT_SECS = 0, or any other way to remove the time delay for an invalid login. I am running dovecot version 2.2.33.2 I am running without root permissions I do not want to make changes outside of the dovecot config file, password file, or run folder. -- Stephen

3 2

Cannot log in to IMAP server and logs are unclear as to why
by Scott A. Wozny 07 Jun '20

07 Jun '20

I’m trying a super basic config based upon https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP but before I work on shipping mail through Postfix to DoveCot, I wanted to make sure IMAP is working first, but I can’t even get a basic login to so I thought I’d see if the gurus on the list might be able to point out I’m doing wrong. The documentation is pretty good, but there were some gaps I had to guess at and I’m presuming that’s where I went wrong. I’ve turned SELinux to permissive mode, for now. Here’s the doveconf -n: # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-1062.12.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: imap first_valid_uid = 1000 listen = 192.168.1.207 mail_gid = vmail mail_home = /var/vmail/%d/%n mail_location = sdbox:~/mail mail_uid = vmail mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = scheme=PLAIN username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap lmtp service lmtp { group = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } I wasn’t sure how to set rights on the users file: [sawozny@imap var]$ cat /etc/dovecot/users test@test.com:{plain}test [sawozny@imap var]$ ls -la /etc/dovecot/users -rw-r--r--. 1 root root 26 Jun 3 23:31 /etc/dovecot/users Also, didn’t know what rights to set on the /var/vmail directoy so I did this: drwxrwx---. 3 vmail vmail 4096 Jun 3 20:52 vmail This directory is also empty except for the lost+fond directory that comes with a disk mount point. My understanding is that the mail home and maildir will manifest automagically on first login, but if I need to prime the pump, please let me know what I need to do. For my test, I did: [sawozny@imap var]$ telnet 192.168.1.207 143 Trying 192.168.1.207... Connected to 192.168.1.207. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN] Dovecot ready. 01 LOGIN test(a)test.com test 01 NO [UNAVAILABLE] Internal error occurred. Refer to server log for more information. Connection closed by foreign host. And the results in the /var/log/maillog file are: Jun 3 23:35:34 imap dovecot: auth: Error: passwd-file /etc/dovecot/users: User test(a)test.com is missing userdb info Jun 3 23:35:44 imap dovecot: auth: Error: passwd-file(test(a)test.com,192.168.1.207,<DBqafDan7ODAqAHP>): user not found from userdb Jun 3 23:35:44 imap dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=843055105 (auth connected 0 msecs ago, handshake 0 msecs ago, request took 0 msecs, client-pid=12047 client-id=1) Jun 3 23:35:44 imap dovecot: imap-login: Internal login failure (pid=12047 id=1) (internal failure, 1 successful auths): user=<test(a)test.com>, method=PLAIN, rip=192.168.1.207, lip=192.168.1.207, mpid=12049, secured, session=<DBqafDan7ODAqAHP> I’m not sure where I’ve gone wrong. From my understanding of the documentation, all I need in the userdb is name and password. UID, GID and HOME are also indicated as required, but I set them at the system level, so why is the system telling me the user was not found? This definitely isn’t my first rodeo with Linux, but I know almost nothing about messaging so in that regard I’m a totally n00b and would really appreciate some guidance. Thanks, Scott

3 5

Only show mails within 30 days or 60 days?
by hfh＠cndns.com 05 Jun '20

05 Jun '20

How to display emails within 30 days or 60 days in inbox, sent box, etc. For example, in the mail client tool, the user clicks the inbox button and only sees the mail within 30 days. The virtual mailbox plugin will only generate a new mailbox. Thank you！！！

4 3

manual mdbox lock
by rudolf＠padaru.de 05 Jun '20

05 Jun '20

Good Morning, i have a question about the mdbox dotlock technique. We create a new backup strategy for our mailservers because we want to switch the mailformat from mbox to mdbox. Our recent backup plan works mainly with rsync and the inbuild tar function. We want to hande the backups with mdbox similar. Is there a way, how i can write-lock a mail user via the doveadm command or with dotlock files? I have searched the doveadm-sync code but i cant make out the point where the command lock the mailbox for write access. We work with Ubuntu 18, dovecot 2.33.2 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

Mailbox & Server Down
by Andrea Miconi 04 Jun '20

04 Jun '20

My mailboxes are on a Dovecot (IMAP) server.On DNS there is an MX record pointing to the server.To read the mail I use Roundcube.If the server is down, I lose the new mail. I would like to do two things, alternatively. First option.1) I keeep the mail on the provider's server, restoring the original MX record.2) Dovecot does not receive the mail, but should go to download it.3) I can access the server with Roundcube to read the downloaded mail, but if the server is down I can always go to read the mail on the provider's server with its webmail Second optionI install a second mail server and the two have to replicate the mail.But I don't know how to do it, so I need a guide with instructions.Furthermore Roundcube would always access only one server and if this is down, how can I connect to the second one?This is a typical situation for webmail like Yahoo, Outlook or GMail, but I'm not Yahoo, Microsoft and Google ;) Thanks in advance for any advice.

5 7

Error deleting INBOX when doing an imap sync
by Des Magner 04 Jun '20

04 Jun '20

Hi I am trying to set up a new mail server with dovecot. I got it all installed and set up successfully but am running into problems trying to migrate from my current email server. I tried the following command: doveadm -Dv -o imapc_host=[current-imap-host] -o imapc_user=[current-user] -o imapc_password=[password] -o imapc_features=rfc822.size -o mail_fsync=never backup -R -u [user] imapc: It connects fine but eventually fails with the following errors: dsync([user]): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. dsync([user]): Debug: brain S: Remote mailbox tree: INBOX guid=[xxx] uid_validity=1591096439 uid_next=1 subs=no last_change=0 last_subs=0 dsync([user] Debug: imapc([current-imap-host]:143): Disconnected I am guessing the new INBOX is not compatible with the Inbox on my current mail server so it is trying to delete it. If so is there a way I can change my configuration to allow it to be deleted?

3 2

I can no longer use TLS for Windows7 and Outlook
by Mark Constable 03 Jun '20

03 Jun '20

I currently use Ubuntu 20.04 with Dovecot 2.3.7.2 and OpenSSL 1.1.1f. A few months ago there was an update to all these systems and since then I've had to talk W7 and old Mac clients through disabling ports 993/995 with TLS enabled back to ports 143/110 without SSL or they could not pick up email. Thunderbird users (ie; me) were unaffected. Could anyone share a set of port 993/995 SSL settings known to work with Windows7 and Outlook16 using "dovecot -n|grep ^ssl_" please ? Mine is currently... ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/ssl/example.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_compression no_ticket ssl_prefer_server_ciphers = yes I have commented out ssl_cipher_list, ssl_min_protocol and others to get back to whatever the defaults are so I am not simply guessing what the optimal settings would be to cover Win7 and up. Yes I know Win7 is no longer supported but that does not help the 100s of older users I have that can't/won't upgrade their computers.

7 6

Packages for CentOS 8
by Peter 01 Jun '20

01 Jun '20

I've now successfully built Dovecot packages for CentOS 8 that do not have the quota support stripped out. I was able to do this because CentOS has now finally shipped the quota-devel package as well as the other -devel packages that were previously missing from CentOS 8. For those of you who are interested they are in the GhettoForge Testing repo for el8 at: http://mirror.ghettoforge.org/distributions/gf/el/8/testing/x86_64/ These are untested so let me know if anyone experiences any issues with them. Peter

3 6

locking question
by Tom Lieuallen 01 Jun '20

01 Jun '20

We're running dovecot 2.3.10 on two different servers (two different environments). Both very similarly configured (sendmail and procmail for mail delivery); same OS and patch levels. One environment has nearly 10,000 users and hasn't seen problems. The other environment has just a handful of users, but one user is very active with email and has a fairly complicated procmail configuration. I'm having ongoing mail file locking problems with that one user... Procmail says it's using dotlocking and fcntl: procmail v3.22 2001/09/10 Locking strategies: dotlocking, fcntl() I'm using defaults for dovecot: #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl I have seen this a number of times in dovecot's logs. This signifies a start of locking problems with a mailbox. Mailbox aa_checkme_second: fcntl() failed with mbox: No locks available Procmail's logs show this: procmail: Locking "mail/aa_checkme_second.lock" procmail: Assigning "LASTFOLDER=mail/aa_checkme_second" procmail: Opening "mail/aa_checkme_second" procmail: Acquiring kernel-lock procmail: Kernel-lock failed procmail: Unlocking "mail/aa_checkme_second.lock" These errors were not concurrent; dovecot's errors happened first. I've been suspicious that there was a locking conflict of some kind. My only remaining question on that front is about the read locks. Is it worth trying dotlock for it instead of fcntl? If that's not the problem, then could we be running into some system limitations or a bug in the kernel or mailbox storage? The server running dovecot is Centos 6.10. The mailbox storage is on Isilon OneFS 8.1.2.0. I should probably increase dovecot's logging to see if anything else jumps out at me. thank you for any suggestions. Tom Lieuallen Oregon State Univesity

1 0

Problems with userdb and mail deliveribility
by Chris Bennett 01 Jun '20

01 Jun '20

I briefly got some mails delivered, but not anymore. Attached are dovecot-info.log, dovecot-debug.log, dovecot.log, maillog, /etc/mail/passwd smtpd.conf, vaddr, vusers, vdomains Thanks for any help. Chris Bennett

3 4

auth_policy_server vs client_id and x-originating-ip
by Zdeněk Zámečník 01 Jun '20

01 Jun '20

I run into troubles when trying to set up auth_policy_server in Dovecot 2.3.10.1. It works almost as expected but I cannot get client ID in this process. By setting up "imap_id_log=*" I see in log that Dovecot gets details about mail client like name and version: May 31 14:20:58 mail dovecot: imap(xxx(a)example.xxx)<24796><ft7ytfCmjdZWMSZQ>: ID sent: name=Thunderbird, version=68.8.1 But the auth_policy_server is getting all details except this ID, it's empty: May 31 14:20:58 mail auth-policy[10357]: { May 31 14:20:58 mail auth-policy[10357]: device_id: '', May 31 14:20:58 mail auth-policy[10357]: login: 'xxx(a)example.xxx', May 31 14:20:58 mail auth-policy[10357]: protocol: 'imap', May 31 14:20:58 mail auth-policy[10357]: pwhash: '097a', May 31 14:20:58 mail auth-policy[10357]: remote: '1.2.3.4', May 31 14:20:58 mail auth-policy[10357]: tls: true May 31 14:20:58 mail auth-policy[10357]: } However in some cases I see that client_id is passed to auth_policy_server: May 31 14:27:41 mail auth-policy[10357]: { May 31 14:27:41 mail auth-policy[10357]: device_id: '"name" "Outlook-iOS-Android" "version" "2.0"', May 31 14:27:41 mail auth-policy[10357]: login: 'yyy(a)example.xxx', May 31 14:27:41 mail auth-policy[10357]: protocol: 'imap', May 31 14:27:41 mail auth-policy[10357]: pwhash: '0b63', May 31 14:27:41 mail auth-policy[10357]: remote: '3.4.5.6', May 31 14:27:41 mail auth-policy[10357]: tls: true May 31 14:27:41 mail auth-policy[10357]: } I think I am missing some important point. Maybe IMAP command ID and client_id are totally different. Can you please advise? Is it possible to pass details about mail client to auth_policy_server? Second question is: how I can get "x-originating-ip" from ID command to auth_policy_server? Below is my config file: # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (67bf5bd7) # OS: Linux 5.3.18-2-pve x86_64 Debian 10.4 # Hostname: mail.z-technics.com 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_hibernate_timeout = 5 secs imap_id_log = * imap_id_retain = yes login_trusted_networks = 127.0.0.1 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 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_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-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } 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 1

2.3.10 + lazy expunge
by Matt Bryant 01 Jun '20

01 Jun '20

Hi, so currently run dovecot 2.2.x on CentOS 7 box and was looking to upgrade to 2.3.10. I use lazy expunge atm into a different namespace but saw on the new doco pages that is is depracted in 2.3.0. Have tested and still seems to work so question is more around why ? Why would this be deprecated given using a different namespace allows 2 things a) the folder where message is located is taken accross so if I want to restore and know where it went b) namespace allows me to specify an alternate location for storing the messages. Also given it does still work is there any indication as to what version the deprecation basically equates to it not working. rgds Matt ------ 8< --------- namespace Deprecated since version v2.3.0.

1 0

identify 143 vs 993 clients
by mj 01 Jun '20

01 Jun '20

Hi, I am trying to find a nice way to identify dovecot clients that are still configured to use port 143 to connect to our mailserver, from the dovecot logs. I would then ask them to move over to 993, and finally disable port 143 altogether. When looking at the dovecot logs, it seems this is not logged in any obvious way. Of course I could use netflow etc, but that would not give us usernames, but IP's, etc. So, is there a nice way to somehow indicate in the dovecot logs, if a client connected on 143 or on 993? Thanks!

13 25

Running doveadm without config file?
by Joseph Tam 01 Jun '20

01 Jun '20

It would be useful to run the "doveadm" utility on a non-dovecot server e.g. generating password hashes: # echo plaintextpass | doveadm pw -s BLF-CRYPT doveadm(user): Fatal: Error reading configuration: stat(/etc/dovecot/dovecot.conf) failed: No such file or directory Is there a way to circumvent the need for a configuration file? Joseph Tam <jtam.home(a)gmail.com>

2 4

Current thinking on backups ?
by Laura Smith 30 May '20

30 May '20

Hi, What are people doing for backups ? My current process is LVM snapshot and backup from that to NFS share. But there seems to be hints around the internet that people use/abuse "doveadm backup" for backup purposes even though it seems its original intention was for transferring mailboxes between dovecot instances. Assuming its ok to "doveadm backup" to an NFS share, is it ok to use "doveadm backup" when dovecot has replication setup (replication-notify etc.) ? Or will it interfere ? Thanks! Laura

4 4

Operation not permitted - fchown() failed for /run/dovecot/login
by Dshah 30 May '20

30 May '20

# dovecot --version 2.3.10.1 (a3d0e1171) Dovecot is unable to start, I see error " Fatal: fchown() failed for /run/dovecot/login: Operation not permitted" what could be the problem? any help please $ls -la /var/mail/ drwxr-xr-x 1 root root 4096 May 29 17:32 . drwxr-xr-x 1 root root 4096 May 28 17:08 .. drw------- 2 root root 4096 May 29 17:32 domains ====# cat /etc/dovecot/dovecot.conf===== auth_mechanisms = plain login auth_username_format = %Lu auth_verbose = yes auth_debug = yes auth_debug_passwords = no log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = IMAP server ready disable_plaintext_auth = no protocols = imap pop3 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/mail/domains/%d/%n first_valid_gid = 105 first_valid_uid = 102 last_valid_gid = 105 last_valid_uid = 102 service anvil { client_limit = 2100 } ssl_cert = </secret/tls.crt ssl_key = </secret/tls.key ssl_ca = </secret/ca.crt namespace inbox { inbox = yes mailbox Trash { auto = create special_use = \Trash } mailbox Spam { auto = no special_use = \Junk } mailbox Ham { auto = no } mailbox Sent { auto = subscribe special_use = \Sent } } # service auth { # unix_listener auth-master { # mode = 0600 # user = vmail # } # unix_listener /var/spool/postfix/private/auth { # mode = 0666 # user = postfix # group = postfix # } # user = root # } # service auth-worker { # user = root # } # protocol lda { # log_path = /home/vmail/dovecot-deliver.log # auth_socket_path = /var/run/dovecot/auth-master # postmaster_address = postmaster(a)razalabs.com # } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } userdb { driver = static args = uid=102 gid=105 home=/var/mail/domains/%d/%n allow_all_users=yes } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== =================/etc/dovecot/dovecot-sql.conf.ext=============== driver = mysql connect = host=localhost dbname=mail user=root password=pass default_pass_scheme = CRYPT password_query = SELECT email as user, password FROM users WHERE email='%u'; =================dovecot-sql.conf.ext=============== and postfix =================/etc/postfix/main.cf=============== inet_protocols = all meta_directory = /etc/postfix shlib_directory = /usr/lib/postfix myhostname = mail.my-domain.com mynetworks = 127.0.0.0/8 message_size_limit = 30720000 virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /var/mail/domains virtual_uid_maps = static:102 virtual_gid_maps = static:105 smtpd_sasl_type = dovecot smtpd_sasl_path = /var/spool/postfix/private/auth smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_use_tls = yes smtpd_tls_cert_file = /secret/tls.crt smtpd_tls_key_file = /secret/tls.key #virtual_create_maildirsize = yes #virtual_maildir_extended = yes proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks virtual_transport = dovecot dovecot_destination_recipient_limit = 1 smtpd_milters = inet:127.0.0.1:8891 milter_default_action = accept =================/etc/postfix/main.cf===============

1 1

migrating dovecot to new server
by David Mehler 30 May '20

30 May '20

Hello, I'm needing to migrate my dovecot installation it's 2.3 on FreeBSD 12.1 to a new server. I'd ideally like to back up all the mails in the maildir location, copy that over, load in my configuration files, and bring the system back up. I doubt it's that easy, any pitfalls I should watch out for? Thanks. Dave.

4 4

director -> POP3s/IMAPs -> mailbox host
by patosec 28 May '20

28 May '20

Hello again, I did a lot of trial and error already, but I can't seem to find a way to encrypt my dovecot director to dovceot mailbox traffic. Is there a way to configure dovecot director to only use ssl/tls encrypted connections for specific tagged mailbox clusters? (or all clusters, in fact does not matter if it could be restricted to tags) Looks like there is also no documentation available for this sort of configuration. I tried setting my mailbox nodes to "ssl = require" butt after doing so I can't login through director proxy anymore. It always looks like ssl/tls termination is finally done on director side. Anyone tried this already or has a running setup doing encryption from lets say frontend to backend? Thanks, greetings Patrick

2 2

service doveadm - how to debug proxying with director
by patosec 28 May '20

28 May '20

Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or anything else about the doveadm commands at all. Can someone guide me in a direction on what to try next or maybe got a working config regarding doveadm proxying? Thanks in advance! Some technical data regarding my problem: Dovecot Version: 2.3.10 (0da0eff44) Output of a 'doveadm director status' command: mail server ip tag vhosts state state changed users 10.0.0.81 tag1 100 up - 0 10.0.0.82 tag1 100 up - 1 Output of a 'doveadm director ring status' command: director ip port type last failed status ping ms input output buffered buffered peak last read last write 10.0.0.193 9090 self never ring synced 5 - - - - - - 10.0.0.194 9090 right never synced 0 2051 6400 0 757 2020-05-28 09:56:37 2020-05-28 09:56:37 10.0.0.195 9090 left never synced 0 4929 1804 0 37 2020-05-28 09:56:37 2020-05-28 09:56:37 This is my dovecot-director hosts configuration (doveadm related part): service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } # same port as doveadm's inet_listener doveadm_port = 24245 protocol doveadm { # NOTE: director-userdb socket is actually used only for passdb lookups, not userdb lookups auth_socket_path = director-userdb } And here the dovecot-backend hosts configuration (doveadm related part): ### director conf service doveadm { inet_listener { # any port you want to use for this: port = 24245 } } local 0.0.0.0 { # password to use for client authentication doveadm_password = secret # allow client to only use specified list of commands (default is all): #doveadm_allowed_commands = } A 'doveadm user -u test(a)test.com' command on the backend host: userdb: test(a)test.com user : test(a)test.com home : /var/spool/imap/test(a)test.com quota : maildir:User quota quota_rule: *:storage=1048576:messages=153000 A 'doveadm user -u test(a)test.com' command on the director host: userdb: test(a)test.com user : test(a)test.com

2 3

Determinant of umask for sieve_pipe_bin_dir scripts?
by Laura Smith 27 May '20

27 May '20

Hi, What determines the umask of sieve_pipe_bin_dir scripts ? The results from my script are always being set to 0600. My script is simple and shown below, even if I adjust the right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2" RUN_UUID=$(cat /proc/sys/kernel/random/uuid) BASE_DIR="/foo/bar" TARGET_DIR="${BASE_DIR}/${MSG_TYPE}" TARGET_FILE="${TARGET_DIR}/${RUN_UUID}" cat > "${TARGET_FILE}" < /dev/stdin && pigz -9 "${TARGET_FILE}"

2 2

How to make IMAPS SSL Cert for Dovecot that works with Thunderbird
by hanasaki＠gmail.com 27 May '20

27 May '20

Hello all, What are the instructions for making an SSL cert for Dovecot IMAPS? Two methods have been tried, and work, with Evolution; however generate the following error when Thunderbird tries to connect. Thank you, method 1 : self signed openssl req -newkey rsa:4096 -sha512 -x509 -days 365 -nodes -keyout mykey.key -out mycert.pem method 2 : Let's Encrypt (LE) CA Created with Certbot ERROR TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<+oooooo>

5 10

doveadm: extra lines?
by Felipe Gasper 27 May '20

27 May '20

Hello, I’m sending doveadm “kick” commands to doveadm-server via the doveadm protocol. When “kick” sends back a NOTFOUND error, though, it’s sending back additional output. strace shows: write(3<UNIX:[3158354->3156665]>, "\t\tkick\tmyssltest\n", 17) = 17 ... read(3<UNIX:[3158354->3156665]>, "\n-NOTFOUND\n\n-\n", 8192) = 14 Going by the protocol documentation (https://wiki2.dovecot.org/Design/DoveadmProtocol) there appear to be 3 extra bytes at the end of the server’s response: "\n-\n". Is this a bug in doveadm-server? Or am I misreading the protocol documentation? Thank you! cheers, -Felipe Gasper

1 2

Panic: assert opcode == HASH_TABLE_OP_UPDATE during replication (dsync-local)
by Alexey 26 May '20

26 May '20

Hello. I got an error and have no idea how to fix it, or workaround it. dsync-local(mymail(a)mymail.org)<PR2hBB86zV52SQAACjx0Gw>: Panic: file hash.c: line 251 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) dsync-local(mymail(a)mymail.org)<PR2hBB86zV52SQAACjx0Gw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7fd8acd5d15d] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fd8acd5d27e] -> /usr/lib/dovecot/libdovecot.so.0(+0xec88b) [0x7fd8acd6688b] -> /usr/lib/dovecot/libdovecot.so.0(+0xec8c1) [0x7fd8acd668c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4ec56) [0x7fd8accc8c56] -> /usr/lib/dovecot/libdovecot.so.0(+0x4f9b3) [0x7fd8accc99b3] -> doveadm(dsync_mailbox_tree_find_delete+0x1b2) [0x5567056b7aa2] -> doveadm(+0x4a265) [0x5567056ad265] -> doveadm(dsync_brain_recv_mailbox_tree_deletes+0xc8) [0x5567056aded8] -> doveadm(dsync_brain_run+0x1ae) [0x5567056aaa9e] -> doveadm(+0x48104) [0x5567056ab104] -> doveadm(+0x58d1f) [0x5567056bbd1f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fd8acd7cb79] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7fd8acd7e0c1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7fd8acd7cc1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fd8acd7cd90] -> doveadm(+0x2e9f4) [0x5567056919f4] -> doveadm(+0x30b16) [0x556705693b16] -> doveadm(+0x3170a) [0x55670569470a] -> doveadm(doveadm_mail_try_run+0x21e) [0x556705694ffe] -> doveadm(main+0x552) [0x5567056851b2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7fd8ac90109b] -> doveadm(_start+0x2a) [0x5567056852fa] This is output of manual run doveadm sync process between dovecot 2.3.10.1 (side with error message) and dovecot 2.3.7.2 (remote side). I have `require ["fileinto"];` on both sides in .dovecot.sieve files. Regards, Alukardd.

1 0

Avoiding logging password when dict lookup fails
by Geo Mander 26 May '20

26 May '20

I've made a unix-socket auth setup, by looking at the examples here: https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-… I need to ship the plain password to the socket as well, so i have simply added %w to the lookup key, like so: key = passdb/U=%u P=%w My problem is, that if the socket connection is down for whatever reason, dovecot will write the entire message above - including the plaintext password - into the logfile. --- May 25 11:17:48 imap-1 dovecot: auth-worker(32690): Error: dict-client: Lookup 'shared/passdb/U=john.doe(a)example.com P=john123 failed: net_connect_unix(/var/run/dovecot/doveauthdsocket) failed: Connection refused (reply took 0.000 secs (0.000 in dict wait, 0.000 in other ioloops, 0.000 in locks)) May 25 11:17:48 imap-1 dovecot: auth-worker(32690): Error: dict( john.doe(a)example.com,8.8.4.4,<Px/Ic3WmsNhb7s1N>): Failed to lookup key shared/passdb/U=john.doe(a)example.com P=john123 -- Can i disable dict client logging? Or can i structure my dict request in a different way to avoid this logging, while still getting the complete user-name and plaintext password shipped over the socket? $ dovecot --version 2.2.36 (1f10bfa63)

1 0

child killed by signal 6
by Peter Nabbefeld 26 May '20

26 May '20

Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my telnet session might help: a11 fetch 1 all * 1 FETCH (RFC822.SIZE 16750 INTERNALDATE "22-May-2020 05:02:34 +0000" ENVELOPE ("Fri, 22 May 2020 03:46:54 +0000" "RE: Http2 tomact server taking time in responding when 1st StreamId is a large integer value like 2147483641" (("Prateek Kohli" NIL "prateek.kohli" "ericsson.com.INVALID")) (("Prateek Kohli" NIL "prateek.kohli" "ericsson.com.INVALID")) (("Tomcat Users List" NIL "users" "tomcat.apache.org")) (("Tomcat Users List" NIL "users" "tomcat.apache.org")) NIL NIL "<d778507f-306b-5395-b583-fc1f2651431d(a)apache.org>" " <DB7PR07MB40285E61F0731810A615E3FB92B40(a)DB7PR07MB4028.eurprd07.prod.outlook.com>") FLAGS (\Seen)) a11 OK FETCH completed a12 fetch 2 all * 2 FETCH (RFC822.SIZE 21146 INTERNALDATE "22-May-2020 06:39:54 +0000" ENVELOPE ("Fri, 22 May 2020 06:39:35 +0000" "RE: RST on TCP level sent by Tomcat" (("Arshiya Shariff" NIL "arshiya.shariff" "ericsson.com.INVALID")) (("Arshiya Shariff" NIL "arshiya.shariff" "ericsson.com.INVALID")) (("Tomcat Users List" NIL "users" "tomcat.apache.org")) (("Tomcat Users List" NIL "users" "tomcat.apache.org")) (("markt(a)apache.org" NIL "markt" "apache.org")("M Venkata Pratap M" NIL "m.m.venkata.pratap" "ericsson.com")) NIL " <AM7PR07MB6561761FA78F23F5AAF398399FB70(a)AM7PR07MB6561.eurprd07.prod.outlook.com>" " <AM7PR07MB65615CD03F422AC8D8384FC09FB40(a)AM7PR07MB6561.eurprd07.prod.outlook.com>") FLAGS ()) a12 OK FETCH completed The first message causes signal 6, the second does not. Probably the problem is killed by the two consecutive "NIL"s? I'm not an experienced administrator, only managing my private computer, so I don't know the meaning of every envelope field. But might these two "NIL"s cause the abort? BTW, to download all messages from my IMAP account to my private dovecot instance I had to delete the first message, since I couldn't download any other messages from the IMAP folder otherwise. Kind regards Peter

3 4

Sieve test string and case sensitivity
by Kim Minh Kaplan 25 May '20

25 May '20

Hello, I have found that Pigeonhole comes with an extensive testsuite against the Sieve RFCs. As I am working on a personal Sieve project I decided to run my tool on this testsuite and it stumbled on "Basic assignment: string test failed"[1]. Pigeonhole defaults to comparator "i;octet"[2] for the string test. But Sieve says that the default comparator should be "i;ascii-casemap"[3]. Did I miss some other part of the standard? Can you point me in the right direction? Thank you, Kim Minh. [1]: https://github.com/dovecot/pigeonhole/blob/master/tests/extensions/variable… [2]: https://github.com/dovecot/pigeonhole/blob/master/src/lib-sieve/plugins/var… [3]: https://tools.ietf.org/html/rfc5228#section-2.7.3

2 1

Sieve addheader directive works only partially
by Peter Folta 25 May '20

25 May '20

Hi all, I want to add a custom header to incoming emails from a particular sender. This is what my user Sieve script looks like: require “editheader”; if address :is "From” “special-sender(a)example.xn--com-9o0a { addheader “X-My-Custom-Header” “Header Value"; } I have enabled the editheader extension in my Dovecot configuration: plugin { … sieve_extensions = +editheader } This doesn’t seem to work and no header is added to the email. However, if I also move the email to a different folder in the same if-block, the header gets added just fine: require “editheader”; require “fileinto”; if address :is "From” “special-sender(a)example.xn--com-9o0a { addheader “X-My-Custom-Header” “Header Value”; fileinto “MyFolder”; } Am I missing something? Thanks Peter

4 6

missing man page for “doveadm dsync-server”?
by Felipe Gasper 25 May '20

25 May '20

Hello, Is there a man page for this command? I don’t see one in the repository. Given its utility in, e.g., syncing mailboxes via SSH, it seems like documentation for this command would be useful? Thank you! -Felipe Gasper

3 3

doveadm backup : Error: Failed to access mailbox
by Laura Smith 25 May '20

25 May '20

Hi All, So close and yet so far. ;-( Have been migrating users from an old Dovecot server to a new one. All of the users have doveadm backup'd perfectly, except for one ! What does the below mean ? $ sudo doveadm -v -o imapc_user=jd(a)example.org.tld -o imapc_password=secretSquirrel -o imapc_host=old-server.example.com backup -1 -R -u jd(a)example.org.tld imapc: dsync(jd(a)example.org.tld): Info: imapc(old-server.example.com:993): Connected to 10.10.10.10:993 (local 10.10.10.11:35858) dsync(jd(a)example.org.tld): Error: Failed to access mailbox Sent Messages (jasmin@example: Mailbox doesn't exist: Sent Messages (jasmin@example (0.001 + 0.000 secs). dsync(jd(a)example.org.tld): Error: Failed to access mailbox Sent Messages (jasmin(a)example.org: Mailbox doesn't exist: Sent Messages (jasmin(a)example.org (0.001 + 0.000 secs). dsync(jd(a)example.org.tld): Error: Failed to access mailbox Drafts (jasmin@example: Mailbox doesn't exist: Drafts (jasmin@example (0.001 + 0.000 secs). dsync(jd(a)example.org.tld): Error: Failed to access mailbox Drafts (jasmin(a)example.org: Mailbox doesn't exist: Drafts (jasmin(a)example.org (0.001 + 0.000 secs). dsync(jd(a)example.org.tld): Error: Failed to access mailbox Deleted Messages (jasmin@example: Mailbox doesn't exist: Deleted Messages (jasmin@example (0.001 + 0.000 secs). dsync(jd(a)example.org.tld): Error: Failed to access mailbox Deleted Messages (jasmin(a)example.org: Mailbox doesn't exist: Deleted Messages (jasmin(a)example.org (0.001 + 0.000 secs).

1 1

A small mistake in a Dovecot error message.
by Bill Shirley 24 May '20

24 May '20

I'm setting up a new mail server and got this message: May 21 11:55:09 vader dovecot[4090]: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssh_dh=</path/to/dh.pem The Dovecot parameter is actually: ss*l*_dh<=/path/to/dh.pem not ssh... Fedora release 32 (Thirty Two) dovecot-2.3.9.3-1.fc32.x86_64 Many thanks for such useful software. Bill

2 1

Dovecot passdb and postfix login
by Laura Smith 24 May '20

24 May '20

Hi, Long story short I've got a fully functional Dovecot IMAP instance and I am now looking to upgrade some perimiter authenticated SMTP relays to authenticate against the Dovecot instance. Trouble is that I am seeing errors such as "auth: Warning: sql: Ignoring changed user_query in /etc/dovecot/local_sql_users.conf, because userdb sql not used." in my Postfix server logs and not able to successfully authenticate via AUTH LOGIN on the Postfi instance. Perhaps I'm missing something obvious from my config ? Here is the doveconf -n from the Postfix server in question: # 2.3.10.1 (a3d0e1171): /etc/dovecot/dovecot.conf # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 # Hostname: foobar.example.com auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1:7 disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u 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/local_sql_users.conf driver = sql } service auth { inet_listener { address = 127.0.0.1 port = 7425 } inet_listener { address = ::1 port = 7425 } unix_listener /var/spool/postfix-authrelay/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } ssl = no The local_sql_users.conf is the same one that's used on the functioning IMAP servers, just copied accross to the authenticated relay server: $ sudo cat /etc/dovecot/local_sql_users.conf driver = pgsql connect = host=foo dbname=bar user=secret password=squirrel default_pass_scheme = ARGON2ID password_query = select dovecot_username as user,password from get_user('%u') user_query = select 'vmail' as uid, 'vmail' as gid iterate_query = select dovecot_username as user from get_users()

2 1

Re: fail2ban setup centos 7 not picking auth fail?
by Voytek Eymont 23 May '20

23 May '20

On Fri, May 22, 2020 2:05 pm, Adi Pircalabu wrote: > On 22-05-2020 10:38, Voytek Eymont wrote: > > Hardly a Dovecot issue. Can you please post the output of this command? > /usr/bin/fail2ban-regex /var/log/dovecot.log > /etc/fail2ban/filter.d/dovecot.conf Adi, thanks, what I get is: # /usr/bin/fail2ban-regex /var/log/dovecot.log /etc/fail2ban/filter.d/dovecot.conf Running tests ============= Use failregex filter file : dovecot, basedir: /etc/fail2ban Use datepattern : Default Detectors Use log file : /var/log/dovecot.log Use encoding : UTF-8 Results ======= Failregex: 5149 total |- #) [# of hits] regular expression | 2) [5149] ^(?:\[\])?\s*(?:<[^.]+\.[^.]+>\s+)?(?:\S+\s+)?(?:kernel:\s?\[ *\d+\.\d+\]:?\s+)?(?:@vserver_\S+\s+)?(?:(?:(?:\[\d+\])?:\s+[\[$]?\S*(?:\(\S+$)?[\]\)]?:?|[\[$]?\S*(?:\(\S+$)?[\]\)]?:?(?:\[\d+\])?:?)\s+)?(?:\[ID \d+ \S+\]\s+)?(?:pop3|imap)-login: (?:Info: )?(?:Aborted login|Disconnected)(?::(?: [^ $]+)+)? \((?:auth failed, \d+ attempts( in \d+ secs)?|tried to use (disabled|disallowed) \S+ auth)$:( user=<[^>]+>,)?( method=\S+,)? rip=<HOST>(?:, lip=\S+)?(?:, TLS(?: handshaking(?:: SSL_accept failed: error:[\dA-F]+:SSL routines:[TLS\d]+_GET_CLIENT_HELLO:unknown protocol)?)?(: Disconnected)?)?(, session=<\S+>)?\s*$ `- Ignoreregex: 0 total Date template hits: |- [# of hits] date format | [338975] {^LN-BEG}(?:DAY )?MON Day %k:Minute:Second(?:\.Microseconds)?(?: ExYear)? `- Lines: 338975 lines, 0 ignored, 5149 matched, 333826 missed [processed in 87.44 sec] Missed line(s): too many to print. Use --print-all-missed to print all 333826 lines

7 8

Sieve regexp matches wrong
by kverizhnikov 23 May '20

23 May '20

Hello! Recently I've faced with strange issue. So, I want to filter some mails which do not contain cyrillic symbols. I would not like receive email on foreign language except russian and I'm using rule below, but it does not work when text of mail has unicode symbol u2019 or ’ - right single quotation mark. |require ["body","regex"];| |# rule:[Regexp test]| |if not body :text :regex ".*[аАбБвВгГдДеЕёЁжЖзЗиИйЙкКлЛмМнНоОпПрРсСтТуУфФхХцЦчЧшШщЩъЪыЫьЬэЭюЮяЯ].*"| |{| | discard;| | stop;| |}| I checked this behavior on different versions of dovecot and pigeonhole, and it was the same in all cases. If I change u2019 to, for instance to apostrophe, it begins work as I expect - the mail discarded. Below some information which was got from sieve-test utility. The text consist of only one phrase *Test’test*. Check string *Test’test *- without u2019, using apostrophe root@a4e4b17d33a1:/srv/mail# tail -2 1586937347.M574837P24389.vps.kveri.ru\,S\=1904\,W\=1944\:2\,S Test'test sieve-test output * Script metadata (block: 0): class = file class.version = 0 location = /srv/mail/roundcube.sieve * Required extensions (block: 1): 0: body (id: 18) 1: regex (id: 13) * Main program (block: 2): Address Line Code 00000000: DEBUG BLOCK: 3 00000001: EXTENSIONS [2]: 00000002: body 00000004: regex 00000006: 3: BODY 00000007: BODY-TRANSFORM: TEXT 0000000b: match type: regex 0000000d: key list: STR[138] ".*[аАбБвВгГдДеЕёЁжЖзЗиИйЙкКлЛмМнНоОпПрРс... 0000009b: 3: JMPTRUE 6 [000000a2] 000000a0: 5: DISCARD 000000a1: 6: STOP 000000a2: 6: [End of code] Performed actions: * discard Implicit keep: (none) In this case the rule works as I expect The second test *Test’test* with ’ instead of apostrophe root@a4e4b17d33a1:/srv/mail# tail -2 1586937347.M574837P24389.vps.kveri.ru\,S\=1904\,W\=1944\:2\,S Test’test sieve-test output * Script metadata (block: 0): class = file class.version = 0 location = /srv/mail/roundcube.sieve * Required extensions (block: 1): 0: body (id: 18) 1: regex (id: 13) * Main program (block: 2): Address Line Code 00000000: DEBUG BLOCK: 3 00000001: EXTENSIONS [2]: 00000002: body 00000004: regex 00000006: 3: BODY 00000007: BODY-TRANSFORM: TEXT 0000000b: match type: regex 0000000d: key list: STR[138] ".*[аАбБвВгГдДеЕёЁжЖзЗиИйЙкКлЛмМнНоОпПрРс... 0000009b: 3: JMPTRUE 6 [000000a2] 000000a0: 5: DISCARD 000000a1: 6: STOP 000000a2: 6: [End of code] Performed actions: (none) Implicit keep: * store message in folder: INBOX In this case email "was located" into INBOX, but I expected it should be discarded. As I said this behavior does not depend on dovecot and pigeonhole version - I've tried dovecot 2.3.7, 2.2.30.x, 2.3.9.3 and 2.3.10, pigeonhole 0.5.7.2, 0.5.9 and 0.5.10, fresh install and working in docker container. The dovecot-sysreport was taken from the last one. What am I doing wrong? Is it pigeonhole bug or smth like that?

2 1

Convert standalone mbox to standalone Maildir with Dsync - hierarchy separator error
by Sam Kuper 23 May '20

23 May '20

Dear Dovecot users/devs, I have the following mbox file: /tmp/dsync_test/mbox/2002-September I would like to convert it to a Maildir: /tmp/dsync_test/maildir (Currently, the latter is just an empty directory.) I am attempting this on an old PC running Debian 9 ("Stretch"). I installed the dovecot-core package in order to make the `dsync` tool available on that PC. I have not otherwise done anything with Dovecot on that PC; for instance, I have not created or edited any Dovecot config files. `man dsync` gives the Dovecot version as 2.2. Inspired by the man page and the Dovecot wiki, here was my first attempt to perform the conversion. (I have added newlines between each line of the output, for readability.) $ dsync -Dv -o 'mail_location=maildir:/tmp/dsync_test/maildir' \ backup \ mbox:/tmp/dsync_test/mbox/:INBOX=/tmp/dsync_test/mbox/2002-September Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_lookup_dict_iterate_visible_next (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(sampablokuper): Debug: Effective uid=1000, gid=1000, home=/home/sampablokuper doveadm(sampablokuper): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/tmp/dsync_test/maildir doveadm(sampablokuper): Debug: maildir++: root=/tmp/dsync_test/maildir, index=, indexpvt=, control=, inbox=/tmp/dsync_test/maildir, alt= doveadm(sampablokuper): Debug: Namespace : Using permissions from /tmp/dsync_test/maildir: mode=0755 gid=default dsync(sampablokuper): Debug: Effective uid=1000, gid=1000, home=/home/sampablokuper dsync(sampablokuper): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:/tmp/dsync_test/mbox/:INBOX=/tmp/dsync_test/mbox/2002-September dsync(sampablokuper): Debug: fs: root=/tmp/dsync_test/mbox, index=, indexpvt=, control=, inbox=/tmp/dsync_test/mbox/2002-September, alt= dsync(sampablokuper): Error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) As you can see, it ends with "Error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace)". So, I tried specifying a hierarchy separator, but this failed too: $ dsync -Dv \ -o 'separator=.' \ -o 'mail_location=maildir:/tmp/dsync_test/maildir' \ backup \ mbox:/tmp/dsync_test/mbox/:INBOX=/tmp/dsync_test/mbox/2002-September Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_lookup_dict_iterate_visible_next (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(sampablokuper): Debug: Effective uid=1000, gid=1000, home=/home/sampablokuper doveadm(sampablokuper): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/tmp/dsync_test/maildir doveadm(sampablokuper): Debug: maildir++: root=/tmp/dsync_test/maildir, index=, indexpvt=, control=, inbox=/tmp/dsync_test/maildir, alt= doveadm(sampablokuper): Debug: Namespace : Using permissions from /tmp/dsync_test/maildir: mode=0755 gid=default dsync(sampablokuper): Debug: Effective uid=1000, gid=1000, home=/home/sampablokuper dsync(sampablokuper): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mbox:/tmp/dsync_test/mbox/:INBOX=/tmp/dsync_test/mbox/2002-September dsync(sampablokuper): Debug: fs: root=/tmp/dsync_test/mbox, index=, indexpvt=, control=, inbox=/tmp/dsync_test/mbox/2002-September, alt= dsync(sampablokuper): Error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) I got the same error again when I tried the command above with "/" instead of "." as the hierarchy separator. Forgive me for my ignorance, but how should I correct the invocation I used above? In other words: using dsync, how can I extract/copy the emails from the mbox to the new Maildir? Thank you! -- A: When it messes up the order in which people normally read text. Q: When is top-posting a bad thing? () ASCII ribbon campaign. Please avoid HTML emails & proprietary /\ file formats. (Why? See e.g. https://v.gd/jrmGbS ). Thank you.

2 3

What causes mails to get striked-over only, and not deleted?
by Sebastian Nielsen 23 May '20

23 May '20

I have tried with this sieve config: imapsieve_mailbox1_name = Sent imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_after = file:/etc/dovecot/sieve/sent.sieve and this sieve file (sent.sieve): discard; This should clearly cause the mail to be deleted right? But whats happen, is that the mail is not deleted, its just marked for deletion (gets a strike-through in Microsoft Outlook). (have tried with _before too, but it wont help). What can I do to ensure the mail actually gets deleted (completely, not moved to trash) and not just flagged for deletion?

3 3

dsync “destination” argument
by Felipe Gasper 22 May '20

22 May '20

Hello, Some code that I didn’t write but am maintaining passes a local script’s path as dsync’s “destination” argument, like so: dsync -D -u john -v backup -R -1 "/code/dsync_client.pl" 127.0.0.1 john(a)mydomain.org dsync_client.pl establishes a TCP connection with a remote dsync process then acts as a proxy between the two dsync processes. “127.0.0.1” and “john(a)mydomain.xn--org-9o0a are given as arguments to dsync_client.pl. I don’t see this usage described in dsync’s man page. I just want to be sure: is this a supported use of dsync? Thank you! cheers, -Felipe Gasper

2 3

fail2ban setup centos 7 not picking auth fail?
by Voytek Eymont 22 May '20

22 May '20

I'm trying to set up fail2ban with dovecot, I have it working on 'old' server Centos 6, but, not getting anywhere with 'new' server on Centos 7 using standard filters I've copied same 'filter' to new server, still get nothing any idea how to figure this out ? on old server, it logs to syslog/messages CentOS release 6.10 (Final) dovecot 2.3.10.1 (a3d0e1171) old # fail2ban-client status dovecot Status for the jail: dovecot |- Filter | |- Currently failed: 2 | |- Total failed: 168 | `- File list: /var/log/dovecot.log `- Actions |- Currently banned: 0 |- Total banned: 32 `- Banned IP list: on new server CentOS Linux release 7.8.2003 dovecot 2.3.10.1 (a3d0e1171) nothing shows up in fail2ban log (ssh, postfix does, only no dovecot) I've copied the actual /etc/fail2ban/filter.d/dovecot.conf from old server, still nothing not sure where/how to look is there a standard/approved doveot filter..? cat jail.local ... [dovecot] enabled = true filter = dovecot logpath = /var/log/dovecot.log maxretry = 3 ignoreip = 127.0.0.1 127.0.0.0/8 ... # fail2ban-client status dovecot Status for the jail: dovecot |- Filter | |- Currently failed: 0 | |- Total failed: 0 | `- Journal matches: _SYSTEMD_UNIT=dovecot.service `- Actions |- Currently banned: 0 |- Total banned: 0 `- Banned IP list: # grep 'auth failed' /var/log/dovecot.log | wc 7669 149916 1558909 # cat dovecot.conf # Fail2Ban filter Dovecot authentication and pop3/imap server # [INCLUDES] before = common.conf [Definition] _daemon = (auth|dovecot(-auth)?|auth-worker) failregex = ^%(__prefix_line)s(?:%(__pam_auth)s(?:$dovecot:auth$)?:)?\s+authentication failure; logname=\S* uid=\S* euid=\S* tty=dovecot ruser=\S* rhost=<HOST>(?:\s+user=\S*)?\s*$ ^%(__prefix_line)s(?:pop3|imap)-login: (?:Info: )?(?:Aborted login|Disconnected)(?::(?: [^ $]+)+)? \((?:auth failed, \d+ attempts( in \d+ secs)?|tried to use (disabled|disallowed) \S+ auth)$:( user=<[^>]+>,)?( method=\S+,)? rip=<HOST>(?:, lip=\S+)?(?:, TLS(?: handshaking(?:: SSL_accept failed: error:[\dA-F]+:SSL routines:[TLS\d]+_GET_CLIENT_HELLO:unknown protocol)?)?(: Disconnected)?)?(, session=<\S+>)?\s*$ ^%(__prefix_line)s(?:Info|dovecot: auth$default$|auth-worker$\d+$): pam$\S+,<HOST>$: pam_authenticate failed: (User not known to the underlying authentication module: \d+ Time$s$|Authentication failure $password mismatch\?$)\s*$ ^%(__prefix_line)s(?:auth|auth-worker$\d+$): (?:pam|passwd-file)$\S+,<HOST>$: unknown user\s*$ ^%(__prefix_line)s(?:auth|auth-worker$\d+$): Info: ldap$\S*,<HOST>,\S*$: invalid credentials\s*$ ignoreregex = [Init] journalmatch = _SYSTEMD_UNIT=dovecot.service # DEV Notes: # * the first regex is essentially a copy of pam-generic.conf # * Probably doesn't do dovecot sql/ldap backends properly (resolved in edit 21/03/2016) # * Removed the 'no auth attempts' log lines from the matches because produces # lots of false positives on misconfigured MTAs making regexp unusable # # Author: Martin Waschbuesch # Daniel Black (rewrote with begin and end anchors) # Martin O'Neal (added LDAP authentication failure regex) # Sergey G. Brester aka sebres (reviewed, optimized, IPv6-compatibility)

2 1

pass a block of parameters to doveadm
by dovecot-user 21 May '20

21 May '20

Hello everyone. Please tell me how to override the configuration file options when using the doveadm utility with the -o switch in case I need to pass a block of parameters, for example, like this: passdb { args = scheme=PLAIN username_format=%u /path/to/file driver = passwd-file } Thanks.

2 1

v2.3.10.1 released
by Aki Tuomi 21 May '20

21 May '20

We are pleased to release v2.3.10.1 Please find it from locations below: https://dovecot.org/releases/2.3/dovecot-2.3.10.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.10.1.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-10957: lmtp/submission: A client can crash the server by sending a NOOP command with an invalid string parameter. This occurs particularly for a parameter that doesn't start with a double quote. This applies to all SMTP services, including submission-login, which makes it possible to crash the submission service without authentication. - CVE-2020-10958: lmtp/submission: Sending many invalid or unknown commands can cause the server to access freed memory, which can lead to a server crash. This happens when the server closes the connection with a "421 Too many invalid commands" error. The bad command limit depends on the service (lmtp or submission) and varies between 10 to 20 bad commands. - 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.

3 2

FTS-lucene errors : language not available for stemming
by David Gessel 21 May '20

21 May '20

I'm getting some log errors with clucene that I am having no luck tracking down on the interwebs. Errors: May 19 05:05:16 indexer-worker(gessel(a)blackrosetech.com)<62971><aPAEI3zLw17A/QAA0J78UA:EF25M3zLw1779QAA0J78UA>: Error: lucene index /mail/blackrosetech.com/gessel//lucene-indexes: IndexWriter::addDocument() failed (#4): language not available for stemming May 19 05:05:16 indexer-worker: Error: May 19 05:05:16 indexer-worker(gessel(a)blackrosetech.com)<62971><aPAEI3zLw17A/QAA0J78UA:EF25M3zLw1779QAA0J78UA>: Error: Mailbox Security: Mail search failed: Internal error occurred. Refer to server log for more information. [2020-05-19 05:05:16] May 19 05:05:16 indexer-worker(gessel(a)blackrosetech.com)<62971><aPAEI3zLw17A/QAA0J78UA:EF25M3zLw1779QAA0J78UA>: Error: Mailbox Security: Transaction commit failed: FTS transaction commit failed: transaction context (attempted to index 1 messages (UIDs 152736..152736)) Config: FreeBSD 11.3-RELEASE-p8 #0 r360490 dovecot-2.3.10_3 clucene-2.3.3.4_19 py37-pystemmer-2.0.0.1 py37-snowballstemmer-1.2.1 icu-67.1,1 plugin { #setting_name = value expire = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size fts_autoindex=yes #zlib_save_level = 6 # 1..9 #zlib_save = gz # or bz2 } plugin { fts = lucene # Lucene-specific settings, good ones are: fts_lucene = whitespace_chars=@. mime_parts } I am considering switch to xapian (solr and java... pls noe) as the port is quite tempting from an ease of integration perspective, but the easiest solution would be to resolve these odd indexing errors. Anyone have a clue? -David

6 11

dsync multiple mailboxes per connection?
by Felipe Gasper 21 May '20

21 May '20

Hello, Is it possible to batch syncs of multiple mailboxes in a single dsync session? We’re transferring users between servers and want to use dsync to transfer the mail; ideally we’d like to avoid creating a separate TCP connection per user. Thank you! cheers, -Felipe Gasper

3 2

how to automatically delete folders from Trash after x days
by chayes＠afo.net 20 May '20

20 May '20

This works great for keeping the Trash from overflowing ... doveadm expunge -A mailbox Trash before 30d ... but it doesn't delete folders that the user put in the trash. What is the recommended method for erasing folders from the trash?

2 1

question about director_mail_servers setting
by Joe Wong 20 May '20

20 May '20

Hello, I have a question about director_mail_servers setting for director, I am aware that I can define a list of dovecot backend hostname there but I am not sure if the hashing apply to the hostname or underlying IP address of each hostname given? What if the IP of a specify hostname is changed? Will director pickup the new IP automatically? Will the same user hashed into the original IP still be mapped back to the new IP in this case? - Joe

1 0

Problem with tika
by Arjen Heidinga 19 May '20

19 May '20

Hello all, For some time now we've bin using solr as a search engine (working great). I have added tika for searching inside documents, however it keeps crashing when indexing. When just indexing mails that arrive works good, but a reindex on all mail constantly crashes with below stacktrace. When I observe the packets with wireshark I see a HTTP-flow going to tika and suddenly, midway a document dovecot (or the server) sends a RST. Sometimes after thousands of documents, sometimes after a few. Usually after a few hundred. It appears there are less errors using http than https. Relevant config: OS: CentOS6, fully updated plugin { fts = solr batch_size = 1 fts_solr = url=https://username:password@solr-01.vevida.net:443/solr/dovecot/ #fts_tika = https://solr-01.vevida.net:443/tika/ batch_size = 1000 fts_autoindex=yes soft_commit=no } # dovecot --version 2.3.9.3 (9f41b88fa) # Configure options: --docdir=%{_docdir}/dovecot \ --disable-static \ --with-nss \ --with-shadow \ --with-pam \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-pgsql \ --with-sqlite \ --with-zlib \ --with-bzlib \ --with-lzma \ --with-libcap \ --with-ssl=openssl \ --with-ssldir=%{ssldir} \ --with-solr \ --with-docs # It is compiled agains the latest openssl # Tika and Solr: Both latest versions. #Stacktrace: doveadm(info(a)samenmetrenske.nl): Info: Sent: Caching mails seq=1..161 doveadm(info(a)samenmetrenske.nl): Panic: file http-client-request.c: line 1173 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) doveadm(info(a)xxxxxxxxxxxxxxxxxxx.x): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x2f) [0x7f95d805acbf] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x26) [0x7f95d805add6] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe90ba) [0x7f95d80660ba] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe9161) [0x7f95d8066161] -> /usr/lib64/dovecot/libdovecot.so.0(+0x41158) [0x7f95d7fbe158] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_send_more+0x424) [0x7f95d8005094] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_connection_output+0x11a) [0x7f95d800a24a] -> /usr/lib64/dovecot/libssl_iostream_openssl.so(+0x8f6a) [0x7f95d57a2f6a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x114483) [0x7f95d8091483] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x61) [0x7f95d807e581] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xdc) [0x7f95d808076c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f95d807e67c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f95d807e8c8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x89105) [0x7f95d8006105] -> /usr/lib64/dovecot/libdovecot.so.0(http_client_request_send_payload+0x1f) [0x7f95d80063cf] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0xd31d) [0x7f95d6ad931d] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_parser_more+0x1a) [0x7f95d6ad83ca] -> /usr/lib64/dovecot/lib20_fts_plugin.so(fts_build_mail+0x761) [0x7f95d6ad6401] -> /usr/lib64/dovecot/lib20_fts_plugin.so(+0x114ca) [0x7f95d6add4ca] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_precache+0x2a) [0x7f95d835ab4a] -> doveadm(+0x31e75) [0x55e7c1052e75] -> doveadm(+0x321fb) [0x55e7c10531fb] -> doveadm(+0x2c321) [0x55e7c104d321] -> doveadm(+0x2c577) [0x55e7c104d577] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x1e8) [0x55e7c104ec38] -> doveadm(doveadm_cmd_run_ver2+0x52e) [0x55e7c105fafe] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55e7c105fb97] -> doveadm(main+0x21a) [0x55e7c1062aca] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f95d7983d20] -> doveadm(+0x1c479) [0x55e7c103d479]

1 1

doveadm backup, question
by dovecot-user 19 May '20

19 May '20

Hello everyone. I am an inexperienced user of dovecot and I faced probably a simple problem, but I still do not understand how to solve it. The issue is related to using doveadm backup - I want to backup mailboxes; make this copy on the same machine (hereinafter, files with backup copies will be taken from this machine into the storage by a separate mechanism, this is not related to the issue). I am using dovecot 2.2.27 (c0f36b0) on Debian GNU/Linux 9 (stretch). The options related to storing mail and attachments are as follows: mail_location = mdbox:/var/mail/%d/%n mail_attachment_dir = /var/mail/%d/%n/attach Thus, the mail of user(a)domain.tld is stored in /var/mail/domain.tld/user/, and mail attachments inside this directory, for example: /var/mail/domain.tld/user/attach. When I start copying (as root while in test mode): #doveadm backup -u "user(a)domain.tld" sdbox:/backup/domain.tld/user, copying passes, but, as I understand it, the attachments are not copied (I am judging so far by the volume of the initial storage and the received one, it should not differ VERY much, but it differs by 10 times, it seems that it’s just the total amount of attachments). Tell me, plz, how to run doveadm backup correctly so that everything is copied so that you can subsequently deploy it from the backup? Thanks.

1 0

Multiple vulnerabilities in Dovecot
by Aki Tuomi 18 May '20

18 May '20

Dear subscribers, we are sending notifications for three vulnerabilities, - CVE-2020-10957 - CVE-2020-10958 - CVE-2020-10967 Please find them below --- Aki Tuomi Open-Xchange Oy ------------------ Open-Xchange Security Advisory 2020-05-18 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-3784 Vulnerability type: NULL pointer dereference (CWE-476) Vulnerable version: 2.3.0 - 2.3.10 Vulnerable component: submission, lmtp Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.10.1 Researcher credits: Philippe Antoine (Catena Cyber) Vendor notification: 2020-03-24 Solution date: 2020-04-02 Public disclosure: 2020-05-18 CVE reference: CVE-2020-10957 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Vulnerability Details: Sending malformed NOOP command causes crash in submission, submission-login or lmtp service. Risk: Remote attacker can keep submission-login service down, causing denial of service attack. For lmtp the risk is neglible, as lmtp is usually behind a trusted MTA. Steps to reproduce: Send ``NOOP EE"FY`` to submission port, or similarly malformed command. Solution: Upgrade to fixed version. ------------------ Open-Xchange Security Advisory 2020-05-18 Product: Dovecot IMAP server Vendor: OX Software GmbH Internal reference: DOV-3875 Vulnerability type: Improper handling of input data (CWE-20) Vulnerable version: 2.3.0 - 2.3.10 Vulnerable component: submission, lmtp Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.10.1 Researcher credits: Philippe Antoine (Catena Cyber) Vendor notification: 2020-03-23 Solution date: 2020-04-02 Public disclosure: 2020-05-18 CVE reference: CVE-2020-10958 CVSS: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Vulnerability Details: Sending command followed by sufficient number of newlines triggers a use-after-free bug that might crash submission-login, submission or lmtp service. Risk: Remote attacker can keep submission-login service down, causing denial of service attack. For lmtp the risk is neglible, as lmtp is usually behind a trusted MTA. Steps to reproduce: This can be currently reproduced with ASAN or Valgrind. Reliable way to crash has not yet been discovered. Solution: Upgrade to fixed version. ------------------ Open-Xchange Security Advisory 2020-05-18 Product: Dovecot Vendor: OX Software GmbH Internal reference: DOV-1745 Vulnerability type: Improper input validation (CWE-20) Vulnerable version: 2.3.0 - 2.3.10 Vulnerable component: submission, lmtp Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.10.1 Researcher credits: mailbox.org Vendor notification: 2020-03-20 Solution date: 2020-04-02 Public disclosure: 2020-05-18 CVE reference: CVE-2020-10967 CVSS: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Vulnerability Details: Sending mail with empty quoted localpart causes submission or lmtp component to crash. Risk: Malicious actor can cause denial of service to mail delivery by repeatedly sending mails with bad sender or recipient address. Steps to reproduce: Send mail with envelope sender or recipient as ``<""@example.org>``. Workaround: For submission there is no workaround, but triggering the bug requires valid credentials. For lmtp, one can implement sufficient filtering on MTA level to prevent mails with such addresses from ending up in LMTP delivery. Solution: Upgrade to fixed version. ------------------

1 0

dovecot sync not pushing automatically ?
by Laura Smith 17 May '20

17 May '20

Hi, I'm aware its an async process, but despite sending test messages and then waiting a few minutes, the stats are still unchanged : $ sudo doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 0 Waiting 'failed' requests 0 Total number of known users 18 However if I manually run it using : sudo doveadm -D sync -u test(a)example.com -1 -d -N -l 30 -U It syncs fine and the mails are visible on the standby server. The master server is setup as per the docs : replication_dsync_parameters = -1 -d -N -l 30 -U plugin { mail_replica = tcps:foobar.example.com:11867 } service replicator { process_min_avail = 1 } service aggregator { fifo_listener replication-notify-fifo { user = foobar } unix_listener replication-notify { user = foobar } } service replicator { unix_listener replicator-doveadm { mode = 0600 user = foobar } } replication_max_conns = 10

1 0

iterate_query with static userdb ?
by Laura Smith 17 May '20

17 May '20

Hi, Going by the "static userdb" example on this page (https://wiki.dovecot.org/VirtualUsers#homedirs) tried to achieve a similar setup in conjunction with pgsql for passdb. However I get an error "auth: Warning: sql: Ignoring changed iterate_query in /etc/dovecot/local_sql_users.conf, because userdb sql not used. (If this is intentional, set userdb_warning_disable=yes)" Does this mean the following is not a valid config ? Or at least I will not be able to achieve iteration ? mail_location = maildir:/foobar/mail/%d/%n/Maildir passdb { driver = sql args = /etc/dovecot/local_sql_users.conf } userdb { driver = static args = uid=foo gid=bar home=/foobar/mail/%d/%n }

3 4

"/etc/dovecot/dovecot.conf: passdb is missing driver"
by Laura Smith 17 May '20

17 May '20

Hi, I'm trying to get dovecot working with postgres, I'm on Debian 10 and have installed dovecot-pgsql from the Dovecot repo (https://repo.dovecot.org/ce-2.3-latest/debian/....) I have the following in my local.conf : passdb sql { args = /etc/dovecot/local_sql_users.conf } And the following in the referenced file: driver = pgsql connect = host=localhost dbname=foobar user=bar password=foo default_pass_scheme = ARGON2ID password_query = select dovecot_username as user,password from get_user('%u') iterate_query = select dovecot_username as user from get_users() So surely it should work ? doveconf -n just to complete the picture .... # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 xfs # Hostname: foobar.example.com auth_verbose = yes auth_verbose_passwords = sha1:7 doveadm_password = # hidden, use -P to show it mail_location = maildir:/foobar/mail/%d/%n/Maildir mail_plugins = " 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 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 } passdb { args = /etc/dovecot/local_sql_users.conf name = sql } plugin { mail_replica = tcps:standby.example.com:11867 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap lmtp replication_dsync_parameters = -1 -d -N -l 30 -U service aggregator { fifo_listener replication-notify-fifo { user = foobar } unix_listener replication-notify { user = foobar } } service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } vsz_limit = 2 G } service doveadm { inet_listener { port = 11867 ssl = yes } } service imap-login { process_min_avail = 5 service_count = 1 } service lmtp { process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = foobar } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieves { address = port = 5190 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = foobar } } ssl = required ssl_ca = </etc/foobar/ssl/example.com.chain ssl_cert = </etc/foobar/ssl/example.com.pem 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 } userdb { args = uid=foobar gid=foobar home=/foobar/mail/%d/%n driver = static } protocol lmtp { mail_plugins = sieve postmaster_address = foobar(a)example.com } protocol lda { deliver_log_format = msgid=%m: %$ mail_plugins = sieve postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r } protocol imap { mail_max_userip_connections = 20 }

2 1

Fallback driver after autodection
by Bjoern Koenig 16 May '20

16 May '20

Dear developers and dovecot users, I am running a dovecot with virtual users that have a mailbox using the Maildir format. mail_location = maildir:/usr/local/virtual/%d/%n New mailboxes are created on-the-fly if a new user logs in. I had the wish that the mailboxes of new users are created using the sdbox format and old mailboxes remain in Maildir format. In case the Maildir and sdbox mailboxes already exist, it is easy to use the "auto" driver which detects the correct format. But it is not possible to create mailboxes with the "auto" driver because there is no way to tell dovecot the preferred mailbox format. I wrote some lines of code which add the possibility to specify a fallback driver that will be used if a mailbox is created with the "auto" driver. mail_location = auto:/usr/local/virtual/%d/%n:FALLBACK=sdbox In case you like the idea you might want to develop it further. I am aware of the fact that there are some caveats if you mix it with other settings like LAYOUT. It won't work in any case. Best regards Bjoern --------------------------------------------------------------------------- diff -ruN src.bak/lib-storage/mail-storage.c src/lib-storage/mail-storage.c --- src/lib-storage/mail-storage.c.bak 2020-03-05 15:35:53.000000000 +0100 +++ src/lib-storage/mail-storage.c 2020-05-15 22:35:40.975992000 +0200 @@ -144,6 +144,10 @@ return classes[i]; } } + + if (set->fallback_driver != NULL) + return mail_storage_find_class(set->fallback_driver); + return NULL; } @@ -216,8 +220,10 @@ } storage_class = mail_storage_autodetect(ns, list_set); - if (storage_class != NULL) + if (storage_class != NULL) { + storage_class->v.get_list_settings(ns, list_set); return storage_class; + } (void)mail_user_get_home(ns->user, &home); if (home == NULL || *home == '\0') home = "(not set)"; diff -ruN src.bak/lib-storage/mailbox-list.c src/lib-storage/mailbox-list.c --- src/lib-storage/mailbox-list.c.bak 2020-03-05 15:35:53.000000000 +0100 +++ src/lib-storage/mailbox-list.c 2020-05-15 22:34:44.329802000 +0200 @@ -173,6 +173,8 @@ list->set.inbox_path = p_strdup(list->pool, set->inbox_path); list->set.subscription_fname = p_strdup(list->pool, set->subscription_fname); + list->set.fallback_driver = + p_strdup(list->pool, set->fallback_driver); list->set.list_index_fname = p_strdup(list->pool, set->list_index_fname); list->set.list_index_dir = @@ -360,6 +362,8 @@ else if (strcmp(key, "FULLDIRNAME") == 0) { set_r->index_control_use_maildir_name = TRUE; dest = &set_r->maildir_name; + } else if (strcmp(key, "FALLBACK") == 0) { + dest = &set_r->fallback_driver; } else if (strcmp(key, "BROKENCHAR") == 0) { if (strlen(value) != 1) { *error_r = "BROKENCHAR value must be a single character"; diff -ruN src.bak/lib-storage/mailbox-list.h src/lib-storage/mailbox-list.h --- src/lib-storage/mailbox-list.h.bak 2020-03-05 15:35:53.000000000 +0100 +++ src/lib-storage/mailbox-list.h 2020-05-15 22:35:01.251579000 +0200 @@ -121,6 +121,7 @@ const char *inbox_path; const char *subscription_fname; + const char *fallback_driver; const char *list_index_fname; /* Mailbox list index directory. NULL defaults to index directory. The path may be relative to the index directory. */ ---------------------------------------------------------------------------

1 0

SSL Error
by Brandon Roa 15 May '20

15 May '20

I just installed a certificate on my mail server to Postfix and Dovecot. The certificate is functional on Postfix, but for some reason I keep getting this error. Any suggestions on how to fix it? mail dovecot: imap-login: Error: SSL: Stacked error: error:1408A10B:SSL routines:ssl3_get_client_hello:wrong version number Here is my configuration: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-45-generic x86_64 Ubuntu 16.04.6 LTS ext4 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain cram-md5 login auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ disable_plaintext_auth = no mail_debug = yes mail_gid = 5000 mail_location = maildir:/home/vmail/%d/%n mail_plugins = quota mail_uid = 5000 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" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_rule = *:storage=5G sieve = /etc/dovecot/sieve/default.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)example.com protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl_cert = </etc/ssl/certs/example.pem ssl_key = </etc/ssl/private/example.key userdb { args = uid=5000 gid=5000 home=/home/vmail/%d/%n driver = static } verbose_ssl = yes protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota }

2 3

converting old uucp buffer files to maildir
by mh＠mike.franken.de 15 May '20

15 May '20

Hi *, besides my dovecot maildir structure, that has been migrated from an Exchange server, I have an even older mail structure in an ancient uucp style. The program named CrossPoint I used for this isn't wideley known, but it used so called mpuffer files in a plain text format. It is the program I still use to write for example this mail. I wonder if there already exists a program or script to convert the files from this program to the Dovecot maildir structure or some Howto for writing it myself. The format of these files looks like shown below. Mails are separated by two new lines. ------------------------< snip snip snip >----------------------------- EMP: /archiv/net/dovecot^M KOP: <some_recipient>^M OEM: dovecot(a)dovecot.org^M ABS: ricardomachini(a)gmail.com (Ricardo Machini Barbosa)^M WAB: dovecot-bounces(a)dovecot.org^M BET: Header search on Dovecot with SOLR^M ROT: perth.mydomain.de!localhost!perth.hirmke.de!aqua.hirmke.de!elvis.otherdomain.de!rachael.otherdomain.de!talvi.dovecot.org!talvi.dovecot.org!mail-qk1-x72e.google.com!smtp.gmail.com!DESKTOP4CIJMB3^M MID: 078901d61d7e$0964bcd0$1c2e3670$(a)gmail.com^M EDA: 20200428165659W-03^M LEN: 6112^M MAILER: Microsoft Outlook 16.0^M X-XP-Boundary: ----=_NextPart_000_078A_01D61D64.E4184820^M MIME-Type: multipart/alternative; boundary="----=_NextPart_000_078A_01D61D64.E4184820"^M U-Content-Type: multipart/alternative; boundary="----=_NextPart_000_078A_01D61D64.E4184820"^M U-Sender: dovecot-bounces(a)dovecot.org^M U-Received: from localhost (localhost [127.0.0.1]) by perth.mydomain.de (Postfix) with ESMTP id 245AF862DA8 for <<some_recipient>>; Tue, 28 Apr 2020 18:58:11 +0200 (CEST)^M U-Authentication-Results: perth.mydomain.de (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com^M U-Received: from perth.mydomain.de ([127.0.0.1]) by localhost (perth.hirmke.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RVP0-5mmK3XH for <<some_recipient>>; Tue, 28 Apr 2020 18:58:09 +0200 (CEST)^M U-Received: from aqua.mydomain.de (aqua.hirmke.de [192.168.1.11]) by perth.hirmke.de (Postfix) with ESMTP id 66A8B862D97 for <<some_recipient>>; Tue, 28 Apr 2020 18:58:07 +0200 (CEST)^M U-Received: by aqua.mydomain.de (Postfix, from userid 10) id 56D88506E; Tue, 28 Apr 2020 18:58:07 +0200 (CEST)^M U-Received: from rachael.otherdomain.de ([193.175.24.38]) by elvis.otherdomain.de with esmtp (Exim 3.36 #1) id 1jTTYK-0007WE-00 for <some_recipient>; Tue, 28 Apr 2020 18:57:48 +0200^M U-Received: from talvi.dovecot.org (talvi.dovecot.org [94.237.25.159]) by rachael.otherdomain.de (Postfix) with ESMTPS id 9C19510642C45 for <<some_recipient>>; Tue, 28 Apr 2020 18:57:46 +0200 (CEST)^M U-Received: from talvi.dovecot.org (localhost.localdomain [127.0.0.1]) by talvi.dovecot.org (Postfix) with ESMTP id 12ABD2B3C9F; Tue, 28 Apr 2020 19:57:06 +0300 (EEST)^M X-Original-To: dovecot(a)dovecot.org^M U-Delivered-To: dovecot(a)dovecot.org^M U-Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) by talvi.dovecot.org (Postfix) with ESMTPS id D48EB2B3C6F for <dovecot(a)dovecot.org>; Tue, 28 Apr 2020 19:57:03 +0300 (EEST)^M U-Received: by mail-qk1-x72e.google.com with SMTP id c63so22534959qke.2 for <dovecot(a)dovecot.org>; Tue, 28 Apr 2020 09:57:03 -0700 (PDT)^M U-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=u9iSrDj6VaHxbCoUFYZ7Zp0PHd/EPA66NRtYVeLn0+Q=; b=QUqHsAo0P6JkAidluC5utFcRyQ3AaJXn6GJwM/l+wJE0XM40Ks/0A5uNE16l76pTNU 37Uu5RETZXTMIvyJHkCgJXDVQS5RPep8U0Bw//DMBSC09XMaxVDVu0hVln2UQvNhFkZy 3DvfA1z1HOMmUlVpyYuAVgJa1FUd7VB34jmKmyrB4+0PS39Cbo9+rVZvyKNxHj/z8Kh+ l/ivk5e35L2eq1cUiomqhcus8m7vZ3edA0wEQbU4Z5p3oGBQcGb/5pe3NczjRjJ0oF1q 5OEcIXAxiREMU3DuiYkJCQE28hPMFf10/1/NtGLwlFGdLTseq8LwMM9hY9h8aKmkFAyB Xrvg==^M X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :thread-index:content-language; bh=u9iSrDj6VaHxbCoUFYZ7Zp0PHd/EPA66NRtYVeLn0+Q=; b=VvYSZ0dCKbTlD3JWsIM+c/IvKn4ODGwMBBDIlHSpKHVjLOX3bAQk5NLCdJgsVrHTH3 eX+fCHmwyIgoaa2bMZK45aURu0H/kELwUc4k/ToQ+MLikNLe7J1GEcDeG2R0Mzk6oOCs wX3JHFLfpK0shX+XRLiJju8Xmk+dFnPWZcQKYVEsBsSIG4y4LaOEE9NCCWcUfmlwqXIH CUBJ/xVHAvrA/Tc4krWhLgjR6M0m8pKM+hX0XvlEcQM9aNgFOzVUJDyM0AgW/hWvurNb fPqEgehT3b2YieMUR90+aYHybQddNGb0PSaD33ocmNb4jhNyuQIWx/B2niV/lRhd68Mm 2IaQ==^M X-Gm-Message-State: AGi0Pub1W8n/ZsL3XKsrqZB7wN3LxZgnRvleyGc7wO5LZcvfpihQoI5H tsYQUwckNuvUN4/JneVuDEGcKyPY^M X-Google-Smtp-Source: APiQypIGqpcSdvRH6NE1wbVeWc8EFZqdGP6OWn+bpMR2BCfPfi4m+swvYIadz5cfAuOe3TXSjYk1Jg==^M X-Received: by 2002:a37:9ad0:: with SMTP id c199mr26948945qke.472.1588093022024; Tue, 28 Apr 2020 09:57:02 -0700 (PDT)^M U-Received: from DESKTOP4CIJMB3 ([2804:14c:90:81be:7d50:c076:9537:75cb]) by smtp.gmail.com with ESMTPSA id w42sm14281733qtj.63.2020.04.28.09.57.00 for <dovecot(a)dovecot.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Apr 2020 09:57:01 -0700 (PDT)^M U-Thread-Index: AdYdffFdO2elBIGpSdyo3M9jdQ9BUQ==^M U-Content-Language: pt-br^M U-Content-Language: pt-br^M U-ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=dovecot.org; s=arc; t=1588093024; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: dkim-signature; bh=u9iSrDj6VaHxbCoUFYZ7Zp0PHd/EPA66NRtYVeLn0+Q=; b=Kfs/zrLFMMS+arGz8yJqX9KfjGpJWquL0QP4ccnziaPKOvpksDppuzM8snn/PS7bvhyiyr eDHKtsVFML1EME6QvvwTAbtUBDfaUN72KdIZsVSUs6raqIXWSNoXyIgH/1YmhSr1ClnY+E x5bNCnH/+rBbn0domw7lyZOLB672jMZsrz0qPOQekATrf7ISyFvwwXeWFO4PasT9R+F2Ci vlac2RY52IojdAiB7SF1E46WEhn6vVTnurM0z3G+lGSYI5UGQSKNkzfYAdyg7sXc1Bjd6f EV5zeNRkDyTpFbgIZWkT/VleWH3pKxzfboMpw6PZByMFJpo/+TgSJG/YiLY58A==^M U-ARC-Seal: i=1; s=arc; d=dovecot.org; t=1588093024; a=rsa-sha256; cv=none; b=grcJhp/zviK1BBKPNhz59Ktlw8wnbtBy/YamNS+vADIvfhbWKxTtQ+2MDQeri7sYFIjbG1 5wP5Ogs2mwF6BX4Ifjdv8Qj96FVD2RMcwVlv4xKH4gDoq/mJE9/lE0LJ2gouBBgt98dX54 itEhXRhSw+oe8bkMXljoV5GTVQEJeJaz5GAg35+XV/I1vbkFrrTVnUOw+JNKNSiFnBswk0 kxWaWOQXZTMJdg6WvKZ/Ru/iiaiiXzyG0q4gdU1Az8FQZ2HoXtZmjtvCOGw2gmXMmQn+Fi sMKbrvzDTeF8lS6L53ZVey0P2mAN172XsMXyaaCuZb7fQFyZvrCBNoXi5mV+TA==^M U-ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=QUqHsAo0; spf=pass (talvi.dovecot.org: domain of ricardomachini(a)gmail.com designates 2607:f8b0:4864:20::72e as permitted sender) smtp.mailfrom=ricardomachini(a)gmail.com^M X-BeenThere: dovecot(a)dovecot.org^M X-Mailman-Version: 2.1.15^M U-Precedence: list^M U-List-Id: Dovecot Mailing List <dovecot.dovecot.org>^M U-List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe>^M U-List-Archive: <https://dovecot.org/pipermail/dovecot/>^M U-List-Post: <mailto:dovecot@dovecot.org>^M U-List-Help: <mailto:dovecot-request@dovecot.org?subject=help>^M U-List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe>^M U-Errors-To: dovecot-bounces(a)dovecot.org^M X-XP-NTP: 40^M ^M This is a multipart message in MIME format.^M ^M ------=_NextPart_000_078A_01D61D64.E4184820^M Content-Type: text/plain;^M charset="us-ascii"^M Content-Transfer-Encoding: 7bit^M ... ------------------------< snip snip snip >----------------------------- TIA. Bye. Michael. -- Michael Hirmke

2 1

doveadm sync backup from old to new server
by Gregory Sloop 15 May '20

15 May '20

So I've done quite a lot of searching on the list and on the web - and perhaps my google-fu is really bad - but I can't find any real recipes on how to sync mail from the old server to the new. As an FYI - the old server is a CPanel/WHM setup on a VPS. The new is mailcow - which uses docker. However, I don't think either of these platforms is what's causing the issue - but I'm certainly not sure of that. --- I've tried several things - but have lost track of all the things I've tried. This seemed like the best of all the things I've tried. This particular mailbox/user+domain is setup on both servers. doveadm backup -D -u mc-user(a)abc.net ssh root(a)abc.net -p2200 doveadm dsync-server -u cp-user(a)abc.net mc-user(a)abc.net is the MC/NEW mailbox/domain cp-user(a)abc.net is the CPanel/OLD user/domain account The SSH server of the remote system is running on port 2200. However when I try this, I get: WARNING: The WATCHDOG_NOTIFY_EMAIL variable is not set. Defaulting to a blank string. dsync-local(user(a)abc.net)<v44NFyRWvF5efgAAb6OASA>: Error: read(remote) failed: EOF (version not received) doveadm(user(a)abc.net): Fatal: execvp(ssh) failed: No such file or directory The process appears to hang, and a Ctrl+C stops it. I'd love to get pointed at a reasonable recipe on how to make this work. I don't really get/understand the docs much at all. [And either everyone else understands it just fine, and never thinks to write a document on how to do it - or, and I think this is a lot more likely - they're using something like imapsync to do it. I found numerous places where others were, essentially, "Dovecot's tool is way too complicated and I can't get it to work right, so I used imapsync." I suppose I should probably just do that too, but it does seem a shame to do that when the dovecot tool is almost certainly the best tool for the job, but I can't figure out how to use it.] If someone can help me grok what's going on, I'm glad to write it up for the list and or a blog entry so it's more accessible. TIA -Greg

3 14