- dovecot - dovecot.org

Buster packages available
by Aki Tuomi 09 Oct '19

09 Oct '19

Hi! We have now buster packages available starting from 2.3.8. You can find them from https://repo.dovecot.org/ In related news, we are planning on dropping packages for Debian Jessie, Ubuntu 18 and CentOS6 starting from 2.3.9. --- Aki Tuomi Open-Xchange oy

2 2

CentOS 8 / 7
by Günther J. Niederwimmer 08 Oct '19

08 Oct '19

Hello List, I have to install a "new" system, what is the best way for this. I like to install a CentOS System but I only found dovecot for CentOS 7 is this compatible for CentOS 8 or have I to setup a CentOS 7 System ? The onboard dovecot is 2.2.36-5 :-( Thanks for a answer, -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

3 2

Pigeonhole v0.5.8 released
by Aki Tuomi 08 Oct '19

08 Oct '19

https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.8.ta… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.8.ta… Binary packages in https://repo.dovecot.org/ Changes - Sieve may leak resources in rare cases when a redirect, vacation or report action fails to send the message. This mainly applies when Sieve is executed in IMAP context; i.e., for the IMAPSIEVE or FILTER=SIEVE capabilities. --- Aki Tuomi Open-Xchange Oy

1 0

ITERINDEX not showing subfolders.
by Erik de Waard 08 Oct '19

08 Oct '19

# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf Hello, we're using mail on NFS and the indexes on localdisk, with a director setup. (18K+ users) now to get more performance i thought to use the ITERINDEX option. however this has the side-effect on some mailboxes that it doesn't show the subfolders under INBOX. they seem 'disappeared'. Removing the ITERINDEX option fixes this again. Deleting the local indexes to be recreated doesn't solve the problem. What could cause this? and how to fix it. # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.9.0-11-amd64 x86_64 Debian 9.11 # Hostname: somemail.host.domain auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_cache_ttl = 1 days auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" default_client_limit = 1500 default_vsz_limit = 1 G disable_plaintext_auth = no info_log_path = /dev/null listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_trusted_networks = 10.0.10.0/24 mail_fsync = never mail_max_userip_connections = 100 mail_prefetch_count = 10 mail_privileged_group = mail mailbox_list_index_include_inbox = yes mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = username_format=%{rip} /etc/dovecot/passdb default_fields = noauthenticate=y driver = passwd-file } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { sieve_execute_bin_dir = /etc/dovecot/sieve-executables sieve_global_extensions = +vnd.dovecot.execute sieve_plugins = sieve_extprograms } protocols = imap lmtp service anvil { unix_listener anvil-auth-penalty { mode = 0600 } } service auth { user = root } service imap-login { client_limit = 6000 process_limit = 4 process_min_avail = 4 service_count = 0 vsz_limit = 600 M } service imap { client_limit = 1 process_limit = 1024 service_count = 50 } service lmtp { inet_listener lmtp { port = 24 } } ssl = no ssl_cert = </etc/dovecot/dovecot.crt ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol lmtp { mail_fsync = optimized mail_plugins = " sieve" plugin { sieve = ~/filters.sieve sieve_after = /etc/dovecot/sieve/after.sieve sieve_before = /etc/dovecot/sieve/before.sieve } userdb { args = /etc/dovecot/dovecot-sql-lmtp.conf driver = sql name = } } dovecot-sql.conf driver = mysql connect = host=10.0.10.150 dbname=maildb user=mail password=5ecret! default_pass_scheme = SHA password_query = select login as user, crypt_sha1 as password, home as userdb_home, uid AS userdb_uid, gid AS userdb_gid, concat('maildir:',maildir,':INDEX=/data/indexes/',login,':ITERINDEX',':VOLATILEDIR=/data/indexes/',login) as userdb_mail from mailbox left join aliases on aliases.systemid = aliasid where login = '%u' and inactive = 0; user_query = select home, maildir as mail, uid, gid from mailbox left join aliases on aliases.systemid = aliasid where login = '%u' and inactive = 0; iterate_query = select distinct login as user from mailbox;

2 1

Is imap "list" required before imap "select" for shared folder?
by Gene Smith 08 Oct '19

08 Oct '19

I set up a shared mailbox with dovecot and it basically works. However, before I can imap SELECT or STATUS the shared mailbox I have to first do an imap LIST, i.e, . list "" * If list is not done first, the imap select or status command on the shared mailbox results in a "NO" response with "mailbox doesn't exist" response text. I can provide more information if this is not expected behavior. -gene

2 2

Sieve redirect is broken in 2.3.7.2 - signal 11
by Demonhost 07 Oct '19

07 Oct '19

Hi, If we use sieve redirect under dovecot 2.3.7.2 we end up with Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 53ac2ae27650 postfix: 0605F207B0F36: to=<xxxx(a)xxxx.xx>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.5, delays=0.36/0/0/1.1, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 6FC89207B0F38) Oct 04 03:30:31 dockerhost docker[12154]: 2019-10-04T03:30:31 53ac2ae27650 postfix: 6FC89207B0F38: to=<xxxx(a)xxxx.xx>, relay=dovecot, delay=0.31, delays=0.05/0/0/0.26, dsn=4.3.0, status=deferred (Command died with signal 11: "/usr/libexec/dovecot/dovecot-lda") Using docker with official alpine image. / # cat /etc/alpine-release 3.8.4 / # apk info -v | grep dovecot WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory dovecot-2.3.7.2-r0 dovecot-fts-solr-2.3.7.2-r0 dovecot-ldap-2.3.7.2-r0 dovecot-pigeonhole-plugin-2.3.7.2-r0 dovecot-pigeonhole-plugin-ldap-2.3.7.2-r0 Sieve rule is: # rule:[test] if header :contains "subject" "test" { redirect "testemail(a)gmail.com"; } In host's dmesg we found the following: [213184.882341] traps: dovecot-lda[6128] general protection ip:7ff6cf8144f7 sp:7fff5f800b30 error:0 in libdovecot.so.0.0.0[7ff6cf724000+360000] Sorry, not knowledgeable enough on how to do the GBD debug. ----------------- We went back to previous version and issue disappeared. 8b45bb255b67:/# cat /etc/alpine-release 3.8.4 8b45bb255b67:/# apk info -v | grep dovecot WARNING: Ignoring APKINDEX.adfa7ceb.tar.gz: No such file or directory WARNING: Ignoring APKINDEX.efaa1f73.tar.gz: No such file or directory dovecot-2.3.6-r0 dovecot-fts-solr-2.3.6-r0 dovecot-ldap-2.3.6-r0 dovecot-pigeonhole-plugin-2.3.6-r0 dovecot-pigeonhole-plugin-ldap-2.3.6-r0 Anyone else already had this problem or you know how to fix it? Thanks in advance.

