- dovecot - dovecot.org

Quota wrongfully reported as exceeded on shared mailbox
by adminkram＠tripelspark.de 07 May '25

07 May '25

Hi, I've been scratching my head without luck with the following problem: I've shared a mailbox from one user "COMPANY" to another user "JOE". Both users have quotas and both quotas are less than 50% used. When the user JOE tries to post a message into the shared folder, dovecot complains that the user would be over quota: bash# /usr/lib/dovecot/imap -u JOE 1 append shared/COMPANY/Sent/JOE {10} a NO [OVERQUOTA] Quota exceeded (mailbox for user is full) (0.057 + 0.000 + 0.057 secs). However, nobody is over quota: bash# doveadm quota get -u COMPANY Quota name Type Value Limit % User quota STORAGE 4754996 10485760 45 User quota MESSAGE 33695 - 0 bash# doveadm quota get -u JOE Quota name Type Value Limit % User quota STORAGE 14 1048576 0 User quota MESSAGE 3 - 0 Some more infos: 1. Dovecot-2.3.21 (+Debian updates) 2.3.21 (47349e2482) (NOTE: dovecot.org/mailing-lists says: Use dovecot –version to get it. The command is dovecot --version, though!) 2. I've performed "doveadm quota recalc" on both users, no change. 3. I've checked sharing ACL permissions, if I give just "l" permission, the response will be "NO [NOPERM] Permission denied". It does not seem to be an ACL permission reported wrongly. 4. I've tried increasing the quota size beyond reason (100 Gbytes for JOE), no change. 5. I've restarted dovecot after each change. 6. When trying to move a message into the shared Sent/joe folder in Thunderbird, same problem happens, Thunderbird displays the over quota message. Thunderbird cannot display the quota info for the shared folder, though. 7. I tried to enable rawlog (rawlog_dir in protocol imap). It does nothing helpful. It logs the manual commands from my pre-auth sessions (imap -u JOE) but it will stubbornly not log any commands issued by Thunderbird. ?! Any idea how to further debug this or what could be wrong? Thank you, Wolfgang

2 1

Dovecot 3.21.1 -> 2.4.0 SegFault
by Cata S 06 May '25

06 May '25

Hi guys, There seems to be some issue with Dovecot deployed on alpine. More specifically, the dovecot.config file is not properly read. I have run some debugging and the SegFault is returned in the function below: #0 0x000055555556779b in config_parsed_get_setting () No symbol table info available. #1 0x0000555555563708 in config_dump_full () No symbol table info available. #2 0x000055555555c814 in main () No symbol table info available. This was also addressed by alpine here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17050 Any idea what could be causing this? Thanks for looking into it, Cata

2 1

(2.4) weird doveadm behavior
by Kamil Jońca 06 May '25

06 May '25

debian package 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf I have namespace: namespace expunged { mail_driver = maildir mail_path = ~/Mail/expunged/ mailbox_list_layout = fs hidden = yes inbox = no list = no prefix = .EXPUNGED/ separator = / } %doveadm search -u kjonca mailbox .EXPUNGED|head -n 1 08ac303413c11168864d2a00a6f72b09 30802 %doveadm fetch -u kjonca text mailbox-guid 08ac303413c11168864d2a00a6f72b09 uid 30802 ...empty output... How can I fetch messages? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Now KEN and BARBIE are PERMANENTLY ADDICTED to MIND-ALTERING DRUGS ...

3 6

2.3 -> 2.4 migration problem(s)
by Kamil Jońca 06 May '25

06 May '25

Recently in debian sid version 2.4 appeared and I tried to migrate. it (mostly working) but Neither dovecot-lda nor doveadm does not see current system user context i.e. --8<---------------cut here---------------start------------->8--- %doveadm mailbox list Fatal: One of -u, -F, -A or --no-userdb-lookup must be provided --8<---------------cut here---------------end--------------->8--- from lda logs --8<---------------cut here---------------start------------->8--- Fatal: Namespace root: mail_storage settings: Failed to parse configuration: Invalid setting mail_path=~/Mail/0/: mail_path setting used home directory (~/) but there is no mail_home and userdb didn't return it --8<---------------cut here---------------end--------------->8--- for dovecot-lda setting "mail_home = /home/%{user|username}" helped but still ... doveadm mailbox list -u kjonca and "-d" option helped in both cases Moreover I found that doveadm does not work when dovecot is stoped (but used to work in 2.3.x) Another thing is: --8<---------------cut here---------------start------------->8--- deliver_log_format = msgid=%m: %$ --8<---------------cut here---------------end--------------->8--- in 2.3.x configuration it created line like this: --8<---------------cut here---------------start------------->8--- 2025-04-27T02:08:31.925845+02:00 alfa dovecot: LDA(kjonca): sieve: msgid=<fd248603-b186-4ee2-9e76-b9b9c0fe7a87@alfa>: fileinto action: stored mail into mailbox 'RSS' --8<---------------cut here---------------end--------------->8--- but now it does not work (what is strange I cannot find %$ description and %m is described as "mechanism" not message id ...) So how can I have old loggin and authentication mechanisms? KJ # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.22-amd64 x86_64 Debian trixie/sid # ... # 4 default setting change dovecot_config_version = 2.4.0 acl_driver = vfile auth_allow_cleartext = yes auth_debug = yes auth_mechanisms = plain digest-md5 cram-md5 login auth_username_format = %{user | username } auth_verbose = yes default_vsz_limit = 1024M dovecot_storage_version = 2.4.0 lazy_expunge_mailbox = .EXPUNGED/ lazy_expunge_only_last_instance = yes listen = alfa mail_driver = maildir mail_inbox_path = ~/Mail/0/INBOX mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mail_log_fields = uid box msgid size from subject flags mail_log_prefix = "%{protocol}(%{user}): " mail_path = ~/Mail/0/ mail_plugins { acl = yes lazy_expunge = yes } postmaster_address = root@localhost protocols { imap = yes } sieve_execute_bin_dir = %{home}/sieve/bin sieve_execute_exec_timeout = 86400s sieve_extensions { fileinto = yes reject = yes envelope = yes encoded-character = yes vacation = yes subaddress = yes comparator-i;ascii-numeric = yes relational = yes regex = yes imap4flags = yes copy = yes include = yes body = yes variables = yes enotify = yes environment = yes mailbox = yes date = yes index = yes ihave = yes duplicate = yes mime = yes foreverypart = yes extracttext = yes vnd.dovecot.pipe = yes vnd.dovecot.execute = yes vnd.dovecot.filter = yes vnd.dovecot.debug = yes editheader = yes } sieve_filter_bin_dir = %{home}/sieve/bin sieve_filter_exec_timeout = 86400s sieve_pipe_bin_dir = %{home}/sieve/bin sieve_pipe_exec_timeout = 86400s sieve_plugins { sieve_extprograms = yes } ssl = no service auth { user = root unix_listener auth-userdb { } } passdb alfa { default_password_scheme = PLAIN driver = passwd-file passwd_file_path = /etc/security/dovecot.pwd } userdb alfa { passwd_file_path = /etc/security/dovecot.pwd driver = passwd-file } namespace root { inbox = yes separator = / } namespace expunged { mail_driver = maildir mail_path = ~/Mail/expunged/ hidden = yes inbox = no list = no prefix = .EXPUNGED/ separator = / } service imap-login { inet_listener imap { } } service imap { } service auth-worker { user = dovecot } service dict { unix_listener dict { } } protocol lda { deliver_log_format = msgid=%m: %$ info_log_path = syslog log_path = syslog mail_plugins { sieve = yes } syslog_facility = mail } protocol imap { mail_max_userip_connections = 20 mail_plugins { mail_log = yes notify = yes acl = yes imap_acl = yes lazy_expunge = yes } } sieve_script personal { path = ~/.dovecot.sieve } sieve_script before { path = /etc/dovecot/sieve } -- http://wolnelektury.pl/wesprzyj/teraz/ The way I understand it, the Russians are sort of a combination of evil and incompetence... sort of like the Post Office with tanks. -- Emo Philips

3 2

Re: Authentication caching and password changes
by Michael Slusarz 04 May '25

04 May '25

