- dovecot - dovecot.org

Dovecot "User-Agent" equivalent
by Plutocrat 08 Apr '20

08 Apr '20

Hi, I was trying to debug an IMAP connection problem. The client accesses an account via webmail, mobile phone, and desktop. I was wondering if there was a way of determining which of these they were using at a given time. My googling turned up the following settings in the imap{} section: protocol imap { imap_id_log = * imap_id_send = "name" * "version" * } ... but setting these didn't seem to log any more information that I could use. Have I misunderstood the usage of these settings? Shouldn't they log a "user agent" type information in /var/log/dovecot.log ? Or are there any other ways I can get information on the client? P.

1 0

\Noselect missing after deleting mailbox
by Onno Molenkamp 07 Apr '20

07 Apr '20

Hi, With mailbox_list_index enabled (which is the default), Dovecot won't return \Noselect when LISTing a mailbox that was deleted but still has subordinate mailboxes. Before creating such a mailbox in the first place, it does return \Noselect. 1 LIST "" Test 1 OK List completed (0.002 + 0.000 + 0.001 secs). 2 CREATE Test/Test 2 OK Create completed (0.014 + 0.000 + 0.014 secs). 3 LIST "" Test * LIST (\Noselect \HasChildren) "/" Test 3 OK List completed (0.001 + 0.000 secs). 4 CREATE Test 4 OK Create completed (0.006 + 0.000 + 0.005 secs). 5 LIST "" Test * LIST (\HasChildren) "/" Test 5 OK List completed (0.001 + 0.000 secs). 6 DELETE Test 6 OK Delete completed (0.011 + 0.000 + 0.011 secs). 7 LIST "" Test * LIST (\HasChildren) "/" Test 7 OK List completed (0.001 + 0.000 secs). Like response 3, response 7 should contain \Noselect. (and it does, when mailbox_list_index is disabled) It looks like Dovecot isn't updating dovecot.list.index properly when deleting such a mailbox. Forcing Dovecot to rebuild the index by deleting dovecot.list.index* will cause \Noselect to re-appear in responses. Onno

1 0

Query change mdbox_rotate_size & mdbox_rotate_interval after sometime
by Durga Prasad Malyala 06 Apr '20

06 Apr '20

Hello All, If I change the mdbox_rotate_size to 100 MB & mdbox_rotate_interval to say 3 days after a year of usage what would be the impact on existing mails and new mails? Thanks/DP

1 1

replication and spam removal ("doveadm expunge")
by Olaf Hopp 06 Apr '20

06 Apr '20

Hello everybody, since now I did no replication and spam is delivered into users folder "spambox" Every night there is a cronjob which deletes spam older than 30 days via something like "find .... -ctime +30 -delete" Now I'm going to set up replication (two way) and I thought that doing "rm" is not a good idea. So I modified the job to something like /usr/bin/doveadm expunge -u test1 mailbox INBOX.spambox BEFORE 30d which works like intended, but I see that on the replication partner the spam isn't deleted. Even if I do a doveadm force-resync -u test1 '*' or log in via imap to the replication partner I still see the old spam. So my question is: is this the intended behaviour and I have to run the "doveadm expunge" on both replication partners or should the deletion via "expunge" being replicated to the partner and I have a misconfiguration or maybe I hit a bug ? Regards, Olaf /etc/dovecot/conf.d/12-replication.conf: mail_plugins = $mail_plugins notify replication service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } service doveadm { inet_listener { port = 1109 } } doveadm_password = XXXXX plugin { mail_replica = tcp:X.Y.Z.X:1109 } -- Karlsruher Institut für Technologie (KIT) ATIS - Abt. Technische Infrastruktur, Fakultät für Informatik Dipl.-Geophys. Olaf Hopp - Leitung IT-Dienste - Am Fasanengarten 5, Gebäude 50.34, Raum 009 76131 Karlsruhe Telefon: +49 721 608-43973 Fax: +49 721 608-46699 E-Mail: Olaf.Hopp(a)kit.edu www.atis.informatik.kit.edu www.kit.edu KIT - Die Forschungsuniversität in der Helmholtz-Gemeinschaft Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.

2 4

net_connect_unix(imap) failed
by Philipp Ewald 06 Apr '20

06 Apr '20

Hello everyone, we have a huge problem with dovecot and IMAP connections. we got the following errors: 39665 today dovecot: imap-login: Error: master(imap): net_connect_unix(imap) failed: Resource temporarily unavailable - http://wiki2.dovecot.org/SocketUnavailable (client-pid=29066, client-id=1755, rip=IP, created 562 msecs ago, received 0/4 bytes) we thinks this may be a problem with authorization take too long? Authorization is not local and with SQL. i found the following in source code of Dovecot: #define SOCKET_CONNECT_RETRY_MSECS 500 #define SOCKET_CONNECT_RETRY_WARNING_INTERVAL_SECS 2 [...] i_error("master(%s): %s (client-pid=%u, client-id=%u, rip=%s, created %u msecs ago, received %u/%zu bytes)", This is no process limit problem: ps auxf | grep -c "[d]ovecot/imap$" 688 ps auxf | grep -c "[d]ovecot/imap-login$" 100 cat /proc/`pidof dovecot`/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 64053 64053 processes Max open files 65535 65535 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 64053 64053 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us ulimit -n 1024 dovecot --version 2.3.4.1 (f79e8e7e4) protocols = imap pop3 service imap-login { process_min_avail = 4 service_count = 0 } service imap { process_limit = 4096 } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3 { process_limit = 4096 } Can someone explain why we got this error and how to fix? If you need another information please tell me. -- Philipp Ewald Administrator DigiOnline GmbH, Probsteigasse 15 - 19, 50670 Köln E-Mail: philipp.ewald(a)digionline.de Web: www.digionline.de, www.webweaver.de AG Köln HRB 27711, St.-Nr. 5215 5811 0640 Geschäftsführer: Werner Grafenhain Informationen zum Datenschutz: www.digionline.de/ds

2 2

Panic due to assertion failure
by Bert JW Regeer 06 Apr '20

06 Apr '20