2 10

Dovecot proxying to some backend using LOGIN proxy_mech
by Sébastien Riccio 06 Oct '19

06 Oct '19

Hello list, I am currently testing a setup for a PoC wit this configuration. - 1 x Frontend dovecot for proxying IMAP/POP3/LMTP/ManageSieve/Submission - 2 x Backend dovecot with local mail storage The frontend does the user authentification and communicate with the backends using a master password The fronted accepts PLAIN and LOGIN auth mechanisms and talk with backends using PLAIN auth mechanism (with the master password). This works very well, it's cool. Then, I've added to this setup an existing mail server (running another mailserver software) as a 3rd backend, and would like the frontend to also proxy for this, but this time not using master password. This is working for IMAP/POP3 when it uses PLAIN auth, but not for Submission. The backend server in this case only accepts LOGIN auth and not PLAIN on port 587. So I found out there is a field in the passdb we can add (proxy_mech), and I've set it to LOGIN. The frontend seems to now use LOGIN auth mech to talk to this 3rd backend, but the authentication still fails. According to the backend logs, tt seems dovecot proxy is now using LOGIN auth, but sends garbage as username and/or password. Also IMAP that was working when using PLAIN doesn't work anymore with LOGIN. Might this be a bug or this setup shouldn't be supported at all ? Passdb MySQL table on frontend: mysql> describe users; +-------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-------------+--------------+------+-----+---------+-------+ | user | varchar(255) | NO | PRI | NULL | | | domain | varchar(255) | NO | PRI | NULL | | | password | varchar(255) | YES | | NULL | | | displayname | varchar(255) | YES | | NULL | | | host | varchar(16) | NO | | NULL | | | usemaster | tinyint(1) | NO | | 1 | | | proxy_mech | varchar(20) | YES | | NULL | | | starttls | varchar(20) | YES | | NULL | | +-------------+--------------+------+-----+---------+-------+ mailstore-01/02 are dovecot backends otherhost is the other mailserver I also would like to proxy through dovecot proxy +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ | user | domain | password | displayname | host | usemaster | proxy_mech | starttls | +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ | user1 | somedomain.com | {SHA512-CRYPT}<some_crypted_pass> | Joe Black | mailstore-01 | 1 | NULL | NULL | | user2 | otherdomain.com | {SHA512-CRYPT}<some_crypted_pass> | Mr. Smith | mailstore-02 | 1 | NULL | NULL | | user3 | area13.com | NULL | Donald Duck | otherhost | 0 | LOGIN | any-cert | | user4 | area13.com | NULL | Thanks Obama | otherhost | 0 | LOGIN | any-cert | +---------+-----------------+-----------------------------------------+----------------+--------------+-----------+------------+----------+ Passdb query : password_query = \ SELECT concat(user, '@', domain) AS user, password, host, 'Y' AS proxy, \ IF(usemaster is TRUE, 'supermasteruserl', NULL) as master, \ IF(usemaster is TRUE, 'supermasterpassword', pass) as pass, \ IF(usemaster is FALSE, 'Y', NULL) as nopassword, \ proxy_mech, \ starttls \ FROM users WHERE user = '%n' AND domain = '%d' Some questions I'm asking myself: Is proxying using LOGIN proxy_mech supported at all to auth on backends ? Is dovecot proxying to "otherhost" supposed to decode original client auth (using PLAIN) and translate it to LOGIN format to auth with "otherhost" ? # otherhost port 587 log Without specifying proxy_mech [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] cmd: EHLO dovecotproxy.local.domain [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] rsp: 250-dovecotproxy.local.domain Hello [192.168.60.220]250-SIZE 52428800250-AUTH LOGIN CRAM-MD5250-STARTTLS250-8BITMIME250-DSN250 OK [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] cmd: AUTH PLAIN <base64string> [2019.09.19] 09:27:22.167 [192.168.60.220][3070269] rsp: 504 Unrecognized authentication type. When using proxy_mech LOGIN [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] cmd: AUTH LOGIN = [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] Exception: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters. [2019.09.20] 08:24:45.201 [192.168.60.220][24148464] rsp: 535 Authentication failed # otherhost port 143 log Works without specyfing proxy_mech When using proxy_mech LOGIN (fails) [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] connected at 20.09.2019 03:37:20 [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] command: C CAPABILITY [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] response: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN UIDPLUS QUOTA XLIST CHILDREN ENABLE IDLE STARTTLS [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] response: C OK CAPABILITY completed [2019.09.20] 03:37:20.896 [192.168.60.220][26310645] command: L AUTHENTICATE LOGIN [2019.09.20] 03:37:20.927 [192.168.60.220][26310645] disconnected at 20.09.2019 03:37:20 I hope I explained my setup so it's kinda understandable. I'm not good at explaining things :) Thank you for your help! root@mailfront-01:~# dovecot --version 2.3.7.2 (3c910f64b) Sébastien RICCIO SYSTEM ADMINISTRATOR