> On 05/03/2025 5:31 AM MDT Diego Alvarez via dovecot <dovecot(a)dovecot.org> wrote: > > In Dovecot docs (https://doc.dovecot.org/2.3/configuration_manual/ > authentication/caching/) we see: > > 1. User logs in with password Y. The cached password X doesn’t match Y and the > previous authentication was unsuccessful, so Dovecot doesn’t bother doing > another backend passdb lookup (until cache TTL expires). The login fails. > > Anyone knows why they chose this design ? Why not simply do a passdb lookup > instead of waiting for cache TTL to expire ? You didn't copy and paste the whole context of this documentation comment: https://doc.dovecot.org/2.4.1/core/config/auth/caching.html#early-change When looking at the full context, this is a situation where a user is either using a password that isn't yet valid (= a bad password, so it's a valid denial), or the user did change their password but the Dovecot system doesn't see the change for some reason (= server/admin issue). In the above situation, doing a passdb lookup without waiting for cache TTL expiration is simply the same situation as not having a negative cache at all. So either don't use the negative cache or fix the password sync (and if you can't fix the authentication sync delay, you can't use a negative cache). An unlikely situation is that the user is using the wrong password originally, and then changes their password to this wrong password. You can always reduce the negative cache TTL if you want to catch this rare situation, at the cost of a lower cache hit rate more generally. michael

2 1

Re: (2.3->2.4) How to expunge with hierarhy saving?
by Michael Slusarz 04 May '25

04 May '25

> On 05/02/2025 10:17 PM MDT Kamil Jońca via dovecot <dovecot(a)dovecot.org> wrote: > > I have used lazy_expunge plugin with namespace (configuration convert): > > namespace expunged { > mail_driver = maildir > mail_path = ~/Mail/expunged/ > hidden = yes > inbox = no > list = no > prefix = .EXPUNGED/ > separator = / > } > > with > lazy_expunge_mailbox = .EXPUNGED > > this allowed me to keep hierarchy (i.e.mails from "admin" mailbox were > expunged to "~/Mail/expunged/admin" ) > this is no longer true - the best I can achieve is to have single > mailbox with all mails :( > Is it possible to get older behavior? > (lazy_expunge_mailbox = .EXPUNGED/ - ends with error) Namespace storage for lazy-expunge plugin was deprecated all the way back in 2.3.0, and was removed for 2.4. I've cleaned up the documentation page to remove all references to namespaces (https://github.com/dovecot/documentation/pull/1234) michael

1 0

Running dovecot 2.4
by Odhiambo Washington 04 May '25

04 May '25

Looking at https://doc.dovecot.org/2.4.1/core/admin/running.html, and comparing with a system where I have installed Dovecot 2.4.1: root@mail:/etc/dovecot/conf.d# ps auxw|grep "dovecot" root 9739 0.0 0.0 8872 4816 ? Ss 14:47 0:00 /usr/sbin/dovecot -F root 9741 0.0 0.0 5324 3280 ? S 14:47 0:00 dovecot/anvil root 9742 0.0 0.0 5428 3256 ? S 14:47 0:00 dovecot/log root 9743 0.0 0.1 51976 10248 ? S 14:47 0:00 dovecot/config Why are my other services not running? For example, the dovecot/auth service is not running. On an system running 2.3.21, I get: wash@eu:~$ ps auxw|grep "dovecot" root 181404 0.0 0.0 8240 4408 ? Ss 14:33 0:00 /usr/sbin/dovecot -F dovecot 181408 0.0 0.0 10668 6936 ? S 14:33 0:00 dovecot/managesieve-login Debian-+ 181409 0.0 0.0 12192 8880 ? S 14:33 0:00 dovecot/lmtp -L dovecot 181410 0.0 0.0 4760 1436 ? S 14:33 0:00 dovecot/anvil root 181411 0.0 0.0 5028 2960 ? S 14:33 0:00 dovecot/log Debian-+ 181412 0.0 0.0 12192 8848 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181413 0.0 0.0 12192 9040 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181414 0.0 0.0 12192 8908 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181415 0.0 0.0 12192 8876 ? S 14:33 0:00 dovecot/lmtp -L root 181416 0.0 0.0 8096 5444 ? S 14:33 0:00 dovecot/config dovecot 181418 0.0 0.0 5964 3496 ? S 14:33 0:00 dovecot/stats dovecot 181419 0.0 0.0 12216 8456 ? S 14:33 0:00 dovecot/auth root@mail:/etc/dovecot/conf.d# doveconf -n # 2.4.1-4+debian12 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4+debian12 (0a86619f) # OS: Linux 6.1.0-34-amd64 x86_64 Debian 12.10 # Hostname: mail.test,domain dovecot_config_version = 2.4.1 auth_debug_passwords = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes info_log_path = /var/log/dovecot.log log_debug = category=auth mail_driver = Maildir mail_path = ~/Maildir protocols = imap pop3 lmtp sieve sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { dbname = exim4u password = # hidden, use -P to show it user = exim4u } passdb sql { default_password_scheme = SHA512 query = SELECT crypt AS password FROM users,domains WHERE users.username = '%{user}' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id } userdb sql { iterate_query = SELECT username AS user FROM users query = SELECT pop as home, uid, gid FROM users WHERE username = '%{user}' } namespace inbox { inbox = yes 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" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } } service auth-worker { } service dict { unix_listener dict { } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] Looking at https://doc.dovecot.org/2.4.1/core/admin/running.html, and comparing with a system where I have installed Dovecot 2.4.1: root@mail:/etc/dovecot/conf.d# ps auxw|grep "dovecot" root 9739 0.0 0.0 8872 4816 ? Ss 14:47 0:00 /usr/sbin/ dovecot -F root 9741 0.0 0.0 5324 3280 ? S 14:47 0:00 dovecot/ anvil root 9742 0.0 0.0 5428 3256 ? S 14:47 0:00 dovecot/log root 9743 0.0 0.1 51976 10248 ? S 14:47 0:00 dovecot/ config Why are my other services not running? For example, the dovecot/auth service is not running. On an system running 2.3.21, I get: wash@eu:~$ ps auxw|grep "dovecot" root 181404 0.0 0.0 8240 4408 ? Ss 14:33 0:00 /usr/sbin/ dovecot -F dovecot 181408 0.0 0.0 10668 6936 ? S 14:33 0:00 dovecot/ managesieve-login Debian-+ 181409 0.0 0.0 12192 8880 ? S 14:33 0:00 dovecot/lmtp -L dovecot 181410 0.0 0.0 4760 1436 ? S 14:33 0:00 dovecot/ anvil root 181411 0.0 0.0 5028 2960 ? S 14:33 0:00 dovecot/log Debian-+ 181412 0.0 0.0 12192 8848 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181413 0.0 0.0 12192 9040 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181414 0.0 0.0 12192 8908 ? S 14:33 0:00 dovecot/lmtp -L Debian-+ 181415 0.0 0.0 12192 8876 ? S 14:33 0:00 dovecot/lmtp -L root 181416 0.0 0.0 8096 5444 ? S 14:33 0:00 dovecot/ config dovecot 181418 0.0 0.0 5964 3496 ? S 14:33 0:00 dovecot/ stats dovecot 181419 0.0 0.0 12216 8456 ? S 14:33 0:00 dovecot/auth root@mail:/etc/dovecot/conf.d# doveconf -n # 2.4.1-4+debian12 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4+debian12 (0a86619f) # OS: Linux 6.1.0-34-amd64 x86_64 Debian 12.10 # Hostname: mail.test,domain dovecot_config_version = 2.4.1 auth_debug_passwords = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes info_log_path = /var/log/dovecot.log log_debug = category=auth mail_driver = Maildir mail_path = ~/Maildir protocols = imap pop3 lmtp sieve sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { dbname = exim4u password = # hidden, use -P to show it user = exim4u } passdb sql { default_password_scheme = SHA512 query = SELECT crypt AS password FROM users,domains WHERE users.username = '% {user}' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id } userdb sql { iterate_query = SELECT username AS user FROM users query = SELECT pop as home, uid, gid FROM users WHERE username = '%{user}' } namespace inbox { inbox = yes 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" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } } service auth-worker { } service dict { unix_listener dict { } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html]

1 0

MySQL AUTH failing
by Odhiambo Washington 03 May '25

03 May '25

I am arriving late to begin the migration to 2.4. The following is my auth-sql.conf.ext: # MySQL Authentication sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { user = user password = SECRET dbname = pass } passdb sql { default_password_scheme = MD5-CRYPT query = SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id } userdb sql { query = SELECT pop as home, uid, gid FROM users WHERE username = '%u' iterate_query = SELECT username AS user FROM users } The queries work for Dovecot 2.3, but fail for 2.4: May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Debug: sql: query: SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id May 03 20:46:44 auth-worker(4758): Debug: mysql(/var/run/mysqld/mysqld.sock): Finished query 'SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id' in 1 msecs May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Info: sql: unknown user May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Debug: sql: Finished passdb lookup May 03 20:46:44 auth-worker(4758): Debug: conn unix:auth-worker (pid=4757,uid=116): auth-worker<1>: Finished: user_unknown May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: sql: Finished passdb lookup May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: Auth request finished May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: delaying auth failure May 03 20:46:46 auth: Debug: conn unix:login (pid=4755,uid=117) [1]: client passdb out: FAIL 1 user=john(a)doe.com -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] I am arriving late to begin the migration to 2.4. The following is my auth-sql.conf.ext: # MySQL Authentication sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { user = user password = SECRET dbname = pass } passdb sql { default_password_scheme = MD5-CRYPT query = SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id } userdb sql { query = SELECT pop as home, uid, gid FROM users WHERE username = '%u' iterate_query = SELECT username AS user FROM users } The queries work for Dovecot 2.3, but fail for 2.4: May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Debug: sql: query: SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id May 03 20:46:44 auth-worker(4758): Debug: mysql(/var/run/mysqld/mysqld.sock): Finished query 'SELECT crypt AS password FROM users,domains WHERE users.username = '%u' AND users.enabled = '1' AND users.type='local' and domains.enabled='1' and domains.domain_id = users.domain_id' in 1 msecs May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Info: sql: unknown user May 03 20:46:44 auth-worker(john(a)doe.com,127.0.0.1)<4758><AAi/1z40rt9/AAAB>: request [1]: Debug: sql: Finished passdb lookup May 03 20:46:44 auth-worker(4758): Debug: conn unix:auth-worker (pid=4757,uid=116): auth-worker<1>: Finished: user_unknown May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: sql: Finished passdb lookup May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: Auth request finished May 03 20:46:44 auth(john@doe.com,127.0.0.1,sasl:plain)<AAi/1z40rt9/AAAB>: Debug: delaying auth failure May 03 20:46:46 auth: Debug: conn unix:login (pid=4755,uid=117) [1]: client passdb out: FAIL 1 user=john(a)doe.com -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html]

1 0

Authentication caching and password changes
by Diego Alvarez 03 May '25

03 May '25

In Dovecot docs (https://doc.dovecot.org/2.3/configuration_manual/ authentication/caching/) we see: 1. User logs in with password Y. The cached password X doesn’t match Y and the previous authentication was unsuccessful, so Dovecot doesn’t bother doing another backend passdb lookup (until cache TTL expires). The login fails. Anyone knows why they chose this design ? Why not simply do a passdb lookup instead of waiting for cache TTL to expire ? In Dovecot docs (https://doc.dovecot.org/2.3/configuration_manual/ authentication/caching/) we see: 1. User logs in with password Y. The cached password X doesn’t match Y and the previous authentication was unsuccessful, so Dovecot doesn’t bother doing another backend passdb lookup (until cache TTL expires). The login fails. Anyone knows why they chose this design ? Why not simply do a passdb lookup instead of waiting for cache TTL to expire ?

1 0

(2.3->2.4) How to expunge with hierarhy saving?
by Kamil Jońca 03 May '25

03 May '25

I have used lazy_expunge plugin with namespace (configuration convert): namespace expunged { mail_driver = maildir mail_path = ~/Mail/expunged/ hidden = yes inbox = no list = no prefix = .EXPUNGED/ separator = / } with lazy_expunge_mailbox = .EXPUNGED this allowed me to keep hierarchy (i.e.mails from "admin" mailbox were expunged to "~/Mail/expunged/admin" ) this is no longer true - the best I can achieve is to have single mailbox with all mails :( Is it possible to get older behavior? (lazy_expunge_mailbox = .EXPUNGED/ - ends with error) KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Zuzanka najwyraźniej pełni obowiązki Albina Siwaka w tej ekipie... (C) Slawek Kotynski w dyskusj nt. pl.whatewer.SETI@home...

1 0

GSSAPI authentication regression with 2.4.x
by Noah Meyerhans 02 May '25

02 May '25

While preparing the Debian packages of Dovecot 2.4.1, I encountered what appears to be a regression that impacts the ability of some clients to successfully negotiate gssapi/krb5 authentication. The regression has so far been observed in gsasl, which was able to successfully authenticate to 2.3.19 but cannot authenticate to 2.4.1. Mutt is able to successfully authenticate with 2.3.19 and 2.4.1. Doveconf output is attached. The debug logs for both failed (gsasl) and successful (mutt) authentications follow. Note that all logs are from an ephemeral debug environment, and sensitive data is not redacted. I can provide additional information as needed, and can test different code and/or configuration changes. Failed authentication dovecot debug log: Apr 30 13:40:09 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:40:09 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:40:09 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libmech_gssapi.so Apr 30 13:40:09 auth: Debug: Read auth token secret from /home/noahm/dovecot-root/b/auth-token-secret.dat Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: Server accepted connection (fd=18) Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: auth client connected (pid=6791) Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: AUTH 1 GSSAPI protocol=imap final-resp-ok session=FhRIDv8zdMzAqAHa lip=172.18.0.205 rip=192.168.1.218 lport=17436 rport=52340 Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: gssapi: Using all keytab entries Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: CONT 1 # Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: CONT 1 # (previous base64 data may contain sensitive data) Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: gssapi: Processed incoming packet correctly, waiting for another. Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: CONT 1 YEcGBisGAQUFAqA9MDugDTALBgkqhkiG9xIBAgKjKjAooCYbJG5vdF9kZWZpbmVkX2luX1JGQzQxNzhAcGxlYXNlX2lnbm9yZQ== Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: CONT 1 YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwMCJkwg3LL7QqlEOunOjvQzpXmA/LMbdtEDyW9b0EQNFL9KFkNuRKDC3V8SFkmG1KlEEHFp2GQNij6AN89xvmEGvhj3tqC280awJs8ve3Bbr7GHRJoFO/sikSRsol1HD/K3sC9OMDufEEItsWf94uu8SmEBpB2OBOzedtfw+PRpoWyYUJYEfAL9T4w0KmBD26KVcehzIv8e3vOl52aT3x9Ovjnw8RfFkZa+t/iGhMpYpf8ApWExZDWBZ6uzVJxcAPg== (previous base64 data may contain sensitive data) Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: Auth request finished Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: delaying auth failure Apr 30 13:40:11 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: FAIL 1 Apr 30 13:40:11 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: Disconnected: Connection closed (fd=18) And the corresponding client log: noahm@42b23a0b5002:~$ gsasl -m GSSAPI -d --no-starttls --imap dovecot-test 17436 Trying 'dovecot-test'... * OK [CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI . OK Pre-login capabilities listed, post-login capabilities have more. . AUTHENTICATE GSSAPI + YEcGBisGAQUFAqA9MDugDTALBgkqhkiG9xIBAgKjKjAooCYbJG5vdF9kZWZpbmVkX2luX1JGQzQxNzhAcGxlYXNlX2lnbm9yZQ== YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwMCJkwg3LL7QqlEOunOjvQzpXmA/LMbdtEDyW9b0EQNFL9KFkNuRKDC3V8SFkmG1KlEEHFp2GQNij6AN89xvmEGvhj3tqC280awJs8ve3Bbr7GHRJoFO/sikSRsol1HD/K3sC9OMDufEEItsWf94uu8SmEBpB2OBOzedtfw+PRpoWyYUJYEfAL9T4w0KmBD26KVcehzIv8e3vOl52aT3x9Ovjnw8RfFkZa+t/iGhMpYpf8ApWExZDWBZ6uzVJxcAPg== . NO [AUTHENTICATIONFAILED] Authentication failed. gsasl: server error Successful authentication (mutt) dovecot debug log: Apr 30 13:32:30 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:32:30 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:32:30 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libmech_gssapi.so Apr 30 13:32:30 auth: Debug: Read auth token secret from /home/noahm/dovecot-root/b/auth-token-secret.dat Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: Server accepted connection (fd=18) Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: auth client connected (pid=6788) Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: AUTH 1 GSSAPI protocol=imap final-resp-ok session=4aLx8v4z8JPAqAHa lip=172.18.0.205 rip=192.168.1.218 lport=17436 rport=37872 resp=YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwHCqBBzSB3g1k9BBC5M8XG5NpM35pvpLMHWjw0HIXloN2XjibgczTBt6l+q4DuWo6OWCuf5U+g+BrQ17y52AnCwUk/l722toAEhxwEKA/f3K+7i/lXBzjfCxGTmD2TTO6NUVZUM6TTa6CvwKgGwzGZLh/kQ90VnyzaOyTErL5oiNtl8ZKfguMt38yV8THESf8ZGjxUCKUUa1n3UNClhVk/0Kl88qGD1h11it0yFoNNK5/tbqI5e+sdi+pK4VHsvjPw== (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(?,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: Using all keytab entries Apr 30 13:32:30 auth(noahm@example.com,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: security context state completed. Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: CONT 1 YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsiRFdcazky9GL2l//v2J+U606pbiLSCahGZ2wUxpp05eo9kGAl7j/UQfkzmlOWW7aMfMzPrJTveYBZiDpcfyeTt/wJfAHiEk5A24KYKTIt2ialxe6YOvrmz1e4B+mULZAghrfq5ftdUkQfh0CP/W Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: CONT 1 (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(noahm@example.com,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: Negotiated security layer Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: CONT 1 BQQF/wAMAAAAAAAAFUr00gH/////HIlwJEVFPtqhtCU= Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: CONT 1 BQQE/wAMAAAAAAAAIfpD4AH///9ub2FobalxyQ7OjgY973Gakw== (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Performing passdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Finished passdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: Credentials: 70656e63696c Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: Auth request finished Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: OK 1 user=noahm original_user=noahm(a)EXAMPLE.COM Apr 30 13:32:30 auth: Debug: conn unix:/home/noahm/dovecot-root/b/auth-master (pid=6790,uid=0): Server accepted connection (fd=19) Apr 30 13:32:30 auth: Debug: master in: REQUEST 4221435905 6788 1 6b8a10b34adc8ace171603fc8d378730 session_pid=6790 request_auth_token Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Performing userdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Finished userdb lookup Apr 30 13:32:30 auth: Debug: master userdb out: USER 4221435905 noahm uid=4711 gid=4711 home=/home/noahm/dovecot-root auth_mech=GSSAPI auth_token=705494201f3425a0145e2f7af1edca82fee2ee17 auth_user=noahm(a)EXAMPLE.COM The corresponding client-side logs generated by mutt are: [2025-04-30 13:32:30] Connecting to dovecot-test... [2025-04-30 13:32:30] Connected to dovecot-test:17436 on fd=4 [2025-04-30 13:32:30] 4< * OK [CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. [2025-04-30 13:32:30] imap_authenticate: Trying method gssapi [2025-04-30 13:32:30] imap_auth_gsasl: using mech GSSAPI [2025-04-30 13:32:30] Authenticating (GSSAPI)... [2025-04-30 13:32:30] 4> a0000 AUTHENTICATE GSSAPI YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwHCqBBzSB3g1k9BBC5M8XG5NpM35pvpLMHWjw0HIXloN2XjibgczTBt6l+q4DuWo6OWCuf5U+g+BrQ17y52AnCwUk/l722toAEhxwEKA/f3K+7i/lXBzjfCxGTmD2TTO6NUVZUM6TTa6CvwKgGwzGZLh/kQ90VnyzaOyTErL5oiNtl8ZKfguMt38yV8THESf8ZGjxUCKUUa1n3UNClhVk/0Kl88qGD1h11it0yFoNNK5/tbqI5e+sdi+pK4VHsvjPw== [2025-04-30 13:32:30] 4< + YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsiRFdcazky9GL2l//v2J+U606pbiLSCahGZ2wUxpp05eo9kGAl7j/UQfkzmlOWW7aMfMzPrJTveYBZiDpcfyeTt/wJfAHiEk5A24KYKTIt2ialxe6YOvrmz1e4B+mULZAghrfq5ftdUkQfh0CP/W [2025-04-30 13:32:30] 4> [2025-04-30 13:32:30] 4< + BQQF/wAMAAAAAAAAFUr00gH/////HIlwJEVFPtqhtCU= [2025-04-30 13:32:30] 4> BQQE/wAMAAAAAAAAIfpD4AH///9ub2FobalxyQ7OjgY973Gakw== [2025-04-30 13:32:30] 4< a0000 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE REPLACE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW SPECIAL-USE STATUS=SIZE SAVEDATE COMPRESS=DEFLATE INPROGRESS NOTIFY LITERAL+] Logged in

5 5

Dovecot 3.21.1 -> 2.4.0 SegFault
by Cata S 02 May '25

02 May '25

Hi guys, There seems to be some issue with Dovecot deployed on alpine. More specifically, the dovecot.config file is not properly read. I have run some debugging and the SegFault is returned in the function below: #0 0x000055555556779b in config_parsed_get_setting () No symbol table info available. #1 0x0000555555563708 in config_dump_full () No symbol table info available. #2 0x000055555555c814 in main () No symbol table info available. This was also addressed by alpine here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17050 Any idea what could be causing this? Thanks for looking into it, Cata

2 3

2.3 -> 2.4 sieve scripts
by Kamil Jońca 01 May '25

01 May '25

I have configured some sieve scripts to run when I append messages to one of mailbox: --8<---------------cut here---------------start------------->8--- imapsieve_mailbox1_name = Archives imapsieve_mailbox1_causes = APPEND imapsieve_mailbox1_before = file:/.../sieve/dovecot.sieve --8<---------------cut here---------------end--------------->8--- I tried to use this with 2.4 with no luck: # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.21-amd64 x86_64 Debian trixie/sid # Hostname: qqrq # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain digest-md5 cram-md5 login compress_zstd_level = 22 default_vsz_limit = 2048M dovecot_storage_version = 2.4.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes mail_compress_write_method = zstd mail_driver = mdbox mail_home = /home/%{user} mail_inbox_path = ~/Mail/0/INBOX mail_path = ~/Mail/0/ mail_plugins { mail_compress = yes acl = yes } mail_privileged_group = mail protocols { imap = yes } sieve_extensions { fileinto = yes reject = yes envelope = yes encoded-character = yes vacation = yes subaddress = yes comparator-i;ascii-numeric = yes relational = yes regex = yes imap4flags = yes copy = yes include = yes body = yes variables = yes enotify = yes environment = yes mailbox = yes date = yes index = yes ihave = yes duplicate = yes mime = yes foreverypart = yes extracttext = yes notify = yes imapflags = yes editheader = yes } sieve_plugins { sieve_imapsieve = yes sieve_extprograms = yes } sieve_redirect_envelope_from = recipient ssl = no passdb passwd-file { default_password_scheme = PLAIN passwd_file_path = /etc/dovecot/users } userdb passwd-file { passwd_file_path = /etc/dovecot/users } namespace inbox { inbox = yes separator = / 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" } } service imap-login { inet_listener imap { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } } service auth-worker { } service dict { unix_listener dict { } } protocol imap { mail_plugins { mail_log = yes notify = yes acl = yes imap_acl = yes sieve = yes imap_sieve = yes lazy_expunge = yes } } sieve_script mailbox1 { imapsieve_from_name = Archives cause = append path = file:/.../sieve/dovecot.sieve type = before } When I add message to Archive, I can see in logs: imap(kjonca): Error: Couldn't load required plugin /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol: mail_deliver_ctx_get_log_var_expand_table -- http://wolnelektury.pl/wesprzyj/teraz/ Never go to bed mad. Stay up and fight. -- Phyllis Diller, "Phyllis Diller's Housekeeping Hints"

1 1

How to backup mdbox
by lutz.niederer＠gmx.net 30 Apr '25

30 Apr '25

Hi, dovecot with mdbox on zfs running fine and robust since one year now. Zfs and mdbox seem to make sense. What we do for backup currently is stop dovecot, take a snapshot and restart dovecot. That only takes a few seconds to complete. After that we have time to do the backup. Is that the correct way, or is there a better, preferred way to get the backup done? Is there a way to freeze dovecot while still keeping the clients happy? Some are thrown off and don't recover (namely outlook, even if it takes a few seconds only). We can live with that, but better would be better. Thanks and cheers, -lutzn

1 0

sieve filter does not work
by Kamil Jońca 29 Apr '25

29 Apr '25

sieve-filter -e -W -D -C -v ~/.dovecot.sieve mailbox sieve-filter: Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol: mail_deliver_ctx_get_log_var_expand_table -- http://wolnelektury.pl/wesprzyj/teraz/ Even if you do learn to speak correct English, whom are you going to speak it to? -- Clarence Darrow

1 0

2025-04-28
by 村上寛 28 Apr '25

28 Apr '25

test222 test222

1 0

Sieve fails to find existing folder?
by Alexander Skwar 25 Apr '25

25 Apr '25

Hello I've got issues using filters. Although a filter matches a message, the message remains in the INBOX. In the log file a(a)skwar.xyz.sieve.log, I find this: sieve: info: started log at 2025-04-14 18:15:31 +0200. error: msgid=<1051036477.1870592.1744647326637(a)mail.yahoo.com>: fileinto action: failed to store into mailbox '🎗 Social Networks/🏔🚴 Draussen': Mailbox doesn't exist: 🎗 Social Networks/🏔🚴 Draussen. Yes, the folders are **really** named "🎗 Social Networks" and "🏔🚴 Draussen" 😜 I like emojis, makes it easier for me to find things again 🙂 The filter rule for this is: require ["regex","imap4flags","fileinto"]; if anyof (address :regex :comparator "i;octet" "from" ".*@(yahoo\\.com|bergportal\\.ch|freezetag\\.com|garmin\\.com|geocaching\\.com|komoot\\.de|munzee\\.com|quaeldich\\.de|spontacts\\.com|squadrats\\.com|strava\\.com|update\\.strava\\.com|velocity\\.ch|wandrer\\.earth)$", address :regex :comparator "i;octet" ["to", "cc"] "hiking-buddies@acc\\.alexs77\\.rodeo|carving\\.fleshed313@alexs77\\.foobar\\.vip|com\\+wandrer\\.earth@skwar\\.me|squadrats\\.com@acc\\.alexs77\\.rodeo", address :regex :comparator "i;octet" "from" "hikingbuddiesteam(a)gmail.com|email.meetup.com") { fileinto "🎗 Social Networks/🏔🚴 Draussen"; stop; } In this case, it matches on "<whatever>@yahoo.com". Why did it not find the folder? I created the folder and rule in SOGo 5.12.0 from mailcow 2025-03b. bd36093fccaa:/var/vmail/sieve# dovecot --version 2.3.21.1 (d492236fa0) Should the Emojis somehow be encoded, so that the filter would work? Cheers, Alexander

5 9

cgroupv2 privileged execution
by Matt Saladna 23 Apr '25

23 Apr '25

In similar vein to "[cgroup support]" from Jan 30, 2011 I'd like to add cgroupv2 support to Dovecot. With v2, moving processes is more restrictive in that groups can only have a single-writer and the process of the common ancestor cgroup between the losing and gaining group must have write privileges. So far as I understand: - Every hook (mail_user_created, mail_storage_created, etc) occurs after chroot + setuid - Wrapping imap or pop3 executables doesn't expose the userdb data in environment, this is done in the actual imap and pop3 processes respectively - Adding a script-login does export the correct userdb details but the pid isn't known. Since everything spawns under dovecot master, the only practical solution is to enumerate every imap or pop3 process owned by the gid to reassign to the new cgroup. This limits implementation to a plugin that solicits the pid to a separate daemon listening on a socket launched by Dovecot in mail_user_created hook. Ideally I would like for cgroup binding to occur before imap/pop3 binaries launch for cgroupv2 pid rejection to occur, although this seems impossible to achieve? - Matt In similar vein to "[cgroup support]" from Jan 30, 2011 I'd like to add cgroupv2 support to Dovecot. With v2, moving processes is more restrictive in that groups can only have a single-writer and the process of the common ancestor cgroup between the losing and gaining group must have write privileges. So far as I understand: - Every hook (mail_user_created, mail_storage_created, etc) occurs after chroot + setuid - Wrapping imap or pop3 executables doesn't expose the userdb data in environment, this is done in the actual imap and pop3 processes respectively - Adding a script-login does export the correct userdb details but the pid isn't known. Since everything spawns under dovecot master, the only practical solution is to enumerate every imap or pop3 process owned by the gid to reassign to the new cgroup. This limits implementation to a plugin that solicits the pid to a separate daemon listening on a socket launched by Dovecot in mail_user_created hook. Ideally I would like for cgroup binding to occur before imap/pop3 binaries launch for cgroupv2 pid rejection to occur, although this seems impossible to achieve? - Matt

1 0

Android mail client capable of utilizing FTS?
by Alexander Skwar 22 Apr '25

22 Apr '25

Hello I enabled FTS Full Text Search using Tika in dovecot and have all the emails now reindexed. Using either "IMAP by hand" (ie via telnet or openssl s_client), SOGo webmail, or Thunderbird on macOS, I can search for and also find emails based on text which is only in a PDF attachment. Using Thunderbird or the now dead k-9, I'm not finding anything. Can someone maybe suggest an email client for Android which is able to find emails based on text in FTS? Technically, I guess it should do a "search TEXT "foo bar"" query. Here's a complete session done in "IMAP by hand": $ openssl s_client -crlf -connect my-sys:993 … --- read R BLOCK * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a LOGIN myuser@sysd pass a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW STATUS=SIZE SAVEDATE LITERAL+ NOTIFY METADATA SPECIAL-USE COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in b SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped \*)] Flags permitted. * 10 EXISTS * 0 RECENT * OK [UNSEEN 8] First unseen. * OK [UIDVALIDITY 1671377672] UIDs valid * OK [UIDNEXT 1709] Predicted next UID * OK [HIGHESTMODSEQ 2613] Highest b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). c SEARCH TEXT "Veloplatzreservierung" * SEARCH 3 c OK Search completed (0.042 + 0.000 + 0.041 secs). d FETCH 3 (BODY.PEEK[HEADER.FIELDS (Message-ID Date)]) * 3 FETCH (BODY[HEADER.FIELDS (MESSAGE-ID DATE)] {124} Message-Id: <202504100258.53A2waba008043-53A2wabb008043(a)mailqueue01.leuchter-cloud.ch> Date: 10 Apr 2025 04:58:36 +0200 ) d OK Fetch completed (0.001 + 0.000 secs). z LOGOUT * BYE Logging out z OK Logout completed (0.001 + 0.000 secs). closed Alexander Hello I enabled FTS Full Text Search using Tika in dovecot and have all the emails now reindexed. Using either "IMAP by hand" (ie via telnet or openssl s_client), SOGo webmail, or Thunderbird on macOS, I can search for and also find emails based on text which is only in a PDF attachment. Using Thunderbird or the now dead k-9, I'm not finding anything. Can someone maybe suggest an email client for Android which is able to find emails based on text in FTS? Technically, I guess it should do a "search TEXT "foo bar"" query. Here's a complete session done in "IMAP by hand": $ openssl s_client -crlf -connect my-sys:993 … =============================================================================== read R BLOCK * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a LOGIN myuser@sysd pass a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW STATUS=SIZE SAVEDATE LITERAL+ NOTIFY METADATA SPECIAL-USE COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in b SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped \*)] Flags permitted. * 10 EXISTS * 0 RECENT * OK [UNSEEN 8] First unseen. * OK [UIDVALIDITY 1671377672] UIDs valid * OK [UIDNEXT 1709] Predicted next UID * OK [HIGHESTMODSEQ 2613] Highest b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). c SEARCH TEXT "Veloplatzreservierung" * SEARCH 3 c OK Search completed (0.042 + 0.000 + 0.041 secs). d FETCH 3 (BODY.PEEK[HEADER.FIELDS (Message-ID Date)]) * 3 FETCH (BODY[HEADER.FIELDS (MESSAGE-ID DATE)] {124} Message-Id: <202504100258.53A2waba008043-53A2wabb008043(a)mailqueue01.leuchter- cloud.ch> Date: 10 Apr 2025 04:58:36 +0200 ) d OK Fetch completed (0.001 + 0.000 secs). z LOGOUT * BYE Logging out z OK Logout completed (0.001 + 0.000 secs). closed Alexander