Hey all, I continue to receive the following messages every so often: dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Panic: file mail-storage.c: line 2122 (mailbox_get_open_status): assertion failed: (box->opened) dovecot[93817]: imap(xistence(a)0x58.com)<39982><>: Fatal: master: service(imap): child 39982 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Even with core dumps enabled I haven't been able to get good information. I'm using FreeBSD and have installed dovecot from the pkg repositories dovecot-2.3.9.3 Is the package I have installed. (I just noticed there is an update available, so I'll upgrade, but this has been happening for a long time now, across multiple versions). What I was wondering, is there a way to rebuild all files that dovecot uses, indexes/caches/everything. Is there a doveadm command I can use for this? Bert JW Regeer

2 2

Disabling system users from mail
by Andrei Petru Mura 04 Apr '20

04 Apr '20

I'm using dovecot 2.2.36 on CentOS 7.7. My configurations are (dovecot -n): disable_plaintext_auth = no first_valid_uid = 1000 mail_location = maildir:~/Maildir 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 = } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it I want to disable accounts for system users. Only virtual users will have accounts (not configured yet). Is this possible? Thanks, Mura Andrei

2 3

index problems after update
by Ajay Guleria 04 Apr '20

04 Apr '20

I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. Sometimes it happens, that dovecot stops showing new mail. There is no error in the log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/user (for some users only) emails are delivered again if I delete index-files from .imap folder. Ajay Guleria

1 0

Background operations
by Joan Moreau 03 Apr '20

03 Apr '20

Hello, Moving a large number of email from one folder to another does create timeout on roundcube, due to either a very very large number of emails or indexing process that increases the processing time. Would it make sense to have a background thread, to process orders asynchronously, instead of executing it on the spot ? For instance, orders (like moving or indexing or others) would be stored in a backlog instead of executing them in place, and then a background operation would process it ? Makes any sense ? Thank you

1 0

Sieve with links?
by ＠lbutlr 03 Apr '20

03 Apr '20

Is there any reason that a .active_sieve file would not load because it is a symbolic link? The target of the link is readable by the mail user, but instead of getting the trace for the .active_sieve file, I only get the trace for the default sieve file. -- 'Winners never talk about glorious victories. That's because they're the ones who see what the battlefield looks like afterwards. It's only the losers who have glorious victories.' --Small Gods

3 6

Disable Dovecot LDA
by Adam Raszkiewicz 02 Apr '20

02 Apr '20

Hi, Is there any way to disable Dovecot LDA? I want to always send email via postfix and relay server even it will be a local delivery within the Dovecot server Thanks, Adam

6 9

auth service stops responding
by Michael Redert 02 Apr '20

02 Apr '20

Hi all, I am running postfix with dovecot configured for local mail delivery. Everything works as expected for a while, but after successfully delivering ~250 mails, dovecot does not accept requests anymore and mails start queueing up in the postfix mailqueue. After restarting dovecot, another ~250 mails are processed and the problem occurs again. The server is running ubuntu 18.04 with dovecot 2.2.33.2 and postfix 3.3.0 installed. Users are stored locally in /etc/dovecot/users. Based on the log messages below and the output of netstat, it seems to me, that the auth service is not accepting any requests on the corresponding socket anymore. Any help is very much appreciated! Kind regards, Michael --- postfix error messages --- Mar 28 09:36:13 srv postfix/lmtp[3850]: 2423F7A21C: to=<system(a)mydomain.de>, relay=srv.mydomain.de[private/dovecot-lmtp], delay=155, delays=0.01/0/0/155, dsn=4.3.0, status=deferred (host srv.mydomain.de[private/dovecot-lmtp] said: 451 4.3.0 <system(a)mydomain.de>Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) Mar 28 09:38:48 srv postfix/lmtp[3850]: 45A0C7A2B5: to=<system(a)mydomain.de>, relay=srv.mydomain.de[private/dovecot-lmtp], delay=308, delays=0.01/153/0.02/155, dsn=4.3.0, status=deferred (host srv.mydomain.de[private/dovecot-lmtp] said: 451 4.3.0 <system(a)mydomain.de>Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) -- dovecot error messages --- Mar 28 09:36:13 lmtp(2631): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Request timed out Mar 28 09:36:14 lmtp(2623): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Request timed out Mar 28 09:38:48 lmtp(2631): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:38:49 lmtp(2623): user-lookup(system(a)mydomain.de)Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:41:23 lmtp(system(a)mydomain.de): Error: userdb lookup(system(a)mydomain.de): Connecting timed out Mar 28 09:41:24 lmtp(system(a)mydomain.de): Error: userdb lookup(system(a)mydomain.de): Connecting timed out --- relevant netstat output when dovecot hangs ---- root@srv:~# netstat | grep dovecot | sort unix 2 [ ] STREAM CONNECTED 1449174 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTED 1449995 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 2 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 3 [ ] STREAM CONNECTED 1468180 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1468267 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1468271 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1469651 /var/run/dovecot/config unix 3 [ ] STREAM CONNECTED 1470606 /var/spool/postfix/private/dovecot-lmtp unix 3 [ ] STREAM CONNECTED 1470614 /var/spool/postfix/private/dovecot-lmtp unix 3 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb unix 3 [ ] STREAM CONNECTING 0 /var/run/dovecot/auth-userdb --- dovecot configuration ---- root@srv:~# dovecot -n # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) doveconf: Warning: SSLv2 not supported by OpenSSL. Please consider removing it from ssl_protocols. # OS: Linux 4.19.75-meson64 aarch64 Ubuntu 18.04.4 LTS auth_debug = yes auth_username_format = %n auth_verbose = yes debug_log_path = /var/log/dovecot-info.log default_client_limit = 16 default_process_limit = 32 first_valid_uid = 1000 hostname = mail.mydomain.de info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes listen = * lock_method = dotlock log_path = /var/log/dovecot.log mail_debug = yes mail_fsync = always mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mmap_disable = yes namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } postmaster_address = postmaster(a)mydomain.de protocols = " imap lmtp pop3" service replication-notify-fifo { name = aggregator } service { client_limit = 102 unix_listener { mode = 00 path = anvil-auth-penalty } name = anvil } service auth-worker { user = root name = auth-worker } service { client_limit = 160 name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service { executable = imap-login -R rawlogs inet_listener { port = 0 name = imap } service_count = 0 vsz_limit = 256 M 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 { process_limit = 8 name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service { unix_listener { group = postfix mode = 0660 user = postfix path = /var/spool/postfix/private/dovecot-lmtp } name = lmtp } service log-errors { name = log } service { inet_listener { port = 0 name = pop3 } inet_listener { port = 0 name = pop3s } name = pop3-login } service { process_limit = 4 name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl = required ssl_cert = </etc/ssl/certs/srv.mydomain.de.pem ssl_cipher_list = ALL:HIGH:!SSLv2:!MEDIUM:!LOW:!EXP:!RC4:!MD5:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv2 !SSLv3 !TLSv1 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_ssl = yes 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-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } 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 imap-master { 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 !indexer-worker { 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-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } 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 imap-master { 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-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } 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 imap-master { 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-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } 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 imap-master { 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 pop3 { 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-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } 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 imap-master { 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 0

"auth_cache_verify_password_with_worker = yes" does not work with proxy
by Theo Pannen 02 Apr '20

02 Apr '20

Hello, i use a proxy only configuration with version 2.2.22 (Ubuntu 16.04) and have now transferred it to version 2.3.10. This works as before. But as soon as i use "auth_cache_verify_password_with_worker = yes", it does not work anymore. The first login still works, but from the second one, where the answer comes from the cache, there is an error. The login is still accepted but dovecot searches the mailbox locally. The configuration for cache and proxy (from dovecot -n): auth_cache_verify_password_with_worker = yes auth_cache_negative_ttl = 0 auth_cache_size = 64 M passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } The sql from /etc/dovecot/dovecot-sql.conf.ext: password_query = SELECT pwdCrypt AS password, \ NULL AS nopassword, \ 'MyMasterUser' AS master, \ 'MyMasterPass' AS pass, \ ipv4address AS host, \ '%u' AS destuser, \ 'Y' AS proxy \ FROM mailbox \ WHERE user = '%u' AND activeFlg = '1' LIMIT 1 The logfile extracts with "auth_cache_verify_password_with_worker = yes": - First Login from mail.log (work's) Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=6fZiPkyiWHJSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=29272#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Performing passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): cache miss Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Module loaded: /usr/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: Module loaded: /usr/lib/dovecot/modules/auth/libdriver_mysql.so Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): Server accepted connection (fd=16) Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): Sending version handshake Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<1>: Handling PASSV request Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Performing passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): query: SELECT pwdCrypt AS password, NULL AS nopassword, 'MyMasterUser' AS master, 'MyMasterPass' AS pass, ipv4address AS host, 'testuser' AS destuser, 'Y' AS proxy FROM mailbox WHERE user = 'testuser' AND activeFlg = '1' LIMIT 1 Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Finished passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<1>: Finished Apr 2 12:27:11 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Finished passdb lookup Apr 2 12:27:11 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<6fZiPkyiWHJSZMhl>): Auth request finished Apr 2 12:27:11 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser#011master=MyMasterUser#011pass=<hidden>#011host=10.1.2.3#011destuser=testuser#011proxy Apr 2 12:27:11 mf-19 dovecot: imap-login: proxy(testuser): started proxying to 10.1.2.3:143 (master MyMasterUser): user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, TLS, session=<6fZiPkyiWHJSZMhl> - Further logins from mail.log (searches locally): Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=L4PQPkyi7plSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=39406#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Performing passdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): cache hit: <hidden>#011master=MyMasterUser#011pass=MyMasterPass#011host=10.1.2.3#011destuser=testuser#011proxy=Y Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): cache: validating password on worker Apr 2 12:27:18 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<2>: Handling PASSW request Apr 2 12:27:18 mf-19 dovecot: auth-worker(18978): Debug: conn unix:auth-worker (pid=18976,uid=109): auth-worker<2>: Finished Apr 2 12:27:18 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Finished passdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Auth request finished Apr 2 12:27:18 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser Apr 2 12:27:18 mf-19 dovecot: auth: Debug: master in: REQUEST#011219414529#01118975#0111#011f78b3499f7157a5daf7eb2050cd79e60#011session_pid=18980#011request_auth_token Apr 2 12:27:18 mf-19 dovecot: auth: Debug: static(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Performing userdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: static(testuser,93.200.174.28,<L4PQPkyi7plSZMhl>): Finished userdb lookup Apr 2 12:27:18 mf-19 dovecot: auth: Debug: master userdb out: USER#011219414529#011testuser#011#011auth_mech=PLAIN#011auth_token=e6819f7eac20f6520440abd937322ff13618741f Apr 2 12:27:18 mf-19 dovecot: imap-login: Login: user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, mpid=18980, TLS, session=<L4PQPkyi7plSZMhl> Apr 2 12:27:18 mf-19 dovecot: imap(testuser)<18980><L4PQPkyi7plSZMhl>: Debug: Added userdb setting: plugin/=yes Because it is pure proxy there is no userdb configuration and no local user. mail.err therefore contains the error message: Apr 2 12:27:18 mf-19 dovecot: imap(testuser)<18980><L4PQPkyi7plSZMhl>: Error: Couldn't drop privileges: User is missing UID (see mail_uid setting) - Further logins without "auth_cache_verify_password_with_worker = yes" works as expected: Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured=tls#011session=9cvDTkyi7XxSZMhl#011lip=178.254.4.122#011rip=93.200.174.28#011lport=143#011rport=31981#011local_name=mf-19.1blu.de#011ssl_cipher=TLS_AES_128_GCM_SHA256#011ssl_cipher_bits=128#011ssl_pfs=KxANY#011ssl_protocol=TLSv1.3 Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client passdb out: CONT#0111 Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client in: CONT<hidden> Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Performing passdb lookup Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): cache hit: <hidden>#011master=MyMasterUser#011pass=MyMasterPass#011host=10.1.2.3#011destuser=testuser#011proxy=Y Apr 2 12:31:46 mf-19 dovecot: auth: Debug: sql(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Finished passdb lookup Apr 2 12:31:46 mf-19 dovecot: auth: Debug: auth(testuser,93.200.174.28,<9cvDTkyi7XxSZMhl>): Auth request finished Apr 2 12:31:46 mf-19 dovecot: auth: Debug: client passdb out: OK#0111#011user=testuser#011master=MyMasterUser#011pass=<hidden>#011host=10.1.2.3#011destuser=testuser#011proxy Apr 2 12:31:46 mf-19 dovecot: imap-login: proxy(testuser): started proxying to 10.1.2.3:143 (master MyMasterUser): user=<testuser>, method=PLAIN, rip=93.200.174.28, lip=178.254.4.122, TLS, session=<9cvDTkyi7XxSZMhl> Apr 2 12:32:37 mf-19 dovecot: auth-worker(19036): Debug: conn unix:auth-worker (pid=19032,uid=109): Disconnected: Connection closed (fd=-1) Did I forget something in the configuration or is this a bug? Thanks Theo

1 0

[Dovecot] Postfixadmin/MySQL/Dovecot 2 and quota
by Matt 01 Apr '20

01 Apr '20

Hi all, I'm setting up a new email server based on the softwares list below: * Postfix * Dovecot 2.0.9 * MySQL * Postfixadmin 2.3.6 My current problem is I'm unsure whether quota feature is well configured or not. In order to test and validate, I use Roundcubemail GUI which provides percentage of the space used by the mailbox (quota should be applied per mailbox). Here, my dovecot configuration: dovecot.conf: dict { quotadict = mysql:/etc/dovecot/dovecot-dict-quota.conf } dovecot-dict-quota.conf: connect = host=localhost dbname=postfix user=postfix password=postfix map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } dovecot-sql.conf.ext: driver = mysql connect = host=localhost dbname=postfix user=postfix password=postfix default_pass_scheme = PLAIN-MD5 password_query = SELECT username AS user, password, \ CONCAT('*:storage=', CAST(quota AS CHAR), 'b') AS quota_rule \ FROM mailbox WHERE username = '%u' AND active='1' user_query = SELECT maildir, 89 AS uid, 12 AS gid, \ concat('dict:storage=',floor(quota/1000),'::proxy::quotadict') AS quota, \ CONCAT('*:storage=', CAST(quota AS CHAR), 'b') AS quota_rule \ FROM mailbox WHERE username = '%u' AND active='1' conf.d/90-quota.conf: plugin { quota = dict:user::proxy::quotadict quota_rule2 = Trash:storage=+10%% } conf.d/20-imap.conf: protocol imap { mail_plugins = $mail_plugins imap_quota } When I check postfixadmin GUI, I can see that quota in realtime in quota2 table, no problem. But Roundcubemail cannot get this information and shows a unknown quota. If I add this line: quota_rule = *:storage=1G in conf.d/90-quota.conf file, it works, I mean roundcubemail gets and shows information (but not the one stored in db of course). I think I'm close to the right configuration but I need your help to complete this setup. Thank you in advance for your help. Best, Matt