2 2

imapsieve administrator scripts are not executed in the order they are defined
by frankagainstthemachine＠gmx.de 06 Oct '19

06 Oct '19

Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I defined several administrator scripts; among them one that should be executed when copying a mail to mailbox "Inbox", and one that should be executed when copying a mail from a mailbox "*.Spam" to any other mailbox. No matter in which order I define the two scripts, the one related to "Inbox" is always executed first when I move a mail from "blah.Spam" to "Inbox", see the snipped from my logs below. I guess there might be a bug in file imap-sieve-storage.c, function imap_sieve_mailbox_rules_match(...): The comment in this function states "Insert sorted by rule index", but in case the index of the rule to be inserted is higher than any index already in the "rules" array, the rule is inserted in position 0 instead of being appended to the end, because "insert_idx" is initialized with 0. Since the rule for "*.Spam" is a pattern rule, it is the first rule to be inserted into "rules" (in imap_sieve_mailbox_rules_match_patterns(...)). Afterwards the rule for "Inbox" is always inserted at position 0 (in imap_sieve_mailbox_rules_match(...)), no matter if its rule index is higher or lower than the index of the other rule. The following change could fix this: - unsigned int insert_idx = 0; + unsigned int insert_idx = array_count(rules); Best regards, Frank ----- log ----- [...] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: mailbox INBOX: MOVE event Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Pigeonhole version 0.5.7.2 (7372921a) initializing Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.5.7.2 (7372921a) loaded Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [1]: mailbox=`*.Spam' from=`*' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/spamassassin-learn- spam.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`*.Spam' causes=(COPY) => before=`file:/usr/lib/dovecot/sieve/spamassassin-learn- ham.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Static mailbox rule [3]: mailbox=`INBOX' from=`*' causes=(COPY APPEND) => before=`file:~/.dovecot.sieve' after=(none) Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Matched static mailbox rule [2] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: imapsieve: Matched static mailbox rule [3] Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file storage: Using Sieve script path: /var/spool/mail/ user/.dovecot.sieve Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file script: Opened script `.dovecot' from `/var/spool/mail/ user/.dovecot.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file storage: Using Sieve script path: /usr/lib/dovecot/sieve/ spamassassin-learn-ham.sieve Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: file script: Opened script `spamassassin-learn-ham' from `/usr/ lib/dovecot/sieve/spamassassin-learn-ham.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Opening script 1 of 2 from `/var/spool/mail/user/.dovecot.sieve' Oct 4 23:51:12 somehost dovecot[22918]: imap(user)<22927><oLq3sRyU0t/AqLwV>: Debug: sieve: Loading script /var/spool/mail/user/.dovecot.sieve [...] ----- dovecot -n ----- # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 (7372921a) # OS: Linux 5.1.18-gentoo x86_64 Gentoo Base System release 2.6 ext4 # Hostname: somehost.de auth_username_format = %Ln mail_debug = yes mail_home = /var/spool/mail/%u mail_location = maildir:/var/spool/mail/%u/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 vnd.dovec ot.debug namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/spamassassin-learn- spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = *.Spam imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/spamassassin-learn- ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = *.Spam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:~/.dovecot.sieve imapsieve_mailbox3_causes = COPY APPEND imapsieve_mailbox3_name = Inbox mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve sieve_extensions = +vnd.dovecot.debug sieve_filter_bin_dir = /usr/lib/dovecot/sieve sieve_filter_exec_timeout = 300s sieve_filter_input_eol = lf sieve_global = /usr/lib/dovecot/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute +vnd.dovecot.filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_pipe_exec_timeout = 300s sieve_pipe_input_eol = lf sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)frankagainstthemachine.de protocols = imap lmtp sieve sieve service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/ssl/dovecot/somehost.cert.pem ssl_cipher_list = ALL:!DH:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:! 3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_ssl = yes protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = sieve } protocol imap { mail_plugins = " imap_sieve" } protocol sieve { mail_debug = yes }