3 2

Dovecot migration to new server with namespace issues
by Gabriel Kaufmann | TYPOworx 22 Apr '25

22 Apr '25

Hello, I'm trying to migrate old ispconfig server with dovecot + postfix to a new modernized server. I'm having some trouble with dovecot doing what I want/need to reuse use my old configuration. I've been using maildir++. The new dovecot makes me some headcache as I cannot simply reuse the old configuration or INBOX folder. Any ideas how to get this fixed? My Maildir's & IMAP looked like this for the old system: Maildir/ <-- obviously not shown in IMAP :) INBOX/ Drafts/ Templates/ Sent/ Archives/ Trash On my old ispconfig server with older linux/dovecot version I simply had this configuration: > namespace inbox { > inbox = yes > > mailbox ".Drafts" { > auto = no > special_use = \Drafts > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > > mailbox ".Junk" { > auto = no > special_use = \Junk > } > mailbox Spam { > auto = no > special_use = \Junk > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > > mailbox ".Trash" { > auto = no > special_use = \Trash > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > > mailbox Archives { > auto = subscribe > special_use = \Archive > } > } My approach to make this work using dovecot 2.3.21 got me in some trouble. Obviously new dovecot wants to store INBOX-Date in Maildir/{cur,tmp,new} instead of Maildir/INBOX? I've tried with this configuration - which at least correctly shows INBOX-Data now in my IMAP, but I also have some troubles: Maildir/ <-- obviously not shown in IMAP :) INBOX/ My Custom Folder/ Drafts/ <------------- repeating from imap-root subscribing it there duplicates it here :-/ Templates/ Sent/ Archives/ Trash .Trash Drafts/ Templates/ Sent/ Archives/ Trash .Trash (somehow same than Trash, only want Trash non-dotted) New configuration approach: > mail_location = > maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/:maildir_copy_with_hardlinks=yes > maildir_copy_with_hardlinks = yes > > plugin { > mailbox_alias_junk1 = Junk > mailbox_alias_junk2 = Spam > > mailbox_alias_sent_de = Gesendet > } > > namespace { > type = private > separator = / > > location = > maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/:LISTINDEX= > > inbox = no > list = yes > subscriptions = yes > > > mailbox .Junk { > auto = no > special_use = \Junk > } > > mailbox .Drafts { > auto = no > special_use = \Drafts > } > > mailbox .Trash { > auto = no > special_use = \Trash > } > > mailbox .Sent { > auto = no > special_use = \Sent > } > > mailbox .Archives { > auto = no > special_use = \Archive > } > > mailbox .Templates { > auto = no > } > } > > namespace inbox { > type = private > separator = / > prefix = INBOX/ > > location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/ > > inbox = yes > list = yes > hidden = yes > subscriptions = yes > > mailbox .Junk { > auto = no > } > > mailbox .Drafts { > auto = no > } > > mailbox .Trash { > auto = no > } > > mailbox .Sent { > auto = no > } > > mailbox .Archives { > auto = no > } > > mailbox .Templates { > auto = no > } > } -- Best regards Gabriel Kaufmann Hello, I'm trying to migrate old ispconfig server with dovecot + postfix to a new modernized server. I'm having some trouble with dovecot doing what I want/need to reuse use my old configuration. I've been using maildir++. The new dovecot makes me some headcache as I cannot simply reuse the old configuration or INBOX folder. Any ideas how to get this fixed? My Maildir's & IMAP looked like this for the old system: Maildir/ <-- obviously not shown in IMAP :) INBOX/ Drafts/ Templates/ Sent/ Archives/ Trash On my old ispconfig server with older linux/dovecot version I simply had this configuration: namespace inbox { inbox = yes mailbox ".Drafts" { auto = no special_use = \Drafts } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox ".Junk" { auto = no special_use = \Junk } mailbox Spam { auto = no special_use = \Junk } mailbox Junk { auto = subscribe special_use = \Junk } mailbox ".Trash" { auto = no special_use = \Trash } mailbox Trash { auto = subscribe special_use = \Trash } mailbox Archives { auto = subscribe special_use = \Archive } } My approach to make this work using dovecot 2.3.21 got me in some trouble. Obviously new dovecot wants to store INBOX-Date in Maildir/{cur,tmp,new} instead of Maildir/INBOX? I've tried with this configuration - which at least correctly shows INBOX-Data now in my IMAP, but I also have some troubles: Maildir/ <-- obviously not shown in IMAP :) INBOX/ My Custom Folder/ Drafts/ <------------- repeating from imap-root subscribing it there duplicates it here :-/ Templates/ Sent/ Archives/ Trash .Trash Drafts/ Templates/ Sent/ Archives/ Trash .Trash (somehow same than Trash, only want Trash non-dotted) New configuration approach: mail_location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs: DIRNAME=/:maildir_copy_with_hardlinks=yes maildir_copy_with_hardlinks = yes plugin { mailbox_alias_junk1 = Junk mailbox_alias_junk2 = Spam mailbox_alias_sent_de = Gesendet } namespace { type = private separator = / location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/: LISTINDEX= inbox = no list = yes subscriptions = yes mailbox .Junk { auto = no special_use = \Junk } mailbox .Drafts { auto = no special_use = \Drafts } mailbox .Trash { auto = no special_use = \Trash } mailbox .Sent { auto = no special_use = \Sent } mailbox .Archives { auto = no special_use = \Archive } mailbox .Templates { auto = no } } namespace inbox { type = private separator = / prefix = INBOX/ location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/ inbox = yes list = yes hidden = yes subscriptions = yes mailbox .Junk { auto = no } mailbox .Drafts { auto = no } mailbox .Trash { auto = no } mailbox .Sent { auto = no } mailbox .Archives { auto = no } mailbox .Templates { auto = no } } -- Best regards Gabriel Kaufmann

1 0

Bash automation for Dovecot
by Travis Bean 21 Apr '25

21 Apr '25

Hello, I developed a Bash script to automate the installation and configuration of open-source software (i.e., launchpad.net/linuxha) I want to make sure the syntax of this script is perfect so I can use it as a teaching tool to educate people about Linux. I need to know if there is anything misconfigured with my Dovecot syntax. If you find a bug in LinuxHA, please submit a bug report to bugs.launchpad.net/linuxha/+filebug. Kind regards, Travis Bean Hello, I developed a Bash script to automate the installation and configuration of open-source software (i.e., launchpad.net/linuxha) I want to make sure the syntax of this script is perfect so I can use it as a teaching tool to educate people about Linux. I need to know if there is anything misconfigured with my Dovecot syntax. If you find a bug in LinuxHA, please submit a bug report to bugs.launchpad.net/ linuxha/+filebug. Kind regards, Travis Bean

1 0

mail crypto in Ubuntu 22.04.5 - Provider routines::invalid salt length
by Max Kostikov 18 Apr '25

18 Apr '25

Hi, I am facing mail crypt extension error. When I try to create keys I get this error. doveadm -o plugin/mail_crypt_private_password=e32f1f464d7576716d5df899e7d5cb6b64cdb55584c71882e9f7e7c79f2e69e6 mailbox cryptokey generate -u "foo(a)example.com" doveadm(foo(a)example.com): Error: mail_crypt_user_generate_keypair(foo(a)example.com) failed: error:1C800070:Provider routines::invalid salt length doveadm(foo(a)example.com): Warning: mailbox cryptokey generate: Nothing was matched. Use -U or specify mask? Folder Public ID x ERROR: error:1C800070:Provider routines::invalid salt length Segmentation fault (core dumped) Any insights why? OS: Ubuntu 22.04.5 LTS (FIPS) Dovecot packages installed: dovecot-core/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-imapd/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-lmtpd/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-managesieved/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-mysql/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-pop3d/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-sieve/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] Mail crypt configuration: ... mail_attribute_dict = file:/var/vmail/%d/%n/dovecot-attributes mail_plugins = mail_crypt quota plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes } ... -- Sincerely, Max Kostikov