7 20

sieve compile error
by Johannes Rohr 01 Apr '20

01 Apr '20

Dear all, I try to recompile my learn_ham.sieve script, which fails with the message root@ida:/etc/dovecot# sievec sieve-scripts/report-ham.sieve report-ham: line 1: error: require command: unknown Sieve capability `vnd.dovecot.pipe'.report-ham: line 1: error: require command: unknown Sieve capability `imapsieve'.report-ham: line 19: error: unknown command 'pipe' (only reported once at first occurrence).report-ham: error: validation failed.sievec(root): Fatal: failed to compile sieve script 'sieve-scripts/report-ham.sieve' Yes, in conf.d/20-imap.conf, imapsieve and vnd.dovecot.pipe are explicitly enabled: protocol imap { mail_plugins = $mail_plugins imap_sieve imap_acl mail_max_userip_connections = 50 plugin {sieve_plugins = sieve_imapsieve sieve_extprograms # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/sieve-scripts/report-ham.sieve#sieve_pipe_bin_dir = /etc/dovecot/sieve-scriptssieve_global_extensions = +vnd.dovecot.execute +vnd.dovecot.pipe }} I am obviously overlooking something here, but what? Any hints will be greatly appreciated! Johannes

2 2

Re: limit for user exceeded
by Maciej Milaszewski 31 Mar '20

31 Mar '20

Hi I Dont understand or I im thinking wrong: process_limit = 25000 Older: #fs.inotify.max_user_watches= 8192 #fs.inotify.max_user_instances = 16384 New: fs.inotify.max_user_instances = 8192 fs.inotify.max_user_watches= process_limit x 2 + fs.inotify.max_user_instances fs.inotify.max_user_watches= 58192 On 31.03.2020 13:44, Aki Tuomi wrote: > I would prefer replies on the list... =) > > no. the idea is to *increase* the *current* value of fs.inotify.max_user_watches and fs.inotify.max_user_instances with 50000 > > fs.inotify.max_user_watches = 8192 + 50000 = 58192 > > Aki > >> On 31/03/2020 14:21 Maciej Milaszewski <maciej.milaszewski(a)iq.pl> wrote: >> >> >> Hi >> How I understood it correctly >> >> service imap { >> process_limit = 25000 >> } >> >> fs.inotify.max_user_watches= 50000 >> fs.inotify.max_user_instances = 50000 >> >> ? >> >> >> On 31.03.2020 12:14, Aki Tuomi wrote: >>> Sorry, ment that we *increase* the current value with twice the process limit for IMAP. >>> >>> Aki >>> >>>> On 31/03/2020 13:12 Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: >>>> >>>> >>>> We usually set them to twice the number of process_limit for imap. >>>> >>>> Aki >>>> >>>>> On 31/03/2020 12:29 Maciej Milaszewski <maciej.milaszewski(a)iq.pl> wrote: >>>>> >>>>> >>>>> Hi >>>>> System debian 8.11 dovecot-2.2.36.4 and I have some warnings in log likes: >>>>> >>>>> Warning: Inotify watch limit for user exceeded, disabling. Increase >>>>> /proc/sys/fs/inotify/max_user_watches >>>>> >>>>> >>>>> cat /proc/sys/fs/inotify/max_user_watches >>>>> 8192 >>>>> >>>>> in sysctl i change >>>>> >>>>> #fs.inotify.max_user_watches= 8192 >>>>> #fs.inotify.max_user_instances = 16384 >>>>> >>>>> fs.inotify.max_user_watches= 16384 >>>>> fs.inotify.max_user_instances = 24576 >>>>> >>>>> One questions - should these values be equal?

1 0

mail_crypt crashing randomly during LMTP
by Andi Krischer 31 Mar '20

31 Mar '20