2 1

Is it possible to create and use some lookup table to replace (for instance) %u in mail_location?
by Gerben Wierda 06 Oct '19

06 Oct '19

Suppose my mail_location is: mail_location = maildir:/private/var/mail/nl.rna.mail/%u But I would like to use a simple lookup table to replace %u with another value, say '8DB4E345-9144-4F92-8C9F-9D47BB61CBF8’ instead of ‘username’. Is there a (simple) way to do this? Gerben Wierda Chess and the Art of Enterprise Architecture <http://enterprisechess.com/> Mastering ArchiMate <http://masteringarchimate.com/> Architecture for Real Enterprises <https://www.infoworld.com/blog/architecture-for-real-enterprises/> at InfoWorld On Slippery Ice <https://eapj.org/on-slippery-ice/> at EAPJ

2 1

Home Directory Creation
by Asai 06 Oct '19

06 Oct '19

Hello, I hate to have to ask this, but... why isn't the home directory being created automatically? Due to legacy compatibility we've had to use this type of home dir config: mail_location = maildir:/vmail/%d/%n mail_home = /vmail/%d/%n/home We're in the middle of upgrading to new hardware, and so I'm migrating configs to the new server, Dovecot 2.3.7 and Postfix 3.4.6 On our old server (Dovecot 2.2, Postfix 2.11) the home directory gets created automatically with a new user, but not on this one. The Dovecot debug logs just say "home dir not found." Can anyone point me in the right direction? Thank you, Asai

5 17