1 1

Auth-worker malloc failure
by Scott Q. 17 Apr '25

17 Apr '25

I recently changed the userdb to sql, using a stored procedure and since then, every so often, maybe 2-3 times per day I see errors like these in the maillog: Apr 17 13:33:04 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: error:140BA041:SSL routines:SSL_new:malloc failure - waiting for 1 seconds before retry Apr 17 13:33:05 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 5 seconds before retry Apr 17 13:33:10 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 25 seconds before retry Apr 17 13:33:35 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 125 seconds before retry Apr 17 13:34:04 imap1 dovecot[41212]: auth-worker(41325): Error: sql(user(a)domain.com,1.2.3.4,): User query failed: Not connected to database Is this the auth-worker running out of memory ? I have these settings: auth_cache_size = 8 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_verbose = yes auth_worker_max_count = 130 service auth { unix_listener auth-master { mode = 0600 user = vuser } user = root client_limit=1500 } I recently changed the userdb to sql, using a stored procedure and since then, every so often, maybe 2-3 times per day I see errors like these in the maillog: Apr 17 13:33:04 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: error:140BA041:SSL routines:SSL_new:malloc failure - waiting for 1 seconds before retry Apr 17 13:33:05 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 5 seconds before retry Apr 17 13:33:10 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 25 seconds before retry Apr 17 13:33:35 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 125 seconds before retry Apr 17 13:34:04 imap1 dovecot[41212]: auth-worker(41325): Error: sql (user(a)domain.com,1.2.3.4,<5ohIy/wyHvox5b/p>): User query failed: Not connected to database Is this the auth-worker running out of memory ? I have these settings: auth_cache_size = 8 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_verbose = yes auth_worker_max_count = 130 service auth { unix_listener auth-master { mode = 0600 user = vuser } user = root client_limit=1500 }