Hello everybody, hope you’re all well! We have a really strange bug with our dovecot setup. After weeks and month of debugging we’re finally reached the point when we ask you for help. Our basic setup is quite simple: a single dovecot 2.3.10 (0da0eff44) install on Debian 10 with LDAP as user/passdb and sieve, imap_sieve and mail_crypt as mail_plugins. For the mail_crypt we have a special rule which allows us to enable crypting for each user individually. See this line from dovecot-ldap.conf.ext: pass_attrs = userPassword=password,=userdb_mail_plugins=%{if;%{real_lport};eq;993;imap_sieve;} %{if;%{real_lport};eq;143;imap_sieve;} notify mail_log %{if;%{ldap:encryptMail};eq;TRUE;mail_crypt; },=userdb_mail_crypt_private_password=%w As you can see for IMAP connections we enable imap_sieve and if the LDAP attribute “encryptMail” is set to TRUE we enable “mail_crypt” as mail_plugin. This works fine except that around 5-10 times a day the dovecot server crashes during a LMTP connection. It crashes in the last steps of LMTP which result that the mail get delivered to Maildir but Postfix doesn’t get a positive response and delivers the mail again after a few minutes. So all of our users get some mails twice or even more times. This is what the log says in the moment of crashing: dovecot: lmtp(53852): Panic: Module context mail_crypt_user_module missing *** backtrace *** (see: https://pastebin.com/YCiFtxmy) dovecot: lmtp(53852): Fatal: master: service(lmtp): child 53852 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Here I’ve pasted the LTMP session in mail.log: https://pastebin.com/A4ughNUF Obviously it looks like it has something to do with our mail_crypt setup. But the thing is that although we’re monitoring this for months we cannot find a condition which cause this. It seems to happen more frequent for mails with lot of people in To or CC (large headers), but definitively not all of them… Some more things we’ve already thought on: First my guess was that the mail_crypt plugin isn’t loaded in some case but in the backtrace are things from “lib10_mail_crypt_plugin.so”, so it should be loaded, right? On the other hand a non-crashing LTMP session looks exactly the same in log except it has three additional lines in mail.log: Debug: Loading modules from directory: /usr/lib/dovecot/modules Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so My college already had a look in the source code, but this didn’t make us much smarter. Here his references: mail context is defined here: https://github.com/dovecot/core/blob/81b5b188c478ec36bea8bda8fcad1e5f32ac61… and removed again here: https://github.com/dovecot/core/blob/81b5b188c478ec36bea8bda8fcad1e5f32ac61… Does any of the experts on this list have an idea what could cause these crashes and how to fix them? Thanks in advance! Best, Andi

2 5

limit for user exceeded
by Maciej Milaszewski 31 Mar '20

31 Mar '20

Hi System debian 8.11 dovecot-2.2.36.4 and I have some warnings in log likes: Warning: Inotify watch limit for user exceeded, disabling. Increase /proc/sys/fs/inotify/max_user_watches cat /proc/sys/fs/inotify/max_user_watches 8192 in sysctl i change #fs.inotify.max_user_watches= 8192 #fs.inotify.max_user_instances = 16384 fs.inotify.max_user_watches= 16384 fs.inotify.max_user_instances = 24576 One questions - should these values be equal?

2 2

IMAP error
by Roy Lemmon 30 Mar '20

30 Mar '20

Hi, I am trying to setup a dovecot server on my laptop to serve my emails to emacs gnus. The emails are pulled from the mail server using isync into particular directories. I am using a Guix system. The dovecot service is running. I can telnet into it with: telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot ready. However if I then do: b select inbox b BAD Error in IMAP command received by server I have not logged in as I have not set any username or password. I assumed that access was open on localhost. Is this not correct ? I am not sure how to check further. I have checked the configuration and it is pointing to my email directories, imap is enabled etc. Thanks Roy.

2 2

Panic/Assert dns-lookup.c
by tim＠linux-daus.de 30 Mar '20

30 Mar '20

Hi, currently we deploying Dovecot as imap/pop3 proxy. Every few minutes some panic/assert occurred (we connect roughly 7k - 8k user at one imap proxy with a connection rate of 200/s). We activate core dumps. Concerning the sensitive information in the dump we would prefer to not share the dump (e.g. i found our ssl private key in the dump). Log/Stack trace: Mar 30 15:54:06 imap16 dovecot: auth: Panic: file dns-lookup.c: line 371 (dns_client_lookup_common): assertion failed: (param != NULL && *param != '\0') Mar 30 15:54:06 imap16 dovecot: auth: Error: Raw backtrace: #0 t_askpass[0x7f27a219b5f0] -> #1 backtrace_append[0x7f27a219b860] -> #2 backtrace_get[0x7f27a219b9c0] -> #3 i_syslog_error_handler[0x7f27a21a6840] -> #4 i_syslog_fatal_handler[0x7f27a21a6970] -> #5 i_fatal[0x7f27a20fc3b7] -> #6 dns_client_connect[0x7f27a216ffb0] -> #7 dns_client_lookup[0x7f27a21702a0] -> #8 auth_request_proxy_finish[0x55c930e9b200] -> #9 auth_request_handler_reply[0x55c930e9cee0] -> #10 auth_policy_check[0x55c930e93a10] -> #11 auth_request_success[0x55c930e9bcf0] -> #12 auth_request_verify_plain_callback_finish[0x55c930e9a650] -> #13 auth_request_verify_plain_callback[0x55c930e9a7a0] -> #14 authdb_ldap_deinit[0x7f279faa9f10] -> #15 db_ldap_result_iterate_deinit[0x7f279faa7f70] -> #16 io_loop_call_io[0x7f27a21c0490] -> #17 io_loop_handler_run_internal[0x7f27a21c1e20] -> #18 io_loop_handler_run[0x7f27a21c05c0] -> #19 io_loop_run[0x7f27a21c0810] -> #20 master_service_run[0x7f27a212d5b0] -> #21 main[0x55c930e8dd10] -> #22 __libc_start_main[0x7f27a14901f0] -> #23 _start[0x55c930e8e2c0] -> #24 [no start/end information] Mar 30 15:54:06 imap16 dovecot: auth: Fatal: master: service(auth): child 6133 killed with signal 6 (core dumped) Config: # 2.3.9.2 (844fc8246): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) # OS: Linux 4.9.0-12-amd64 x86_64 Debian 9.12 # Hostname: imap16.domain.de auth_default_realm = domain.de auth_failure_delay = 0 auth_mechanisms = plain login cram-md5 auth_username_format = %{if;%d;eq;domain.de;%n(a)olddomain.de;%u} auth_verbose = yes base_dir = /var/run/dovecot/ default_client_limit = 4096 default_internal_user = pop default_process_limit = 400 default_vsz_limit = 1 G doveadm_password = # hidden, use -P to show it first_valid_uid = 48 import_environment = TZ last_valid_uid = 48 login_trusted_networks = 192.168.11.0/24 mail_gid = pop mail_plugins = " mail_log notify zlib quota" mail_uid = pop passdb { args = /etc/dovecot/conf.d/dovecot-ldap-domain-proxy.conf.ext driver = ldap result_failure = return-fail result_success = continue-ok } passdb { args = allow_real_nets=192.168.11.0/24 driver = static result_failure = continue-ok } passdb { args = /etc/dovecot/conf.d/dovecot-ldap-domain-protocol-deny.conf.ext driver = ldap result_failure = return-ok result_success = return-fail } passdb { args = /etc/dovecot/passdb-domain-ldap-cram.conf.ext driver = ldap mechanisms = CRAM-MD5 result_failure = continue-fail result_success = continue-ok } passdb { args = /etc/dovecot/passdb-domain-ldap.conf.ext driver = ldap mechanisms = LOGIN,PLAIN result_failure = return-fail result_success = continue-ok } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size zlib_save = gz zlib_save_level = 6 } protocols = " imap pop3" service auth { unix_listener auth-client { group = dovecot_auth mode = 0660 user = $default_internal_user } } service doveadm { group = pop inet_listener { port = 12345 } user = pop } service imap-login { process_min_avail = 24 service_count = 0 } service pop3-login { process_min_avail = 24 service_count = 0 } ssl = required ssl_cert = </etc/ssl/certs/star_domain_de.crt ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-CAMELLIA128-SHA:DHE-RSA-CAMELLIA256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:CAMELLIA128-SHA:CAMELLIA256-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it verbose_proctitle = yes

2 4

Namespace problem? duplicated folders...
by Gregory Sloop 30 Mar '20

30 Mar '20

I'm sure this is related to name-spaces, but for some reason [brain damage perhaps? :) ] I can't seem to figure out how to fix it. In TBird, for example, I have a folder tree that looks like this Inbox -| Folder-A Folder-B Folder-C Folder-A Folder-B Folder-C And Folder-A, Folder-B, Folder-C are the same folders, just shown twice. [In two different hierarchies.] I'm using mbox files to store mail. [If that matters.] Here's what I have in my conf files for namespace defs namespace { inbox = yes #hidden = yes prefix = INBOX/ separator = / } namespace inbox { mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Trash { special_use = \Trash } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } } I've had this problem for literally years, and it's not been that big of a deal (mostly irritating) - and I've tried to "fix" it before without any success. But now it's causing some issues and I'd really like to get this nagging issue gone. Since it's been so long since I last tried to fix it, I really can't recall any of settings changes I made in an attempt to fix it. I'd guess this is a trivial issue, but if so, can someone point me in the right direction. Thanks in advance! -Greg

2 5

Re: Help with migration to Dovecot from raw files
by Stefano Antonelli 30 Mar '20

30 Mar '20

On 2020-03-28 23:54, Stefano Antonelli wrote: > I've attached my script in case it's helpful to anyone in a similar > situation. It took quite a bit of effort to get this right, highly > depends on the format of the original mailstore, and I've only tested > this on one smaller mailbox (<400 messages). And I wasn't concerned > with any client having to download everything again since this was a > fresh import. > > In any case, it worked for me. Err had a few issues on a larger 4gb mailbox: 1. small bug in the script, new script attached. Change: # Grab the flags from the filename. F=`echo $fname | cut -c 26-27` to: # Grab the flags from the filename. F=0x`echo $fname | cut -c 26-27` without the 0x in front, the masking operation interprets $F as octal. 2. there are cases where the old mail server wrote files with identical timestamps even though the dates of the email are clearly different. I presume this was just buggy behaviour and could explain why I couldn't successfully download via imap. 201011072323050332-000001060000028C3D2E9D97.imap 1289200985.M000000P12345.icewarp,S=5614,W=5614:2,RS Received: Tue, 14 Sep 2010 19:44:47 -0700 201011072323050330-000001060000028A3D2C9676.imap 1289200985.M000000P12345.icewarp,S=2317,W=2317:2,RS Received: Sun, 12 Sep 2010 18:51:44 -0700 I may consider fixing this. 3. for some reason there were some off by one file sizes that resulted in errors like this: dovecot.index.cache: UID 278: Broken physical size in mailbox ... failed: Cached message size smaller than expected (1972 < 1973 ,box=INBOX, UID=278) In my case 298 out of 22023 files were affected. Script to fix this is after using the import-from-icewarp-files.sh script is attached. I couldn't find a good way to find only maildir messages by filename. Seems difficult to parse. When I renamed the files, I used icewarp as the server name and that's how I searched for files: FILES=`find /path/to/mail/user -name \*\.icewarp\,\*` If there's a better way to do this, I would like to know for future reference. Thanks, Stef

1 0

Help with migration to Dovecot from raw files
by Stefano Antonelli 29 Mar '20

29 Mar '20

Hello list, I recently migrated to Dovecot from a very old version of IceWarp running on failing hardware running Windows XP. I had a lot of issues downloading mail through imap. What I have instead are the email files directly off the harddrive from IceWarp's mail store. I rearranged the mail files to look like a Dovecot maildir and tried to use these emails directly. Dovecot did not complain, but I ran into my first problem. The emails were out of order on the client side. None of my imap clients store email. They all just fetch headers and download mail as it's required. So a resync is not a problem. I just can't figure out how and I don't know if the filenames are a problem. The files I'm working with have this format: 2020032512105639B0-000001000000D2D45079615C.imap The first part is the date and all the the filenames appear to be unique. Is it okay to leave them this way or should I rename them in the same fashion as Dovecot? If so, is there a tool I can use or do I need to write a script? If I have to write a script, could someone help me decipher this filename: 1585197800.M440284P10160.hostname,S=2812,W=2875:2,S I understand the first bit is a unix timestamp. I couldn't find out what M440284P10160 means or how I might create that number myself to use in a renaming script. Additionally, I'd like to customise the hostname without changing the machine's hostname and I understand that the S and W can also be omitted. I'm not using quotas. I couldn't find anywhere in the documentation where it talked about any configuration options for the filenames. Are there any or do I have to patch the source? I was also planning on directly backing up the email using rsync, but the changing filenames with flags is obviously an issue. I understand that dovecot can store flags in a file instead, if the mailbox is shared or public. Is there any way to have this behaviour with a private mailbox? Ideally the filenames are not touched after creation in which case rsync will work nicely to my NAS. The last issue is that since Dovecot went live, I've started receiving mail. For the time being, I have left my "yet to be migrated" mail outside of maildir. So Dovecot doesn't know about it. I will need to merge this newly received mail with my "yet to migrated mail" once I sort out exactly how to migrate that mail. And I would really like all the mail to sort properly. From what I can tell doveadm is the tool for the job, but I just can't make sense of the documentation. Thanks, Stef Dovecot version: 2.3.4.1 (f79e8e7e4)

2 3

managesieve user
by André Rodier 28 Mar '20

28 Mar '20

Hello, I am updating dovecot, from Debian Stretch to Buster, and I have an issue with the managesieve service: > Mar 28 15:05:06 mail dovecot[2637]: managesieve-login: Error: auth: > connect(login) in directory / failed: Permission denied > (euid=120(<getpwuid() error>) egid=128(<getgrgid() error>) missing +x > perm: /, we're not in group 127, dir owned by 0:127 mode=0770) > Mar 28 15:05:06 mail dovecot[2637]: managesieve-login: Error: auth: > connect(login) in directory / failed: Permission denied > (euid=120(<unknown>) egid=128(<unknown>) missing +x perm: /, we're > not in group 127, dir owned by 0:127 mode=0770) The two folders I found with these permissions are /run/dovecot/login and /run/dovecot/token-login. Both folders belongs to root:dovecot If I change the permissions of the following folders, like this: chmod 0775 /run/dovecot/login chmod 0775 /run/dovecot/token-login Then, dovecot managesieve is working, but this is just a test, I suppose the service should run with a specific user? Do you have any idea on what is wrong here? If I restart dovecot, I have an error message that states the permissions are wrong, and they are set again to 0770 Thanks, André Rodier

2 2

Forward a copy
by ＠lbutlr 28 Mar '20

28 Mar '20

<https://wiki.dovecot.org/Pigeonhole/Sieve/Examples> has this example: if header :contains "subject" ["order", "buy"] { redirect "orders(a)company.xn--dom-9o0a; } Can I simply add fileinto :create “mailbox”; before that redirect line so that a COPY of the message is forwarded? And does redirect imply stop, since I don;’t see stop in the example. -- They say only the good die young. If it works the other way too I'm immortal

2 1

doveadm rebuild: Failed to add attachment keywords
by Patrick Ben Koetter 27 Mar '20

27 Mar '20

Greetings, I'm using the current dovecot release 2.3.10 and I try to rebuild mailboxes with broken attachment paths. When I run this command: doveadm rebuild attachments -u user(a)example.com ALL I runs fine for 6199 of 6223 messages and fails then at message 6200 with this message: doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) doveadm(user(a)example.com): Error: Mailbox INBOX: UID=6200: Failed to add attachment keywords: mail_get_parts() failed: Mailbox INBOX: UID=6200: read(attachments-connector(/MailStore/mail/mailboxes/CFEE0E67-6269-4AD3-8DED-6AB71A8E4BD7/dbox/mailboxes/INBOX/dbox-Mails/u.6200)) failed: read(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200[base64:19 b/l]) failed: open(/MailStore/mail/attachment/b9/52/b952b91441e53d3bb57453af2df66bb003e551f4-e94b170ff8bb685e943f0000162bf795-5d0b3129034c8957284d00007dfcf92d-6200) failed: No such file or directory (read reason=) 6200 error Assuming the attachments are still there, what would I need to do to 'fix' that? And if I can't fix it, can 'rebuild' skip the error and go on rebuilding the rest? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

2 1

Deliver log with "msgid=?" when email come from Exchange/Office 365
by Alessio Cecchi 27 Mar '20

27 Mar '20

Hi, I noticed that all emails that come from Exchange/Office 365 have the message-id, in deliver log, reported as msgid=? <DBBPRDD0(a)DBBPR023.eurprd08.prod.outlook.com> instead of expected msgid=<DBBPRDD0(a)DBBPR023.eurprd08.prod.outlook.com> My deliver_log format is: deliver_log_format = deliverytime=%{delivery_time}, msgid=%m, sender=%e, from=%f, subject="%s": %$ The behaviour is the same on Dovecot 2.2 and 2.3, and only dovecot have the "?", we have a mail filter before dovecot and the message-id is registred fine, without the ? in front. Is an issue of my setup or a bug in dovecot? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

1 0

Not able to start dovecot
by Adam Raszkiewicz 26 Mar '20

26 Mar '20

Freshly compiled dovecot 2.3.9.3 on Centos 7 for some reason not able to start sudo systemctl status dovecot.service ● dovecot.service - LSB: Starts the Dovecot POP3/IMAP service Loaded: loaded (/etc/rc.d/init.d/dovecot; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2020-03-18 16:32:17 UTC; 15s ago Docs: man:systemd-sysv-generator(8) Process: 2868 ExecStart=/etc/rc.d/init.d/dovecot start (code=exited, status=127) Mar 18 16:32:17 systemd[1]: Starting LSB: Starts the Dovecot POP3/IMAP service... Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 34: log_info_msg: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 35: start_daemon: command not found Mar 18 16:32:17 dovecot[2868]: /etc/rc.d/init.d/dovecot: line 36: evaluate_retval: command not found Mar 18 16:32:17 systemd[1]: dovecot.service: control process exited, code=exited status=127 Mar 18 16:32:17 systemd[1]: Failed to start LSB: Starts the Dovecot POP3/IMAP service. Mar 18 16:32:17 systemd[1]: Unit dovecot.service entered failed state. Mar 18 16:32:17 systemd[1]: dovecot.service failed. I have compiled the same code on Centos 6 and had no problem to run it. Any thoughts on that? Thanks, Adam

4 4

Understanding doveadm rebuild
by Patrick Ben Koetter 26 Mar '20

26 Mar '20

Greetings, I'm trying to understand if the doveadm rebuild command is suited to fix a problem we have on a customers platform. The customer uses sdbox in combination with SIS and for $REASONS dovecot cannot find the attachements anymore. They are there, but the references to them in the messages seem to be wrong. Is that what the rebuild subcommand has been made for? Will it e.g. scan the messages for attachment references and try to find them in the SIS storage location and then fix the references in messages? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

1 0

At rest encryption (with protected crypto keys)
by Kees de Jong 25 Mar '20

25 Mar '20

Hi, As stated on the Dovecot documentation, at rest encryption is possible [1]. However, these keys are present on the system itself and are unprotected. Therefore, if a system is compromised, the attacker has access to the encrypted mail and the keys. There is no security benefit in that situation, except for hoping that the attacker doesn't understand that this is happening and how. Nextcloud does this a bit better. A key is used to encrypt user data as well [2]. However, that key is protected with the user's password. When the user logs in and requests data, the user's password unlocks the key and data can be read and written safely. This also takes into account password changes. Files don't need to be encrypted again, the encryption key is simply re-encrypted with the new user's password. How does the Dovecot community see this? Is at rest encryption needed in times of increased security and privacy problems? I think it is a must, just like 2FA, but that's a different story. I think the current possibility of at rest encryption is not well applied enough. Is this something that's on the agenda to improve? Or am I missing something? Is there a better way of doing this? [1] https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/#mail-crypt-… [2] https://nextcloud.com/encryption/

2 1

dovecot-2.2.36-4 and antispam
by Maciej Milaszewski 24 Mar '20

24 Mar '20

Hi I use dovecot-2.2.36.4 on Debian 8.11 and plugin dovecot-antispam from http://johannes.sipsolutions.net/Projects/dovecot-antispam All works fine but in roundcube i get two folder: Spam (real: Junk) and SPAM in sieve i have: require ["fileinto","imap4flags"]; # rule:[SPAM Box] if header :contains "X-Spam-Flag" "YES" { setflag "\\Seen"; fileinto "SPAM"; # ---> because dovecot-antispam need folder SPAM to teach spam or ham stop; } problem probably fixed when I change fileinto "SPAM"; to fileinto "Junk"; But plugin "dovecot-antispam" probably not working ... Maybe I think wrongly Can you recommend any other plugin that will work properly and teach spam with Junk for dovecot2.2.36-4 in dovecot: 15-mailboxes.conf: ....... mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox SPAM { special_use = \Junk } mailbox Trash { special_use = \Trash } .... 90-plugin.conf: ..... antispam_backend = MAILTRAIN #antispam_mail_sendmail_args = --for;%u antispam_mail_spam = --spam antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/local/bin/spam-learn.sh antispam_pipe_tmpdir = /tmp antispam_spam_pattern_ignorecase = spam;inbox.spam;Unwanted antispam_trash_pattern_ignorecase = trash;Deleted *;Junk*;wiadomo&AVs-ci-&AVs-mieci;kosz antispam_debug_target = syslog antispam_verbose_debug = 1 script to learn cat /usr/local/bin/spam-learn.sh #!/bin/sh date >> /tmp/spam.txt echo $@ >> /tmp/spam.txt if [ "x$1" = "x--spam" ]; then /usr/bin/pyzor report >> /tmp/spam.txt 2>&1 fi if [ "x$1" = "x--ham" ]; then /usr/bin/pyzor whitelist >> /tmp/ham.txt 2>&1 fi -- Maciej Miłaszewski Starszy Administrator Systemowy IQ PL Sp. z o.o. Biuro Obsługi Klienta: e-mail: bok(a)iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 0000007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853

3 2

imapc quota support
by Сергей Петренко 24 Mar '20

24 Mar '20

Hi, I use Dovecot 2.3.9.2 as IMAP proxy for other mail server and configure it with imapc_host/imapc_port/imapc_user options. All works fine exclude quota information. Although my IMAP server supported quota Dovecot does not relay it to users. As I read in docs/MailboxFormat.imapc.txt in Dovecot v2.2.30+ there is a way to relay quota data to end users: Quota ----- Using the "imapc" quota backend allows asking for the quota from remote IMAP server (v2.2.30+). By default it uses GETQUOTAROOT INBOX for getting the quota. There are also two parameters that can be used to control how the quota is looked up: * box=<mailbox>: Use GETQUOTAROOT <mailbox> * root=<name>: Use GETQUOTA <name> For example: ---%<------------------------------------------------------------------------- plugin { quota = imapc:root=User Quota } ---%<------------------------------------------------------------------------- The above example is not clear. Please advise how to configure Dovecot in IMAP proxy mode with quota support.

1 0

Question on pop3
by ratatouille 23 Mar '20

23 Mar '20

Hello! Email is stored as plain textfile in /var/mail/andreas. I assume this is mbox-format. I get the following in the log telneting to localhost: 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Error: chdir(/var/spool/mail/andreas) failed: Not a directory 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Error: Namespace '': Mail storage autodetection failed with home=/var/spool/mail/andreas 2020-03-22 20:21:10 imap(andreas(a)dualbit.de): Info: Namespace '': Mail storage autodetection failed with home=/var/spool/mail/andreas in=0 out=372 In case in the passwd-file I specify userdb_mail=mbox:/var/mail/andreas:INBOX=/var/mail/%n I see: 2020-03-22 20:31:00 imap(andreas(a)dualbit.de): Error: chdir(/var/spool/mail/andreas) failed: Not a directory 2020-03-22 20:31:00 imap(andreas(a)dualbit.de): Error: Namespace '': mbox: mbox root directory can't be a file: /var/mail/andreas (http://wiki2.dovecot.org/MailLocation/Mbox) How can I make this work? Regards Andreas

2 1

Problem with mail_uid
by ratatouille 23 Mar '20

23 Mar '20

Hello! I have problems fetching mail for a system user. In use is a passwd-file. If I set (for virtual users) mail_uid = vmail mail_gid = vmail in 10-mail.conf, I get permission denied. 2020-03-23 18:39:23 imap(andreas(a)dualbit.de): Error: chdir(/home/andreas/Maildir/) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +x perm: /home/andreas/Maildir, dir owned by 5006:5006 mode=0700) The mailbox has permissions drwx------. 9 andreas susers If I don't set mail_uid I get an error because of missing mail_uid. I can only access the users mailbox if I set mail_uid = 5006 in 10-mail.conf On another system I don't haver this problem. I made diffs, read alot of stuff and can't find a solution. What is the way to go, please? I would like to know why this does not work. Below my doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-1062.9.1.el7.x86_64 x86_64 CentOS Linux release 7.7.1908 (Core) # Hostname: dualbit1.dualbit.de auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain cram-md5 auth_verbose = yes auth_verbose_passwords = yes debug_log_path = /var/log/dovecot-debug disable_plaintext_auth = no first_valid_uid = 1000 listen = *,[::] log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_gid = vmail mail_home = /home/%n/Maildir mail_location = maildir:~/ mail_plugins = " quota" mail_privileged_group = vmail mail_uid = 5006 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4fl ags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext 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 = /etc/dovecot-sql.conf driver = sql } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { quota = dict:user::file:/var/vmail/%d/%n/.quotausage sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 500 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it ssl_protocols = !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot-sql.conf driver = sql } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = sieve quota postmaster_address = root@localhost } protocol lmtp { mail_plugins = quota sieve } Any help appreciated. Andreas

2 3

imapc master login for shared mailboxes
by Mark Zealey 21 Mar '20

21 Mar '20

Hi there, I'm trying to set up shared mailboxes such that any access to the shared namespace like INBOX/shared/<sub-email-address> will take <current-user> and use imapc to log in with <sub-email-address>*<current-user> (ie the current user is the master account for imapc). I've set up like https://wiki2.dovecot.org/SharedMailboxes/ClusterSetup on centos8 latest dovecot build (a late 2.2 series version I believe. However I'm running in to a couple of issues: 1) setting imapc_master_user = %u has %u as <sub-email-address> rather than <current-user>. I can't find any sort of variable substitution that will allow me to access the details of <current-user>. From looking at the logs it seems to do a userdb lookup for<sub-email-address> to check it exists but then the substitutions appear to be using these rather than the current user's details 2) In a similar vein, I believe imapc_password = %w (ie trying to just get current user logging in with the password that was specified when they initially logged in, but as a master user) is also not substituting correctly and is just a blank string Is there any way around this so I don't have to worry about trying to do sharing based on the filesystem and the same process but rather just allow the main user to log in to any other account (in this case domain owner logging in to any accounts under their domain) ? Thanks Mark

1 0

systemuser login
by ratatouille 20 Mar '20

20 Mar '20

Hello! I have one systemuser on my testsystem running CentOS. All other users live in a mysql- database. I created a /etc/dovecot/users file and use auth-passwdfile.conf.ext. andreas@dualbit.de:{CRAM-MD5}334bb91aad4fb976870535bbbd9f07db512fce13bc8f7b58f9dedca404a421aa:5006:5006::/var/spool/mail/andreas::userdb_mail=mbo x:/var/mail/andreas:INBOX=/var/mail/%u When I try to login via telnet I see in the logifle: 2020-03-20 14:40:01 auth: Debug: prefetch(andreas@dualbit.de,::1,<+9T4a0mhKO0AAAAAAAAAAAAAAAAAAAAB>): success 2020-03-20 14:40:01 auth: Debug: master userdb out: USER 734789633 andreas(a)dualbit.de mail=mbox:/var/mail/andreas:INBOX=/var/ma il/andreas(a)dualbit.de auth_token=dc1f852724345081ff3a18958f05fc61b2544ab4 The domainpart is added to the username when I use %u. I assume this is why the login fails. How do I correct this, please? Kind regards Andreas

3 5

Director with dovecot 2.3 and Panic/Fatal error
by Alessio Cecchi 19 Mar '20

19 Mar '20

Hi, after the upgrade to Dovecot 2.3 for our director ring we found some times in the log errors like this: Mar 18 14:22:51 Panic: imap-login: file iostream-openssl.c: line 599 (openssl_iostream_handle_error): assertion failed: (errno != 0) Mar 18 14:22:51 Fatal: imap-login: master: service(imap-login): child 1726 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Backend is still Dovecot 2.2.36 and Director is 2.3.10. I hope it can be fixed. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

2 1

.dovecot.sieve.log/tmp failed: Not a directory
by mabi 19 Mar '20

19 Mar '20

Hello I am running Dovecot 2.3.9 for IMAP access with RainLoop webmail and have noticed for an account where I have some filters setup that I get the following error messages in the dovecot log file: Mar 17 19:02:50 mbox dovecot: imap(mail(a)domain.tld)<10511><ubAzvhCh1N2yxeu/>: Error: stat(/var/vmail/domain.tld/mail/.dovecot.sieve/tmp) failed: Not a directory Mar 17 19:02:50 mbox dovecot: imap(mail(a)domain.tld)<10511><ubAzvhCh1N2yxeu/>: Error: stat(/var/vmail/domain.tld/mail/.dovecot.sieve.log/tmp) failed: Not a directory This happens when I access the Dovecot mailbox server using an iphone. Also on the iphone I see these "mail" folders but they are not really mail folders... With Thunderbird as mail client it looks all good and I don't get this error. Is this normal? if not, how can I prevent this issue? Regards, Mabi

2 3

Quota plugin and director
by Simone Lazzaris 19 Mar '20

19 Mar '20

Hello dovecot! I administer a dovecot installation with 30k users. I've got 4 dovecot directors as frontend and 10 backends. The mailbox are now in maildir format, with maildir++ quota, on a shared netapp filer. Indexes are local on each backend. I'm reconfiguring the quota plugin: as a first step, I want to use the clone plugin to keep a copy of the quota on a redis database. Next, I'm going to use the "count" quota backend. I've configured without (many) issues the quota clone plugin, but now I want to force the recalculation on all the mailboxes, because I've got some (not many, but some) mailboxes that are mostly unused and are not refreshed. At first, I was going to use "doveadm quota recalc -A", but.... I want each backend to perform the recalculation ONLY for the users he it's managing. I can't perform "doveadm quota recalc -A" on the directors, because the quota plugin is enabled only on the backends. I can parse the user mapping on the directors and split the calculation, one user a time, on the backends, but I feel I'm choosing a overly complicated path. So.... which is the right way to do this? Thanks. -- *Simone Lazzaris* *Qcom S.p.A. a Socio Unico* Via Roggia Vignola, 9 | 24047 Treviglio (BG)T +39 0363 47905 | D +39 0363 1970352 simone.lazzaris(a)qcom.it[1] | www.qcom.it[2] * LinkedIn[3]* | *Facebook*[4] -------- [1] mailto:simone.lazzaris@qcom.it [2] https://www.qcom.it [3] https://www.linkedin.com/company/qcom-spa [4] http://www.facebook.com/qcomspa

3 5

lmtp(------): Debug: SSL_get_servername() failed
by chayes＠afo.net 18 Mar '20

18 Mar '20

I have a smoothly running dovecot 2.3.7.2 & sendmail IMAP with SSL combo on Fedora 30. However, I see oodles of these when ssl verbosity is turned up: lmtp(25738): Debug: SSL_get_servername() failed Should I be concerned or is there a setting that stops that?

1 0

Re: Headsup on feature removal - password
by Rupert Gallagher 18 Mar '20

18 Mar '20

> Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5 The web is flooded with plain text passwords and hashed passwords harvested from hacked servers. Dovecot stores passwords with the same scheme used for client authentication. Therefore, we use crammd5/hmac-md5. It does not look like much, but is better than plaintext. As md5 is about to go, and I have no intention to store passwords in plaintext, I need to split the scheme used to store passwords from the scheme used for authentication, and migrate storage from md5 to bcrypt. Since this is not possible, I think I will drop passwords entirely and use certificates.

6 7

Getting autoexpunge to work
by Philip Colmer 17 Mar '20

17 Mar '20

dovecot 2.2.33.2 (d6601f4ec) on Ubuntu 18.04 The recent announcement that expunge is going to be deprecated and that autoexpunge should be used instead reminded me that my recent switch over to autoexpunge is not working. There has been an active discussion today about getting expunge working so I thought I'd use the commands suggested there to figure out why autoexpunge might not be doing anything. "doveadm search -u local-finance-support mailbox INBOX savedbefore 12w" returns nothing even though the first email for that user is dated November 12th 2019. Using the message ID for that first email, I then tried this: doveadm search -u local-finance-support HEADER MESSAGE-ID "CAHgKB_f5ttC3kLgxgZiNzwyySvUfb-NXodqZ7K3+dkHKCOUwhg(a)mail.gmail.com" f55e9737e270c2564d1a0000e171d23e 37 then doveadm fetch -u local-finance-support "mailbox date.saved" UID 37 mailbox: INBOX date.saved: 2020-03-17 14:34:12 Why on earth is dovecot showing today's date for that message? What have I misunderstood or misconfigured? Regards Philip

2 2

doveadm expunge not expunging anymore
by mabi 17 Mar '20

17 Mar '20

Hello, I have migrated my mailbox server from Dovecot 2.1.7 (Debian 7) to Dovecot 2.3.4 (Debian 10) and have a crontab setup in root to daily delete all mails in the INBOX of a specific user which are older than 90 days like this: /usr/bin/doveadm expunge -u username\(a)domain.com mailbox INBOX savedbefore 90d Unfortunately this does not work anymore. I also tried to run the command manually as root which does not return any output or errors. Any idea why this command does not work anymore? Regards, Mabi

3 20

LDAP pass_filter seems to be not working
by Balázs Zeller 16 Mar '20

16 Mar '20

Hi, we are using dovecot --version: 2.3.9.3 (9f41b88fa) with LDAP integration Just discovered the the config which was working for a while is not working now. (we are constantly upgrading dovecot). we have smtp/imap/pop3/sieveEnabled field in our LDAP directory to control which user is able to use witch services. The pass filter was used for control the usage for years now with %LsEnabled filter (see below at config dump) We just discovered that this filter is not working anymore! We not even see any pass_filter queries in LDAP. We see user_filter queries but no pass_filter queries. Did we miss something in the changelog? *LDAP configuration:* grep -v '^ *$#.*$\?$' dovecot-ldap.conf.ext uris = ldap://ldap.services/ dn = cn=administrator,dc=top dnpass = ************ debug_level = 1 auth_bind = yes auth_bind_userdn = mail=%u,ou=service_mail,dc=top ldap_version = 3 base = ou=service_mail,dc=top deref = never scope = subtree user_attrs = mailQuota=quota_rule=*:bytes=%$,mailLocation=mail user_filter = (&(objectClass=customMail)(!(mailEnabled=FALSE))(mail=%u)) pass_attrs = =user=%{ldap:mail} pass_filter = (&(objectClass=customMail)(!(mailEnabled=FALSE))(mail=%u)(%LsEnabled=TRUE)) iterate_attrs = mail=user iterate_filter = (objectClass=demonMail) default_pass_scheme = SSHA *Dovecot main config:* dovecot -n # 2.3.9.3 (9f41b88fa): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.9 (db4e9a2f) # OS: Linux 4.19.87-1.ph3-esx x86_64 xfs # Hostname: 26feef366ef9 auth_cache_negative_ttl = 1 mins auth_cache_size = 10 M auth_cache_ttl = 1 mins auth_debug = yes auth_master_user_separator = * auth_mechanisms = login plain auth_verbose = yes default_vsz_limit = 512 M disable_plaintext_auth = no doveadm_api_key = # hidden, use -P to show it first_valid_gid = 901 first_valid_uid = 901 hostname = mail.****.** imap_client_workarounds = tb-extra-mailbox-sep imapc_features = rfc822.size fetch-headers imapc_host = x.x.x.x imapc_master_user = masteruser imapc_password = # hidden, use -P to show it imapc_user = %u last_valid_gid = 901 last_valid_uid = 901 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 901 mail_home = /vmail/%d/%n/ mail_location = maildir:/vmail/%d/%n/ mail_plugins = " quota zlib trash fts fts_solr" mail_prefetch_count = 20 mail_privileged_group = mail mail_uid = 901 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 { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://hostname:8983/solr/dovecot/ quota = dict:user::file:/vmail/%d/%n/dovecot.quota quota_exceeded_message = The quota of the recipient is full, please try it again later sieve = /vmail/%d/%n/dovecot.sieve sieve_dir = /vmail/.sieve/%u sieve_max_redirects = 20 trash = /etc/dovecot/dovecot-trash.conf.ext zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls postmaster_address = postmaster(a)hostname.com protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener http { port = 8099 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 4 service_count = 0 vsz_limit = 2 G } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service stats { unix_listener stats-reader { group = mail mode = 0666 user = } unix_listener stats-writer { group = mail mode = 0666 user = } } ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </ssl/cert.pem ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lda { mail_plugins = " quota zlib trash fts fts_solr sieve quota zlib" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " quota zlib trash fts fts_solr imap_quota zlib" } protocol pop3 { mail_plugins = " quota zlib trash fts fts_solr quota" } Regards Balazs

2 1

lmtp and recipient_delimiter
by Juri Haberland 16 Mar '20

16 Mar '20

Hi list, I have a small problem with recipient_delimiters contained in usernames. Recently I have extended recipient_delimiter from "+" to "+-" in both Postfix and Dovecot (using lmtp) and now any user that have a '-' in it's username can't receive mail anymore, because lmtp truncates the localpart after the '-' and of course can't find the first half in the user database. To illustrate: given an account "foo-bar(a)example.com", I get the following log entry from postfix: Mar 9 09:31:43 batleth postfix/lmtp[6196]: 9A7BA33E005B: to=<foo-bar(a)example.com>, relay=batleth.sapienti-sat.org[private/dovecot-lmtp], delay=20, delays=20/0.01/0.01/0.08, dsn=5.1.1, status=bounced (host batleth.sapienti-sat.org[private/dovecot-lmtp] said: 550 5.1.1 <foo-bar(a)example.com> User doesn't exist: foo(a)example.com (in reply to RCPT TO command)) Is there any way to tell lmtp to first look for <user><delimiter><extension> and if that fails look for <user> only (the reverse order would be ok, too)? Thanks in advance, Juri doveconf -n: # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: Linux 4.4.0-174-generic x86_64 Ubuntu 16.04.6 LTS ext4 # Hostname: batleth.sapienti-sat.org auth_default_realm = sapienti-sat.org first_valid_uid = 115 imap_idle_notify_interval = 29 mins last_valid_uid = 115 mail_location = maildir:/srv/vmail/%Ld/%Ln 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 { autoexpunge = 180 days special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { autoexpunge = 365 days special_use = \Trash } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { address = 127.0.0.1 ::1 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } } ssl_cert = </etc/letsencrypt/live/sapienti-sat.org/fullchain.pem ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+AES256:+CAMELLIA128:+AES128:+SSLv3:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = uid=postfix gid=postfix home=/srv/vmail/dovecot_state/%Ld/%Ln driver = static } protocol lmtp { auth_username_format = %Lu mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 20 }

6 10

RE: Not works URL
by Tuomi, Aki 15 Mar '20

15 Mar '20

I added redirect for missing urls Aki -------- Original message --------From: Remo Mattei <rm(a)rm.ht> Date: 15/03/2020 19.04 (GMT+02:00) To: Olgerdas <olgerdas(a)balinskis.lt> Cc: dovecot(a)dovecot.org Subject: Re: Not works URL It works from my side. > Il giorno 15 mar 2020, alle ore 04:08, Olgerdas <olgerdas(a)balinskis.lt> ha scritto:> > Hi,> URL not reachable: https://doc.dovecot.org/plugin-settings/acl/> > -- > Pagarbiai,> Olgerdas Balinskis> https://www.balinskis.lt

1 0

Not works URL
by Olgerdas 15 Mar '20

15 Mar '20

Hi, URL not reachable: https://doc.dovecot.org/plugin-settings/acl/ -- Pagarbiai, Olgerdas Balinskis https://www.balinskis.lt

2 1

RE: Not works URL
by Tuomi, Aki 15 Mar '20

15 Mar '20

It has been changed recently. See https://doc.dovecot.org/settings/plugin/aclPlugins/AkiSent from my Samsung Galaxy smartphone. -------- Original message --------From: Olgerdas <olgerdas(a)balinskis.lt> Date: 15/03/2020 13.07 (GMT+02:00) To: dovecot(a)dovecot.org Subject: Not works URL Hi,URL not reachable: https://doc.dovecot.org/plugin-settings/acl/-- Pagarbiai,Olgerdas Balinskishttps://www.balinskis.lt

1 0

Catchall with UserDB?
by Ferenc 15 Mar '20

15 Mar '20

Hi! I've set up Postfix with virtual users. I wanted to get Dovecot and LMTP up and running with Passwd-file UserDB, which they do, but I can't figure out how to make use of a catch-all. Currently, mail to joe(a)example.com needs Joe to be in the Passwd-file. I would like anyone(a)example.com to go to Joe's mailbox, or actually mail to @example.com should go to Joe. But what do I put in the Passwd-file? I need this for several domains. Like @somedomain.org should go to jim(a)example.com and @anydomain.net to jake(a)example.com. I've googled myself silly but I cannot find the it. Everybody is hooked on a sql userdb which seems like overkill to me. With Postfix doing local delivery this is rather trivial. With Dovecot LDA I got it working by using virtual_alias_maps and the right parameters in master.cf. But with LMTP I'm stumped. cheers, Ferenc

2 2

imap-hibernate won't start
by Webservice 14 Mar '20

14 Mar '20

I can't get imap-hibernate to fire up. The process is not starting, and there are no clues in the logs. I tried several users/groups, but nothing happens (although I see plenty of IDLE imap-connections). Even mode 0666 didn't work. I'm on Slackware (no FreeBSD), built from source with ./configure --with-mysql My systems runs with a virtual user, and imap-processes are run under vmail vmail 21840 0.0 0.0 14076 2596 ? S 01:11 0:00 dovecot/imap vmail 21842 0.0 0.0 14108 2568 ? S 01:11 0:00 dovecot/imap I see the socket in var/run/dovecot with OK-permissions: srw-rw---- 1 vmail dovecot 0 Mar 14 01:11 imap-hibernate= Added in my config: mail_debug = yes verbose_proctitle=yes service imap { unix_listener imap-master { user = $default_internal_user } } service imap { extra_groups = $default_internal_group } service imap-hibernate { unix_listener imap-hibernate { user = vmail mode = 0660 group = $default_internal_group } } Can someone give me a clue where it's going wrong? Or an option so I can debug?

2 2