1 0

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 17 Apr '25

17 Apr '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any /dove/ command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I'm using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I'm using the wrong mailing list, please point me to the right channel

3 7

Problem email client iPhone ios18.2
by andrzej.milewski＠gmail.com 17 Apr '25

17 Apr '25

Hello, I have a fairly new installation of the Dovecot server version 2.3.19.1 on Debian 12.8. In general, the server works correctly. It sends and receives emails without issues. The clients primarily use Thunderbird on desktops and Gmail on Android. However, some clients are using iPhones with various hardware versions. Those with iOS below version 18 work correctly without any issues. Those who have updated their phones to version 18 and now even 18.2 are experiencing problems with mailbox synchronization. On version 18.2, the issue appears as follows: When you open the app, you can read several messages. They load correctly, but, for instance, attachments do not. If I wait for some time, the attachment eventually loads. During this time, I observe the server logs, and it shows that a certain session on the Dovecot server has ended. Dec 17 13:13:01 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<44785><1QGZCHcp/+3AqM2O>: Disconnected: Connection closed (UID SEARCH finished 92.295 secs ago) in=2972 out=6076956 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=36 body_bytes=6059064 Dec 18 08:40:41 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<177412>: Disconnected: Connection closed (UID FETCH finished 90.079 secs ago) in=5126 out=1304237 deleted=0 expunged=0 trashed=0 hdr_count=94 hdr_bytes=289688 body_count=89 body_bytes=969615 Dec 18 08:42:19 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<177410><D5mqU4cpZ+nAqM2O>: Disconnected: Connection closed (UID FETCH finished 95.051 secs ago) in=4475 out=1162785 deleted=0 expunged=0 trashed=0 hdr_count=95 hdr_bytes=281674 body_count=61 body_bytes=839545 Dec 18 08:44:17 iredmail0 dovecot[408]: imap(edyta.kowalewska(a)laktopol.com.pl)<177918>: Disconnected: Connection closed (UID FETCH finished 92.132 secs ago) in=29399 out=30266644 deleted=0 expunged=0 trashed=0 hdr_count=565 hdr_bytes=1726228 body_count=628 body_bytes=28109455 After the session is closed, the attachment loads immediately. From the logs and router analysis, it appears that the download happens in another previously opened session. After this incident, I go to another message with an attachment, and the situation repeats. There are also situations where the email body does not load, and the app waits for the server until the session closes and the content is fetched in another session. It does not matter whether I connect to the server via the internet or through a local network. On an iPhone 7 with iOS 15.8.3, everything works smoothly. Attachments open without issues. On iOS 18.1.1, attachments do not load, and the session does not close on its own. It takes forever unless the app is closed. In the Gmail app, everything works correctly without any issues. This is clearly a problem with the mail client on iPhone. However, is there anything I can adjust in my server settings to mitigate this issue for users? My dovecot configuration https://pastebin.com/UPNQ5dZz

26 58

config help with sieve_script
by Genes Lists 17 Apr '25

17 Apr '25

Any advice what I am doing wrong: I am in process of converting our 2.3 configs to 2.4.1 and sieve / sieve_script has me stumped. When I use: plugin { sieve_script xxx { ... } sieve_script yyy { ... } } each xxx/yyy is personal or before or after etc. dovecot -n give: ./conf.d/90-sieve.conf line 6: Unknown section name: plugin If I remove the plugin { } part then I get: Unknown section name: sieve_script Obviously I am doing something wrong - appreciate any help? thank you -- Gene Any advice what I am doing wrong: I am in process of converting our 2.3 configs to 2.4.1 and sieve / sieve_script has me stumped. When I use: plugin { sieve_script xxx { ... } sieve_script yyy { ... } } each xxx/yyy is personal or before or after etc. dovecot -n give: ./conf.d/90-sieve.conf line 6: Unknown section name: plugin If I remove the plugin { } part then I get: Unknown section name: sieve_script Obviously I am doing something wrong - appreciate any help? thank you -- Gene

2 2

Decouple the username hash from the login given
by José Celestino 16 Apr '25

16 Apr '25

Hi all, Is there a way to do the hash on the director without setting the user (or destuser) for the Dovecot backend authentication? The scenario is: Our accounts have multiple aliases where each alias can have a different password (long story): Alias1 accountX password1 Alias2 accountX password2 Alias3 accountX password3 accountX accountX passwordX Our goal is to map the same account, regardless of the alias used to authenticate, to the same backend server. We use checkpassword for userdb on the director, and when we set either the user or username to the main account id (accountX on the example) it sends the authentication as accountX, passwordN, and fails. Is there a var that can be set and used for hashing, leaving the authentication untouched? Our installed version is 2.3.21. Thank you. Best regards, José Celestino

1 1

Question about dovecot quota calculation
by Zakaria 16 Apr '25

16 Apr '25

Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug, if not it would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB through quota command? I think both should present identical results, anyone thinks otherwise, I would appreciate if you share with us the reasoning? Also, which one I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak. Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug, if not it would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB through quota command? I think both should present identical results, anyone thinks otherwise, I would appreciate if you share with us the reasoning? Also, which one I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak.

1 0

Question about quota calculation
by Zakaria 16 Apr '25

16 Apr '25

Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug but this would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB in my case through quota command and why is this? Which one would I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak. Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug but this would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB in my case through quota command and why is this? Which one would I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak.

1 0

Dovecot24 - passdb configuration syntax
by Juergen Edner 16 Apr '25

16 Apr '25

Hello, as Dovecot 2.4.1 has been published, I started investigation how I need to modify my existing Dovecot 2.3.x configuration, which worked flawlessly the last 5 years. With the help of the doveconf tool I've identified the parameters which need to be modified and I got rid of the error message at the end. Nevertheless, not getting any errors displayed, does not automatically mean, that it has correctly been configured. Here is the initial auth configuration and hopefully the right 2.4 version: Dovecot23: disable_plaintext_auth = yes auth_username_format = %Lu auth_mechanisms = plain login cram-md5 passdb { driver = passwd-file args = username_format=%Lu /path/to/aliases-file } passdb { driver = passwd-file args = scheme=cram-md5 /path/to/cram-md5-file } userdb { driver = passwd } Dovecot24: auth_allow_cleartext = no auth_username_format = %{user | lower} auth_mechanisms = plain login cram-md5 passdb aliases-file { passwd_file_path = /path/to/aliases-file } passdb md5-file { passwd_file_path = /path/to/cram-md5-file } userdb passwd-file { passwd_file_path = /etc/passwd } Here are my questions: - The first passdb configuration (aliases file) initially contained the "args = username_format=%Lu ..." option. Do I still need to convert this to a dedicated "auth_username_format = %{user | lower}" line or is this already covered by the global "auth_username_format" setting? - The second passdb configuration (cram-md5 file) initially contained the "args = scheme=cram-md5 ..." option. I couldn't find any replacement for it. Does this mean the only alternative would be to prefix all passwords in the password file with "{CRAM-MD5}"? - For the third userdb configuration (passwd file) I made use of the "passwd_file_path" parameter. Is this a valid replacement for the original "driver = passwd" entry or have I forgotten anything? BTW, I was curious if ChatGPT could do the job faster than me, but I can say "not yet". It made several errors and had to be corrected one by one but that might change in the future if more and more people are asking for support on this topic. Thanks Juergen -- Mail: juergen(a)eisfair.org

2 2

Stats-writer permission denied
by Ken Wright 15 Apr '25

15 Apr '25

I've got a new Dovecot error (well, new to me, at least)! I ran tail /var/log/mail.err and got the following: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied I checked the file, and it's owned by www-data and the www-data group, with read and write permissions for owner and group... just like I have specified in /etc/dovecot/conf.d/10-master.conf. I can't understand why permission is denied when the file permissions appear to be correct. Can anyone shed any light on this for me? Ubuntu 20.04 Dovecot 2.3.7.2 Ken

3 2

shared folders in dovecot
by Anton Shevtsov 15 Apr '25

15 Apr '25

I used dovecot without shared folders some time ago. All work fine. old dovecot config: |mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox |mail_plugins = acl |protocol imap { mail_plugins = $mail_plugins } | All work fine. Now I want to add shared folder functionality. I am defining namespaces and doing it wrong (maybe) new dovecot config: |mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox |mail_plugins = acl |mail_debug=yes namespace inbox { type = private separator = / prefix = inbox = yes } namespace { type = shared separator = / prefix = shared/%%u/ # wrong #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/shared/%%u |# wrong again location = maildir:%%h/:INDEX=~/%%u |subscriptions = no list = children } protocol imap { mail_plugins = $mail_plugins imap_acl acl } plugin { acl = vfile acl_shared_dict = file:/var/mail/%d/shared-mailboxes.db } | I can set access right for shared folder (screenshot - https://ibb.co/ccxQ63wN) but i can not see shared folder in subscriptions (screenshot - https://ibb.co/PRfpD7X) -- *Anton* I used dovecot without shared folders some time ago. All work fine. old dovecot config: mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox mail_plugins = acl protocol imap { mail_plugins = $mail_plugins } All work fine. Now I want to add shared folder functionality. I am defining namespaces and doing it wrong (maybe) new dovecot config: mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox mail_plugins = acl mail_debug=yes namespace inbox { type = private separator = / prefix = inbox = yes } namespace { type = shared separator = / prefix = shared/%%u/ # wrong #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/ Maildir/shared/%%u # wrong again location = maildir:%%h/:INDEX=~/%%u subscriptions = no list = children } protocol imap { mail_plugins = $mail_plugins imap_acl acl } plugin { acl = vfile acl_shared_dict = file:/var/mail/%d/shared-mailboxes.db } I can set access right for shared folder (screenshot - https://ibb.co/ccxQ63wN) but i can not see shared folder in subscriptions (screenshot - https://ibb.co/ PRfpD7X) -- Anton

3 8

Reindex all e-mails for FTS?
by Alexander Skwar 14 Apr '25

14 Apr '25

Hello How do I reindex all e-mails (for a user or for all users) for FTS? Seems I can find new emails, but not old ones. I tried this: askwar@mail /o/mailcow-dockerized> time sudo docker compose exec dovecot-mailcow doveadm index -A '*' ________________________________________________________ Executed in 1.73 secs fish external usr time 0.00 millis 0.00 millis 0.00 millis sys time 12.90 millis 1.08 millis 11.83 millis As you can see, this was very fast — should it be…? I'd like to be able to search for a text which is in attachments and then I'd need to be able to find the email. This works fine for new emails, but not for old ones. To verify that the attachment would be readable by tika, I took an old e-mail, saved the PDF attachment, and then mailed it to me. Searching for the e-mail will find the new e-mail, but not the old one. The mailbox is not exactly small: askwar@mail /o/mailcow-dockerized> sudo docker compose exec dovecot-mailcow doveadm quota get -u a(a)skwar.xyz Quota name Type Value Limit % Userquota STORAGE 34908222 61685760 56 Userquota MESSAGE 458837 - 0 bd36093fccaa:/# du -sh /var/vmail_index/a\(a)skwar.xyz/ /var/vmail/skwar.xyz/a 2.4G /var/vmail_index/a(a)skwar.xyz/ 27G /var/vmail/skwar.xyz/a I've enabled full text search fts in dovecot with these settings: plugin { fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts = flatcurve fts_tika = http://tika:9998/tika fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=30 fts_languages = en es de fts_tokenizers = generic email-address fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball english-possessive stopwords fts_index_timeout = 300s } askwar@mail /o/mailcow-dockerized> docker --version Docker version 27.3.1, build ce12230 askwar@mail /o/mailcow-dockerized> sudo docker compose exec dovecot-mailcow dovecot --version 2.3.21.1 (d492236fa0) Thanks, Alexander

3 4

Compile failure on git head : lib-settings/settings-history-core.h
by Genes Lists 14 Apr '25

14 Apr '25

Summary: -------- Our daily test builds of git head started failing on Archlinux using gcc 14.2.1+r753+g1cd744a6828f-1 Compile error occurs on git HEAD branch main: commit : beca41cc94dbc81cb2586aab311762bde39bdb11 Possible relevant commit: ------------------------ commit 9dca2f961f83a071d2ff516cd332cd4aa88484dd Build Error: ------------ ... CCLD test-dns-util make[3]: Leaving directory '.. /src/core/src/lib-dns' Making all in lib-settings make[3]: Entering directory '.. /src/lib-settings' GEN settings-history-core.h Line 3: Invalid version sort order make[3]: *** [Makefile:897: settings-history-core.h] Error 1 Thanks for any help. gene (more detail below) config / build details: ---------------------- git fetch --all; git pull git clean -fdx ./autogen.sh ./configure \ --enable-maintainer-mode \ --prefix=/usr \ --sbindir=/usr/bin \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=/usr/lib \ --with-rundir=/run/dovecot \ --with-moduledir=/usr/lib/dovecot/modules \ --disable-static \ --with-pam \ --with-sqlite \ --with-pgsql \ --with-mysql \ --with-ssldir=/etc/ssl \ --with-gssapi \ --with-ldap=yes \ --with-lua=plugin \ --with-bzlib \ --with-lz4 \ --with-zstd \ --with-solr \ --with-sodium \ --with-libcap \ --enable-experimental-mail-utf8 \ --enable-experimental-imap4rev2 Install prefix . : /usr File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : openssl GSSAPI ......... : yes passdbs ........ : static lua (plugin) passwd passwd-file pam ldap sql : -bsdauth userdbs ........ : static lua (plugin) prefetch passwd passwd-file ldap sql CFLAGS ......... : -std=gnu11 -g -O2 -fstack-protector-strong - U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect- branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations - Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno- builtin-strftime -Wstrict-aliasing=2 SYSTEMD ........ : notify - /usr/lib/systemd/system/dovecot.service SQL drivers .... : pgsql mysql sqlite : -cassandra Full text search : solr make clean make -- Gene

2 2

email-address Tokenizer Splits Hyphenated Local-Parts, Causing Inaccurate FTS Search Results
by Daniel 11 Apr '25

11 Apr '25

I’m using Dovecot FTS with the flatcurve backend in a mailcow: dockerized setup. When searching for an email address with a hyphenated local-part (e.g., ma-g(a)example.com) the email-address tokenizer splits the local-part on hyphens, producing tokens like ma, g, and ma-g(a)example.com. This prevents searching for ma-g as a single term. With fts_flatcurve_substring_search = yes, searching for ma-g matches unrelated addresses containing ma (e.g., manager(a)example.com) leading to irrelevant results. Dovecot version: 2.3.21.1 (d492236fa0) Including only relevant part of dovecot config: plugin { fts = flatcurve fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_max_recent_msgs = 999999 fts_tokenizers = generic email-address fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=100 fts_flatcurve_substring_search = yes fts_languages = en es de ru fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball english-possessive stopwords fts_filters_ru = lowercase snowball stopwords fts_index_timeout = 300s } service indexer-worker { process_limit = 12 vsz_limit = 512 MB } Steps to Reproduce: Index an email with ma-g(a)example.com in the From field also index email contains "ma" and "g" in the From field. Check tokenization: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma g example com ma-g(a)example.com Search: doveadm search -u user(a)example.com FROM ma-g Results include manager(a)example.com due to ma matching. Expected Behavior: FROM ma-g should match only emails with ma-g(a)example.com, treating ma-g as a single term or exact local-part. Expected tokens: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma-g ma g example com ma-g(a)example.com Actual Behavior: The tokenizer splits ma-g into ma and g. Substring search matches "ma" or "g" in unrelated addresses (e.g., manager(a)example.com, greg(a)example.com) Without substring search, ma-g matches nothing unless searching the full address. Impact: Searching hyphenated local-parts for short email address local-parts is unreliable, especially for common fragments like ma, flooding results with irrelevant matches. Request: Add a configuration option, such as "fts_tokenizer_email_address_keep_hyphenated = yes|no" (default: no, for compatibility), to include the hyphenated local-part of an email address as an additional token. For example, with "yes", tokenizing "ma-g(a)example.com" would produce "ma-g", "ma", "g", "example", "com", and "ma-g(a)example.com". This allows searches for "FROM ma-g" to match emails with "ma-g(a)example.com" exactly, while preserving "ma" and "g" for substring searches. Consider "yes" as a future default, as including hyphenated local-parts aligns with RFC 5322 and user expectations for precise email searches, especially for common hyphenated addresses like "first-last(a)domain.com". If changing defaults, provide upgrade notes for users relying on the current token set. Is there any workaround to search hyphenated local-parts accurately? Best regards, Daniel Levin

1 0

Enable Full-Text search for attachments?
by Alexander Skwar 10 Apr '25

10 Apr '25

Hello Is it possible to enable a full-text search (FTS) for attachments (PDF, Text, Docx, …) using the open source dovecot server? If so, how would I do that? I've read https://doc.dovecot.org/2.3/configuration_manual/fts/ but that wasn't clear to me. Thanks, Alexander

2 2

2.4.1: oauth2 - Error: lua: db-lua: 'auth_passdb_lookup' is not a function
by Luigi Trovato 10 Apr '25

10 Apr '25

Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi

1 1

2.4 Error: login_trusted_networks: Invalid network '::1'
by James 10 Apr '25

10 Apr '25

Good afternoon, With this line added to the default dovecot.conf: login_trusted_networks = ::1 I get this error: Apr 10 12:41:22 mailhost dovecot: [ID 702911 mail.info] master: Dovecot v2.4.1-4 (7d8c0e5759) starting up for imap, lmtp Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: getaddrinfo() failed: non-recoverable name resolution failure Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: login_trusted_networks: Invalid network '::1': user=<>, rip=2a02:1234:abcd:1::3, lip=2a02:1234:abcd:a::2, session=<sA2GEWsyNfIqAoAQ0BwAAQAAAAAAAACH> Version 2.4.1 Works with 2.3.21.1 and many versions before. It complains with any IPv6 address in login_trusted_networks.

1 0

Multiple namespaces with individual quota values from LDAP
by Andreas Oster 10 Apr '25

10 Apr '25

Hi all, I have successfully managed to get individual user qota for inboxes with values from LDAP working on Dovecot 2.4. I achieved this with the help of a posting from Aki Tuomi: <-- I'd recommend moving the storage_size out of quota "User Quota", since it's then easier to override: quota "User quota" { driver = count ... } quota_storage_size = 10G Aki --> However, in my setup I am using a separate namespace for mail "archiving" on a slower storage. I would like to also restrict the available storage space for users individually in this namespace. To achieve this I ideally would like to fetch the value from a different LDAP attribute. Can this be achieved with dovecot 2.4 ? In version 2.3 this was not a problem. Thank you very much for your kind help. Best regards Andraes

2 2

SQL userdb homedir
by Scott Q. 08 Apr '25

08 Apr '25

I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you

1 0

Per-User quota with LDAP
by Damien Brémont 07 Apr '25

07 Apr '25

Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/home/users_LDAP/user uidNumber=10017 *quotaBytes=32000000* dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B* dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B*#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 *10485760 60* User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https://doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B *Dovecot version:* 2.4.1-4+ubuntu24.04 *dovecot -n:* # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private 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" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve } Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/ home/users_LDAP/user uidNumber=10017 quotaBytes=32000000 dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 10485760 60 User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https:// doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B Dovecot version: 2.4.1-4+ubuntu24.04 dovecot -n: # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private 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" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve }

2 2

Pigeonhole: (Sub-)Folders containing emojis not found
by Alexander Skwar 07 Apr '25

07 Apr '25

Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined:require ["regex","imap4flags","fileinto"];if anyof (address :regex :comparator "i;octet" "from" ".*@(bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop;} There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/ Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined: require ["regex","imap4flags","fileinto"]; if anyof (address :regex :comparator "i;octet" "from" ".*@ (bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop; } There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/

1 1

dovecot-pigeonhole 2.4.1 example config files are deprecated
by Peter Varkoly 05 Apr '25

05 Apr '25

dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90-sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve-extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90- sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve- extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/ imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0

sieve-filter editheader
by Claudinei Luís Bianchini 03 Apr '25

03 Apr '25

Hi, I'm trying to use the editheader extension of sieve, without success. If you can help, I would appreciate it. My setup looks like this: cat 90-sieve.conf plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +body +editheader # with this line it doesn't work either: # sieve_global_extensions = +editheader } dovecot restarted ### # dovecot.sieve # ### # require [ "fileinto", "editheader", "body", "envelope", "imap4flags", "regex", "variables", "relational" ]; # ... sievec dovecot.sieve : dovecot: line 8: error: require command: unknown Sieve capability 'editheader'. dovecot: error: validation failed. sievec(root): Fatal: failed to compile sieve script 'dovecot.sieve' dovecot -n : root@email:/etc/dovecot/conf.d# doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-23-amd64 x86_64 Debian 11.7 # Hostname: email.netcon.com.br auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$ dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } disable_plaintext_auth = no first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_attribute_dict = file:%Lh/dovecot-attributes mail_gid = 2000 mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl mail_log notify mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded- character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl imapsieve_mailbox1_before = file:/var/vmail/sieve/report_spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/var/vmail/sieve/report_ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_url = sieve://127.0.0.1:4190 last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it mail_log_events = delete undelete expunge copy mailbox_create mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject flags mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent quota = dict:user::proxy::quotadict quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u sieve = ~/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_redirects = 30 sieve_pipe_bin_dir = /etc/dovecot/sieve/pipe sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_send_from_recipient = yes } protocols = pop3 imap sieve lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } service stats { fifo_listener stats-mail { mode = 0644 user = vmail } inet_listener { address = 127.0.0.1 port = 24242 } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/imap.netcon.com.br/fullchain.pem ssl_cipher_list = EECDH+CHACHA20:EECDH+AESGCM:EDH+AESGCM:AES256+EECDH ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve } protocol lmtp { lmtp_save_to_detail_mailbox = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve recipient_delimiter = + } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 30 mail_plugins = quota mailbox_alias acl mail_log notify imap_quota imap_acl last_login imap_sieve } protocol pop3 { mail_max_userip_connections = 30 mail_plugins = quota mailbox_alias acl mail_log notify last_login pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } root@email:/etc/dovecot/conf.d# -- Claudinei Luís Bianchini nei(a)netcon.com.br

2 1

Late E-Mails
by Kent Borg 03 Apr '25

03 Apr '25

This morning I noticed e-mail out of sequence. I looked in `/var/log/mail.log` and postfix seems to have handled them correctly, recording the same things for them as any other e-mail, and in sensible sequence with the surrounding timestamps. But in my e-mail client (Thunderbird) some were delayed when viewed as I always do by "Order Received". These are the examples I noticed, when compared to surrounding messages: * 1 delayed ~3-hours, then 4-hours after that… * 7 delayed ~16-hours, followed immediately by… * 2 delayed over 5-hours. Other notes: * Thunderbird was not running at the time that these came in (that computer was asleep). * I am running dsync between two servers and both servers show the same details in Thunderbird (so syncing seems working). * I don't notice any dovecot errors in the log in the vicinity of when the delayed e-mails were processed by postfix, nor when the surrounding e-mails were processed by postfix. * There were no reboots during this period. * I do see some other little timestamp "errors", but these seem to be mailing list messages getting an internal timestamp a couple minutes before the message got delivered to my server (I also will see spam with completely false timestamps, but that it not what is going on here). Does Dovecot sometimes not notice new mail? Thanks, -kb/ / This morning I noticed e-mail out of sequence. I looked in `/var/log/mail.log` and postfix seems to have handled them correctly, recording the same things for them as any other e-mail, and in sensible sequence with the surrounding timestamps. But in my e-mail client (Thunderbird) some were delayed when viewed as I always do by "Order Received". These are the examples I noticed, when compared to surrounding messages: * 1 delayed ~3-hours, then 4-hours after that… * 7 delayed ~16-hours, followed immediately by… * 2 delayed over 5-hours. Other notes: * Thunderbird was not running at the time that these came in (that computer was asleep). * I am running dsync between two servers and both servers show the same details in Thunderbird (so syncing seems working). * I don't notice any dovecot errors in the log in the vicinity of when the delayed e-mails were processed by postfix, nor when the surrounding e- mails were processed by postfix. * There were no reboots during this period. * I do see some other little timestamp "errors", but these seem to be mailing list messages getting an internal timestamp a couple minutes before the message got delivered to my server (I also will see spam with completely false timestamps, but that it not what is going on here). Does Dovecot sometimes not notice new mail? Thanks, -kb

1 0

Issue: Attachment from Later Email Appears on Earlier Email
by postfix_dovecot＠gmx.de 03 Apr '25

03 Apr '25

Hello, Today, I encountered a very strange phenomenon, and I'm not sure if Dovecot is involved: A user sent an email at 11:55 AM with a PDF attachment. When checking their inbox in Outlook, they noticed that this exact PDF had somehow been attached to an email that was originally received at 10:50 AM. I verified the timestamps in the logs, and they are correct. So essentially, the attachment from a later-sent email was appended to an earlier-received email sitting in the inbox-even though the two messages are completely unrelated. I have never seen anything like this before-how is this even possible? Does anyone have any advice? Thanks in advance! Jens Hello, Today, I encountered a very strange phenomenon, and I’m not sure if Dovecot is involved: A user sent an email at 11:55 AM with a PDF attachment. When checking their inbox in Outlook, they noticed that this exact PDF had somehow been attached to an email that was originally received at 10:50 AM. I verified the timestamps in the logs, and they are correct. So essentially, the attachment from a later-sent email was appended to an earlier-received email sitting in the inbox—even though the two messages are completely unrelated. I have never seen anything like this before—how is this even possible? Does anyone have any advice? Thanks in advance! Jens

2 1

lmtp problems with dovecot while seeking to build dovecot, postfix, mailman3, opendkim on Debian 12
by pjbondi＠systemdatabase.com 02 Apr '25

02 Apr '25

Hello to all: I have been trying to integrate and to stand up dovecot, postfix, mailman3 and opendkim. I have been studying the following: - https://www.frontline.ro/en/blog/how-to-configure-opendkim-with-postfix-on-… - https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… - https://www.linuxbabe.com/mail-server/build-email-server-from-scratch-debia… - https://www.linuxbabe.com/mail-server/install-dovecot-imap-server-debian This appears to be the best available coaching, but it would take me weeks to find the time to follow this post: - https://pieterhollander.nl/post/mailserver/ I was trying to place the Maildir outside my Debian 12 virtual machine for easier backup. The directory /Debian-12-dovecot-Maildir is setup as NFS share on my NAS. I can orchestrate a daily backup or an rclone of that to OneDrive or some other cloud target via my NAS. I have these errors: Apr 02 11:17:01 shackleton12 postfix/local[795238]: CA26A2D23: passing <mailman(a)systemdatabase.ca> to transport=lmtp Apr 02 11:17:01 shackleton12 postfix/local[795238]: warning: connect #1 to subsystem private/lmtp: Connection refused Apr 02 11:07:00 shackleton12 systemd[1]: Starting dovecot.service - Dovecot IMAP/POP3 email server... Apr 02 11:07:00 shackleton12 dovecot[789615]: Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp Apr 02 11:07:00 shackleton12 dovecot[789615]: master: Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp Apr 02 11:07:00 shackleton12 dovecot[789615]: Fatal: Failed to start listeners Apr 02 11:07:00 shackleton12 dovecot[789615]: master: Fatal: Failed to start listeners Apr 02 11:07:00 shackleton12 systemd[1]: dovecot.service: Main process exited, code=exited, status=89/n/a Apr 02 11:07:00 shackleton12 systemd[1]: dovecot.service: Failed with result 'exit-code'. Apr 02 11:07:00 shackleton12 systemd[1]: Failed to start dovecot.service - Dovecot IMAP/POP3 email server. postconf -n doveconf -n postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no compatibility_level = 3.6 inet_protocols = ipv4 local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp mailbox_size_limit = 0 mailbox_transport = lmtp:unix:private/dovecot-lmtp masquerade_domains = systemdatabase.ca milter_default_action = accept milter_protocol = 2 mydestination = $myhostname, systemdatabase.ca, localhost.systemdatabase.ca, localhost, systemdatabase.homelinux.com mydomain = systemdatabase.ca myhostname = systemdatabase.ca mynetworks = 127.0.0.0/8 myorigin = systemdatabase.ca non_smtpd_milters = $smtpd_milters owner_request_special = no proxy_interfaces = 192.168.1.8 readme_directory = no recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains relayhost = [smtp.bellnet.ca]:25 smtp_tls_loglevel = 1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_security_level = may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_milters = inet:localhost:8891 smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination permit_inet_interfaces smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination permit_inet_interfaces smtpd_tls_cert_file = /etc/letsencrypt/live/systemdatabase.ca-0001/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/systemdatabase.ca-0001/privkey.pem smtpd_tls_loglevel = 1 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_security_level = may smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtputf8_enable = no transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 doveconf -n # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-32-amd64 x86_64 Debian 12.10 nfs4 # Hostname: shackleton12.systemdatabase.ca auth_mechanisms = plain login auth_username_format = %n mail_location = maildir:/Debian-12-dovecot-Maildir/%d-%u-Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/systemdatabase.ca-0001/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd }

2 1

Bug: dovecot 2.3.21.1 fails to build with recent ICU
by Marcel Telka 01 Apr '25

01 Apr '25

Hi, dovecot 2.3.21.1 fails to build with ICU 77. There are also reports it does not build with ICU 76 for the same reason: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284832 There is no issue when built with ICU 75. The failure is this: /bin/bash ../../libtool --tag=CC --mode=link /usr/gcc/14/bin/gcc -std=gnu99 -m64 -O3 -Wno-incompatible-pointer-types -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/openssl/3/include -no-undefined -m64 -o test-fts-icu test-fts-icu.o fts-icu.lo -licui18n ../lib-test/libtest.la ../lib/liblib.la -lsocket -lnsl -lsendfile libtool: link: /usr/gcc/14/bin/gcc -std=gnu99 -m64 -O3 -Wno-incompatible-pointer-types -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/usr/openssl/3/include -m64 -o test-fts-icu test-fts-icu.o .libs/fts-icu.o -licui18n ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -lsocket -lnsl -lsendfile Undefined first referenced symbol in file ucasemap_utf8ToLower_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_strFromUTF8Lenient_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_errorName_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_cleanup_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ucasemap_close_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_strToUTF8WithSub_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ucasemap_open_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ld: fatal: symbol referencing errors. No output written to test-fts-icu collect2: error: ld returned 1 exit status The workaround is easy: to add -licuuc to LDFLAGS, however it would be great if dovecot builds without any workarounds needed. Thank you. -- +-------------------------------------------+ | Marcel Telka e-mail: marcel(a)telka.sk | | homepage: http://telka.sk/ | +-------------------------------------------+

3 2

Dovecot v2.4.1 released
by Aki Tuomi 31 Mar '25

31 Mar '25

Hi! We arey happy to release Dovecot v2.4.1! Some IMPORTANT things to notice (still): - We have changed the signing key for 2.4 going forward, releases are signed with EF0882079FD4ED32BF8B23B2A1B09EF84EDC5219, which can be found at https://repo.dovecot.org/DOVECOT-REPO-GPG-2.4 and is signed with the previous key. The old key has been renamed to https://repo.dovecot.org/DOVECOT-REPO-GPG-2.3. - New 2.4 packages **are not** compatible with old 2.3 configuration, please carefully review https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html before installing the new packages. - We are happy to provide experimental arm64 support in the form of a Docker image. There are now three kinds of images, latest, latest-dev and latest-root. - The latest docker image is now ran rootless, with UID 1000 as vmail. Please take this into consideration when upgrading. The latest-root image still runs as root. Latest 2.3 image can be used with tag 2.3-latest still We won't be sending separate mail about Pigeonhole anymore as we will release one anyways when we release Dovecot, and Pigeonhole versioning has been changed to match Dovecot versioning. Source codes available at - https://www.dovecot.org/releases/2.4/dovecot-2.4.1.tar.gz - https://www.dovecot.org/releases/2.4/dovecot-2.4.1.tar.gz.sig - https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.1.tar.gz - https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.1.tar.gz… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Kind regards, Aki Tuomi Open-Xchange oy --- Dovecot Core NEWS ----------------- * auth: Change unix_listener/auth-userdb/group = $SET:default_internal_group This change needs dovecot_config_version=2.4.1. * auth: lua - Remove support for single string result. * imap: Unconditionally advertise SPECIAL-USE capability. * lib-dcrypt: Install dcrypt_openssl.so into dovecot modules directory. * lib-master: For glibc, default MALLOC_MMAP_THRESHOLD_=131072. * lib-storage: Change default mail_cache_fields to: hdr.date hdr.subject hdr.from hdr.sender hdr.reply-to hdr.to hdr.cc hdr.bcc hdr.in-reply-to hdr.message-id date.received size.virtual imap.bodystructure mime.parts hdr.references hdr.importance hdr.x-priority hdr.x-open-xchange-share-url pop3.uidl pop3.order. This change needs dovecot_config_version=2.4.1. * lib-var-expand: Use moduledir instead of pkglibdir for crypt. * lmtp: Change the default lmtp_user_concurrency_limit to 10. This change needs dovecot_config_version=2.4.1. * lmtp: Change the default service_restart_request_count to 1. This change needs dovecot_config_version=2.4.1. + auth: Allow configuring passdb/userdb sql to use auth-workers. + config: Add default group @mailbox_defaults = english. + config: Improve "Unknown setting" error with more details and suggestions. + doveconf: Add -U parameter to ignore unknown settings in config file. + fts-flatcurve: Support lock files in VOLATILEDIR. + imap-acl: Add support for the IMAP LIST-MYRIGHTS capability (RFC 8440). + imap-client: Support ANONYMOUS authentication. + imap: Implement support for the REPLACE capability. - auth: ldap - Passdb fields were ignored with passdb_ldap_bind_userdn=yes. - auth: lua - Fix error result handling in lua passdb/userdb. - auth: oauth2 - When building oauth2 failure reply, memory would leak. - config: local_name handling would work wrong with multiple names and wildcards. - fts-flatcurve: A potential crash could occur when searching virtual mailboxes. Fixes: Panic: file fts-search.c: line 87 (level_scores_add_vuids): assertion failed: (array_count(&vuids_arr) == array_count(&br->scores)) - fts-flatcurve: Maybe queries were done wrong. - fts-flatcurve: Non-selectable mailboxes were not ignored when doing optimize/rescan. - fts-flatcurve: Signal 11 crash could happen with fts rescan. - fts: Fix crash caused by event object lifecycle mishandling. - imap-hibernate: Client counters would get reset on unhibernation, affecting imap_logout_format variables. - imap: Crash would occur with Maildir when trying to send INPROGRESS during mailbox syncing. - ldap: Dovecot could not be compiled without LDAP. - lib-dcrypt: Output stream encryption can cause assert crash if attempting to encrypt over 64 GiB of data with GCM. This is still not supported with GCM, but it fails better. - lib-http: HTTP client context memory usage was increasing. - lib-http: Pipeline corruption could happen after 100 Continue response. - lib-settings: Variable expansion initialization could crash with Panic: file settings.c: line 1560 (settings_var_expand_init_add): assertion failed: (I_MAX(num_tables, num_provs) == num_ctx) - lib-smtp: Pipelining initial SASL response after AUTH was broken. - lib-var-expand: If filter failed, memory leak would occur. - lib-var-expand: Older bison versions did not have error symbol for handling causing unexpected behaviour on the parser on error conditions. - quota: Quota calculations had minor bugs causing small errors. Pigeonhole NEWS --------------- - global: Fix settings handling bugs. Especially %variables weren't working in various settings. - ldap: Pigeonhole could not be built without LDAP.

5 8

Bug: Inconsistency in configuration between various clients.
by Louis Schmitz 27 Mar '25

27 Mar '25

We found out about this through a misconfiguration in our web panel. In the main config file the following line includes a subdirectory; !include conf.d/*.conf The web panel created the following two relevant configuration snippets in /etc/dovecot/conf.d/ 11-plesk-security-ssl.conf > ssl_dh=</opt/psa/etc/dhparams2048.pem > ssl_min_protocol=TLSv1.2 > ssl_cipher_list=EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EECDH+SHA256+AES128:EECDH+SHA384+AES256:EECDH+SHA1+AES128:EECDH+SHA1+AES256:EECDH+HIGH:AESGCM+AES128:AESGCM+AES256:CHACHA20:SHA256+AES128:SHA256+AES256:SHA1+AES128:SHA1+AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!KRB5:!aECDH:!kDH:!EDH > ssl_prefer_server_ciphers=yes > ssl=yes > ssl_cert=</etc/dovecot/private/dovecot.pem > ssl_key=</etc/dovecot/private/dovecot.pem This sets a server wide certificate as being the cert in /etc/dovecot/private/dovecot.pem. Let's say our main server domain is 'acme.com' for example, its 'hostname' (linux hostname) is for example 's02.acme.com'. Then it would also create 14-plesk-sni-mail.acme.com.conf, containing something akin to: > local_name mail.acme.com { > ssl_cert = </opt/psa/var/certificates/scf7b9lcY > ssl_key = </opt/psa/var/certificates/scf7b9lcY > } These point to the ssl cert and key configured for that specific vhost (not the entire server), which can be different from that configured for the server. When some clients connected to the server (connecting to mail.acme.com) it would serve the /etc/dovecot/private/dovecot.pem certificate. This was renewed and the clients would work without issue. Other clients, however, used the certificate at /opt/psa/var/certificates/scf7b9lcY. This certificate is supposed to be the same, but expired and wasn't renewed along with the other one. This was tricky to figure out since the problems did not appear on our side, only when looking at a client. Once I went around the panel GUI and into the actual dovecot configuration files I found the culprit(s). I think, but do not know, that it could be related to which IP protocol (V4 or V6) is used to connect to dovecot. All clients who failed happened to connect over V6. The cases that did not used V4. This seems entirely unrelated and strange behaviour that must be a bug of some kind. Either both should use the one certificate, or the other, or there should be an error or warning if local_name includes a variant subdomain of the server name, the latter in addition to making a consistent choice. It appears that sometimes the first relevant ssl_key and ssl_cert are used, and other times the second when the option is included twice in the configuration, pointing to different matching certificates/keys. It's not apparently a race condition: The behaviour is very consistent for the same client connecting.

1 0