- dovecot - dovecot.org

oath-toolkit pam authentication with dovecot
by "Tóth Attila" 04 Apr '26

04 Apr '26

Anybody has experience in deploying oath-toolkit totp authentication for dovecot? It works for ssh in a challenge response fashion, but I have concernes against concatenating the password with the totp digits, because I have difficulties even with su+oath_toolkit... Thx: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057

1 0

Bug report: filter `default` in LDAP context does not suppress error logging
by Johannes Nohl 03 Apr '26

03 Apr '26

Bug report: Expanding variables with filter `default` in LDAP context does not suppress error logging if LDAP attribute is missing. Expected behaviour: Missing LDAP attribute does not throw an error. Example `nologin = %{ldap:missingAttribute | default}` Details: Please note: The missing attribute is called `shadowInactive` in reality. There might be another issue, the field nologin is boolean and set true if any value is assigned -- while default without parameter returns empty (thus, you cannot use default with nologin without workaround). The intended behaviour is documented clearly, however due to a bug in rendering you need to look into the doc sources (my PR for that was accepted already: https://doc.dovecot.org/2.4.2/core/config/auth/databases/ldap.html#ldap-spe… https://github.com/dovecot/documentation/pull/1478#pullrequestreview-403461… Full context: passdb ldap { driver = ldap ldap_filter = (&(objectClass=posixAccount)(mail=%{user})) fields { user = %{ldap:uid} nologin = %{ldap:shadowInactive | default} reason = The account for this email address is disabled. } } The same error was reported already a year ago, although among others, see point 4: https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/TLJ2O… Please excuse my first attempt of 31-03-2026. It was unreadable. Aki already tried to help but was - I guess - distracted from the main point. I found a workaround for the missing attribute translation to boolean fields (if someone is interested) https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/67Z4C… I tested with dovecot 2.4.2 and 2.4.3 (openSUSE repos) against local LDAP. The check for disabled users throws permanently errors in the log file, whenever the user is missing the ldap attribute for disabled. Thus, for each login of all enabled users (you will probably agree that this not acceptable). This results in the following log line: 2026-03-31T00:46:31.102690+02:00 mailserver dovecot: auth(test,ipv4,sasl:plain)<YE81n0VOVuofEeSD>: Error: ldap: auth_passdb_post settings: Failed to parse configuration: Failed to expand passdb_fields/nologin setting variables: ldap: No such attribute 'shadowinactive' Thank you Johannes -- Johannes Nohl postmaster(a)i-t-cloud.de

1 1

enabling fts_flatcurve on debian
by Stefan G. Weichinger 03 Apr '26

03 Apr '26

Which xapian-related packages do I need? I have issues enabling the plugin ... pls advise

2 6

2.4 upgrade : INBOX does not exist
by Stefan G. Weichinger 02 Apr '26

02 Apr '26

Today I upgraded a server at a customer. I modified the config I had built over the last week, with the help of this list. So far nearly everything works, but thunderbird complains about non-existing mailboxes like INBOX. But we can access it, it's a bit strange. In the filesystem it looks like: # ls -la /home/vmail/our.tld/user\(a)our.tld/ insgesamt 7096 drwx------ 69 vmail vmail 4096 2. Apr 19:00 . drwx------ 129 vmail vmail 12288 2. Apr 18:56 .. drwx------ 5 vmail vmail 4096 8. Jun 2021 .Administrator drwx------ 5 vmail vmail 4096 2. Apr 18:40 .Administrator.Archiv drwx------ 5 vmail vmail 4096 2. Apr 18:40 '.Administrator.Domainwechsel AquaCC' drwx------ 5 vmail vmail 4096 11. Mai 2025 .Archives drwx------ 5 vmail vmail 4096 2. Apr 18:40 .Archives.2001 drwx------ 5 vmail vmail 4096 2. Apr 18:40 .Archives.2002 drwx------ 5 vmail vmail 4096 2. Apr 18:40 .Archives.2003 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2004 drwx------ 5 vmail vmail 4096 2. Apr 18:40 .Archives.2005 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2006 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2007 drwx------ 5 vmail vmail 4096 10. Feb 18:17 .Archives.2008 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2009 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2010 drwx------ 5 vmail vmail 4096 10. Feb 18:10 .Archives.2011 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2012 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2013 drwx------ 5 vmail vmail 4096 10. Feb 18:09 .Archives.2014 drwx------ 5 vmail vmail 4096 12. Aug 2024 .Archives.2015 drwx------ 5 vmail vmail 4096 2. Apr 17:51 .Archives.2016 drwx------ 5 vmail vmail 4096 11. Feb 11:57 .Archives.2017 drwx------ 5 vmail vmail 4096 10. Jun 2025 .Archives.2018 drwx------ 5 vmail vmail 4096 11. Feb 11:57 .Archives.2019 drwx------ 5 vmail vmail 4096 10. Feb 18:23 .Archives.2020 drwx------ 5 vmail vmail 4096 1. Apr 20:18 .Archives.2021 drwx------ 5 vmail vmail 4096 30. Mär 09:37 .Archives.2022 drwx------ 5 vmail vmail 4096 1. Apr 20:18 .Archives.2023 drwx------ 5 vmail vmail 4096 1. Apr 20:18 .Archives.2024 drwx------ 5 vmail vmail 4096 2. Apr 17:48 .Archives.2025 drwx------ 5 vmail vmail 4096 2. Apr 17:59 .Archives.2026 drwx------ 2 vmail vmail 323584 2. Apr 19:00 cur -rw------- 1 vmail vmail 0 2. Aug 2021 dovecot-acl-list -rw------- 1 vmail vmail 70712 2. Apr 18:37 dovecot.index -rw------- 1 vmail vmail 6266860 2. Apr 19:01 dovecot.index.cache -rw------- 1 vmail vmail 32160 2. Apr 19:00 dovecot.index.log -rw------- 1 vmail vmail 46940 2. Apr 06:20 dovecot.index.log.2 -rw------- 1 vmail vmail 91 18. Aug 2020 dovecot-keywords -rw------- 1 vmail vmail 65 2. Apr 18:37 .dovecot.lda-dupes drwx------ 5 vmail vmail 4096 2. Apr 18:37 .dovecot.lda-dupes.locks -rw------- 1 vmail vmail 6504 2. Apr 18:49 dovecot.list.index -rw------- 1 vmail vmail 3356 2. Apr 19:02 dovecot.list.index.log -rw------- 1 vmail vmail 2904 7. Jän 13:53 dovecot.mailbox.log -rw------- 1 vmail vmail 186894 2. Apr 18:59 dovecot-uidlist -rw------- 1 vmail vmail 8 7. Jän 13:53 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 21. Apr 2020 dovecot-uidvalidity.5e9efc52 drwx------ 5 vmail vmail 4096 2. Apr 12:02 .Drafts drwx------ 5 vmail vmail 4096 12. Jun 2025 '.Entw&APw-rfe' drwx------ 5 vmail vmail 4096 6. Mai 2020 .Gesendet drwx------ 5 vmail vmail 4096 2. Apr 18:22 .INBOX.Administrator drwx------ 5 vmail vmail 4096 2. Apr 18:21 .INBOX.Alerts [..] We have mail_home = /home/vmail/%{user | domain}/%{user} I tried mail_home = /home/vmail/%{user | domain}/%{user | username} but that breaks things completely. In 2.3 we had these namespaces: namespace { type = private separator = / prefix = #location defaults to mail_location. inbox = yes } namespace { type = public separator = / prefix = Oeffentlich/ location = maildir:/home/vmail/oeffentlich subscriptions = yes } I tried "prefix = INBOX/" ... not good. I share the config, a little bit anonymized, acls removed ... # doveconf -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.74+deb13+1-amd64 x86_64 Debian 13.4 # Hostname: xxxx dovecot_config_version = 2.4.1 auth_allow_weak_schemes = yes auth_cache_size = 4M auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_process_limit = 300 dovecot_storage_version = 2.4.0 import_environment { CORE_ERROR = %{env:CORE_ERROR} CORE_OUTOFMEM = %{env:CORE_OUTOFMEM} LISTEN_FDS = %{env:LISTEN_FDS} LISTEN_PID = %{env:LISTEN_PID} MALLOC_MMAP_THRESHOLD_ = 131072 NOTIFY_SOCKET = %{env:NOTIFY_SOCKET} PATH = %{env:PATH} TZ = :/etc/localtime } info_log_path = /var/log/dovecot.info listen = * [::] log_path = /var/log/dovecot.log mail_debug = yes mail_driver = maildir mail_gid = 5000 mail_home = /home/vmail/%{user | domain}/%{user} mail_path = ~ mail_plugins { acl = yes notify = yes quota = no } mail_uid = 5000 protocols = imap sieve lmtp 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 editheader = yes mboxmetadata = yes servermetadata = yes spamtest = yes spamtestplus = yes virustest = yes } sieve_global_extensions { vnd.dovecot.debug = yes vnd.dovecot.environment = yes vnd.dovecot.pipe = yes } sieve_pipe_bin_dir = /usr/lib/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_score_max_value = 15 sieve_spamtest_status_header = X-Spamd-Result: .*? \[([[:digit:]]+\.[[:digit:]]+) / [[:digit:]]+\.[[:digit:]]+\]; sql_driver = mysql ssl = required verbose_proctitle = yes mysql /var/run/mysqld/mysqld.sock { dbname = postfix_db password = # hidden, use -P to show it user = postfix_user } passdb sql { default_password_scheme = MD5-CRYPT query = SELECT username as user, password FROM mailbox WHERE ((username = '%{user | username}(a)domain1.at') OR (username = '%{user | username}(a)domain2.at')) AND active = '1' } userdb sql { iterate_query = SELECT userid AS username, domain FROM users query = SELECT username as user FROM mailbox WHERE ((username = '%{user | username}(a)domain1.at') OR (username = '%{user | username}(a)domain2.at') ) AND active = '1' } namespace inbox { inbox = yes prefix = separator = / type = private } namespace oeffentlich { mail_path = /home/vmail/oeffentlich prefix = Oeffentlich/ separator = / subscriptions = yes type = public mailbox Oeffentlich { acl [DELETED for now] } service imap-login { process_min_avail = 8 inet_listener imap { port = 0 ssl = no listen = } inet_listener imaps { port = 993 ssl = yes listen = } } service lmtp { extra_groups = $SET:default_internal_group user = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service imap { } service auth { client_limit = 1200 user = root unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0660 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/pfsense/cloud_imap_mail_smtp_LE_cert.fullchain key_file = /etc/letsencrypt/pfsense/cloud_imap_mail_smtp_LE_cert.key } protocol lda { mail_plugins = sieve } protocol imap { imap_idle_notify_interval = 29 mins mail_max_userip_connections = 50 mail_plugins { imap_acl = yes imap_quota = no imap_sieve = yes } } protocol lmtp { mail_plugins = sieve postmaster_address = logs(a)xunil.at } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol sieve { 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 ihave } sieve_script personal { active_path = /home/vmail/%{user | domain}/%{user}/sieve/scripts/.dovecot.sieve driver = file path = /home/vmail/%{user | domain}/%{user}/sieve/scripts } sieve_script before-0 { driver = file path = /usr/lib/dovecot/sieve/global-spam.sieve type = before } service anvil { unix_listener anvil { group = $SET:default_internal_group mode = 0660 } } I assume I am not far from full success, I'd just like to get rid of these errors because tomorrow dozens of users will access their mailboxes ... Thanks for any pointers!

1 1

BUG-Report: mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) third attempt!
by Klaus Tachtler 02 Apr '26

02 Apr '26

Hello everyone, Problem info: ============ An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: ================== 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log > 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) > 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: =============== OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: > 45 sql_driver = mysql > 46 > 47 mysql db.idmz.tachtler.net { > 48 host = db.idmz.tachtler.net > 49 port = 3306 > 50 user = postfixuser > 51 password = secret > 52 dbname = postfix > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA > 58 } WITHOUT the following line, a database connections is possible and works as expected: > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

3 17

decode2text
by Joan Moreau 02 Apr '26

02 Apr '26

Hi I can't find decode2text.sh in the git Where is it maintained ? Thank you Joan Hi I can't find decode2text.sh in the git Where is it maintained ? Thank you Joan

2 1

Error: sieve: fail2ban: line 23: read(<lmtp DATA local>) failed: Seeking past EOF by 2364 bytes
by Graham Cobb 01 Apr '26

01 Apr '26

Hi, dovecot is crashing for me while doing sieve processing for messages received via lmtp. This is reproducible, and seems to hit every message which runs a particular sieve script. Any thoughts or help would be appreciated! The error is: Error: sieve: fail2ban: line 23: read(<lmtp DATA local>) failed: Seeking past EOF by 2364 bytes Note: the number of bytes is always one of: 2169, 2272, 2259, 2364. I have many of these. I cannot see how the "Seeking past EOF" error can be caused by a bug in my sieve script. But please let me know if it can! Background: I have (and have had for many years) a complex set of sieve scripts for controlling my incoming email. They have worked fine for all that time. However, recently (ish), processing which uses a particular script is crashing dovecot. The actual log extract is below. The sieve script line 23, mentioned in the error report, is a large "if anyof (" statement containing many clauses like: body :raw :regex "country:[[:space:]]+KR", I can provide the full sieve script if required. This is what I see in the dovecot log (note: I reformatted the backtrace to make it easier to read. I also changed all my server names): Mar 29 03:03:52 SERVER dovecot-HOST: lmtp(4008073): Connect from local Mar 29 03:03:52 SERVER dovecot-HOST: lmtp(cobb)<4008073><PiAQHoiIyGmJKD0Ay7SJiA>: Error: sieve: fail2ban: line 23: read(<lmtp DATA local>) failed: Seeking past EOF by 2364 bytes Mar 29 03:03:52 SERVER dovecot-HOST: lmtp(cobb)<4008073><PiAQHoiIyGmJKD0Ay7SJiA>: Error: sieve: Execution of script 'auto:personal/.dovecot' was aborted due to temporary failure (user logfile /home/cobb/.dovecot.sieve.log may reveal additional details) Mar 29 03:03:52 SERVER dovecot-HOST: lmtp(cobb)<4008073><PiAQHoiIyGmJKD0Ay7SJiA>: Panic: file istream-concat.c: line 27 (i_stream_concat_close): assertion failed: (cstream->cur_input == cstream->input[cstream->cur_idx]) Mar 29 03:03:52 SERVER dovecot-HOST: lmtp(cobb)<4008073><PiAQHoiIyGmJKD0Ay7SJiA>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 i_panic[0x7f41540655e6] -> #4 [unw_get_proc_name() failed: -10] -> #5 io_stream_unref[0x7f415413c120] -> #6 i_stream_unref[0x7f4154145c30] -> #7 index_storage_mailbox_close[0x7f4154383e70] -> #8 mailbox_close[0x7f41542fd9e0] -> #9 mailbox_free[0x7f4154302ab0] -> #10 lmtp_local_deinit[0x55dfa9c4e320] -> #11 client_state_reset[0x55dfa9c4f0d0] -> #12 smtp_server_transaction_free[0x7f4154091880] -> #13 smtp_server_connection_reset_state[0x7f4154093c90] -> #14 smtp_server_command_call_hooks[0x7f415408be60] -> #15 smtp_server_command_send_replies[0x7f4154090050] -> #16 [unw_get_proc_name() failed: -10] -> #17 [unw_get_proc_name() failed: -10] -> #18 io_loop_call_io[0x7f4154151710] -> #19 io_loop_handler_run_internal[0x7f41541534b0] -> #20 io_loop_handler_run[0x7f4154153640] -> #21 io_loop_run[0x7f4154153820] -> #22 master_service_run[0x7f41540a6330] -> #23 main[0x55dfa9c4a260] -> #24 __libc_start_call_main[0x7f4153e32c30] -> #25 __libc_start_main_alias_2[0x7f4153e32ce0] -> #26 _start[0x55dfa9c4a470] Mar 29 03:03:54 SERVER dovecot-HOST: lmtp(cobb)<4008073><PiAQHoiIyGmJKD0Ay7SJiA>: Fatal: master: service(lmtp): child 4008073 killed with signal 6 (core dumped) Mar 29 03:04:05 SERVER postfix/lmtp[4008072]: 005083DC75D: to=<MYADDRESS@MYDOMAIN>, orig_to=<ANOTHER@ANOTHERDOMAIN>, relay=SERVERNAME[private/dovecot-lmtp], delay=1740676, delays=1740674/0.25/0.04/1.5, dsn=4.4.2, status=deferred (lost connection with SERVERNAME[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) The only message in .dovecot.sieve.log is: fail2ban: line 23: error: failed to read input message: internal error occurred: refer to server log for more information. [2026-04-01 18:54:13]. Thanks in advance for any thoughts! Graham

2 1

Broken table in dovecot-pw manual
by Célestin Matte 01 Apr '26

01 Apr '26

Hello, I just noticed while reading the dovecot-pw man on Arch Linux that the table in the -r option is broken (missing newline between row): | Scheme | Minimum | Maximum | Default | | ------ | ------- | ------- | ------- | | BLF-CRYPT | 4 | 31 | 5 | | SHA256-CRYPT | 1000 | 999999999 | 5000 | | SHA512-CRYPT | 1000 | 999999999 | 5000 | Regards, -- Célestin Matte

2 1

dovecot.list.index.log owned by root: why?
by Stefan G. Weichinger 01 Apr '26

01 Apr '26

I use these sql-queries to let all mailboxes be accessed by the uid=1001: passdb sql { default_password_scheme = MD5-CRYPT passdb_sql_query = SELECT username as user, password, \ '/home/vmail/%{user | domain }/%{user}' as userdb_home, 'maildir:/home/vmail/%{user | domain }/%{user}' as userdb_mail,\ 1001 as userdb_uid, 1001 as userdb_gid FROM mailbox WHERE username = '%{user}' AND active = '1' } userdb prefetch { } ( I assume this following query isn't used then anymore) userdb sql { userdb_sql_query = SELECT username as user, password, \ '/home/vmail/%{user | domain }/%{user}' as userdb_home, 'maildir:/home/vmail/%{user | domain }/%{user}' as userdb_mail,\ 1001 as userdb_uid, 1001 as userdb_gid \ FROM mailbox WHERE username = '%{user}' AND active = '1' userdb_sql_iterate_query = SELECT userid AS username, domain FROM users } id 1001 uid=1001(vmail) gid=1001(vmail) groups=1001(vmail),118(dovecot) I get errors like: Apr 01 11:43:05 imap(logs(a)xunil.at)<1564491><N8oZ6WJO/uwgAQRwHwsMRX9ul+gRMpfY>: Error: open(/home/vmail/xunil.at/logs(a)xunil.at/dovecot.list.index.log) failed: Permission denied (euid=1001(vmail) egid=1001(vmail) missing +r perm: /home/vmail/xunil.at/logs(a)xunil.at/dovecot.list.index.log) ls -l /home/vmail/xunil.at/logs(a)xunil.at/ total 944 drwx------ 2 vmail vmail 622592 Apr 1 11:43 cur -rw------- 1 vmail vmail 0 Jul 30 2021 dovecot-acl-list -rw------- 1 vmail vmail 3304 Apr 1 11:35 dovecot.index -rw------- 1 vmail vmail 202444 Apr 1 11:43 dovecot.index.cache -rw------- 1 vmail vmail 2908 Apr 1 11:43 dovecot.index.log -rw------- 1 vmail vmail 32892 Apr 1 11:35 dovecot.index.log.2 -rw------- 1 vmail vmail 91 Feb 9 2024 dovecot-keywords -rw------- 1 root root 5744 Apr 1 10:30 dovecot.list.index -rw------- 1 root root 480 Apr 1 10:52 dovecot.list.index.log [..] Why do these 2 files get owned by root now ... ? All files below "/home/vmail" should be owned by vmail:vmail I ran chown, and chgrp, sure .. but the errors return. How to fix this? Thanks in advance!

2 5

cannot get IOS or MacOSX to connect to dovecot:995 since upgraded Mac or iPhone
by Bill Scheding 01 Apr '26

01 Apr '26

Versions: [wls(a)www.wls.org]$ uname -a Linux www.wls.org 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [wls(a)ww.wls.org]$ dovecot --version 2.2.36 (1f10bfa63) My Certs: Testing cert dovecot.key unable to load certificate 139668060415888:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:707:Expecting: TRUSTED CERTIFICATE lrwxrwxrwx 1 root root 21 Mar 25 15:44 dovecot.key -> dovecot.key.old_sep_2 Testing chain dovecot.pem SHA1 Fingerprint=4A:29:34:1D:D5:9C:67:59:FA:31:7E:FF:F4:53:F8:DB:25:73:15:07 subject= /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com issuer= /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com serial=C8AA4C688A3F2638 b5bd7939 notBefore=Sep 2 20:17:33 2018 GMT notAfter=Sep 2 20:17:33 2019 GMT lrwxrwxrwx 1 root root 21 Mar 25 15:44 dovecot.pem -> dovecot.crt.old_sep_2 New Certs: Testing key ca.key.3.13.4 RSA key ok lrwxrwxrwx 1 root root 31 Mar 13 14:14 ca.key.3.13.4 -> ../../tls/private/ca.key.3.13.4 Testing chain ca.crt.3.13.4 SHA1 Fingerprint=79:69:88:2A:E0:BF:58:A8:21:E3:88:12:8D:45:20:4F:FD:68:33:63 subject= /C=XX/ST= /L= /O= /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com issuer= /C=XX/ST= /L= /O= /OU=IMAP server/CN=imap.example.com/emailAddress=postmaster@example.com serial=B912DD19FEDC441C 402b4e2a notBefore=Mar 13 20:02:58 2026 GMT notAfter=Mar 13 20:02:58 2027 GMT lrwxrwxrwx 1 root root 29 Mar 13 14:13 ca.crt.3.13.4 -> ../../tls/certs/ca.crt.3.13.4 They install OK, dovecot starts; but iPhone and mac cannot connect to pop3 Cannot get my iPhone or Mac to accept new certs from lets encrypt, et. al. This is a new problem, started recently. My existing cert expired in 2016 William

2 1

Variable expansion syntax: Filter "default" throws error (unwanted)
by Johannes Nohl 01 Apr '26

01 Apr '26

I am using dovecot 2.4.2 (almost) with new config language and I have a working configuration. However, the check for disabled users throws permanently errors in the log file, whenever a user is missing the ldap attribute for disabled. This is - in my view - due to a misfunction of Filter "default". passdb ldap { driver = ldap ldap_bind = yes ldap_filter = (&(|(objectClass=posixAccount)(objectClass=mailAccount))(uid=%{user})) fields { user = %{ldap:uid} nologin = %{ldap:shadowInactive | default(null)} reason = The account for this email address is disabled. } } This results in the following log line: 2026-03-31T00:46:31.102690+02:00 mailserver dovecot: auth(test,ipv4,sasl:plain)<YE81n0VOVuofEeSD>: Error: ldap: auth_passdb_post settings: Failed to parse configuration: Failed to expand passdb_fields/nologin setting variables: ldap: No such attribute 'shadowinactive' The right behaviour would be no logging on login success. Because the Filter "default" is intended to suppress any errors ("When value is missing or empty, you can use the default filter to provide value. Missing variables will cause errors and must be negated with default. This does not apply to all providers, some providers return empty when value is missing."). https://doc.dovecot.org/2.4.2/core/settings/variables.html#variable-expansi… As you may have seen I had to borrow null-value from sql db config also to make nologin ignoring a non present attribute. This is undocumented obviously. Instead, a non-working tip is provided ("Changed: 2.4.0 Extra fields can now also be set to empty string, "). However, the following does not work: "nologin = {ldap:shadowinactive | default("")}". https://doc.dovecot.org/2.4.2/core/settings/variables.html Also, the documentation is missing/hiding the part which explains that "default()" can be used to avoid error logs. PR regarding the documentation source is sent already. See "Fails if the attribute is not present, unless the ` <missing part>" https://doc.dovecot.org/2.4.0/core/config/auth/databases/ldap.html#ldap-spe… Is there another way to verify if account is disabled? -- Johannes Nohl postmaster i-t-cloud -- Johannes Nohl postmaster(a)i-t-cloud.de I am using dovecot 2.4.2 (almost) with new config language and I have a working configuration. However, the check for disabled users throws permanently errors in the log file, whenever a user is missing the ldap attribute for disabled. This is - in my view - due to a misfunction of Filter "default". passdb ldap { driver = ldap ldap_bind = yes ldap_filter = (&(|(objectClass=posixAccount)(objectClass=mailAccount))(uid=%{user})) fields { user = %{ldap:uid} nologin = %{ldap:shadowInactive | default(null)} reason = The account for this email address is disabled. } } This results in the following log line: *2026-03-31T00:46:31.102690+02:00 mailserver dovecot: auth(test,ipv4,sasl:plain)<YE81n0VOVuofEeSD>: Error: ldap: auth_passdb_post settings: Failed to parse configuration: Failed to expand passdb_fields/nologin setting variables: ldap: No such attribute 'shadowinactive' The right behaviour would be no logging on login success. Because the Filter "default" is intended to suppress any errors ("When value is missing or empty, you can use the default filter to provide value. Missing variables will cause errors and must be negated with default. This does not apply to all providers, some providers return empty when value is missing."). https://doc.dovecot.org/2.4.2/core/settings/variables.html#variable-expansi… As you may have seen I had to borrow null-value from sql db config also to make nologin ignoring a non present attribute. This is undocumented obviously. Instead, a non-working tip is provided ("Changed: 2.4.0 Extra fields can now also be set to empty string, "). However, the following does not work: "nologin = {ldap:shadowinactive | default("")}". https://doc.dovecot.org/2.4.2/core/settings/variables.html Also, the documentation is missing/hiding the part which explains that "default()" can be used to avoid error logs. PR regarding the documentation source is sent already. See "Fails if the attribute is not present, unless the ` <missing part>" https://doc.dovecot.org/2.4.0/core/config/auth/databases/ldap.html#ldap-spe… Is there another way to verify if account is disabled? -- Johannes Nohl postmaster i-t-cloud -- Johannes Nohl postmaster(a)i-t-cloud.de

2 1

[BUG] 2.4.3 SIGSEGV in fts_solr
by Nick O'Connor 01 Apr '26

01 Apr '26

Dovecot 2.4.3 crashes with SIGSEGV in indexer-worker and lmtp during FTS Solr indexing. The crash is a use-after-free triggered when the HTTP client does a DNS lookup for the Solr host. Environment: - Dovecot 2.4.3 (Alpine 3.23 / musl) - Linux x86_64 - Filesystem: maildir on ZFS - Solr 10.0.0 - fts_solr plugin with DNS-based Solr URL dovecot -n: # 2.4.3 (e278b1e09b): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.3 (0bf9ee48) # OS: Linux 6.12.74+deb13+1-amd64 x86_64 dovecot_config_version = 2.4.0 auth_mechanisms = oauthbearer xoauth2 dovecot_storage_version = 2.4.0 fts_autoindex = yes fts_search_add_missing = yes mail_always_cache_fields = date.save mail_driver = maildir mail_plugins { fts = yes fts_solr = yes } protocols = imap lmtp sieve ssl = required fts solr { url = http://solr.example.com/solr/dovecot } (LDAP userdb/passdb, pigeonhole sieve, imapsieve for spam learning, and oauth2 passdb omitted) How to reproduce: The crash occurs in the indexer-worker when processing multiple user mailboxes sequentially for FTS indexing, using a DNS hostname for the Solr URL. Steps: 1. Configure fts_solr with a DNS-based URL (not an IP address) 2. Have the indexer-worker process mailboxes for more than one user (e.g. fts_autoindex = yes with multiple users, or manual doveadm index -A) 3. The first user session completes successfully. On the second user session, the indexer-worker crashes with SIGSEGV during the DNS lookup for the Solr host. Reproduces reliably on musl (Alpine) due to aggressive memory reuse. Likely also affects glibc but may not crash immediately due to delayed reuse of freed memory. Root cause: The solr_http_client singleton outlives the user session that created it. Its event chain holds a ref on the mail_storage_service_user event, keeping it alive after the user is freed. The SETTINGS_EVENT_INSTANCE on that event still points to the already-freed settings_instance. On the next user session, dns_lookup() walks the stale event chain and dereferences the dangling pointer in settings_instance_get(). Stack trace (from core dump, debug build with musl-dbg): #0 strlen(s=0x415641d189485741) -- SIGSEGV, freed/reused memory #1 p_strdup() strfuncs.c:56 #2 event_add_str(key="protocol", value=...) lib-event.c:1099 #3 settings_instance_get() settings.c:2521 #4 settings_get_real() settings.c:2706 #5 settings_get_full() settings.c:2915 #6 settings_get(dns_client_setting_parser_info) settings.c:2976 #7 dns_client_init() dns-lookup.c:465 #8 dns_client_init_handle_failure() dns-lookup.c:317 #9 dns_lookup("solr.example.com") dns-lookup.c:337 #10 http_client_host_shared_lookup() http-client-host.c:166 #11 http_client_host_shared_refresh() http-client-host.c:195 #12-#19 http_client queue/host/request submit chain #20 http_client_request_continue_payload() http-client-request.c:1170 #21 http_client_request_send_payload() http-client-request.c:1261 #22 solr_connection_post_more() solr-connection.c:269 Proposed fix: Destroy solr_http_client in solr_connection_deinit() so it is recreated with a fresh event chain on the next user session: --- a/src/plugins/fts-solr/solr-connection.c +++ b/src/plugins/fts-solr/solr-connection.c @@ -117,6 +117,8 @@ void solr_connection_deinit(struct solr_connection **_conn) *_conn = NULL; event_unref(&conn->event); + if (solr_http_client != NULL) + http_client_deinit(&solr_http_client); i_free(conn->http_host); i_free(conn->http_base_url); I've been running for few days with the patch applied. FTS indexing across multiple user sessions completes without crashes using a DNS-based Solr URL. Please let me know if there's anything else that would be helpful. The core files have sensitive information so I've omitted them from the report. -Nick Dovecot 2.4.3 crashes with SIGSEGV in indexer-worker and lmtp during FTS Solr indexing. The crash is a use-after-free triggered when the HTTP client does a DNS lookup for the Solr host. Environment: - Dovecot 2.4.3 (Alpine 3.23 / musl) - Linux x86_64 - Filesystem: maildir on ZFS - Solr 10.0.0 - fts_solr plugin with DNS-based Solr URL dovecot -n: # 2.4.3 (e278b1e09b): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.3 (0bf9ee48) # OS: Linux 6.12.74+deb13+1-amd64 x86_64 dovecot_config_version = 2.4.0 auth_mechanisms = oauthbearer xoauth2 dovecot_storage_version = 2.4.0 fts_autoindex = yes fts_search_add_missing = yes mail_always_cache_fields = date.save mail_driver = maildir mail_plugins { fts = yes fts_solr = yes } protocols = imap lmtp sieve ssl = required fts solr { url = http://solr.example.com/solr/dovecot } (LDAP userdb/passdb, pigeonhole sieve, imapsieve for spam learning, and oauth2 passdb omitted) How to reproduce: The crash occurs in the indexer-worker when processing multiple user mailboxes sequentially for FTS indexing, using a DNS hostname for the Solr URL. Steps: 1. Configure fts_solr with a DNS-based URL (not an IP address) 2. Have the indexer-worker process mailboxes for more than one user (e.g. fts_autoindex = yes with multiple users, or manual doveadm index -A) 3. The first user session completes successfully. On the second user session, the indexer-worker crashes with SIGSEGV during the DNS lookup for the Solr host. Reproduces reliably on musl (Alpine) due to aggressive memory reuse. Likely also affects glibc but may not crash immediately due to delayed reuse of freed memory. Root cause: The solr_http_client singleton outlives the user session that created it. Its event chain holds a ref on the mail_storage_service_user event, keeping it alive after the user is freed. The SETTINGS_EVENT_INSTANCE on that event still points to the already-freed settings_instance. On the next user session, dns_lookup() walks the stale event chain and dereferences the dangling pointer in settings_instance_get(). Stack trace (from core dump, debug build with musl-dbg): #0 strlen(s=0x415641d189485741) -- SIGSEGV, freed/reused memory #1 p_strdup() strfuncs.c:56 #2 event_add_str(key="protocol", value=...) lib-event.c:1099 #3 settings_instance_get() settings.c:2521 #4 settings_get_real() settings.c:2706 #5 settings_get_full() settings.c:2915 #6 settings_get(dns_client_setting_parser_info) settings.c:2976 #7 dns_client_init() dns-lookup.c:465 #8 dns_clien t_init_handle_failure() dns-lookup.c:317 #9 dns_lookup("solr.example.com") dns-lookup.c:337 #10 http_client_host_shared_lookup() http-client-host.c:166 #11 http_client_host_shared_refresh() http-client-host.c:195 #12-#19 http_client queue/host/request submit chain #20 http_client_request_continue_payload() http-client-request.c:1170 #21 http_client_request_send_payload() http-client-request.c:1261 #22 solr_connection_post_more() solr-connection.c:269 Proposed fix: Destroy solr_http_client in solr_connection_deinit() so it is recreated with a fresh event chain on the next user session: --- a/src/plugins/fts-solr/solr-connection.c +++ b/src/plugins/fts-solr/solr-connection.c @@ -117,6 +117,8 @@ void solr_connection_deinit(struct solr_connection **_conn) *_conn = NULL; event_unref(&conn->event); + if (solr_http_client != NULL) + http_client_deinit(&solr_http_client); i_free(conn->http_host); i_free(conn->http_base_url); I've been running for few days with the patch applied. FTS indexing across multiple user sessions completes without crashes using a DNS-based Solr URL. Please let me know if there's anything else that would be helpful. The core files have sensitive information so I've omitted them from the report. -Nick

1 0

Dovecot and Pigeonhole v2.4.3 released
by Aki Tuomi 31 Mar '26

31 Mar '26

Hi! We are happy to publish version 2.4.3 of Dovecot and Pigeonhole. These contain several CVEs, discovered by external researches. The majority of these have been discovered with help of automated code analysis tools like claude code security, which is why some of these are rather old, missed bugs. No new supported distros have been added or old removed, no new dependencies have been added. Note that there are experimental features in 2.4, one is enabled with `--enable-experimental-mail-utf8`, and another with `--enable-experimental-imap4rev2`, and you also need to set mail_utf8_extensions=yes and imap4rev2_enabled=yes to enable them in config. https://dovecot.org/releases/2.4/dovecot-2.4.3.tar.gz https://dovecot.org/releases/2.4/dovecot-2.4.3.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.3.tar.gz https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.3.tar.gz… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- * CVE-2025-59028: Invalid base64 authentication can cause DoS for other logins. * CVE-2025-59031: decode2text.sh OOXML extraction may follow symlinks and read unintended files during indexing. Fixed by dropping the script. * CVE-2026-24031: SQL injection possible if auth_username_chars is configured empty. Fixed escaping to always happen. v2.4 regression. * CVE-2026-27859: Excessive RFC 2231 MIME parameters in email would cause excessive CPU usage. Fixed by limiting number of parameters to process. * CVE-2026-27860: LDAP query injection possible if auth_username_chars is configured empty. Fixed escaping to always happen. v2.4 regression. * CVE-2026-27857: Sending excessive parenthesis causes imap-login to use excessive memory. * CVE-2026-27856: Doveadm credentials were not checked using timing-safe checking function. * CVE-2026-27855: OTP driver vulnerable to replay attack. * Remove default service/*/service_extra_groups=$SET:default_internal_group. They are now replaced by default mail_access_groups=$SET:default_internal_group. * The version file has been renamed as version.txt to avoid clash with C++ headers. * auth: oauth2 - Do not export token automatically, must be exported using fields. * config: Don't accept 0 as meaning unlimited anymore for last_valid_uid, last_valid_gid, mail_cache_max_headers_count, mail_cache_max_header_name_length, mail_vsize_bg_after_count, mail_sort_max_read_count, message_max_size, submission_max_recipients and quota_mail_size. * imap, pop3: Don't autoexpunge if Dovecot is shutting down or process is killed. * imap: LIST - Handle invalid mUTF-7 mailbox names as never matching anything * lazy-expunge: Change lazy_expunge_only_last_instance default to yes. * lda: Use EX_TEMPFAIL (75) if configuration is invalid instead of 89. v2.4 regression. * lib-master: Increase ANVIL_DEFAULT_LOOKUP_TIMEOUT_MSECS from 5s to 30s * lib: crc32 - Use zlib's built-in CRC32 function + Improve UTF-8 support for mail storage. + auth: Add default auth-token UNIX socket for token-based authentication. + doc: solr-config-9.xml - Make it compatible with Solr 9.8.0 + doveadm: dsync - Search mails when exporting to reduce number of mails exported by dsync-server. + dovecot-sysreport: Add -D|--destdir support. + imap, imap-hibernate: Use DOVECOT-TOKEN authentication for unhibernation. Default imap-master socket permissioms have been changed due to this. + imap: Add APPENDLIMIT capability when configured with quota_mail_size. + imap: Support STATUS (DELETED) for IMAP4rev2. + imapc: Add support for SEARCH MIMEPART + imapc: Improve error forwarding. + imapc: Support SORT and ESORT extensions. + imapc: Support STATUS (DELETED) for IMAP4rev2. + lib-sql: Support parameterized queries. + lib-test: Add new test-dir API for better temporary test directory handling. + lmtp: Advertize SIZE capability when configured with quota_mail_size. + lmtp: Support XCLIENT DESTADDR and DESTPORT + pop3-login: proxy - Add support for XCLIENT DESTIP and DESTPORT + submission-login: proxy - Add support for XCLIENT DESTIP and DESTPORT + Various optimizations have been made to the code. - Fix building dovecot with BSD, Solaris and macOS. - auth: Crash would occur if users were iterated but userdb_ldap_iterate_fields was not set. - auth: Fix request leak when client authenticates with unsupported mechanism. - auth: Some passdbs would default to PLAIN instead of CRYPT scheme. - config: Section and setting names could have been intermixed, resulting in the setting being silently ignored. - configure: Fix checking if BUILD_IMAP_HIBERNATE is set - doveadm: dsync - -e parameter was handled wrong with dsync-server. - fts-flatcurve: Mailbox leak would occur if mailbox failed to open. - imap: Fix potential issues with unhibernation and process state handling. - imapc: SEARCH failure handling was done wrong. - imapc: UID STORE commands included extra comma in uidset. - lib-auth-client: auth-master - Fix panic when reconnecting after handshake timeout. - lib-compression: Lz4 algorithm would assert-crash with malicious data. - lib-dcrypt: Fix digest algorithm handling. - lib-dict: Escape username paths to prevent traversal issues with dict-fs. - lib-http: Fix HTTP parsing edge cases and state handling. - lib-iostream: Disallow empty ssl_min_protocol. - lib-json: Fix incorrect character handling logic. - lib-ldap: Fix various TLS related bugs. - lib-mail: Fix charset translation and MIME parsing edge cases. - lib-mail: Fix multiple bounds checks and parsing issues in message handling. - lib-var-expand: Multiple fixes and improvements for expansion handling. - lib: Fix punycode decoding out-of-bounds reads. - lib: Fix unicode normalization edge cases causing crashes. - lib-http: Chunked transfer trailer size was not limited. - login-common: Improve logging and internal error handling. - login-common: login_log_format_elements was split by spaces naively, which could break variable expansion. Use template aware splitting now. - master: Dovecot would fail to start if listen directive was used and dovenull or dovecot user was missing. - pop3c: Connection might've hung with SSL. - util: Fix handling of environment variables containing control characters. - Many other bugs have been fixed. --- * CVE-2026-27858: managesieve-login can allocate large amount of memory during authentication. * CVE-2025-59032: ManageSieve panic occurs with sieve-connect as a client. * lib-sieve: Don't accept 0 as meaning unlimited anymore for sieve_quota_script_count and sieve_quota_storage_size. * managesieve-login: If mail_max_userip_connections is reached, return LIMIT/CONNECTIONS resp-code. * managesieve-login: proxy - Return unexpected backend failures as TRYLATER/NORETRY resp-code. * managesieve: Remove default service_extra_groups=$SET:default_internal_group. + managesieve-login: proxy - Add support for XCLIENT DESTIP and DESTPORT. - imapsieve: Fix panic occurring upon implicit flag changes. - lib-sieve: include-extension - Fix crash occurring when previous global command has no arguments. - lib-sieve: Fix erroneous attempt to read active script for non-personal storage. - lib-sieve: ldap: Fix linking non-shared LIBDOVECOT.

7 9

migration from 2.3 to 2.4 : postfix can't deliver via lmtp
by Stefan G. Weichinger 31 Mar '26

31 Mar '26

I am in the process of upgrading and rewriting my config. I can access IMAP etc ... so my database access is working. I have issues with LMTP: postfix can't deliver to dovecot. The postfix-confiog wasn't touched at all. the error: Mar 27 11:46:37 co dovecot: auth(stefan(a)oops.co.at): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) What I don't understand: I configure this: service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service auth-worker { user = postfix } service lmtp { user = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } protocol lmtp { mail_plugins = sieve postmaster_address = logs(a)xunil.at } And in postfix: virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 local_transport = virtual local_recipient_maps = $virtual_mailbox_maps smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth Where does "/run/dovecot/auth-userdb" come from? I understand that according to my config /var/spool/postfix/private/auth should be used? ls /var/spool/postfix/private/auth -l srw-rw-rw- 1 postfix postfix 0 Mar 27 11:45 /var/spool/postfix/private/auth ls /var/spool/postfix/private/dovecot-lmtp -l srw-rw---- 1 postfix postfix 0 Mar 27 11:45 /var/spool/postfix/private/dovecot-lmtp I'd appreciate any quick help here ... while googling and testing around ... thanks!

2 17

upgrade to 2.4
by John Hill 31 Mar '26

31 Mar '26

Dovecot may go down as one of the best/worst software in its category. I'm staying on Debian 12 doing backports, till the dust settles several times. --john

1 0

Fwd: dovecot mailing list probe message
by Jaco Kroon 30 Mar '26

30 Mar '26

Hi, It seems like the list system is breaking DKIM - triggering bounces, resulting in unsuscribes. Is there recommendations on how to deal with this? Looks like it relates 100% to the addition of the footer: ______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org Kind regards, Jaco -------- Forwarded Message -------- Subject: dovecot mailing list probe message Date: Mon, 30 Mar 2026 06:32:58 +0000 From: dovecot-bounces+a190cb9ae5d94d8fa6e2af68fc964a7aaa13256b(a)dovecot.org To: jaco(a)uls.co.za This is a probe message. You can ignore this message. The dovecot(a)dovecot.org mailing list has received a number of bounces from you, indicating that there may be a problem delivering messages to jaco(a)uls.co.za. A sample is attached below. Please examine this message to make sure there are no problems with your email address. You may want to check with your mail administrator for more help. You don't need to do anything to remain an enabled member of the mailing list. If you have any questions or problems, you can contact the mailing list owner at dovecot-owner(a)dovecot.org Hi, It seems like the list system is breaking DKIM - triggering bounces, resulting in unsuscribes. Is there recommendations on how to deal with this? Looks like it relates 100% to the addition of the footer: ______________________________________________ dovecot mailing list -- [1]dovecot(a)dovecot.org To unsubscribe send an email to [2]dovecot-leave(a)dovecot.org Kind regards, Jaco -------- Forwarded Message -------- Subject: dovecot mailing list probe message Date: Mon, 30 Mar 2026 06:32:58 +0000 From: [3]dovecot-bounces+a190cb9ae5d94d8fa6e2af68fc964a7aaa13256b(a)dovecot.org To: [4]jaco(a)uls.co.za This is a probe message. You can ignore this message. The [5]dovecot(a)dovecot.org mailing list has received a number of bounces from you, indicating that there may be a problem delivering messages to [6]jaco(a)uls.co.za. A sample is attached below. Please examine this message to make sure there are no problems with your email address. You may want to check with your mail administrator for more help. You don't need to do anything to remain an enabled member of the mailing list. If you have any questions or problems, you can contact the mailing list owner at [7]dovecot-owner(a)dovecot.org References Visible links 1. mailto:dovecot@dovecot.org 2. mailto:dovecot-leave@dovecot.org 3. mailto:dovecot-bounces+a190cb9ae5d94d8fa6e2af68fc964a7aaa13256b@dovecot.org 4. mailto:jaco@uls.co.za 5. mailto:dovecot@dovecot.org 6. mailto:jaco@uls.co.za 7. mailto:dovecot-owner@dovecot.org

3 4

Update to v2.4.3 breaks ldap connection
by markus-dovecot＠doits.de 30 Mar '26

30 Mar '26

Unfortunately the upgrade to v2.4.3 broke the ldap connection. I have configured an ldap connection like this: ``` ldap_uris = ldaps://xxx.com ldap_auth_dn = uid=xxx,ou=general accounts,dc=xxx,dc=com ldap_auth_dn_password = xxx ldap_base = dc=xxx,dc=com passdb ldap { ldap_bind = yes [...] } ``` v2.4.3 cannot connect and says: ``` auth: Error: ldap(ldaps://xxx.com636): Can't connect to server: ldaps://xxx.com ``` Ldap server logs: ``` ACCEPT from IP=[XXX]:45674 (IP=[::]:636) TLS established tls_ssf=256 ssf=256 tls_proto=TLS1.3 tls_cipher=AES-256-GCM closed (connection lost) ``` Downgrade to dovecot v2.4.2 makes it work again. Was there any ldap change in v2.4.3 that required a config change? Using ubuntu 24.04 with the dovecot ppa, now forced version 2.4.2 by using https://repo.dovecot.org/ce-2.4.2/ubuntu/noble

4 6

Dovecot 2.4.3 virtual now broken even more
by sev monster 30 Mar '26

30 Mar '26

As of 2.4.2, Dovecot no longer crashed and broken config vars no longer caused it to error out, so I finally (reluctantly) switched to it over 2.3, though I had to disable/change a few things to get it to work. However, my virtual namespaces were still broken, since the `autosubscribe = yes` option would cause the driver to attempt to create the virtual directories, and fail when they already existed. Turning off autosubscribe meant that the folders were not visible to my users without manually subscribing. With 2.4.3, now the virtual configs that "worked" before now cause Dovecot to error out completely! Yay It seems this commit introduced a "feature" that restricts the virtual driver to the fs list format: https://github.com/dovecot/core/commit/b4a4a32361b8f0e68ef230add6467eddd0ff… But why? Is fs the only format that works? But maildir++ worked in both 2.3 and in previous versions of 2.4. The 2.4.3 docs (still) also recommend switching to maildir++ if desired: https://doc.dovecot.org/2.4.3/core/plugins/virtual.html#virtual-mailbox-plu… In my config, I use maildir for everything. That means in my mailboxes and all my namespaces. But with this change, I must now use fs as my list format for the virtuals. But, I can't do that, because all `list = yes` namespaces in use by a mailbox must use the same list format... So now my previously invisible virtual folders now cause Dovecot to fall over and I have to completely remove the virtual declarations from my config. What am I supposed to do now?

3 2

Executing a sieve-extprograms pipe script as non-root
by Roland Hieber 29 Mar '26

29 Mar '26

Hi, Ultimately I'm trying to call procmail via a `pipe "procmail";` in my Sieve script on Dovecot 2.4.1. I have therefore created the respective wrapper script in /usr/lib/dovecot/sieve-pipe/procmail, but I noted that the script is apparently run as root. With some debug output in the wrapper script, I see: # `id` output uid=0(root) gid=1059(rhi) groups=1059(rhi),116(dovecot) # `pstree -s -u $$` systemd(1)---dovecot(1064)---lmtp(266577,rhi)---procmail(266706,root)---pstree(266711) This Dovecot gets mail delivered via LMTP from another server. 1059 (rhi) is my local user ID on the IMAP server both in /etc/passwd and in /etc/dovecot/users (using auth-passwdfile.conf.ext in 10-auth.conf instead of auth-system.conf.ext), since mail needs to be delivered and chown'ed correctly into Maildirs that should be user-accessible. However I don't understand how the `procmail` wrapper can be run as the root user rights when the LMTP process starting it is running as my own user?!? I'd like to prevent procmail from running as root as far as possible, so for now I've been able to work around this by wrapping the procmail call into an additional `sudo -U $USER` (after determining the user who owns the target maildir), but I'd like to understand the problem a bit further and like to know if this is really how calling sieve-extprograms is supposed to work – I'd have expected that the external scripts are also run as my unprivileged user. I'm running a fairly standard config on Debian stable (dovecot package version 1:2.4.1+dfsg1-6+deb13u2) with only minimal changes by enabling the passwdfile backend and some sieve plugins. Thanks for any insights, - Roland -- Roland Hieber, Pengutronix e.K. | rhi(a)pengutronix.de | Steuerwalder Str. 21 | https://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |

6 8

dovecot 2.4.x director
by Maciej Milaszewski 27 Mar '26

27 Mar '26

HI Has anyone managed to create a fork or other solution that provides director functionality? A small setup where it can be managed, for example, with Rabit/Redis, is one thing, but not a larger environment. The documentation for 2.4.x seems to have something like this: https://doc.dovecot.org/2.4.3/howto/lua_director.html "This is an unsupported method of running Dovecot. Caveat emptor. It is only intended for small-scale deployments – this is NOT designed to scale for more than a few servers."

2 1

Dovecot Security Advisory OXDC-2026-0001
by Aki Tuomi 27 Mar '26

27 Mar '26

Hi! We're sharing our latest advisory with you and like to thank everyone who contributed in finding and solving those vulnerabilities. This advisory is also published at https://documentation.open-xchange.com/dovecot/security/advisories/html/202… --- Internal reference: DOV-7830 Type: CWE-1250 (Improper Preservation of Consistency Between Independent Representations of Shared State) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.1 Discovery date: 2025-07-24 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: Erik <erik(a)broadlux.com> CVE: CVE-2025-30189 CVSS: 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) Details: v2.4 regression: auth cache broken with several passdb / userdb. When cache is enabled, some passdb/userdb drivers incorrectly cache all users with same cache key, causing wrong cached information to be used for these users. Risk: After cached login, all subsequent logins are for same user. No publicly available exploits are known. Solution: Install fixed version or disable caching either globally or for the impacted passdb/userdb drivers. --- Internal reference: DOV-8349 Type: CWE-20 (Improper Input Validation) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2025-11-04 Solution date: 2026-03-27 Disclosure date: 2026-03-27 CVE: CVE-2025-59028 CVSS: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Details: Invalid base64 authentication can cause DoS for other logins. When sending invalid base64 SASL data, login process is disconnected from the auth server, causing all active authentication sessions to fail. Risk: Invalid BASE64 data can be used to DoS a vulnerable server to break concurrent logins. No publicly available exploits are known. Solution: Install fixed version or disable concurrency in login processes (heavy perfomance penalty on large deployments). --- Internal reference: DOV-8508 Type: CWE-20 (Improper Input Validation) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2025-11-29 Solution date: 2026-03-27 Disclosure date: 2026-03-27 CVE: CVE-2025-59032 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Details: v2.4/v3.1 regression: Pigeonhole: ManageSieve panic occurs with sieve-connect as a client. ManageSieve AUTHENTICATE command crashes when using literal as SASL initial response. Risk: This can be used to crash ManageSieve service repeatedly, making it unavailable for other users. No publicly available exploits are known. Solution: Control access to ManageSieve port, or disable the service if it's not needed. Alternatively upgrade to a fixed version. --- Internal reference: DOV-8584 Type: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2025-12-29 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: cavid@yeswehack CVE: CVE-2025-59031 CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Details: decode2text.sh OOXML extraction may follow symlinks and read unintended files during indexing. Dovecot has provided a script to use for attachment to text conversion. This script unsafely handles zip-style attachments. Risk: Attacker can use specially crafted OOXML documents to cause unintended files on the system to be indexed and subsequently ending up in FTS indexes. No publicly available exploits are known. Solution: Do not use the provided script, instead, use something else like FTS tika. --- Internal reference: DOV-8591 Type: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0 First fixed revision: OX Dovecot CE core 2.4.0 Discovery date: 2026-01-07 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: strokep@yeswehack CVE: CVE-2026-0394 CVSS: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Details: auth: Path traversal in passwd-file passdb using `%d` (domain) escapes base directory and opens `/etc/passwd`Pre-auth path traversal in passwd-file passdb using `%d` (domain) escapes base directory and opens `/etc/passwd`. When dovecot has been configured to use per-domain passwd files, and they are placed one path component above /etc, or slash has been added to allowed characters, path traversal can happen if the domain component is directory partial. Risk: This allows inadvertently reading /etc/passwd (or some other path which ends with passwd). If this file contains passwords, it can be used to authenticate wrongly, or if this is userdb, it can unexpectly make system users appear valid users. No publicly available exploits are known. Solution: Upgrade to fixed version, or use different authentication scheme that does not rely on paths. Alternatively you can also ensure that the per-domain passwd files are in some other location, such as /etc/dovecot/auth/%d. --- Internal reference: DOV-8775 Type: CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-02-20 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: cookiejack15@yeswehack CVE: CVE-2026-27860 CVSS: 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) Details: v2.4/v3.1 regression: auth-ldap is not escaping usernames. If auth_username_chars is empty, it is possible to inject arbitrary LDAP filter to Dovecot's LDAP authentication. Risk: This leads to potentially bypassing restrictions and allows probing of LDAP structure. No publicly available exploits are known. Solution: Do not clear out auth_username_chars, or install fixed version. --- Internal reference: DOV-8781 Type: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-02-23 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: whisperer@yeswehack CVE: CVE-2026-24031 CVSS: 7.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L) Details: v2.4/v3.1 regression: SQL injection allows bypassing authentication. Dovecot SQL based authentication can be bypassed when auth_username_chars is cleared by admin. Risk: This vulnerability allows bypassing authentication for any user and user enumeration. No publicly available exploits are known. Solution: Do not clear auth_username_chars. If this is not possible, install latest fixed version. --- Internal reference: DOV-8787 Type: CWE-400 (Uncontrolled Resource Consumption) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-02-24 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: djvirus@yeswehack CVE: CVE-2026-27859 CVSS: 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Details: v3.0.2+ regression: Message headers MIME parameter parsing can cause excessive CPU usage. A mail message containing excessive amount of RFC 2231 MIME parameters causes LMTP to use too much CPU. Risk: A suitably formatted mail message causes mail delivery process to consume large amounts of CPU time. No publicly available exploits are known. Solution: Use MTA capabilities to limit RFC 2231 MIME parameters in mail messages, or upgrade to fixed version where the processing is limited. --- Internal reference: DOV-8816 Type: CWE-400 (Uncontrolled Resource Consumption) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-02-27 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: whisperer@yeswehack CVE: CVE-2026-27857 CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) Details: imap-login: Excessive memory usage DoS. Sending "NOOP (((...)))" command with 4000 parenthesis open+close results in ~1MB extra memory usage. Longer commands will result in client disconnection. This 1 MB can be left allocated for longer time periods by not sending the command ending LF. So attacker could connect possibly from even a single IP and create 1000 connections to allocate 1 GB of memory, which would likely result in reaching VSZ limit and killing the process and its other proxied connections. Risk: Attacker could connect possibly from even a single IP and create 1000 connections to allocate 1 GB of memory, which would likely result in reaching VSZ limit and killing the process and its other proxied connections. No publicly available exploits are known. Solution: Install fixed version, there is no other remediation. --- Internal reference: DOV-8818 Type: CWE-400 (Uncontrolled Resource Consumption) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0, OX Dovecot CE core 2.4.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-02-28 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: ilyar@yeswehack CVE: CVE-2026-27858 CVSS: 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Details: managesieve-login out-of-memory DoS. Attacker can send a specifically crafted message before authentication that causes managesieve to allocate large amount of memory. Risk: Attacker can force managesieve-login to be unavailable by repeatedly crashing the process. No publicly available exploits are known. Solution: Protect access to managesieve protocol, or install fixed version. --- Internal reference: DOV-8830 Type: CWE-287 (Improper Authentication) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-03-04 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: bksparajuli@yeswehack CVE: CVE-2026-27856 CVSS: 7.4 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) Details: doveadm: Credentials verified without timing safety. Doveadm credentials are verified using direct comparison which is susceptible to timing oracle attack. An attacker can use this to determine the configured credentials. Risk: Figuring out the credential will lead into full access to the affected component. No publicly available exploits are known. Solution: Limit access to the doveadm http service port, install fixed version. --- Internal reference: DOV-8859 Type: CWE-294 (Authentication Bypass by Capture-replay) Component: core Report confidence: Confirmed Solution status: Fixed by vendor Last affected revision: OX Dovecot Pro core 2.3.0 First fixed revision: OX Dovecot CE core 2.4.3 Discovery date: 2026-03-09 Solution date: 2026-03-27 Disclosure date: 2026-03-27 Researcher credits: hamizanazman@yeswehack CVE: CVE-2026-27855 CVSS: 6.8 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) Details: auth: OTP driver vulnerable to replay attack. Dovecot OTP authentication is vulnerable to replay attack under specific conditions. If auth cache is enabled, and username is altered in passdb, then OTP credentials can be cached so that same OTP reply is valid. Risk: An attacker able to observe an OTP exchange is able to log in as the user. No publicly available exploits are known. Solution: If authentication happens over unsecure connection, switch to SCRAM protocol. Alternatively ensure the communcations are secured, and if possible switch to OAUTH2 or SCRAM.

1 0

Imap Sieve errors in 2.4.2
by Alberto 26 Mar '26

26 Mar '26

Hi, I have a Dovecot docker image with last version (2.4.2). I'm getting some errors, last time a few minutes ago, when dragging some emails into a folder I had just created. ... Mar 26 10:48:20 imap(alberto(a)bersol.info)<451><wHkgJepNsLRYDtBg>: Info: Mailbox INBOX.carpetanueva: Mailbox created Mar 26 10:48:24 imap(alberto(a)bersol.info)<397><x8N6YuhNMs9YDtBg>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed : (ismt->src_box == NULL || ismt->src_box == src_box) Mar 26 10:48:24 imap(alberto(a)bersol.info)<397><x8N6YuhNMs9YDtBg>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 i_panic[0x7fbaed2ee8ab] -> #4 [unw_get_proc_name() failed: -1] Mar 26 10:48:24 imap(alberto(a)bersol.info)<397><x8N6YuhNMs9YDtBg>: Fatal: master: service(imap): child 397 killed with signal 6 (core dumped) This breaks Dovecot and I have to restart the container, but it doesn't fix it either. When I access again, I've receive this errors again, until I disable sieve in the imap.conf: conf.d/20-imap.conf ------------------- ... protocol imap { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins { # imap_sieve = yes imap_quota = yes last_login = yes } And I have to keep "imap_sieve" disabled. Regards, Alberto

2 1

Issues with doveadm sync
by cryintothebluesky＠gmail.com 21 Mar '26

21 Mar '26

Hello, I have two replica IMAP servers both running dovecot-2.4.2: imap1.example.com imap2.example.com I'm observing the following issues when replicating mailboxes with doveadm sync: 1. Permission errors with public and shared mailboxes For this test I delete all mailboxes on imap2.example.com and then use full sync from imap1.example.com to replicate mailboxes: # doveadm sync -f -s "" -N -l 10 -u ${user:?} ${server:?} The first time I run this command, the following error messages are logged: doveadm(XXX(a)example.com)<1363><eZzOJic5vWlTBQAAMBZ7fQ>: Error: brain S: Can't create mailbox Shared/support(a)example.com: Permission denied doveadm(XXX(a)example.com)<1334><ZV88Byg5vWk2BQAAMBZ7fQ>: Error: brain S: Can't create mailbox Public/Test: Permission denied If I wait 10 seconds and run the same sync command again, all mailboxes are replicated correctly. This only happens with public and shared mailboxes. I'm not sure of the exact cause, but it looks as if there is a race condition, where on the target server replicated ACLs are not applied immediately and this results in permission errors. Can anyone confirm the root cause? 2. Mailboxes are not always synchronised correctly For this test I'm using stateful sync. The man page states it performs a two-way sync, hence both server should end up with the same state. 1) I log into imap2.example.com and move some messages from Inbox to Drafts and Junk folders. 2) On imap1.example.com I run: doveadm sync -s "${state}" -N -l 10 -u ${user:?} ${server:?} 3) I log into imap1.example.com and sometimes observe the recently moved messages missing from Drafts and/or Junk folders. 4) The only way to resolve this issue is to either run full sync from imap1.example.com or to run another stateful sync but from imap2.example.com. Can anyone confirm if this is a bug or if stateful sync is required to be run on both IMAP servers against each other?

1 0

Error: ldap: auth_passdb_post settings
by Ruud Baart 21 Mar '26

21 Mar '26

Dovecot 2.4.1 works fine on my Debian Trixie server. I use LDAP as backend for the users. I don't have problems. Authentication works fine. However logging show every time the following line: auth-worker(<user name@domain,::1)<109040><3v5ddOlJvrgAAAAAAAAAAAAAAAAAAAAB>: request [7]: Error: ldap: auth_passdb_post settings: Failed to parse configuration: Failed to expand passdb_fields/password setting variables: ldap: No such attribute 'userpassword' The LDAP authentication works correct. So I don't understand this message. My correct working LDAP configuration in auth-ldap.conf.ext: passdb ldap { passdb_use_worker = yes passdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) ldap_bind = yes fields { user = %{ldap:mailDeliveryaddress} password = %{ldap:userPassword} } } userdb ldap { userdb_use_worker = yes userdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) fields { home = %{ldap:mailBase} mail = %{ldap:mailMessageStore} mail_path = %{ldap:mailMessageStore} quota_storage_size = %{ldap:dovecotQuota} } }

6 21

Panic in logs
by Kamil Jońca 21 Mar '26

21 Mar '26

Recently I found in my lda logs: 2025-12-30T07:55:14.717927+01:00 alfa dovecot: lda(kjonca): Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 i_syslog_fatal_handler[0x7f99a2351430] -> #3 i_panic[0x7f99a226d453] -> #4 [unw_get_proc_name() failed: -10] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 buffer_append[0x7f99a2345270] -> #8 dregex_code_match_groups[0x7f99a233f1a0] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 sieve_match_value[0x7f99a117f770] -> #12 sieve_match[0x7f99a117fa30] -> #13 [unw_get_proc_name() failed: -10] -> #14 sieve_interpreter_continue[0x7f99a117e100] -> #15 sieve_multiscript_run[0x7f99a1190330] -> #16 [unw_get_proc_name() failed: -10] -> #17 mail_deliver[0x7f99a27e54a0] -> #18 main[0x55e371c555e0] -> #19 __libc_start_call_main[0x7f99a1e29f00] -> #20 __libc_start_main_alias_2[0x7f99a1e29fa0] -> #21 _start[0x55e371c566a0] And sadly it seems, that mail is missing (it was passed to pipe program to further processing) KJ -- http://wolnelektury.pl/wesprzyj/teraz/ When you go out to buy, don't show your silver.

4 5

shared mailbox error
by Marc 19 Mar '26

19 Mar '26

I am getting this error. This file does not exist. Error: t_readlink(/xxxxxx/dbox-alt-root) failed: readlink() failed: Permission denied

2 4

dovecot-2.4.2: doveconf seg fault
by Eray Aslan 16 Mar '26

16 Mar '26

Running dovecot -c /dev/null -n results in: # 2.4.2 (0962ed2104): /dev/null # Pigeonhole version 2.4.2 (767418c3) Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7c0f3a6 in str_to_uint () at ../lib/strnum.c:76 for a user. And the issue seems to be const unsigned char ** vs const char * mismatch: int str_to_uintmax(const char *str, uintmax_t *num_r) { const char *endp = NULL; uintmax_t n; int ret = str_parse_uintmax(str, &n, &endp); if ((ret != 0) || (*endp != '\0')) /* <--- reading via 'const char *' return -1; *num_r = n; return 0; } vs int str_parse_data_uintmax(const unsigned char *data, size_t size, uintmax_t *num_r, const unsigned char **endp_r) { const unsigned char *p = data, *pend = data + size; uintmax_t n = 0; if (p >= pend || *p < '0' || *p > '9') return -1; do { if (n >= ((uintmax_t)-1 / 10)) { if (n > (uintmax_t)-1 / 10) return -1; if ((uintmax_t)(*p - '0') > ((uintmax_t)-1 % 10)) return -1; } n = n * 10 + (*p - '0'); p++; } while (p < pend && *p >= '0' && *p <= '9'); if (endp_r != NULL) *endp_r = p; /* <--- writing via 'const unsigned char *' *num_r = n; return 0; } We don't know enough to choose which one would be preferable so that the interfaces match. It needs an informed decision as it shows up in a bunch of other places as well. More details at: https://bugs.gentoo.org/971191 Thank you -- Eray

1 0

Issues with 2.4.1 & remote postgresql server
by Terry Braun 14 Mar '26

14 Mar '26

Hello, I'm stumped with using a remote postgresql database for authentication. I went through the process once, failed, debugged, failed again. I could successfully use psql to access the remote database from my host machine, so I do not believe the remote access is an issue. I implemented an instance using sqlite3 database and it worked just fine. ``` from auth-sql.conf.ext ``` sql_driver = pgsql pgsql 72.44.55.66 { parameters { sslmode = require user = user password = 123 dbname = db } } I'm using lmtp over sockets to deliver mail to dovecot, in order to isolate any interaction issues. With a postgresql db I get "Mailbox isn't a valid mbox file", but with changes only to auth-sql.conf.ext it fails. I can run the queries from psql and they work. I'm pretty much out of ideas of things to try. - I could not find anything to validate the syntax of the psql data. All the examples had "psql localhots {" - Because of the above, I am wondering if there may be an issue in the postgres driver somehow? - I did look at the documentation for https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWO… but I'm unsure what is needed. Thanks for any ideas, help, hints. If someone has an example that works with 2.4.1-4 (7d8c0e5759) on debian 13 that would be great Terry

2 1

How to declare port 143
by Steve Litt 10 Mar '26

10 Mar '26

Hi all, I have Dovecot 2.4.2 working (plain text only) on my Qemu virtual machine, with Claws-Mail able to work with all its files. However, I want to declare the Dovecot server as running on Port 143, and when I do, I dovecot -F throws the error message shown later in this message. If I comment out the explicit port declaration, it works fine, and I want to know why. To the best of my knowledge, my declaration of port 143 exactly matches your 2.4.2 documentation: The following is my attempt to tell Dovecot to serve *explicitly* at port 143: =============================================== # My Dovecot server will operate on Localhost listen = 127.0.0.1 service imap { inet_listener imap-login { port = 143 } # inet_listener imaps { # port = 993 # ssl = yes # } } =============================================== The following is the result: =============================================== [root@dovecotvoid ~]# dovecot -F doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: duplicate listener: 143:127.0.0.1 [root@dovecotvoid ~]# =============================================== If I comment out the port = 143, it works. Why is it griping about a duplicate listener? At the bottom of this email is the entire dovecot.conf and the result of dovecot -n, and there are no sub-configuration files in conf.d : =============================================== # Start new configs with the latest Dovecot version numbers here: dovecot_config_version = 2.4.2 # Must be current version dovecot_storage_version = 2.4.2 # Must be current version or earlier # 2.3 is minimum # I only want imap protocols { imap = yes lmtp = no pop3 = no } # My Dovecot server will operate on Localhost listen = 127.0.0.1 service imap { inet_listener imap-login { port = 143 } # inet_listener imaps { # port = 993 # ssl = yes # } } # mail_home is only for virtual users # A virtual user is a user with no system account # I have no virtual users, so I've commented out mail_home. #mail_home = /srv/mail/%{user} # mail_driver is the storage format mail_driver = maildir # mail_path is location of top of storage data # WARNING: For troubleshooting be prepared to switch # to literal location of ~ mail_path = ~/mail/Maildir # In my case # mail_home is the home directory of the user identified as ~ # WARNING: system users have no ~ without it. mail_home = /home/slitt # You need a log you can locate # There might not be a log_path=/var/log/dovecot.log #mail_uid = slitt #mail_gid = slitt mail_uid = vmail mail_gid = vmail # By default first_valid_uid is 500. #If your vmail user's UID is smaller, # you need to modify this: #first_valid_uid = uid-number-of-vmail-user namespace inbox { inbox = yes separator = / } # Authenticate as system users: passdb pam { driver = pam #driver = passwd } userdb passwd { driver = passwd } #ssl_server_cert_file = /etc/dovecot/ssl-cert.pem #ssl_server_key_file = /etc/dovecot/ssl-key.pem =============================================== The following is the output of dovecot -n: =============================================== # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # OS: Linux 6.12.71_1 x86_64 # Hostname: dovecotvoid dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.2 listen = 127.0.0.1 log_path = /var/log/dovecot.log mail_driver = maildir mail_gid = vmail mail_home = /home/slitt mail_path = ~/mail/Maildir mail_uid = vmail protocols { imap = yes lmtp = no pop3 = no } service imap { inet_listener imap-login { port = 143 } } namespace inbox { inbox = yes separator = / } passdb pam { driver = pam } userdb passwd { driver = passwd } ===============================================

5 5

Republish of 2.4.2
by Aki Tuomi 10 Mar '26

10 Mar '26

Hi all! We have republished 2.4.2 packages to fix some packaging issues with Pigeonhole. Please note that for now dovecot-sieve and dovecot-managesieved will get installed together due to dependency issues. Kind regards, Aki Tuomi

1 0

solr-config-9.xml Fails to Load with Solr 9.10.1
by Steven Smith 10 Mar '26

10 Mar '26

I’m trying to use the latest dovecot solr module solr-config-9.xml at with Solr 9.10.1: https://github.com/dovecot/core/blob/956fd0f9a101673be72a7df7d643dd20cf4c40… This dovecot module has been updated to work with version 9.8 and removes the deprecated <lib> directives. However, I observe that it does not load under solr 9.10.1 with the Java exception below. Does anyone have any pointers on how to modify this module for the latest solr versions? var/solr/logs/solr-8983-console.log: > 2026-03-10 01:34:45.983 INFO (main) [] o.a.s.c.CorePropertiesLocator Found 1 core definitions underneath /opt/local/var/solr > 2026-03-10 01:34:45.984 INFO (main) [] o.a.s.c.CorePropertiesLocator Cores are: [dovecot] > 2026-03-10 01:34:46.012 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.c.SolrConfig Using Lucene MatchVersion: 9.8.0 > 2026-03-10 01:34:46.045 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.s.ManagedIndexSchemaFactory The schema is configured as managed, but managed schema resource managed-schema.xml not found - loading non-managed schema schema.xml instead > 2026-03-10 01:34:46.064 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.s.IndexSchema Schema name=dovecot > 2026-03-10 01:34:46.100 ERROR (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.c.CoreContainer SolrCore failed to load on startup =>org.apache.solr.common.SolrException: Unable to create core [dovecot] > at org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1803) I'm trying to use the latest dovecot solr module solr-config-9.xml at with Solr 9.10.1: [1]https://github.com/dovecot/core/blob/956fd0f9a101673be72a7df7d643dd20cf4c… This dovecot module has been updated to work with version 9.8 and removes the deprecated <lib> directives. However, I observe that it does not load under solr 9.10.1 with the Java exception below. Does anyone have any pointers on how to modify this module for the latest solr versions? var/solr/logs/solr-8983-console.log: 2026-03-10 01:34:45.983 INFO (main) [] o.a.s.c.CorePropertiesLocator Found 1 core definitions underneath /opt/local/var/solr 2026-03-10 01:34:45.984 INFO (main) [] o.a.s.c.CorePropertiesLocator Cores are: [dovecot] 2026-03-10 01:34:46.012 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.c.SolrConfig Using Lucene MatchVersion: 9.8.0 2026-03-10 01:34:46.045 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.s.ManagedIndexSchemaFactory The schema is configured as managed, but managed schema resource managed-schema.xml not found - loading non-managed schema schema.xml instead 2026-03-10 01:34:46.064 INFO (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.s.IndexSchema Schema name=dovecot 2026-03-10 01:34:46.100 ERROR (coreLoadExecutor-13-thread-1) [ x:dovecot] o.a.s.c.CoreContainer SolrCore failed to load on startup =>org.apache.solr.common.SolrException: Unable to create core [dovecot] at org.apache.solr.core.CoreContainer.createFromDescriptor(CoreContainer.java:1803) References Visible links 1. https://github.com/dovecot/core/blob/956fd0f9a101673be72a7df7d643dd20cf4c40…

1 1

Preventing Plain Auth
by Steve Litt 10 Mar '26

10 Mar '26

Hi all, https://doc.dovecot.org/2.4.2/core/summaries/settings.html , the auth_allow_cleartext section, says "If no, disables the LOGIN command and all other cleartext authentication unless SSL/TLS is used (LOGINDISABLED capability) or the connection is secured (see ssl). See SSL configuration for more detailed explanation of how this setting interacts with the ssl setting. This setting replaces the disable_plaintext_auth setting." I put auth_allow_cleartext = no in my 2.4.2 dovecot.conf, but my Claws-Mail client can still access it, even though there are no key files. I tried putting this setting in several different places: Didn't prevent plain access. I tried switching from 127.0.0.1 to 10.0.2.15, same problem. The following is the output of my dovecot -n command: ========================================= # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # OS: Linux 6.12.74_1 x86_64 # Hostname: dovecotvoid dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.2 listen = 10.0.2.15 log_path = /var/log/dovecot.log mail_driver = maildir mail_gid = vmail mail_home = /home/slitt mail_path = ~/mail/Maildir mail_uid = vmail protocols { imap = yes lmtp = no pop3 = no } service imap { inet_listener imap-login { auth_allow_cleartext = no } } namespace inbox { inbox = yes separator = / } passdb pam { driver = pam } userdb passwd { driver = passwd } ========================================= How do I disable plain text authentication? Thanks, SteveT Steve Litt http://444domains.com

4 13

[BUG?] Dovecot 2.4.2 from Dovecot repo (RHEL 9) does not implement Sieve (properly/fully)
by Patrick S 09 Mar '26

09 Mar '26

Hi all Below is report of what I suspect is a bug arising in Dovecot 2.4.x regarding Sieve functionality after Pigeonhole functionality was folded into Dovecot/Dovecot-sieve. ISSUE: ====== I am building a new mail server on Rocky Linux 9.7 with Postfix 3.10 and Dovecot 2.4.2. The base installation & setup of Dovecot was OK with core functionality (Postfix interoperability and mail into virtual mail domain mailboxes no problem). Once I had the base setup done I started with Sieve functionality: 1) Incoming mail marked as SPAM by Rspamd auto moved into /Junk 2) Mail manually moved in/out of /Junk handed to Rspamd for training as SPAM/HAM This consistantly failed - the first issue I found was Dovecot failing to restart and `dovecot -n` reporting fatal errors related to sieve — section not found etc. etc. From my reading previously I knew I needed to install `dovecot-sieve` and it was installed before I started working on Sieve functionality. I also saw `dovecot-pigeonhole` but I seemed to read that (version >= 2.4) the functionality for that had been included in `dovecot-sieve` **and** there was no Pigeonhole included in the Dovecot 2.4.2 repo — also if I tried to install it I got errors of course because of the version mismatch, and it was not in the dovecot-2.4-latest repo. ``` # dnf info dovecot-pigeonhole Last metadata expiration check: 1:21:15 ago on Fri 06 Mar 2026 08:05:08. Available Packages Name : dovecot-pigeonhole Epoch : 1 Version : 2.3.16 Release : 15.el9 Architecture : x86_64 Size : 371 k Source : dovecot-2.3.16-15.el9.src.rpm Repository : appstream Summary : Sieve and managesieve plug-in for dovecot URL : https://www.dovecot.org/ License : MIT and LGPLv2 Description : This package provides sieve and managesieve plug-in for dovecot LDA. ``` I also saw `dovecot-managesieved` but as I was **not** going to implement a client sieve functionality I did not install that. Anyway I could not even get to first base with Sieve, Dovecot simply did not know about it. I went on IRC and chatted with Aki Tuomi who confirmed that "yeah, looks like there is some packaging mistake." because the directory `/usr/lib64/dovecot/settings` was empty. As a workaround he suggested "you need to install dovecot-managesieved as workaround". I did that and as a result the following files appeared: ``` -rwxr-xr-x 1 root root 15560 Jan 8 12:13 libmanagesieve_login_settings.so -rwxr-xr-x 1 root root 15840 Jan 8 12:13 libmanagesieve_settings.so -rwxr-xr-x 1 root root 19656 Jan 8 12:13 libpigeonhole_settings.so ``` The `dovecot -n` errors went away, it recognised the sieve directives, and I continued with the Sieve setup. All — `dovecot.conf`, sieve files source and compiled — installed OK. But the sieve functionality simply refused to work. I got advice and we found the following which essentially points to sieve (even with `dovecot-managesieved` installed) not working. After installing everything — dovecot.conf, sieve files (compiled successfully) and a pipe to a shell script to call `rspamc` nothing seemed to happen. * `journalctl -f -u dovecot | grep -E "sieve|pipe"` -> nothing showed * `rspamc stat` -> 'Messages scanned' & 'Messages learned' no increase When we checked we found the following: 1) `lib90_sieve_settings.so` (which should be in `/etc/lib64/dovecot/settings`) is missing from the system. `find / -name "lib90_sieve_settings.so"` -> not found I believe the file is critical for the running of (Dovecot using) Sieve? 2) The Dovecot build options missing any sieve functionality: ``` #dovecot --build-options Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL driver plugins: mysql postgresql sqlite Passdb: ldap pam passwd passwd-file sql Userdb: ldap(plugin) passwd prefetch passwd-file sql ``` I believe (I was told) that minus the above (even though `dovecot-managesieved` was installed as well as `dovecot-sieve`) Sieve simply will not function. Is this a bug/packaging error? Regards Patrick ENVIRONMENT: ============ Software -------- * Rocky Linux 9.7 (RHEL) * Postfix 3.10 Built from source * Postscreen running in Postfix * Dovecot 2.4 installed from Dovecot repo * Valkey 9.0.3 (Redis replacement) * Rspamd 3.14.3 Setup ----- * Rspamd <-> Valkey communicate via Unix socket * Postfix & Dovecot <-> Rspamd via inet port/milter: smtpd_milters = inet:localhost:11332 non_smtpd_milters = inet:localhost:11332 * 'First line defence' = DNSBL via postscreen * Rspamd SPF checking, DKIM signing and DMARC configured All of the above installed, working and tested. DOVECOT PACKAGES INSTALLED: =========================== ``` Name : dovecot Version : 2.4.2 Architecture : x86_64 Source : dovecot-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-sieve Version : 2.4.2 Architecture : x86_64 Source : dovecot-sieve-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-managesieved (see note about this in the email) Version : 2.4.2 Architecture : x86_64 Source : dovecot-sieve-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-submissiond Version : 2.4.2 Architecture : x86_64 Source : dovecot-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-imapd Version : 2.4.2 Architecture : x86_64 Source : dovecot-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-lmtpd Version : 2.4.2 Architecture : x86_64 Source : dovecot-2.4.2-2.src.rpm From repo : dovecot-2.4-latest Name : dovecot-lua Version : 2.4.2 Architecture : x86_64 Source : dovecot-2.4.2-2.src.rpm From repo : dovecot-2.4-latest ``` OUTPUT OF `dovecot -n`: ======================= ``` # dovecot -n # 2.4.2-2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2-2 (767418c3) # OS: Linux 5.14.0-611.34.1.el9_7.x86_64 x86_64 Rocky Linux release 9.7 (Blue Onyx) # Hostname: srv01.example.com dovecot_config_version = 2.4.2 auth_default_domain = example.com auth_mechanisms = plain auth_username_format = %{user | lower } dovecot_storage_version = 2.4.2 mail_access_groups = vmail mail_control_path = ~/control mail_driver = maildir mail_gid = 5000 mail_home = /var/vmail/%{user | domain }/%{user | username } mail_index_path = ~/indexes mail_path = %{home}/Maildir mail_privileged_group = vmail mail_uid = 5000 mailbox_list_utf8 = yes protocols = imap lmtp sieve_global_extensions { vnd.dovecot.pipe = yes } sieve_pipe_bin_dir = /etc/dovecot/sieve/bin sieve_plugins { sieve_imapsieve = yes sieve_extprograms = yes } sieve_trace_dir = /var/log/dovecot/sieve-trace sieve_trace_level = actions ssl = required syslog_facility = local5 protocol lmtp { mail_plugins { sieve = yes } } ssl_server { cert_file = /etc/ssl/server/server_example_com.crt key_file = /etc/ssl/server/server_example_com.key } passdb passwd-file { auth_username_format = %{user | username} default_password_scheme = SHA512-CRYPT passwd_file_path = /etc/dovecot/passwd } userdb passwd-file { auth_username_format = %{user | username} passwd_file_path = /etc/dovecot/passwd fields { gid:default = 5000 uid:default = 5000 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service auth-worker { user = $SET:default_internal_user } service anvil { unix_listener anvil { group = $SET:default_internal_group mode = 0660 } } service doveadm { unix_listener doveadm-server { mode = 0600 user = $SET:default_internal_user } } sieve_script rspamd_to_junk { driver = file path = /etc/dovecot/sieve/rspamd-to-junk.sieve type = before } namespace inbox { mail_plugins { imap_sieve = yes } inbox = yes mailbox Junk { auto = create autoexpunge = 90d special_use = "\\Junk" sieve_script report-spam { cause = copy path = /etc/dovecot/sieve/report-spam.sieve type = before } } imapsieve_from Junk { sieve_script report-ham { cause = copy path = /etc/dovecot/sieve/report-ham.sieve type = before } } mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Sent { auto = subscribe special_use = "\\Sent" } mailbox Trash { auto = subscribe special_use = "\\Trash" } } ```

4 7

Curve25519/Ed25519 ?
by Steve Litt 09 Mar '26

09 Mar '26

On my new Dovecot 2.4.2 IMAP server, which when completed will be accessible only via SSL, I plan to use Curve25519/Ed25519 self-signed-cert/private-key. Is there any reason this would be a mistake? Thanks, SteveT Steve Litt http://444domains.com

2 2

Dovecot 2.4 doveadm_worker_count corrupts tab-formatted output
by Philip Iezzi 08 Mar '26

08 Mar '26

Hi there On a Dovecot 2.4.2 (Debian Bookworm) server with over 1300 users, I am using the following config to retrieve quota usage information with doveadm: --------------------------------------- quota "User quota" { } mail_plugins = quota acl mail_log notify userdb sql { iterate_query = SELECT username AS user, CONCAT(quota, 'M') AS quota_storage_size FROM mailaccounts WHERE active = 1 query = \ SELECT '/var/vmail/%{user | domain}/%{user | username}' AS home, 'vmail' AS uid, 'vmail' AS gid, CONCAT(quota, 'M') AS quota_storage_size \ FROM mailaccounts \ WHERE username = '%{user}' AND (active = 1 OR transport_suspended = 0) } --------------------------------------- Initially, I had to run `doveadm quota recalc -A` to recalc quotas and populate the `count` quota driver which is enabled by default for "User quota". But still, it took roughly 20ms per single user or 15-20s for all users: $ time doveadm -f tab quota get -u demo(a)example.com real 0m0.020s $ time doveadm -f tab quota get -A real 0m16.800s Now, to greatly speed this up, I have introduced parallel processing: doveadm_worker_count = 4 Like this, `doveadm -f tab quota get -A` runs approx 10x faster, done in 1.5 - 2.5s But there is one major drawback which I assume to be a bug: # sane output without `doveadm_worker_count = 4` => always 6 fields demo(a)example.com User quota STORAGE 29 204800 0 demo(a)example.com User quota MESSAGE 1 - 0 # broken output with `doveadm_worker_count = 4` => sometimes 7 fields demo(a)example.com User quota STORAGE 29 2048 00 0 demo(a)example.com User quota MESSAGE 1 - 0 Somehow, the tab formatter does not play nicely together with parallel processing. On some output, the value gets split apart by an extra tab, e.g. '2024<TAB>00' in above example. Can you explain this corrupted data? Some kind of "output interleaving" seems to happen when running parallel workers. If I switch to json output (`doveadm -f json quota get -A`), this does not seem to happen and I always get valid JSON output, even with `doveadm_worker_count = 4`. Cheers, Philip

2 8

Sync'ing two dovecot servers
by Marc Singer 04 Mar '26

04 Mar '26

Greetings, I was pleased to see that dovecot has a sync function in doveadm. So far, other tools for moving mailbox contents from one server to another has not been successful. However. Perhaps I don't understand how this should work. I have a new containerized dovecot v2.4.2 # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # OS: Linux 6.12.63+deb13-amd64 x86_64 and I have an existing dovecot running in a VPS: # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-35-amd64 x86_64 Debian 12.11 I want to move one user, as a test. I execute this in the container. # doveadm sync -R1 -u USER tcps:OLD_SERVER:993 doveadm(USER): Error: conn OLD_SERVER:993 (IP:993): doveadm server sent invalid handshake: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. doveadm(USER): Error: cmd sync: Disconnected from remote: Connection closed I'm pretty sure that doveadm sync was able to negotiate the TLS connection. I don't see what it could object to in the sign-on. What am I missing? Cheers -- /Marc Oscar Singer/ *Woollysoft* Dial 817.1823.602.1+ from right to left. Greetings, I was pleased to see that dovecot has a sync function in doveadm. So far, other tools for moving mailbox contents from one server to another has not been successful. However. Perhaps I don't understand how this should work. I have a new containerized dovecot v2.4.2 # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # OS: Linux 6.12.63+deb13-amd64 x86_64 and I have an existing dovecot running in a VPS: # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-35-amd64 x86_64 Debian 12.11 I want to move one user, as a test. I execute this in the container. # doveadm sync -R1 -u USER tcps:OLD_SERVER:993 doveadm(USER): Error: conn OLD_SERVER:993 (IP:993): doveadm server sent invalid handshake: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. doveadm(USER): Error: cmd sync: Disconnected from remote: Connection closed I'm pretty sure that doveadm sync was able to negotiate the TLS connection. I don't see what it could object to in the sign-on. What am I missing? Cheers -- Marc Oscar Singer Woollysoft Dial 817.1823.602.1+ from right to left.

3 4

Getting quota limits from DB
by Alberto 04 Mar '26

04 Mar '26

Hi group: I have a Docker Dovecot 2.4.2 installation with MySQL user management, with this record: SELECT * FROM users; +---------------------------------------------------------------------------- | username | domain | password | home | uid | gid | active | quota | quotamsgs | crampassword +---------------------------------------------------------------------------- | alberto | bersol.info | {MD5-CRYPT}$1$Jm... | /var/mail/alberto | 1000 | 1000 | Y | 3221225472 | 149999 | {CRAM-MD5}fd246... | +---------------------------------------------------------------------------- But I have a problem with user quota definitions... If I run "doveadm" command, I get the user quota occupation, I have "quota_clone" plugin working, but I don't get user quota limit, I don't know why: ----- # docker exec -it midovecot doveadm quota get -A Username Quota name Type Value Limit % alberto(a)bersol.info User quota STORAGE 1925805 3145728 61 alberto(a)bersol.info User quota MESSAGE 37608 100000 37 ----- That limit isn't the correct limit set in DB, but the one is put in the config, and it must to be override in my userdb:Extra Fields. ----- # # docker exec -it midovecot doveadm config # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf ... userdb sql { iterate_query = SELECT CONCAT(username,'@',domain) AS user FROM users query = SELECT home,CONCAT(username,'@',domain) AS username,crampassword AS password,uid AS userdb_uid,gid AS userdb_gid,CONCAT(quota,'B') AS userdb_quota_storage_size,concat('*:messages=',quotamsgs) AS userdb_quota_storage_size FROM users WHERE username = '%{ user | username | lower }' AND domain = '%{ user | domain | lower }' } ... quota_storage_size = 3G quota_message_count = 100000 ... ----- Do you have any idea of the problem? Best Regards, Alberto

2 3

Dovecot marking outgonig emails as unread
by stef204 03 Mar '26

03 Mar '26

Starting a few days ago, I have one email account where ALL outgoing emails are automatically marked as UNREAD. The message is sent, then copied to the "Sent" folder, and has status "unread". Then, a couple of minutes later, something happens where this message gets marked as UNREAD, without ANY interaction of client side. This occurs not matter the email client used, I have tried it with multiple email clients, both local and via web interface, the behavior does not change. This is via Dovevot on Cpanel. if I look at the [1]changelog, it is difficult to identify which changes could have triggered this as there seem to be changes impacting Dovecot almost with every update. I do not control the server myself, this is on a shared hosting plan; tech support has been willing to troubleshoot but is unable to locate the problem. This problem does NOT occur on other email accounts on the same domain, so it looks to me like some corruption or problem syncing flags perhaps? I am at a loss at the moment to fix this behavior. Any suggestions or ideas welcome. Thanks. References Visible links 1. https://docs.cpanel.net/changelogs/132-change-log/

3 5

[Pigeonhole] extracttext on "message/rfc822" attachment ignores included headers
by quentinduchemin＠tuta.io 03 Mar '26

03 Mar '26

Hi everyone! I'm not sure this is a design decision, a bug, something not implemented or malformed input on my side. My use case is the following: users that forward their mails outside the domain I manage have the option to report spam as attachment so the spam classifier can learn anyway. I prefer attachment over forward because MUAs have their own way to do it and it's difficult to reliably reconstruct some headers/email structure that can be important for the spam classifier. Each input message is processed through a Sieve extensions of RFC 5703 to extract the attachment. I ask user to produce a file with .eml extension through any export-like feature of their MUA. Below is an example EML file produced by Tuta (Thunderbird does a similar thing with a different encoding for the body). I'll use a bunch of = characters as a separator in the rest of this. =============================================== [...bunch of header...] X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-0000000000 00 X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYSPR04MB7035 Content-Type: multipart/related; boundary="------------79Bu5A16qPEYcVIZL@tutanota" --------------79Bu5A16qPEYcVIZL@tutanota Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQXB0b3MsIEFwdG9zX0VtYmVkZGVkRm9udCwgQXB0b3 NfTVNGb250U2VydmljZSwgQ2FsaWJyaSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBmb250LXNpemU6 [...base64 encoding of the body...] =============================================== While attached and sent, the received messaged looks like this: =============================================== [...headers of the actual email...] X-Infomaniak-Routing: alpha This is a multi-part message in MIME format. --------------5jyKrhQ08xXUif7LHhgg648N Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit --------------5jyKrhQ08xXUif7LHhgg648N Content-Type: message/rfc822; name="a.eml" Content-Disposition: attachment; filename="a.eml" Content-Transfer-Encoding: 7bit [...headers of the spam....] Subject: Re: //Re: AI + Ranking /// Thread-Topic: //Re: AI + Ranking /// [....] Content-Type: multipart/related; boundary="------------79Bu5A16qPEYcVIZL@tutanota" --------------79Bu5A16qPEYcVIZL@tutanota Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: base64 DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTogQXB0b3MsIEFwdG9zX0VtYmVkZGVkRm9udCwgQXB0b3 NfTVNGb250U2VydmljZSwgQ2FsaWJyaSwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmOyBmb250LXNpemU6 [...base64 encoding of the spam....] --------------79Bu5A16qPEYcVIZL@tutanota-- --------------5jyKrhQ08xXUif7LHhgg648N-- =============================================== I face two issues: 1. Only the base64 decoded string can be retrived through foreverypart/extracttext; 2. It has a lot of newlines. - 2. is not a big deal. The original spam has a lot of HTML junk, and each line with HTML without an inner text node is stripped, but the newline is kept. I don't know if this is intended. - 1. is more of a big deal. To try to confirm that, I made an over-simplified version of the Sieve script (I skip configuration but plugins are loaded etc, please ask if useful). =============================================== [...require...] foreverypart { extracttext "eml"; debug_log "PART ============================== ${eml}"; } =============================================== mail_debug is activated. In the logs, I can read: =============================================== Info: sieve: DEBUG: PART ============================== Info: sieve: DEBUG: PART ============================== Info: sieve: DEBUG: PART ============================== Info: sieve: DEBUG: PART ============================== Info: sieve: DEBUG: PART ============================== Info: sieve: Info: sieve: Info: sieve: Info: sieve: Info: sieve: Info: sieve: Info: sieve: Hello, Info: sieve: Info: sieve: Hope you're doing well. Info: sieve: Info: sieve: Info: sieve: Info: sieve: Info: sieve: Would you like attract more traffic with our AEO + GEO + SEO services. AI-driven search is here—don’t miss out. =============================================== So multiple parts are analyzed but only the last gives something. The RFC says that "If the transfer encoding or character set is unrecognized by the implementation or recognized but invalid, an empty string will result.". But it's over my knowledge. I activated trace for Sieve with "matching" level, and the file looks like (this is another test but was the same result): =============================================== Sieve trace log for message delivery: Username: REDACTED Session ID: ozNMOEPNl2nlAAAAO14Lzw Sender: REDACTED Final recipient: REDACTED Default mailbox: INBOX ## Started executing script 'move-spam' 33: foreverypart loop begin 33: loop ends at line 36 35: extracttext command 36: assign 'eml' [0] = "" 36: debug_log "PART ============================== " 36: foreverypart loop end 36: switched to next message part 36: looping back to line 35 35: extracttext command 36: assign 'eml' [0] = "" 36: debug_log "PART ============================== " 36: foreverypart loop end 36: switched to next message part 36: looping back to line 35 35: extracttext command 36: assign 'eml' [0] = "" 36: debug_log "PART ============================== " 36: foreverypart loop end 36: switched to next message part 36: looping back to line 35 35: extracttext command 36: assign 'eml' [0] = "" 36: debug_log "PART ============================== " 36: foreverypart loop end 36: switched to next message part 36: looping back to line 35 35: extracttext command 36: assign 'eml' [0] = "Hi, Just checking in to see if you had a chance to review my earlier message. [...body spam....] 36: debug_log "PART ============================== ????????????Hi, ?? ??Just checking in t..." 36: foreverypart loop end 36: no more message parts 36: exiting loops at line 36 ## Finished executing script 'move-spam' =============================================== Hypothesis: A. Could it be because the mail headers are indistinguishable from the part headers? B. Or is it related to Pigeonhole not implementing yet the enclose extension, which do this the other way? I hope this message is not too hard to read with all the code/logs. Please tell me if there is a better way of doing it. And thanks in advance for any help, because I don't really know what to do and trying to take a (superficial) look at the Pigeonhole code didn't helped.

1 2

Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Christian Kivalo 28 Feb '26

28 Feb '26

Reposting my reply from a few days ago to a thread with the same panic message. I found this in my logs when some mails that got deleted on the phone were still visible in roundcube. I currently have three users that trigger the panic. One user with an iPad accounts for nearly all of the panics. The problem shows when the account is accessed from android (thunderbird) or ipad. The same accounts show no problems when beeing used with roundcube or thunderbird on windows. I enabled core dumps on 2026-01-14 and have ~8500 core dumps of the imap binary until now. What causes this error and how can I fix it? In the logs all I see is the users login, then the panic. # doveconf -n # 2.4.2-2+debian13 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2-2+debian13 (767418c3) # OS: Linux 6.12.0-custom.kvm x86_64 Debian 13.3 ext4 2026-01-13T21:44:32.317609+01:00 uschi dovecot: imap-login: Logged in: user=<user(a)example.com>, method=PLAIN, rip=<IP1>, lip=<IP2>, mpid=4194077, TLS, session=<cpkID0tId7dUc9rl> 2026-01-13T21:44:38.455379+01:00 uschi dovecot: imap(user(a)example.com)<4194077><cpkID0tId7dUc9rl>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) 2026-01-13T21:44:38.458755+01:00 uschi dovecot: imap(user(a)example.com)<4194077><cpkID0tId7dUc9rl>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 i_panic[0x7f6b6c46c2f6] -> #4 [unw_get_proc_name() failed: -10] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 mailbox_save_alloc[0x7f6b6ca103c0] -> #8 [unw_get_proc_name() failed: -10] -> #9 command_exec[0x55654e677400] -> #10 [unw_get_proc_name() failed: -10] -> #11 [unw_get_proc_name() failed: -10] -> #12 [unw_get_proc_name() failed: -10] -> #13 client_handle_input[0x55654e67ddc0] -> #14 client_continue_pending_input[0x55654e67e0b0] -> #15 io_loop_call_io[0x7f6b6c565490] -> #16 io_loop_handler_run_internal[0x7f6b6c567230] -> #17 io_loop_handler_run[0x7f6b6c5673c0] -> #18 io_loop_run[0x7f6b6c5675a0] -> #19 master_service_run[0x7f6b6c4b27f0] -> #20 main[0x55654e6688a0] -> #21 [unw_get_proc_name() failed: -10] -> #22 __libc_start_main[0x7f6b6c234ce0] -> #23 _start[0x55654e668eb0] 2026-01-13T21:44:38.459536+01:00 uschi dovecot: imap(user(a)example.com)<4194077><cpkID0tId7dUc9rl>: Fatal: master: service(imap): child 4194077 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) # coredumpctl dump PID: 1071230 (imap) UID: 5000 (vmail) GID: 5000 (vmail) Signal: 6 (ABRT) Timestamp: Fri 2026-01-16 19:17:15 CET (2s ago) Command Line: $'dovecot/imap [user(a)example.com <IP redacted> UID MOVE]' Executable: /usr/lib/dovecot/imap Control Group: /system.slice/dovecot.service Unit: dovecot.service Slice: system.slice Boot ID: 3668d179bda340229a780d5d43e426c3 Machine ID: 05698baa30ae984c9bd014566e16da18 Hostname: uschi Storage: /var/lib/systemd/coredump/core.imap.5000.3668d179bda340229a780d5d43e426c3.1071230.1768587435000000.zst (present) Size on Disk: 1.1M Message: Process 1071230 (imap) of user 5000 dumped core. Module libgcc_s.so.1 from deb gcc-14-14.2.0-19.amd64 Module libstdc++.so.6 from deb gcc-14-14.2.0-19.amd64 Module libzstd.so.1 from deb libzstd-1.5.7+dfsg-1.amd64 Stack trace of thread 1071230: #0 0x00007fbd1ca9f95c n/a (libc.so.6 + 0x9495c) #1 0x00007fbd1ca4acc2 raise (libc.so.6 + 0x3fcc2) #2 0x00007fbd1ca334ac abort (libc.so.6 + 0x284ac) #3 0x00007fbd1cc6caa0 n/a (libdovecot.so.0 + 0x6caa0) #4 0x00007fbd1cd49e67 n/a (libdovecot.so.0 + 0x149e67) #5 0x00007fbd1cc6c3d0 i_panic (libdovecot.so.0 + 0x6c3d0) #6 0x00007fbd1c42f942 n/a (lib95_imap_sieve_plugin.so + 0x4942) #7 0x00007fbd1c431223 n/a (lib95_imap_sieve_plugin.so + 0x6223) #8 0x00007fbd1d258f10 n/a (libdovecot-storage.so.0 + 0x11bf10) #9 0x00007fbd1d1a843b mailbox_save_alloc (libdovecot-storage.so.0 + 0x6b43b) #10 0x00005590b7ed4a69 n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 -- Christian Kivalo

5 12

LDAP AD Quota override not working
by wt.forsaken＠gmail.com 26 Feb '26

26 Feb '26

Hi there, I'm testing the new version of Dovecot 2.4 in Debian 13 before upgrading to my customers and I'm having difficult on trying to override the user's quota. The LDAP base is from Samba4 AD and having been trying the following configuration: auth-ldap.conf.ext: ldap_uris = ldap://localhost ldap_auth_dn = cn=admin,dc=localdomain ldap_auth_dn_password = password ldap_base = ou=users, dc=localdomain passdb ldap { filter = (&(objectClass=person)(sAMAccountName=%{user})) bind = yes fields { userdb_quota_storage_size = %{ldap:telephoneNumber}B } } userdb prefetch { driver = prefetch } userdb ldap { fields { quota_storage_size = %{ldap:telephoneNumber}B } } 90-quota.conf mail_plugins { quota = yes } quota "User quota" { } quota_storage_size = 40M Since there is no quotaBytes in Samba AD, I'm testing to map the telephoneNumber parameters to override the quota, also I'm just testing a 40M to see how it works. Roundcube webmail can see the quota being overriden in its inferior bar, but when I send an email to the user which is above the quota, the journal log inform "failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full)". I don't know how to override the quota, since in passdb section I used the "userdb_" prefix but it is not being passed to userdb when I input the "doveadm user ..." command. I don't know if I have been clear in my request, but I'd appreciate any help.

3 3

Dovecot 2.4 LMTP socket for Postfix / Dovecot base_dir not created upon restart
by Philip Iezzi 24 Feb '26

24 Feb '26

Hi there, After over a week of Dovecot 2.3 -> 2.4 upgrade testing in various mailserver clones, I am now ready for the big picture. Thanks Aki for the Config Upgrader https://dovecot.org/upgrader/ which helped a lot! Tomorrow, I am planning to upgrade a larger mailserver in these 3 steps: 1) Debian Bullseye / Dovecot 2.3.21 => 2.4.1 2) Debian Bullseye => Bookworm / Dovecot 2.4.1 => 2.4.2 3) Debian Bookworm => Trixie Postfix needs to talk to Dovecot over LMTP, using the following in main.cf: virtual_transport = lmtp:unix:/run/dovecot/lmtp Now, while testing this in a full server clone, I stepped over my planned LMTP server setup: =============================================== service lmtp { unix_listener /run/dovecot/lmtp { mode = 0666 user = postfix group = postfix } } protocols = imap pop3 sieve lmtp =============================================== The socket needs to be owned by postfix:postfix for some (security) reasons, otherwise Postfix complains. That's why I cannot go with the default, as documented here: https://doc.dovecot.org/2.4.2/core/config/delivery/lmtp.html#lmtp-server > The UNIX listener on $base_dir/lmtp is enabled by default when protocols setting contains lmtp. But, when using an absolute path on unix_listener, upgrade step 2) Bullseye=>Bookworm breaks with: Processing triggers for dovecot-core (2:2.4.2-2+debian12) ... Job for dovecot.service failed because the control process exited with error code. (...) dovecot[34446]: master: Error: service(lmtp): Socket already exists: /var/run/dovecot/lmtp dovecot[34446]: master: Fatal: Failed to start listeners I then moved to `unix_listener lmtp`: service lmtp { unix_listener lmtp { mode = 0666 user = postfix group = postfix } } Bookworm upgrade (restarted from scratch with a fresh server clone) went through fine. But even after several dovecot.service restarts, the socket ended up in /run/lmtp without creating the /run/dovecot directory, and after a full system reboot, it was suddenly back where I have expected it: /run/dovecot/lmtp I never changed base_dir, which defaults to /var/run/dovecot/ So, here's my question: Is that really the recommended setup (using `inet_listener lmtp` instead of an absolute path) and how can I trust Dovecot to always create the socket in $base_dir/lmtp as documented? Are you guys aware of this issue or was it just me, a temporary hiccup on my just upgraded server? I just found this in mail.log: dovecot: master: Error: bind(/var/run/dovecot/lmtp) failed: No such file or directory dovecot: master: Error: service(lmtp): net_listen_unix(/var/run/dovecot/lmtp) failed: No such file or directory dovecot: master: Fatal: Failed to start listeners Again, this problem seems to have occurred both with `unix_listener /run/dovecot/lmtp` and `unix_listener lmtp` and only resolved after a full system reboot. Thanks, Philip

2 2

Migrating a mailbox from v2.2 to v2.4, production server to pre-production server.
by Mike 23 Feb '26

23 Feb '26

I'm migrating a mailbox from dovecot v2.2 to v2.4. Not that it matters, I'm also changing from mbox to Maildir. As an initial test I used this command: sudo doveadm sync -1D -u theuser -m amailbox remote:theuser@destination.com I received this error: Error: doveadm: Unexpected or incomplete option: -U After changing the dsync_remote_cmd to: dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u I was able to transfer the mailbox without issue. Before changing it, the setting on the source server was: dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -U I'm interested to discover what the -U was intended for since I couldn't find specific documentation to its use. I'll accept that it was a legacy thing and removing it won't cause any unintended consequences...but I do still have that curiosity about what it was for. Additionally, the subscription status doesn't seem to flow to the new server. When checking the source server with: doveconf -d | grep subscriptions doveconf -n | grep subscriptions No value is returned...So I'm wondering if I need to specifically set subscriptions = yes in the source server to make this happen properly. Maybe this is an artifact of using sync -1? Thanks for any insight you may provide. Mike

1 0

Localhost Dovecot server without ssl?
by Steve Litt 23 Feb '26

23 Feb '26

Hi all, I'd like your opinions to add to my own opinion. Bottom line question: If I trust everybody with physical access to my Daily Driver Desktop (DDD) computer, my Dovecot IMAP runs on my DDD, I access my Dovecot IMAP *exclusively* from my DDD, and I trust everybody with physical access to my DDD (that would be my wife), then if I serve out IMAP on localhost (127.0.0.1), am I being unduly risky using plain text auth (port 143)? Details: I use a Dovecot IMAP server, on my DDD, specifically to hold all my email messages. Therefore, I can use any IMAP aware email client, interchangeably, to view every email I've received since April 2001. People whose emails are held by their email clients are "locked in" to their email client unless they convert their email data. I can switch between Evolution and Claws-Mail, because one of the two is always doing something stupid. Bottom line: I use Dovecot IMAP exclusively to hold my emails and folders. Graphical description below: ISP ---> My --------> procmail --> Dovecot IMAP fetchmail Maildir | | V email <--- Dovecot client IMAP server For the time being, I don't need to access my Dovecot IMAP from any computer except my DDD, and therefore, I can serve Dovecot IMAP on 127.0.0.1. So here's my question. Assuming (and I know this is a big assumption) I'm not worried about somebody gaining physical possession of my DDD, is there any reason not to use plain text to access this server? Thanks, SteveT Steve Litt http://444domains.com

2 1

Copies/duplicates of Dovecot indices
by Joseph Tam 23 Feb '26

23 Feb '26

In my setup, I put mail indices outside the user's mailbox locations (user mailboxs are NFS, indices stored local attached storage). I notice that sometimes, there are 2 sets of indices representing the same mailbox: one at top level, one underneath .imap/. (They usually appear in the latter.) For example, if I have the configuration (Dovcot version 3.2.21) mail_location = mbox:~/mail:INBOX=/nfs/mail/%n:INDEX=/cache/%n I see for a particular user [1] drwx------ 5 user group 512 Feb 22 21:56 /cache/user/box [2] drwxr-xr-x 5 user group 512 Feb 22 21:46 /cache/user/.imap/box cooresponding to their mailbox in ~user/mail/box. Each of these have the dovecot.* index files. If I delete [1], it comes back. The timestamps are close to each other so both sets are being used, possibly by different clients. Another quirky discovery is 2 /.imap/ folders beneath each other e.g. /cache/user/.imap/folder1/folder2/.imap/box/dovecot.index What determines which index pathname gets created or used? Joseph Tam <jtam.home(a)gmail.com>

1 0

2.3 replication issue throwing errors
by Paul Kudla 22 Feb '26

22 Feb '26

shows same error on both servers Server 1 : # sync faye(a)scom.ca doveadm(faye(a)scom.ca)<90952><BJq9J2dHmGlIYwEA0dxyZQ>: Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID f982a82747469869ea0f0100cf58dcff (maybe it was just deleted?) Server 2: # sync faye(a)scom.ca doveadm(faye(a)scom.ca)<90952><BJq9J2dHmGlIYwEA0dxyZQ>: Warning: Mailbox changes caused a desync. You may want to run dsync again: Remote lost mailbox GUID f982a82747469869ea0f0100cf58dcff (maybe it was just deleted?) i am aware there is a mismatch on one of the servers but there does not seem to be a clear cut way to find the offending file to delete it or force a backwards sync ? How would i identify what GUID f982a82747469869ea0f0100cf58dcff means? same on both servers. doveadm force-resync -u faye(a)scom.ca '*' have tried reindex etc etc etc issue persists logs ?? mail18 02-20 06:45:24 {dovecot} [67632] (3014654310) doveadm(faye(a)scom.ca)<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug: open(/proc/self/stat) failed: No such file or directory mail18 02-20 06:45:24 {dovecot} [67632] (3014654311) doveadm(faye(a)scom.ca)<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug: open(/proc/self/io) failed: No such file or directory mail18 02-20 06:45:24 {dovecot} [67632] (3014654312) doveadm(faye(a)scom.ca)<71073><hOl0ClRJmGmhFQEAz1jc/w>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/ any help would be appreciated -- Thanks - Paul Kudla (Manager SCOM.CA Internet Services Inc.) Have A Happy Friday AND Happy Sucessful 2026 ! Scom.ca Internet Services <http://www.scom.ca> 104-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3 Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266 Email paul(a)scom.ca

2 2

How do you use doveadm fetch -S
by Steve Litt 20 Feb '26

20 Feb '26

Hi all, I have a working plain text 127.0.0.1:143 Dovecot 2.4.2 on my Qemu VM guest. The following command displays the Receive date, From and Subject for every email in my golugTech mailbox, exactly like the docs say it should: =================================================== doveadm fetch -u slitt "date.received hdr.from hdr.subject" mailbox golugTech =================================================== But when I add the -S in order to specify the 127.0.0.1 listener at port 143, it throws the following error: =================================================== [slitt@mydesk ~]$ cat junk.jnk [root@dovecotvoid dovecot]# doveadm fetch -S 127.0.0.1:143 -u slitt "date.received hdr.from hdr.subject" mailbox golugTech doveadm(slitt): Error: conn 127.0.0.1:143 (127.0.0.1:143): doveadm server sent invalid handshake: * OK Waiting for authentication process to respond.. doveadm(slitt): Error: cmd fetch: 127.0.0.1:143: Command fetch failed for slitt: Connection closed [root@dovecotvoid dovecot]# [slitt@mydesk~]$ =================================================== The docs say -S is to specify the socket_path, and it should be expressed as hostname:port. For hostname, besides 127.0.0.1, I tried localhost and dovecotvoid, the latter of which should not work because dovecotvoid is not 127.0.0.1, it's 10.0.2.15. The docs say "This allows an administrator to execute doveadm(1) mail commands through the given socket." So I guess finding the server isn't the purpose of socket_path. My plain text 143 Dovecot 2.4.2 IMAP works just fine without the -S. Is there ever a case where doveadm fetch would need to know the specific address and port of the dovecot IMAP server, and if so, how would I specify it? Thanks, SteveT Steve Litt http://444domains.com

2 1

What replaced mail_home in 2.4.2?
by Steve Litt 20 Feb '26

20 Feb '26

Hi all, In my Dovecot 2.4.2 virtual machine guest I've used mail_home to indicate the value of ~ and presumably of ${home}. However, the only documentation I can find on mail_home is on https://doc.dovecot.org/main/core/summaries/settings.html#mail_home , which is NOT a 2.4.2 document. I find no reference to mail_home on any 2.4.2 documentation. Has something replace mail_home, and if so what's it called and can I put it outside of any {} blocks? Thanks, SteveT Steve Litt http://444domains.com

2 2

mail_utf8_extensions and IMAP Folder Naming
by max.wriedt＠rehost.eu 20 Feb '26

20 Feb '26

i just upgraded my 2.3 installation to 2.4. I like to be bleeding edge and i want to use SMTPUTF8. I came across problems with mailboxes that have german umlauts. when enabling "mail_utf8_extensions=yes" e.g. Microsoft Outlook gives me mUTF-7 encoded folder names. Also the folder names when list via openssl s_client are encoded in mUTF-7. Am i missing something or can i disable utf8 for IMAP (UTF8=ACCEPT) only, but keep for LMTP Transport/SMTPUTF8 from postfix to dovecot? I am using mdbox format as storage, if that matters. My namespace config (shortened): namespace inbox { inbox = yes type = private #mailbox_list_utf8 = yes # also tried this -> when folder didn't exist before it would create a new one with utf8, no matter mail_utf8_extensions is on or off mailbox Drafts { auto = no special_use = \Drafts } mailbox Entw&APw-rfe { special_use = \Drafts } mailbox Entw%26APw-rfe { special_use = \Drafts } mailbox Entw\&APw-rfe { special_use = \Drafts } mailbox Entwürfe { auto = create special_use = \Drafts } mailbox Trash { auto = no special_use = \Trash quota_storage_percentage = 110 } mailbox "Gel&APY-schte Elemente" { special_use = \Trash quota_storage_percentage = 110 } mailbox "Gelöschte Elemente" { auto = subscribe special_use = \Trash quota_storage_percentage = 110 } mailbox Sent { auto = no special_use = \Sent } mailbox Archiv { auto = subscribe special_use = \Archive } mailbox Spam { special_use = \Junk auto = no } }

3 4

2.4.2 breaks user iterations for LDAP
by cpfeiffer＠rev-crew.info 20 Feb '26

20 Feb '26

Hello everyone, Due to the fix for CVE-2025-30189, routines like userdb_ldap_preinit() call auth_cache_parse_key_and_fields() unconditionally, with the eventually called auth_cache_parse_key_exclude() erroring if a cache key could not be constructed. It’s also noteworthy that this call happens regardless of whether use_cache is set or not, and as of such failing to construct a cache key would cause an error even if use_cache = no was set for that database. This is however an issue for user iteration with LDAP, as documented here LDAP | Dovecot CE <https://doc.dovecot.org/2.4.2/core/config/auth/databases/ldap.html#user-ite…> . Such a userdb only has iterate_filter fields that would inherently not be containing any user variables. The call to auth_cache_parse_key_and_fields() uses a combination of ldap_base and userdb_ldap_filter anyway (so whatever is in iterate_filter isn’t considered), and for an iteration userdb as described in the documentation, the latter would be empty. Alas, I ended up getting the rather confusing error * auth: Fatal: auth-cache: dc=rev-crew,dc=info: Cache key must contain at least one variable With dc=rev-crew,dc=info being my ldap_base setting for the iteration userdb. I’m not critically dependent on the user iteration, so I’ve commented the userdb out for now, but this would need fixing. Regards, Christian Pfeiffer Hello everyone, Due to the fix for CVE-2025-30189, routines like userdb_ldap_preinit() call auth_cache_parse_key_and_fields() unconditionally, with the eventually called auth_cache_parse_key_exclude() erroring if a cache key could not be constructed. It's also noteworthy that this call happens regardless of whether use_cache is set or not, and as of such failing to construct a cache key would cause an error even if use_cache = no was set for that database. This is however an issue for user iteration with LDAP, as documented here [1]LDAP | Dovecot CE. Such a userdb only has iterate_filter fields that would inherently not be containing any user variables. The call to auth_cache_parse_key_and_fields() uses a combination of ldap_base and userdb_ldap_filter anyway (so whatever is in iterate_filter isn't considered), and for an iteration userdb as described in the documentation, the latter would be empty. Alas, I ended up getting the rather confusing error o auth: Fatal: auth-cache: dc=rev-crew,dc=info: Cache key must contain at least one variable With dc=rev-crew,dc=info being my ldap_base setting for the iteration userdb. I'm not critically dependent on the user iteration, so I've commented the userdb out for now, but this would need fixing. Regards, Christian Pfeiffer References Visible links 1. https://doc.dovecot.org/2.4.2/core/config/auth/databases/ldap.html#user-ite…

4 5

Search for missing To: header?
by Joseph Tam 20 Feb '26

20 Feb '26

Is there a proper way to torture doveadm search query to look for messages with a missing "To:" header? I played around with it and this seems to work: doveadm fetch -A text mailbox {box} NOT TO '' (Looking through a large spam corups: spam often exclude recipients in the headers as it gives the game away their personalized fraud was blasted to hundreds of addresses.) Joseph Tam <jtam.home(a)gmail.com>

1 0

More Dovecot 2.4 woes: LDAP cache bug and virtual autosubscribe
by sev monster 19 Feb '26

19 Feb '26

8 months ago I messaged this list communicating some of the issues I had with 2.4. Before I could even start testing 2.4 properly, 2 bugs had to be fixed—one that caused crashes on startup (https://gitlab.alpinelinux.org/alpine/aports/-/issues/17050) and one that caused passdb to use the same caching key for all connections and as such always have the same user log in. There was another bug, one that prevented me from using LDAP binds for passdb, but it had a workaround that mostly worked without side-eeffects. All of those have since been fixed, hurray! So in my infinite naïveté, I decided to give 2.4 another shake. And it, again, does not work. Surprise! I did manage to massage the configuration to allow me to at least run 2.4 without crashing and with users able to access (most of) their mailboxes, but there are still blockers to full functionality. I face the following issues: 1. Christian Pfeiffer back in November found a bug where auth caching with LDAP did not work, and due to how it's implemented, even turning caching off would still raise an error. I experienced the same issue for both userdb iteration and passdb bind logins. I had to comment out the userdb and use a static one instead (all my users, currently, use the same UID and easily composable path, so this wasn't a big deal) and start using a service account for LDAP binds. 2. Virtual mailbox autosubscribe does not work anymore. It throws an error about trying to create the virtual mailbox. This worked in 2.3. My virtual mailbox config: namespace virtual { type = private prefix = Search Folders. mail_driver = virtual mail_path = /etc/dovecot/virtual mail_index_path = ~/dovecot-virtual.cache mail_control_path = ~/dovecot-virtual.cache mail_volatile_path = ~/dovecot-virtual.cache hidden = yes list = children subscriptions = no mailbox All { auto = subscribe special_use = \All comment = All messages, excluding Junk and Trash } mailbox Unread { auto = subscribe special_use = \Important comment = All unread messages, excluding Junk and Trash } mailbox Flagged { auto = subscribe special_use = \Flagged comment = All flagged messages } } If there is something wrong with this config that might be responsible for my issue, please let me know. Otherwise, I believe this is a regression. I understand autosubscribe is documented to (and in other situations with non-virtual boxes) create mailboxes if missing, so if this is actually a fix to make the feature work as documented, we need a new option that allows for autosubscription without attempting to create the mailbox. Otherwise, my users will not know they even have these mailboxes—no one anymore knows or cares about mailbox (re: folder) subscription and won't know where to look to get them to show up in their client. With autosubscribe enabled, I can see the mailboxes in my mail client without explicitly subscribing, but attempting to open them will throw a server error. Removing the setting will make the mailbox disappear without going into settings and explicitly subscribing. Any ETA on the first bug being fixed, and any help with the second issue (bug or not) would be greatly appreciated. Best regards. P.S.: I wanted to spread this information that wasn't mentioned at all in the documentation. The shadow passdb was removed in the move to 2.4; why exactly is neither here nor there, though I will remark that I still don't know why it was done. I had believed at the time this necessitated enabling PAM for Dovecot, which it is not by default in my distro's package (Alpine), so if I wanted to continue allowing local users to log in, I would have to build Dovecot it myself and install PAM, neither of which I particularly wanted to do. I did play with passwd-file in the past, but there were issues with it that prevented me from using it—I don't remember what they were exactly, but I believe they have since been fixed, since in my testing now it does seem to work properly in the use-cases I tested. Anyway, while going over my config and getting ready to re-install PAM, I had a thought. /etc/shadow uses the same format for the first two fields as /etc/password, and Dovecot still (supposedly) allows for passwords to be used when reading /etc/password, so wouldn't it be possible to point the driver at the shadow file? Turns out, yes, it works! I am now able to authenticate local users from /etc/shadow again. Thanks to this, I no longer need to build with PAM support and don't need to install PAM on a PAM-less system. I hope this isn't considered a bug or something and support for this use-case is removed, because I really don't want to bother once again with adding PAM when I don't have to. :)

2 2

Fedora 43 and Dovecot version 2.4.2
by Bill Steinberg 19 Feb '26

19 Feb '26

Hello, I am running Fedora 43 on a server which is running a dovecot server, version 2.4.1-8. I am not running a cluster, there is only one dovecot server running on the Fedora 43 instance. Redhat has just updated the dovecot version on Fedora 43 to version 2.4.2-5. I would like to upgrade dovecot to version 2.4.2. I assume that the dovecot_config_version should be changed to 2.4.2. Should the dovecot_storage_version be changed to 2.4.2 as well? Are there any steps that should be taken to upgrade the dovecot storage to version 2.4.2? FYI the mail_driver on the dovecot server is mbox: mail_driver = mbox. Best regards, -Bill Hello, I am running Fedora 43 on a server which is running a dovecot server, version 2.4.1-8. I am not running a cluster, there is only one dovecot server running on the Fedora 43 instance. Redhat has just updated the dovecot version on Fedora 43 to version 2.4.2-5. I would like to upgrade dovecot to version 2.4.2. I assume that the dovecot_config_version should be changed to 2.4.2. Should the dovecot_storage_version be changed to 2.4.2 as well? Are there any steps that should be taken to upgrade the dovecot storage to version 2.4.2? FYI the mail_driver on the dovecot server is mbox: mail_driver = mbox. Best regards, -Bill

2 1

deliver fails because of a permission issue with SSL private key file
by Markus Schönhaber 19 Feb '26

19 Feb '26

Hi, I'm trying to make Postfix hand incoming mail to Dovecot by using Dovecot's deliver. But this fails with a permission error: > Feb 17 15:50:12 debian13-cont postfix/pipe[13133]: 171C17206: to=<recipient(a)dest.examle.org>, relay=dovecot, delay=0.17, delays=0.1/0/0/0.07, dsn=5.3.0, status=bounced (Command died with status 89: "/usr/lib/dovecot/deliver". Command output: doveconf: Fatal: Error in configuration file /etc/dovecot/certs.conf line 3: key_file: open(/etc/ssl/private/ssl-cert-snakeoil.key) failed: Permission denied ) How can I solve this (short of making the private key file world readable, of course)? Regards mks I have this in Postfix' master.cf: > dovecot unix - n n - - pipe > flags=DROhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -e -f ${sender} -a ${recipient} -d ${user}@${domain} # LANG=C id vmail uid=501(vmail) gid=501(vmail) groups=501(vmail),104(ssl-cert) # LANG=C ls -l /etc/ssl/private/ total 4 -rw-r----- 1 root ssl-cert 1704 Feb 4 17:15 ssl-cert-snakeoil.key # doveconf -n # 2.4.2-2+debian13 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2-2+debian13 (767418c3) # OS: Linux 6.19.0-2-MANJARO x86_64 Debian 13.3 btrfs # Hostname: debian13-cont dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.2 log_debug = category=sql mail_driver = sdbox mail_gid = vmail mail_home = /var/spool/vmail/home/%{user | domain}/%{user | username} mail_path = /var/spool/vmail/mail/%{user | domain}/%{user | username} mail_plugins { quota = yes } mail_uid = vmail protocols = imap lmtp sieve sql_driver = mysql mysql localhost { dbname = postfixadmin password = # hidden, use -P to show it user = postfixadmin } passdb sql { query = SELECT 'vmail' AS userdb_uid, 'vmail' AS userdb_gid, CONCAT('/var/spool/vmail/home/', maildir) AS userdb_home, CONCAT(quota, 'B') AS userdb_quota_storage_size, username AS user, password FROM mailbox WHERE username = '%{user}' AND active = '1'; } userdb prefetch { } userdb sql { iterate_query = SELECT username AS user FROM mailbox WHERE active = '1'; query = SELECT 'vmail' AS uid, 'vmail' AS gid, CONCAT('/var/spool/vmail/home/', maildir) AS home, CONCAT(quota, 'B') AS quota_storage_size, username AS user, password FROM mailbox WHERE username = '%{user}' AND active = '1'; } namespace inbox { inbox = yes separator = / mailbox Drafts { special_use = "\\Drafts" } mailbox Entwürfe { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox "Gelöschte Objekte" { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Gesendete Objekte" { special_use = "\\Sent" } } service auth { inet_listener tcp_auth { port = 12345 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service auth-worker { } ssl_server { cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem key_file = /etc/ssl/private/ssl-cert-snakeoil.key } protocol imap { mail_plugins { imap_quota = yes } } quota "User quota" { } dict_server { dict mysql { driver = sql sql_driver = mysql dict_map priv/quota/messages { sql_table = quota username_field = username dict_map_value_field messages { } } dict_map priv/quota/storage { sql_table = quota username_field = username dict_map_value_field bytes { } } } } quota_clone { dict proxy { name = mysql } }

6 14

dovecot 2.4 changes
by Curtis J Blank 18 Feb '26

18 Feb '26

I just did a Tumbleweed upgrade. then I had to fix dovecot. No warning that dovecot was going to break what so ever. Below is all the things I had to fix. And then I could not read my email in Thunderbird because you changed: mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u to mail_driver = mbox mail_path = ~/mail mail_inbox_path = /var/spool/mail/%{user} and the "%u" to "%{user}" was the showstopper. What a crock of BS! I spent 3 hours determining the problem and then fixing dovecot because you decided to make major changes for no good reason. It worked just fine the way it was. You could have automated the changes by providing a utility that would make the changes the first time it started up after the upgrade. I had to try to start dovecot and when it failed to start look in the log and see the error and fix it. Over and over and over and over and over and over and over and... Like I said what a bunch of BS! Yes this is a rant. And maybe openSuSE's is too blame also. Jan 24 03:33:35 server dovecot[2223449]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 25: The first setting must be dovecot_config_version Jan 24 03:36:45 server dovecot[4626]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 25: The first setting must be dovecot_config_version Jan 24 03:46:10 server dovecot[21464]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 2: Invalid dovecot_config_version: Currently supported versions are: 2.4.0 2.4.1 2.4.2 Jan 24 03:48:45 server dovecot[22135]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 92: dict { } is missing section name Jan 24 03:51:47 server dovecot[28824]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/auth-system.conf.ext line 10: passdb { } is missing section name Jan 24 03:53:22 server dovecot[29258]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/auth-system.conf.ext line 10: passdb { } is missing section name Jan 24 03:55:26 server dovecot[29906]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/auth-system.conf.ext line 49: userdb { } is missing section name Jan 24 03:56:57 server dovecot[30179]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-director.conf line 40: inet_listener { } is missing section name Jan 24 03:58:37 server dovecot[30652]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-logging.conf line 64: Unknown section name: plugin Jan 24 04:01:32 server dovecot[37805]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-mail.conf line 31: mail_location: Unknown setting: mail_location Jan 24 04:05:30 server dovecot[38898]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-mail.conf line 32: mail_location: Unknown setting: mail_location Jan 24 04:06:35 server dovecot[39158]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 23: ssl_cert: Unknown setting: ssl_cert Jan 24 04:09:07 server dovecot[39707]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 25: ssl_server_cert_file: open(/etc/dovecot/conf.d/-----BEGIN CERTIFICATE----- Jan 24 04:09:07 server dovecot[39707]: doveconf: Fatal: -----END CERTIFICATE----- Jan 24 04:09:07 server dovecot[39707]: doveconf: Fatal: ) failed: File name too long Jan 24 04:14:52 server dovecot[47156]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 27: ssl_server_cert_file: open(/etc/dovecot/conf.d/-----BEGIN CERTIFICATE----- Jan 24 04:14:52 server dovecot[47156]: doveconf: Fatal: -----END CERTIFICATE----- Jan 24 04:14:52 server dovecot[47156]: doveconf: Fatal: ) failed: File name too long Jan 24 04:17:35 server dovecot[54187]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 72: ssl_dh: Unknown setting: ssl_dh Jan 24 04:19:04 server dovecot[54532]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 93: ssl_prefer_server_ciphers: Unknown setting: ssl_prefer_server_ciphers Jan 24 04:21:07 server dovecot[60961]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-acl.conf line 11: Unknown section name: plugin Jan 24 04:22:40 server dovecot[61409]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-acl.conf line 17: Unknown section name: plugin Jan 24 04:23:35 server dovecot[61624]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-plugin.conf line 9: Unknown section name: plugin Jan 24 04:24:40 server dovecot[61932]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-quota.conf line 17: Unknown section name: plugin Jan 24 04:25:38 server dovecot[62301]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-quota.conf line 41: Unknown section name: plugin Jan 24 04:26:12 server dovecot[62335]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-quota.conf line 69: Unknown section name: plugin Jan 24 04:26:42 server dovecot[62550]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-quota.conf line 78: Unknown section name: plugin Jan 24 04:27:05 server dovecot[62582]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve-extprograms.conf line 9: Unknown section name: plugin Jan 24 04:28:11 server dovecot[62819]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin Jan 24 04:29:02 server dovecot[63099]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 39: sieve: Unknown setting: sieve Jan 24 04:36:01 server dovecot[71295]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 39: sieve: Unknown setting: sieve Jan 24 04:39:04 server dovecot[72067]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 40: sieve: Unknown setting: sieve (sieve_script_sieve or sieve_script_personal_sieve not found either.) Jan 24 04:47:39 server dovecot[86665]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: ssl_options: unknown flag: 'no_compression' Jan 24 04:50:51 server dovecot[93375]: doveconf: Fatal: dovecot_storage_version setting must be set Jan 24 05:01:51 server dovecot[105836]: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-mail.conf line 31: mail_location: Unknown setting: mail_location Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107288><SOtYQyBJTOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107288><SOtYQyBJTOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107289><9+pYQyBJTeXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<10Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107288><SOtYQyBJTOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107288><SOtYQyBJTOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107289><9+pYQyBJTeXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:06:18 cjbnew dovecot: imap(bob)<107289><9+pYQyBJTeXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=07557289><9+pYQyBJTeXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:08:38 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:08:38 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:11:10 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:11:10 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:0 mode=0755) Jan 24 05:15:09 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:473 mode=0755) Jan 24 05:15:09 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, dir owned by 0:473 mode=0755) Jan 24 05:18:35 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:18:35 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:19:09 cjbnew dovecot: imap(bob)<122933></apLcSBJaKrAqBTq>: Disconnected: Connection closed (SELECT finished 0.138 secs ago) in=102 out=787 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jan 24 05:19:58 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:19:58 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:20:20 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:20:20 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:21:17 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775) Jan 24 05:21:17 cjbnew dovecot: imap(bob)<107806><1/QbSyBJUOXAqBTz>: Error: Mailbox INBOX: Failed to autocreate mailbox: open(/var/spool/mail/%u) failed: Permission denied (euid=500(bob) egid=100(users) missing +w perm: /var/spool/mail, we're not in group 473(mail), dir owned by 0:473 mode=0775)

12 19

"Synchronization corrupted index header" with mdbox: thousands of deleted e-mails reappeared in INBOX
by Ákos Szőts 17 Feb '26

17 Feb '26

Hi everyone, Suddenly, the following messages appeared in my Dovecot error log: master: Warning: Killed with signal 15 (by pid=0 uid=0 code=kill) Error: Mailbox Trash: Synchronization corrupted index header [...]/Trash/dbox-Mails/dovecot.index: uidvalidity=0, but next_uid=73 Warning: Mailbox Trash: fscking index file [...]/Trash/dbox-Mails/dovecot.index Warning: mdbox([...]/mail/storage): rebuilding indexes: Mailbox Trash index was fsck'd Warning: mdbox([...]/mail/storage): fscking index file [...]/index/inbox/storage/dovecot.map.index Error: Mailbox INBOX: [...]/INBOX/dbox-Mails/dovecot.index reset, view is now inconsistent The first message is because I restarted the container. Since then, Thunderbird shows thousands of previously deleted e-mails again in INBOX where all my messages are marked as unread. - Do you know what can cause it and how can I avoid to happen again? - Is the used mdbox storage engine that fragile? Is the fault tolerance of other engines better? I have a backup from some days ago. Is it possible to somehow revert back to it and sync the new e-mails on top of those? Version: 2.4.2. Thank you, Ákos

2 1

Most relevant documents for 2.4.x config file syntax
by Steve Litt 16 Feb '26

16 Feb '26

Hi all, Some time has gone by, so I'm hoping there's some good documentation for somebody needing syntax help on building a 2.4.x Dovecot. I've seen https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html , but it's not useful to me because I don't know *where* all those various pieces go. Which things go in what curly braces? It doesn't say. https://doc.dovecot.org/2.4.2/core/config/quick.html looks like an excellent starting place. Do you agree? What other *simple* documentation do you recommend? Because I am not and never was a Dovecot expert, I'll need something that does a considerable amount of teaching: A sort of Dovecot 4.2 For Dummies type thing. Thanks, SteveT Steve Litt http://444domains.com

3 4

Configuration upgrade tool
by Aki Tuomi 15 Feb '26

15 Feb '26

Hi! To make migrating from Dovecot 2.3 to 2.4 a bit easier, we are now providing a tool that helps upgrade your existing configuration. The tool allows you to upload either a full dovecot.conf or selected ancillary configuration files from a 2.3 setup, and will attempt to convert them accordingly. You can find the tool here: https://dovecot.org/upgrader/ We do not store any of the configurations processed by the tool, nor do we track who uses it. It's offered as-is, without any warranty or guarantee. If you run into any issues, unexpected results, or have feedback about the tool, please let us know — it’s very much appreciated. Please note that the tool can make mistakes, so we strongly recommend carefully reviewing and testing the output before using it in production. There are currently no plans to release this tool as open source. Regards, Aki Tuomi Open-Xchange oy

11 18

Sdbox/mdbox purge on Public folders
by luke+dovecot＠psy.io 15 Feb '26

15 Feb '26

Hi dovecot mailing list people, After having looked through the mailing list archives, tried various search engines & asked an LLM to hallucinate an answer all to no avail, I now pose the following question to you all: For a Dovecot 2.4 system that uses mail_driver = mdbox for regular mailboxes and also has a public namespace, how might I invoke the maintenance routine of `doveadm purge` against the m.1, m.2 ... m.N files under the mail_path location? Below is the snippet of what I have in the configuration files for the public namespace: namespace public { type = public separator = / prefix = Public/ mail_path = /var/spool/mail/Public mail_index_private_path = ~/public subscriptions = yes mailbox "communal" { auto = subscribe } } Since my dovecot instance is a self-hosted matter, I am in a position to move all mail data out of there, delete any left over storage files and change the mail_driver to Maildir, if that is the easiest way to manage the risk of dbox m file sprawl/growth. Best regards, Luke

2 1

Is there a lint utility for 2.4.x configuration?
by Steve Litt 14 Feb '26

14 Feb '26

Hi all, I use a local Dovecot IMAP server to store all my emails, which I access from either Claws-Mail or Evolution. On 7/7/2025 my email stopped working, a few hours of troubleshooting led to a Dovecot problem, a few more hours led to the 2.3 to 2.4 config file changes, and the next 3 days I went without email while trying to get a working 2.4. Finally I managed to downgrade back to 2.3.x and restore the config from backup, and didn't lose too many emails. I've waited 6 months for all the dust to settle, and now I'm going to try to make a test VM (Void Linux) with 2.4.x, using phony baloney data because I don't want to lose my email capabilities again. So my first question is this: Is there a lint utility for my configuration, so that I can cut down on experimenting with 50 different variables at once and reading conflicting documentation? Here's what I know so far about lint utilities: * I know doveconf -n and dovecot -n dump non-default settings, but I don't think they can detect syntax errors. * dovecot-sysreport doesn't seem to give me info about syntax errors. * None of the doveadm commands seem to check syntax. Thanks, SteveT Steve Litt http://444domains.com

2 3

My plan for a test Dovecot 2.4.2
by Steve Litt 14 Feb '26

14 Feb '26

Hi all, I need to thoroughly test Dovecot 2.4.2 on a Virtual Machine before upgrading my real machine. Please tell me whether you think this plan is good... I install Void Linux, my Daily Driver Distro, on a Qemu VM. I also install Dovecot and Claws-Mail. Then I copy part or all of my current (2.3.21.1 (d492236fa0)) maildir to the VM, and work until I can configure a Dovecot on the VM that serves IMAP only, SSL only (ssl = required on 2.3.x), such that Claws-Mail can read, search and delete messages on the VM just the same as on 2.3.21.1 on my daily driver. I'm using few or no Dovecot features other than using it as a Maildir driven IMAP server. Maildir is a must because I write to it from Procmail, and Procmail doesn't write every kind of mail storage. Does this sound like a good, safe way to test before upgrading? Thanks, SteveT Steve Litt http://444domains.com

1 0

Clean up of dovecot.index.pvt.log files
by Sad Clouds 14 Feb '26

14 Feb '26

Hello, I'm trying to understand how to clean up old dovecot.index.pvt.log files, which are used for per user private \Seen flags. Running "doveadm purge" does not seem to remove them. I have the following public namespace configured: namespace public { type = public separator = / prefix = Public/ inbox = no hidden = no mail_driver = mdbox mail_path = /data/mailstore/%{user|domain|lower}/mail_public/mdbox mail_index_private_path = ~/mdbox/Public.index.pvt # Enable user private \Seen flags list = yes subscriptions = no # Allow users in the 'admin' group to have complete control over the namespace acl group=admin { rights = lrwstipekxa } } The problem is - if the admin deletes a public folder, the old dovecot.index.pvt.log files forever remain in all of the users' home mailbox directories, like tombstones. I see two ways around it: 1. Attempt to store private index files in the original folder's mail path, so when the folder is deleted, all files underneath it are also deleted automatically: mail_path = %{mail_directory}/Public.index.pvt/%{user|domain|lower} However there appears to be no %{mail_directory} variable which would expand to mdbox/mailboxes/<folder_name>/dbox-Mails/ and even if there was one, with public folders, for every user subscribed to this folder, there would be a user-specific directory just for the private index file. This may not scale well with thousands of users. 2. Run a cron script to list all public folders and then compare ~/mdbox/Public.index.pvt directory of each user for stale private index files which refer to non-existent folders. This can probably be done efficiently with commands like find, awk and sed, but it feels a bit cumbersome and arcane. Can anyone suggest any other or better alternatives to solve this issue? Thanks.

1 0

shared mailbox on 2.3 - will I avoid concurrency (mailbox corruption) issues if both users are on the same server
by daniel.botting＠codethink.co.uk 13 Feb '26

13 Feb '26

Hi all, Currently we are running 2.3, with a plan to move to 2.4 later this year. Our current setup is two replicating servers, I have setup on my test servers a shared name space as this is a limited requirement at this time for an assistant to view their managers inbox. I had read here: https://doc.dovecot.org/2.3/configuration_manual/shared_mailboxes/cluster_s… For two or more servers Director is required because (taken from the docs): As mentioned in Director, you can’t have multiple servers accessing the same user at the same time or it will lead into trouble. This can become problematic with shared mailboxes, because two users who are sharing a folder may run in different servers. As this is a limited requirement at this time and we'll be migrating to 2.4 where Director has been removed (I read the Docs that there is an unsupported replacement) if I have both the manager and the assistant only accessing the managers inbox via the same server will I avoid concurrency issues (ie I presume mailbox corruption). Many thanks and have a nice weekend Daniel

1 1

Rebuilding missing index/paths
by Alain Perry 13 Feb '26

13 Feb '26

Hello, First of all, I'm sorry if this isn't the best place to ask for that kind of help, in which case I'd appreciate a pointer to any adequate asynchronous channel. ------------ Some context (skip to next horizontal line if you don't care): I'm happily self-hosting a few services at home. Some months ago I decided I needed to backup my emails to my NAS, in a way that would allow me to read or search them from a web browser as easily as I did with my "cloud" mailboxes. Since I didn't find a modern yet simple webmail that could directly read a Maildir storage, I finally bit the bullet and ran a dovecot container to copy my emails to (using imapsync). Since I opted for an IMAP server, I thought I didn't need to worry too much about the storage format and used the sdbox that (I believe) was the default. Backing up worked and searching worked and I was a happy person. I used my local webmail a couple of times to search for an old email, found it, thought this was a job well done that I wouldn't have to worry too much about anymore. Then, it stopped working. I honestly don't remember what I did around that time that might have broken things or caused a data loss, but IMAP clients couldn't access my emails anymore. Since I had other more urgent matters to address, I let that problem rot. Now that I have a bit more time, I decided to try again. ------------ My problem is that, while it is clear that some data is missing, I have no clue what that data is and how (if ?) I can rebuild it. The folder structure is there in /src/vmail/username/Mail/mailboxes. I do see index(.log) and dbox-Mails/u.* in the folders, so it does look like it conforms to the doc in this regard. However, the paths returned for the mailboxes by "doveadm mailbox path" all use guid's, and do not exist on the filesystem. I don't quite understand how it got to this point, nor what I should have lying around at those paths but I wonder if it is at all possible to rebuild them so I might regain access to my archives. Is there something I can do to recover my emails ? Thanks for reaching this point, and thank you for any help and/or pointers you might be able to provide. Regards,

2 2

History Assignment Writing Help – Expert Assistance
by Theo Wilson 13 Feb '26

13 Feb '26

Struggling with your history assignments? Our History Assignment Writing Help service offers expert guidance to help you craft well-researched, structured, and original assignments. Fill out this form to get personalized support from experienced writers and improve your grades with ease. https://www.newassignmenthelp.co.uk/history-assignment-help

1 0

fts-flatcurve change index location
by grabsoon＠gmail.com 12 Feb '26

12 Feb '26

hi is there any way to change location ONLY FOR flatcurve indexes all I want is to write fts-flatcurve directories outside ~/Maildir path I do not want to change location of: dovecot.list.index.log dovecot.mailbox.log dovecot-uidvalidity Only for flatcurve indexes. when i set mail_index_path = ~/Indexes all indexes are saved to this new location, not just flatcurve i'm afraid that changing mail_index_path value on production environment is very riski Thanks

2 1

Re: 2.4: fts flatcurve remove?
by Michael Slusarz 11 Feb '26

11 Feb '26

> On 02/10/2026 3:07 PM MST Bjoern Franke via dovecot <dovecot(a)dovecot.org> wrote: > > in the pre release docs > https://doc.dovecot.org/main/core/man/doveadm-fts.1.html#fts-flatcurve-remo… > > doveadm fts flatcurve remove > > was mentioned, but in https://doc.dovecot.org/2.4.2/ it's gone. ? https://doc.dovecot.org/2.4.2/core/man/doveadm-fts.1.html#fts-flatcurve-rem…

2 1

2.4: fts flatcurve remove?
by Bjoern Franke 11 Feb '26

11 Feb '26

Hi, in the pre release docs https://doc.dovecot.org/main/core/man/doveadm-fts.1.html#fts-flatcurve-remo… doveadm fts flatcurve remove was mentioned, but in https://doc.dovecot.org/2.4.2/ it's gone. So, how to remove the flatcurve data again? Simply a find ...--delete? Regards Bjoern

1 0

doveadm quota get issue in lcx container
by Kim Haverblad 09 Feb '26

09 Feb '26

Hi, I'm having some issues getting the quota plugin to work properly. Based on the error message, it looks like the plugin doesn't fully cooperate with Proxmox mount points for LXC containers. It appears to be referencing the secondary disk directly as /dev/nvme1n1p1, rather than the actual mount point inside the container. Here's the full error message: mlgate:/usr/lib/systemd/system# doveadm quota get -u [1]some(a)example.com doveadm([2]some(a)example.com): Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, /dev/nvme1n1p1) failed: No such file or directory Are there any parameters that need to be adjusted to make this work, or is there an alternative plugin that would handle this setup better? //Kim

2 1

In an email client, tasks accumulate and are queued using the IMAP protocol
by Lafiel Elentari 08 Feb '26

08 Feb '26

Hello. By default, the email client uses 4 IMAP connections. However, tasks often hang, and changes to email statuses made via the web interface are not reflected in the client. I tried enabling imap-hibernate, which cleared the queue, but the issue with updating email statuses persisted. Is this a problem with the email client or the Dovecot server? -- Best regards, Lafiel Elentari mailto:lafiel@elven.pw

1 0

Configuring the Outbox folder in an email client
by Lafiel Elentari 08 Feb '26

08 Feb '26

Hello. The Bat! email client, when using the IMAP protocol, comes with three pre-defined folders: "Outbox," "Sent Mail," and "Trash." While setting up the "Sent Mail" and "Trash" folders is simple, configuring the "Outbox" folder may be less obvious. How should it be set up? Is it correct to designate the Drafts folder for this purpose? -- Best regards, Lafiel Elentari mailto:lafiel@elven.pw

1 0

doveadm sync panic
by Roberto Puzzanghera 07 Feb '26

07 Feb '26

I am experiencing a consistent panic while using doveadm sync on Dovecot v2.4.2. The panic occurs during a synchronization attempt between two servers. It appears that the sync panics when entering in a .Junk.Something folder. Any idea? I attach the log lines and my configuration Any help would be appreciated Roberto # doveadm -D sync -u postmaster@domain-tld tcp:10.0.0.24:12345 [...] Feb 06 22:39:46 doveadm(postmaster(a)domain.tld): Panic: file hash.c: line 252 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) Feb 06 22:39:46 doveadm(postmaster(a)domain.tld): Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x40) [0x7f7bba941860] -> libdovecot.so.0(backtrace_get+0x22) [0x7f7bba9419b2] -> libdovecot.so.0(+0x14fc12) [0x7f7bba94fc12] -> libdovecot.so.0(+0x14fc41) [0x7f7bba94fc41] -> libdovecot.so.0(+0x72375) [0x7f7bba872375] -> libdovecot.so.0(+0x732c3) [0x7f7bba8732c3] -> doveadm(dsync_mailbox_tree_build_name128_hash+0x9a) [0x55e5f58108ba] -> doveadm(dsync_mailbox_tree_fill+0x750) [0x55e5f5811bb0] -> doveadm(dsync_brain_mailbox_trees_init+0x192) [0x55e5f58055b2] -> doveadm(dsync_brain_master_init+0x191) [0x55e5f5801f51] -> doveadm(+0x3544b) [0x55e5f57e644b] -> doveadm(+0x3794e) [0x55e5f57e894e] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x244) [0x55e5f57e9684] -> doveadm(doveadm_cmdline_run+0x593) [0x55e5f57fd473] -> doveadm(doveadm_cmdline_try_run+0xba) [0x55e5f57fc67a] -> doveadm(main+0x2fd) [0x55e5f57dacfd] -> libc.so.6(__libc_start_main+0xcd) [0x7f7bba4fd03d] -> doveadm(_start+0x2a) [0x55e5f57db0ea] # doveconf -n # 2.4.2 (): /usr/local/dovecot/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.15.3 x86_64 Slackware 15.0 # Hostname: qt dovecot_config_version = 2.4.2 auth_allow_cleartext = yes auth_allow_weak_schemes = yes auth_default_domain = mydomain.tld auth_mechanisms = plain login auth_socket_path = ../../../var/run/dovecot/auth-userdb debug_log_path = /var/log/dovecot/dovecot.log default_login_user = vpopmail doveadm_password = # hidden, use -P to show it dovecot_storage_version = 2.4.2 first_valid_gid = 89 first_valid_uid = 89 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = mydomain.tld last_valid_gid = 89 last_valid_uid = 89 listen { * = yes :: = no } log_debug = category=mail log_path = /var/log/dovecot/dovecot.log mail_access_groups = 89 mail_driver = maildir mail_gid = 89 mail_path = ~/Maildir mail_plugins { notify = yes fts = no fts_solr = no quota = yes } mail_privileged_group = 89 mail_uid = 89 mailbox_list_validate_fs_names = no passdb_default_password_scheme = SHA512-CRYPT postmaster_address = postmaster(a)mydomain.tld protocols { imap = yes pop3 = yes sieve = yes } sendmail_path = /var/qmail/bin/sendmail sql_driver = mysql ssl_min_protocol = TLSv1.1 passdb sql { query = SELECT CONCAT(vpopmail.pw_name, '@', vpopmail.pw_domain) AS user, vpopmail.pw_passwd AS password, vpopmail.pw_dir AS userdb_home, 89 AS userdb_uid, 89 AS userdb_gid, CONCAT(REPLACE(SUBSTRING_INDEX(vpopmail.pw_shell, 'S', 1), 'NOQUOTA', '0'), 'B') AS userdb_quota_storage_size FROM vpopmail LEFT JOIN aliasdomains ON aliasdomains.alias='%{user | domain}' LEFT JOIN limits ON limits.domain='%{user | domain}' WHERE vpopmail.pw_name='%{user | username}' AND (vpopmail.pw_domain='%{user | domain}' OR vpopmail.pw_domain=aliasdomains.domain) AND ('%{local_port}'!='995' OR !(vpopmail.pw_gid & 2)) AND ('%{remote_ip}'!='10.0.0.4' OR !(vpopmail.pw_gid & 4)) AND ('%{remote_ip}'='10.0.0.4' OR '%{local_port}'!='993' OR !(vpopmail.pw_gid & 8)) AND ('%{remote_ip}'!='10.0.0.4' OR COALESCE(disable_webmail,0)!=1) AND ('%{remote_ip}'='10.0.0.4' OR COALESCE(disable_imap,0)!=1) } userdb prefetch { driver = prefetch } userdb sql { iterate_query = SELECT CONCAT(pw_name,'@',pw_domain) AS user FROM vpopmail query = SELECT vpopmail.pw_dir AS home, 89 AS uid, 89 AS gid, CONCAT(REPLACE(SUBSTRING_INDEX(vpopmail.pw_shell, 'S', 1), 'NOQUOTA', '0'), 'B') AS quota_storage_size FROM vpopmail WHERE vpopmail.pw_name='%{user | username}' AND vpopmail.pw_domain='%{user | domain}' } namespace inbox { inbox = yes mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { autoexpunge = 30d special_use = "\\Junk" } mailbox Junk.TeachSpam { auto = subscribe autoexpunge = 30d } mailbox Junk.TeachNotSpam { auto = subscribe autoexpunge = 30d } mailbox Trash { autoexpunge = 60d special_use = "\\Trash" quota_storage_extra = 100M } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } protocol !indexer-worker { mail_vsize_bg_after_count = 100 } maildir { broken_filename_sizes = yes } service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service imap { executable = imap postlogin } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login ../../etc/scripts/dovecot_postlogin.sh user = vpopmail unix_listener postlogin { group = vchkpw mode = 0660 user = vpopmail } } service auth { user = $SET:default_internal_user unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service auth-worker { user = $SET:default_internal_user } service stats { unix_listener stats-reader { group = vchkpw mode = 0660 user = vpopmail } unix_listener stats-writer { group = vchkpw mode = 0660 user = vpopmail } } protocol lda { mail_plugins { sieve = yes mail_log = yes } } protocol imap { mail_plugins { notify = yes mail_log = yes imap_sieve = yes imap_quota = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol pop3 { mail_plugins { notify = yes mail_log = yes } } language en { default = yes } quota "User quota" { driver = count storage_grace = 10M quota_warning overquota { quota_storage_percentage = 100 execute quota-warning { args = 100 %{user} } } quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-85 { quota_storage_percentage = 85 execute quota-warning { args = 85 %{user} } } } service quota-warning { executable = script ../../etc/scripts/quota-warning.sh user = vpopmail unix_listener quota-warning { group = vchkpw mode = 0660 user = dovenull } } sieve_script personal { active_path = ~/.sieve/dovecot.sieve driver = file path = ~/.sieve } sieve_script move-spam { cause = delivery path = /usr/local/dovecot/etc/sieve/move-spam.sieve type = before } mysql 10.0.0.112 { dbname = vpopmail_test password = # hidden, use -P to show it user = vpopmail_test } ssl_server { cert_file = /etc/ssl/certs/dovecot.pem key_file = /etc/ssl/private/dovecot.pem }

2 1

About mail_inbox_path and mail location
by Aki Tuomi 06 Feb '26

06 Feb '26

Hi! We've been noticing that many people are configuring mail_inbox_path. I assume that for most people this is because debian decided to include it in their default config, so that it would use /var/mail boxes for user INBOXes. If your inbox *does not* reside in some weird location, you should *not* set this setting to any value, instead you can either ensure it's commented out, or set to empty value. IN PARTICULAR, IT IS **NOT** REQUIRED SETTING. Setting it to some random weird value like '.' will just cause Problems, setting it to $MAIL_HOME/ or something else will just be either pointless or cause problems. Some most common conversions (please adjust to your environment) mail_home= /home/vmail/%u => mail_home = /home/vmail/%{user} mail_home = /home/vmail/%d/%u => mail_home = /home/vmail/%{user|domain}/%{user|username} or some variant of this. mail_location = maildir:~/ => mail_path = ~/ mail_driver = maildir mail_location = maildir:/var/srv/foo/%d/%u => mail_path = /var/srv/foo/%{user|domain}/%{user|username} mail_driver = maildir In addition you might want to convert INDEX=~/.index => mail_index_path=~/.index CONTROL=~/.control => mail_control_path=~/.control LAYOUT=fs => mailbox_list_layout=fs A minimal working config is mail_home=/home/vmail/%{user} mail_driver=maildir mail_path=~/maildir mail_uid=vmail mail_gid=vmail ## If you have settings like namespace other { location = maildir:/foo/bar } this converts into namespace other { mail_path = /foo/bar # optional, if this is matches your top level mail_driver = maildir } Hope this clears out some of the confusion. Aki

3 4

Pigeonhole 2.4.2 build failure: cannot find -ldovecot-ldap even without LDAP support
by adesh＠backuply.com 04 Feb '26

04 Feb '26

I'm building Pigeonhole 2.4.2 (fresh tarball from https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: > > CC ext-fileinto.lo > CC ext-reject.lo > ... > CC sieve.lo > CCLD libdovecot-sieve.la > /opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: cannot find -ldovecot-ldap > collect2: error: ld returned 1 exit status > make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1 NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no Confirmed no openldap-devel influencing detection (or temporarily removed) Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot.

1 0

How to let postfix use dovecot to check quotas for virtual aliases
by jerome＠jolimont.fr 04 Feb '26

04 Feb '26

Hi all. Receiving an email for an alias, I got those errors: <alias(a)domain.tld>Recipient address rejected: Unknown user; I realized this happened when postfix queries dovecot about user quota. Basically, what happens is that postfix queries dovecot using the virutal alias as name, not the virtual user. And since dovecot doesn't find a user under that name, it returns an error and postfix rejects the mail. ### Configuration I followed the docs at https://doc.dovecot.org/latest/core/plugins/quota.html when setting up the server. /etc/postfix/main.cf ``` smtpd_recipient_restrictions = check_policy_service unix:private/quota-status ``` /etc/dovecot/conf.d/90-quota.conf ``` service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { user = postfix } client_limit = 1 } ``` /etc/dovecot/conf.d/auth-sql.conf.ext ``` userdb sql { query = SELECT '/var/mail/vmail/'||maildir AS home, 110 AS uid, 113 AS gid, quota || 'B' AS quota_storage_size FROM mailbox WHERE username = '%{user}' iterate_query = SELECT username FROM mailbox } ``` ### Solution 1: modify user query This issue was reported and analyzed here: https://dovecot.dovecot.narkive.com/FtjhqCuU/postfix-aliases-with-quota-sta… and there: https://github.com/docker-mailserver/docker-mailserver/issues/2091 A comment (https://dovecot.dovecot.narkive.com/FtjhqCuU/postfix-aliases-with-quota-sta…) suggests to modify the SQL query to also look for aliases. I modified my query like so: ``` query = SELECT '/var/mail/vmail/'||maildir AS home, 110 AS uid, 113 AS gid, quota || 'B' AS quota_storage_size FROM mailbox JOIN alias ON mailbox.username = alias.goto WHERE alias.address = '%{user}'; ``` and it seemed to work. I mean, I can query user quota with an alias: doveadm quota get -u alias(a)domain.tld but the iterate query ignores aliases so doveadm quota get -A only lists users, not aliases (which is what I want) and I can't IMAP login using aliases (which is also what I want) since I didn't modify the password query either. I find this configuration slightly inconsistent: the user query returns aliases, not the iterate query. Is the user query really meant to return aliases as well? Also, I realized this query is broken for alias to multiple addresses. I'd get the following error: Recipient address rejected: Unknown user Surprisingly, it seems to only affect messages from an external source to an alias pointing to an external mailbox. Messages submitted locally (and perhaps messages sent to an alias to local destinations only, I'm not sure) were not affected. ### Solution 2: ignore aliases, it will fail later anyway On another server, I had this configuration: /etc/dovecot/conf.d $ vi 90-quota.conf (Don't put this in `plugin` on dovecot 2.4+.) ``` plugin { quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" } ``` The alias is unknown so the check returns DUNNO and postfix lets the message pass (postfix log read "delivered via spamassassin service") but then it fails at sieve stage when writing the message: sieve: msgid=<xxx>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) The result is what is expected: the message is rejected due to mailbox full. But I don't think it was intended to work this way. And since the message is quota-rejected at sieve stage, I could remove the `check_policy_service` line since it will be rejected for a virtual user (not alias) as well anyway. Right? ### Question What is the recommended configuration to let postfix use dovecot to check quotas for virtual aliases? I couldn't find documentation for this specific use case. Ideally, postfix would query using the resolved user, not the alias. Can this be achieved? Should I remove the check and rely on the fact that writing the message fails at a later step anyway? Thanks. (Question also posted on ServerFault: https://serverfault.com/questions/1197914/how-to-let-postfix-use-dovecot-to…)

3 3

Question about behavior I wound up patching 2.4 to fix
by Andy Baugh 03 Feb '26

03 Feb '26

Howdy, I had a complaint from RoundCube users that the maildir quotas weren't accurate when they logged in after something wound up deleting their maildirsize file on Dovecot 2.4. Since that does IMAP GETQUOTAROOT to fetch the info, I figured we're probably not triggering quota recalculation on maildir like we did on dovecot 2.3 (which doesn't seem to have this issue). Wound up writing a patch to src/plugins/imap-quota/imap-quota-plugin.c to add a hook into cmd_setquota which looks to see if imap_quota is enabled, and if so trigger maildir quota recalculation on IMAP login. This does work to solve the reported issue, but I'm ultimately more curious whether this could even be considered a regression, as per your own documentation for the quota plugin: > Once the maildirsize reaches 5120 bytes, the quota is recalculated and the file is recreated. This makes sure that if quota happens to be broken (e.g. externally deleted files) it won't stay that way forever. This suggests to me that the behavior I'm "fixing" a regression in is actually working "as designed." As such my question would be: Is there a good reason I *should not* be doing this? I would of course be happy to share this patch with the list, but I'm not going to bother if it's actually something the maintainers are not interested in due to it not being a good idea in the first place. Thanks, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

1 0

Unexpected Configuration Error `Unknown setting: ssl_server_cert_file`
by David Weingut 02 Feb '26

02 Feb '26

Hello, I upgraded from Debian 12 to 13 and thereby also from dovecot 2.3 to 2.4. Now I am facing a weird error in dovecot. The actual error is the following # doveconf -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 22: ssl_server_cert_file : Unknown setting: ssl_server_cert_file The corresponding entry in my config is ssl = yes ssl_server_cert_file = /etc/letsencrypt/live/example.com/fullchain.pem ssl_server_key_file = /etc/letsencrypt/live/example.com/privkey.pem I am sorry if I missed something in the archives but I did not find any similar posts. Is there something I am missing here and what would be further required to debug this? Best, David Hello, I upgraded from Debian 12 to 13 and thereby also from dovecot 2.3 to 2.4. Now I am facing a weird error in dovecot. The actual error is the following # doveconf -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 22: ssl_server_cert_file : Unknown setting: ssl_server_cert_file The corresponding entry in my config is ssl = yes ssl_server_cert_file = /etc/letsencrypt/live/example.com/fullchain.pem ssl_server_key_file = /etc/letsencrypt/live/example.com/privkey.pem I am sorry if I missed something in the archives but I did not find any similar posts. Is there something I am missing here and what would be further required to debug this? Best, David

2 3

Compiling Dovecot 2.4 on OpenBSD
by Joel Mawhorter 02 Feb '26

02 Feb '26

I'm writing to see if anyone has had success compiling Dovecot 2.4 on OpenBSD. I can't seem to find any documentation that lists prerequisites. At the moment, the 2.4.2 source tarball from the Dovecot site does not seem to compile on my OpenBSD 7.8 system and the error message is not very helpful. I'm unsure if this is just a problem of some required package not being installed. If anyone could point me to info to help move forward, I would appreciate that. Joel

6 19

How can these MBOX files on a Dovecot-based IMAP server be converted to PST for access in Outlook?
by Rawnie Dolgato 31 Jan '26

31 Jan '26

MBOX files stored on a Dovecot-based IMAP server cannot be accessed directly in Microsoft Outlook, because Outlook does not support the MBOX file format. Outlook works with PST files, so a conversion step is mandatory. While it is technically possible to convert MBOX files to EML and then import them into Outlook, this approach is impractical for real-world scenarios. It is time-consuming, difficult to manage, and not suitable when handling bulk mailboxes or large datasets, which is typically the case with server-level backups. For this reason, an MBOX to PST conversion tool (such as BitRecover MBOX to PST Converter) is recommended. It supports bulk MBOX data, preserves folder structure and metadata, and allows selective migration based on criteria like date, sender, or subject. The process runs 100% offline, ensuring data security, and works on Windows, macOS, and Linux, making it suitable for both single and multi-mailbox migrations.

2 1

Meaning of auth-worker disconnected message and relation to LMTP 451 errors on Ubuntu
by Kim Haverblad 31 Jan '26

31 Jan '26

Hi dovecot list, I’m troubleshooting an LMTP delivery issue with Dovecot and would appreciate clarification on the meaning and impact of the following log message, which appears repeatedly during delivery attempts: auth-worker(2961): Debug: conn unix:auth-worker (pid=2948,uid=107): Disconnected: Connection closed (fd=-1) *Environment* * OS: Ubuntu (latest LTS, fully up to date) * Dovecot: distribution package (current version for Ubuntu) * MTA: Postfix * Delivery: LMTP to Dovecot * User database: MySQL (userdb lookup succeeds) * Mail storage: Maildir * Quotas: enabled via userdb (quota_rule) *Context* * LMTP accepts the recipient and completes userdb lookup successfully. * The mailbox path, uid, gid, and quota are correctly returned. * Postfix later receives a 451 4.3.0 Temporary internal error after the DATA phase. * The above auth-worker ... Disconnected: Connection closed (fd=-1)message appears around the same time. *Questions* 1. Is this Disconnected: Connection closed (fd=-1) message expected/normal behavior for auth-worker processes once a lookup is complete? 2. Under what circumstances would this indicate a real problem versus a harmless connection teardown? 3. Could this message itself contribute to, or explain, LMTP 451 4.3.0 Temporary internal error responses? 4. Are there specific auth-worker, LMTP, or debug settings recommended to determine whether this disconnect is abnormal? So far, authentication and userdb lookups appear clean, and there are no explicit permission or quota errors logged, which makes it unclear whether this message is relevant to the delivery failure or simply informational. Any clarification on how to interpret this log entry — and how to confirm whether it is benign or problematic — would be greatly appreciated. Kind Regards, Kim Hi dovecot list, I'm troubleshooting an LMTP delivery issue with Dovecot and would appreciate clarification on the meaning and impact of the following log message, which appears repeatedly during delivery attempts: auth-worker(2961): Debug: conn unix:auth-worker (pid=2948,uid=107): Disconnected: Connection closed (fd=-1) Environment o OS: Ubuntu (latest LTS, fully up to date) o Dovecot: distribution package (current version for Ubuntu) o MTA: Postfix o Delivery: LMTP to Dovecot o User database: MySQL (userdb lookup succeeds) o Mail storage: Maildir o Quotas: enabled via userdb (quota_rule) Context o LMTP accepts the recipient and completes userdb lookup successfully. o The mailbox path, uid, gid, and quota are correctly returned. o Postfix later receives a 451 4.3.0 Temporary internal error after the DATA phase. o The above auth-worker ... Disconnected: Connection closed (fd=-1) message appears around the same time. Questions 1. Is this Disconnected: Connection closed (fd=-1) message expected/normal behavior for auth-worker processes once a lookup is complete? 2. Under what circumstances would this indicate a real problem versus a harmless connection teardown? 3. Could this message itself contribute to, or explain, LMTP 451 4.3.0 Temporary internal error responses? 4. Are there specific auth-worker, LMTP, or debug settings recommended to determine whether this disconnect is abnormal? So far, authentication and userdb lookups appear clean, and there are no explicit permission or quota errors logged, which makes it unclear whether this message is relevant to the delivery failure or simply informational. Any clarification on how to interpret this log entry -- and how to confirm whether it is benign or problematic -- would be greatly appreciated. Kind Regards, Kim

2 4

sieve auto-creation/subscription - Thunderbird cannot re-arrange folders
by listy 31 Jan '26

31 Jan '26

Hi guys. In Thunderbird auto-subscribed folders - in my case a path with sub-folders - cannot be moved around, meaning top-bottom order. Parent folders Thunderbird shows in cursive and sub-folders (targets for sieve fules) are shown "normal" It seems impossible to re-arrange top/parent folders - but every other folder, top or not, which is not auto created & auto subscribed, Thunderbird can move around as expected. Anybody seen, anybody knows this and knows a way to "fix" it? many thanks, L.

2 4

How can these MBOX files on a Dovecot-based IMAP server be accessed in Outlook?
by Rawnie Dolgato 31 Jan '26

31 Jan '26

MBOX files stored on a Dovecot-based IMAP server cannot be accessed directly in Microsoft Outlook, because Outlook does not support the MBOX file format. Outlook works with PST files, so a conversion step is mandatory. While it is technically possible to convert MBOX files to EML and then import them into Outlook, this approach is impractical for real-world scenarios. It is time-consuming, difficult to manage, and not suitable when handling bulk mailboxes or large datasets, which is typically the case with server-level backups. For this reason, an MBOX to PST conversion tool (such as BitRecover MBOX to PST Converter) is recommended. It supports bulk MBOX data, preserves folder structure and metadata, and allows selective migration based on criteria like date, sender, or subject. The process runs 100% offline, ensuring data security, and works on Windows, macOS, and Linux, making it suitable for both single and multi-mailbox migrations.

1 0

Subscriptions file broken in 2.4.x against 2.3.21 (V2)
by DaLiV 31 Jan '26

31 Jan '26

Hello! /eror at update from 2.3.21 to 2.4.2 / Maildir+ currently is broken. posix - so main hierarchy separator is "/" for file "subscriptions" in versions 2.4 lost possibility to recognize v2 format also as writes v1 instead with header V2 ... so all users will lost their subscriptions and must re-subscribe depsite in folder persist file in format V2 (tab separated) ... on subscribe that appends subscriptions delimeted with "/" namespace Public { type = public prefix = Public/ mail_driver = maildir mail_path = /var/mail/Public/%{auth_user|domain}/ mail_index_private_path = pvt.idx/Public mailbox_list_layout=fs separator = / subscriptions = no list = children } seems not taking in account separators and using "." instead of "/" slighlz debugged - in subsfile_set_subscribed - that gets on subscription for processing : "name"="Public/TEST" but "separator" = "." therefore splits not and decides that is version "0" ... so - somewhere deeper or possible need additional configuration Hello! eror at update from 2.3.21 to 2.4.2 Maildir+ currently is broken. posix - so main hierarchy separator is "/" for file "subscriptions" in versions 2.4 lost possibility to recognize v2 format also as writes v1 instead with header V2 ... so all users will lost their subscriptions and must re-subscribe depsite in folder persist file in format V2 (tab separated) ... on subscribe that appends subscriptions delimeted with "/" namespace Public { type = public prefix = Public/ mail_driver = maildir mail_path = /var/mail/Public/%{auth_user|domain}/ mail_index_private_path = pvt.idx/Public mailbox_list_layout=fs separator = / subscriptions = no list = children } seems not taking in account separators and using "." instead of "/" slighlz debugged - in subsfile_set_subscribed - that gets on subscription for processing : "name"="Public/TEST" but "separator" = "." therefore splits not and decides that is version "0" ... so - somewhere deeper or possible need additional configuration

1 0

New Member
by Jochen Becker 30 Jan '26

30 Jan '26

Hi all My name is Jochen and I have joined the list in order to get some first hand advice on my journey of migrating my SOHO mail server from 2.3 to 2.4. I set up my first server back in 2005 or so. OpenSuse and Cyrus IMAP. That went fine until all of a sudden, some 8 or 10 years ago, Suse no longer supported Cyrus directly. So I switched over to Dovecot and did not regret it. My current production server (OpenSuse Leap 16, Dovecot 2.4.2) is running fine after a recent migration. But the HW is ageing and disk usage is getting close to 80%. So I got new and larger HW. I run OpenSuse Leap 16.0 and Dovecot 2.4.2 on it. As I ran into unsurmountable problems there (could not move mail_path away from /var/mail), I decided to set up a test system under Ubuntu server 25.10. There I have got Dovecot running much better, but still, I ran into problems I could not solve for quite some time now. So here I am. I will start with questions about Dovecot on Ubuntu - my test system - because there I hope my mistakes are not as bad. Aki, thanks for taking me on board. Kind regards Jochen Mainz, Germany

2 1

Re: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Jeffrey Böhm 29 Jan '26

29 Jan '26

Hi, I’m seeing the same issue after upgrading to Dovecot 2.4.2. I reproduced it with both the Alpine Linux build and the official Dovecot Docker image referenced at [1]. In my case, the crash correlates strongly with iOS devices auto-deleting older messages from the Trash folder. As Christian described, it starts after a larger number of IMAP MOVE operations. Key finding: when I disable the imap_sieve extensions, the crashes stop. Personal Sieve rules continue to work as expected, so the problem appears to be specific to imap_sieve (or its interaction with frequent MOVE operations). > sieve_plugins { > sieve_imapsieve = no > } > > protocol imap { > mail_plugins { > imap_sieve = no > imap_filter_sieve = no > } > } My configuration with the enabled imap_sieve extension is located at [2]. Kind regards Jeff [1]: https://github.com/dovecot/docker [2]: https://github.com/jeboehm/docker-mailserver/blob/7433443ebd4af1c422cb4030c…

1 0

Migration to 2.4: Howto get the quota dict writing into a second DB
by volker.jaenisch＠inqbus.de 29 Jan '26

29 Jan '26

Dear Dovecot wizards! I have a question concerning the migration from 2.3.4 to 2.4.1. On 2.3.4 I had the following config dict { sql_store_user_quota = pgsql:/etc/dovecot/dovecot-sql-store-user_quota.conf } With /etc/dovecot/dovecot-sql-store-user_quota.conf: connect = host=127.0.0.1 port=5433 dbname=dddd user=uuuu password=pppp: map { pattern = priv/quota/storage table = fill_user username_field = username value_field = bytes } map { pattern = priv/quota/messages table = messages_user username_field = username value_field = messages } On 2.4.1 I tried dict_map priv/quota/storage { sql_table = emailaddress_fill username_field = emailaddress dict_map_value_field quota_bytes { type = uint } } dict fill { sql_driver = pgsql pgsql pg_mc2 { parameters { dbname = dddd host = hhhh password = ppppp user = uuuuu } } } But it is doing nothing. Am sure I am missing something here (I guess howto connect these config snippets). Any help appreciated. Cheers, Volker -- =========================================================== inqbus Scientific Computing GmbH Dr. Volker Jaenisch Hungerbichlweg 3 +49 (8860) 9222 7 92 86977 Burggen https://inqbus.de ===========================================================

4 8

Pigeonhole 2.4.2 build failure: cannot find -ldovecot-ldap even without LDAP support
by Adesh 29 Jan '26

29 Jan '26

Hi, I'm building Pigeonhole 2.4.2 (fresh tarball from https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: > _CC ext-fileinto.lo_ > _CC ext-reject.lo_ > _..._ > _CC sieve.lo_ > _CCLD libdovecot-sieve.la_ > _/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: > cannot find -ldovecot-ldap_ > _collect2: error: ld returned 1 exit status_ > _make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1_ NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: * make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no * Confirmed no openldap-devel influencing detection (or temporarily removed) * Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot. -- Thanks and Regards, Adesh Rane Hi, I'm building Pigeonhole 2.4.2 (fresh tarball from [1]https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.…) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: CC ext-fileinto.lo CC ext-reject.lo ... CC sieve.lo CCLD libdovecot-sieve.la /opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: cannot find -ldovecot-ldap collect2: error: ld returned 1 exit status make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1 NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: o make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no o Confirmed no openldap-devel influencing detection (or temporarily removed) o Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot. -- Thanks and Regards, Adesh Rane References Visible links 1. https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz

1 0

Bug-Report config handling with named filters
by Patrick Cernko 27 Jan '26

27 Jan '26

Hello Dovecot devs, I think I found a bug in Dovecot's config handling. The semantic of e.g. ssl_server { cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem key_file = /etc/ssl/private/ssl-cert-snakeoil.key } in a config file is slightly different to ssl_server_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_server_key_file = /etc/ssl/private/ssl-cert-snakeoil.key If the directives are used in the second (flat) format, they can be overridden by doveadm (or the sieve* binaries), if the first (structured) version is used, they cannot be overridden. Even if the flat format is used in a "local" config file to override the default config as installed by the CE Debian package (which uses the structured), overriding the value of ssl_server_key_file on the doveadm cmdline is not possible. This prevents unprivileged users to use doveadm or the sieve* binaries as they cannot the tools will fail with an access error for the key file, even if the users knows and uses "-o ssl_server_key_file=''" or "-o ssl_server/key_file=''". I did not test overriding other settings in structured format, but I assume, that the issue is also present there. That means, settings that are specified in the structured format CANNOT be overridden with the "-o" cmdline option. I would like to ask you, to fix this issue in one of the next releases, please! Best regards, P.S.: It would be nice, if doveconf would also get a "-o" option to test overrides. -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Scientific IT and Technical Service Max-Planck-Institute für Informatik & Softwaresysteme

1 0

mountpoint.c:264:33: error: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration]
by Andrew Watkins 27 Jan '26

27 Jan '26

Hello, I am trying to build dovecot-2.4.2 on Solaris 11.4 with gcc 14.2 and getting the following error: CC module-dir.lo CC mountpoint.lo mountpoint.c: In function ‘mountpoint_iter_next’: mountpoint.c:264:33: error: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration] 264 | iter->mnt.dev = makedev(ent.ext.mnt_major, ent.ext.mnt_minor); | ^~~~~~~ *** Error code 1 The following command caused the error: echo " CC " mountpoint.lo;/bin/sh ../../libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -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 -MT mountpoint.lo -MD -MP -MF .deps/mountpoint.Tpo -c -o mountpoint.lo mountpoint.c make: Fatal error: Command failed for target `mountpoint.lo' Current working directory /var/tmp/dovecot-2.4.0/src/lib *** Error code 1 I have been using dovecot for a long time and haven't seen this before. I just checked and rebuilt dovecot-2.3.21 and had no problems. Any ideas? Thanks, Andrew Hello, I am trying to build dovecot-2.4.2 on Solaris 11.4 with gcc 14.2 and getting the following error: CC module-dir.lo CC mountpoint.lo mountpoint.c: In function `mountpoint_iter_next': mountpoint.c:264:33: error: implicit declaration of function `makedev' [-Wimplicit-function-declaration] 264 | iter->mnt.dev = makedev(ent.ext.mnt_major, ent.ext.mnt_minor); | ^~~~~~~ *** Error code 1 The following command caused the error: echo " CC " mountpoint.lo;/bin/sh ../../libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -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 -MT mountpoint.lo -MD -MP -MF .deps/mountpoint.Tpo -c -o mountpoint.lo mountpoint.c make: Fatal error: Command failed for target `mountpoint.lo' Current working directory /var/tmp/dovecot-2.4.0/src/lib *** Error code 1 I have been using dovecot for a long time and haven't seen this before. I just checked and rebuilt dovecot-2.3.21 and had no problems. Any ideas? Thanks, Andrew

2 5

Blocking with RBLs
by Lefteris Tsintjelis 27 Jan '26

27 Jan '26

Hi, Is there a way to block with RBLs? I already have a really good and very trustworthy and accurate internal one that works extremely well and fast with my SMTP servers for years now. Is there a way to apply the same RBL to dovecot? Logs are really going crazy as they stopped with SMTP and started with IMAP for a while now since dovecot is wide open to these attacks. Anvil does not seem to do much here. I am looking for solutions other than fail2ban or anything similar to this. Lefteris

11 26

Possible Bug: Dovecot LDAP userdb search ignores DN template
by Esteban Heschung 25 Jan '26

25 Jan '26

Hello Dovecot Team, I am currently using *Dovecot 2.4.1* with *Windows Active Directory* via LDAPS (self-signed certificate). I have configured a *bind DN template* for authentication. Authentication works perfectly. However, when Dovecot tries to perform the *userdb lookup*, it seems to *ignore the DN template*. Instead, it attempts to perform a search using the *ldap_base and filter* I configured... According to the documentation, the *bind DN template should be sufficient*, and Dovecot should not need to perform this search. Additionally, if I *remove the ldap_base or filter fields*, Dovecot fails with an error and cannot perform the lookup at all. This results in doveadm user failing, even though authentication succeeds. Could this be a bug in the way Dovecot handles bind_userdn for LDAP userdb lookups? I would appreciate any guidance or confirmation on this behavior. Thank you for your help. Hello Dovecot Team, I am currently using Dovecot 2.4.1 with Windows Active Directory via LDAPS (self-signed certificate). I have configured a bind DN template for authentication. Authentication works perfectly. However, when Dovecot tries to perform the userdb lookup, it seems to ignore the DN template. Instead, it attempts to perform a search using the ldap_base and filter I configured... According to the documentation, the bind DN template should be sufficient, and Dovecot should not need to perform this search. Additionally, if I remove the ldap_base or filter fields, Dovecot fails with an error and cannot perform the lookup at all. This results in doveadm user failing, even though authentication succeeds. Could this be a bug in the way Dovecot handles bind_userdn for LDAP userdb lookups? I would appreciate any guidance or confirmation on this behavior. Thank you for your help.

3 5

YESCRYPT_COST_FACTOR=11 not working
by Matthias Bodenbinder 25 Jan '26

25 Jan '26

Hi, dovecot does not work with ENCRYPT_METHOD YESCRYPT and YESCRYPT_COST_FACTOR=11. I have tested with 2.4.2-4 and 2.3.21.1-4 on endeavouros. When changing YESCRYPT_COST_FACTOR to 11 in /etc/login.defs and recreacting the user password for my user and restarting the dovecot service I get: # doveadm auth test matthias Password: passdb: matthias auth failed extra fields: user=matthias When reverting the change to YESCRYPT_COST_FACTOR=5 it works again: # doveadm auth test matthias Password: passdb: matthias auth succeeded extra fields: user=matthias I have tested this back and forth. The culprit is definitely a high value for YESCRYPT_COST_FACTOR. A value of 7 is still good but a value of 9 or 11 fails. Matthias

4 11

Has anyone ever managed to link their AD to Dovecot?
by ByteWave 25 Jan '26

25 Jan '26

Are there any Dovecot configuration examples for linking an Active Directory? The documentation doesn't mention it, and my configuration only works for IMAP authentication; for some unknown reason, the user is then not found...

2 4

Question about mail_utf8_extensions on Dovecot 2.4
by Andy Baugh 25 Jan '26

25 Jan '26

Is there a reason this isn't enabled by default other than perhaps compatibility with very old systems/clients? This sounds like a pretty useful feature if I'm understanding it correctly, and there already were enough new breaking changes with 2.4 that I don't see much downside to making this the default behavior there. What am I missing? Thanks, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

3 4

Issue connecting Windows AD ↔ Dovecot via LDAPS
by heschung.esteban＠gmail.com 24 Jan '26

24 Jan '26

Hello, I’m trying to connect my Windows Active Directory to Dovecot 2.4.1 via LDAPS with a self-signed certificate. Authentication works correctly using the template method. I’m using a DN template for the bind DN. The ldap_base and passdb_ldap_filter field is present in my config because its required, otherwise it doen't work, maybe a internal requirement. Authentication succeeds, but sending mail fails. ldap_uris = ldaps://gr4.lan ldap_base = cn=Users,dc=gr4,dc=lan ssl_client_require_valid_cert = no # self-signed certificate passdb { driver = ldap passdb_ldap_filter = (objectClass=*) passdb_ldap_bind = yes bind_userdn = cn=%{user},cn=Users,dc=gr4,dc=lan } userdb { driver = static args = uid=vmail gid=vmail } So, the command doveadm auth test user@domain work but not doveadm user user@domain The issue in on Debian 13. Also i have print a doveadm -Dv user pol(a)gr4.lan root@deb13:/etc/dovecot/conf.d/ doveadm-Dv user pol(a)gr4.lan Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib1@_doveadm_acl plugin.so: undefined symbol: acl_user_moc ule (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/11b10_doveadm_quota_plugin.so: undefined symbol: quota_us er module (this is usually Intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/1ib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_ rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined syn bol: fts flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadn/libdoveadm_mail_crypt_plugin.so: undefined symbol: c rypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 24 18:51:29 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libie_doveadm_acl_plugin.so: undefined symb ol: acl user module (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Skipping nodule doveadm_quota_plugin, because diopen() failed: /usr/lib/dovecot/modules/doveadm/lib1(a)_doveadm_quota_plugin.so: undefined this message) symbol : quota_user_module (this is usually intentional, so just ignore Jan 24 18:51:29 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symb Fol: fts backend_rescan (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.s o: undefined symbol: fts flatcurve_user_module (this is usually intentional, so just ignore this message) Skipping module doveadm_mail_crypt plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: und Jan 24 18:51:29 Debug: ef ined symbol: crypt_acl_setting_parser info (this is usually intentional, so just ignore this message) // this is normal Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: userdb lookup (pol@gr4, lan): Started userdb lookup Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777>>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=e): Client connected (fd=9) Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=0): auth input: //why its empty ??? on passwd file its not Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>: Error: auth-master: userdb lookup(pol(a)gr4.lan): Auth USER Lookup failed //help ! Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: userdb lookup(polegr4.lan): auth USER Input: Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>>: Debug: auth-master: userdb lookup(pol(a)gr4.lan): Userdb lookup failed userdb lookup: Internal error occurred. Refer to server log for more information. Jan 24 18:51:35 Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=0): Disconnected: Connection closed (fd=9) field value Thank for help.

3 5

Help with migration to dovecot 2.4
by Richard 23 Jan '26

23 Jan '26

Hi, I've just migrated our mail server from Debian 12 to 13. With this, dovecot was upgraded to v2.4. I was previously aware of the new config schema, but it seems the documentation wasn't enough to make the transition that smooth. I'm encountering several issues where I'd need some assistance: I have issues with message sizes not fitting: Jan 22 19:16:04 imap(user)<82612><thWtCP5I7OuGPXzg>: Error: Mailbox INBOX: UID 31518: Deleting corrupted cache record: Broken virtual size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769006028.M895618P2636851.mail,S=21001,W=21465:2,S): FETCH BODY[] got too little data: 11619 vs 21465 Jan 22 19:16:05 imap(user)<82614><Oy+wCP5I/OuGPXzg>: Error: Mailbox INBOX: UID 31517: Deleting corrupted cache record: Broken physical size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769002524.M378861P2632916.mail,S=229241,W=232394:2,S) failed: Cached message size larger than expected (229241 > 149967, box=INBOX, UID=31517) I have set maildir_broken_filename_sizes = yes in 10-mail.conf, which I expected to prevent this, but is seemingly doesn't really. Do I have to purge some cache? Also something similar happens when sending mail: Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: fts-flatcurve: fts-flatcurve(Sent): Could not write message data: uid=1075; InvalidArgumentError: Term too long (> 245): B)l�5y�h�^H1gg^W^�^O�o�]s�ቄ�^Elkhv/�g^Cok3�)�{^Ft^Cm�b�lw,�1l^B�^[u^MbҾ\�u�b�n[f�j�w;�r�y7+�eȯqu�^L^\�x^L�f�(`�xfkw�<�ǣ�x5rv^G^L)�#zhh^B_7w/ztl}^Q.�1�5a�/�q�^M�^C^_^�"^Dd�j_�o�"x^Dya͘_^_n Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: Deleting corrupted cache record: Broken physical size in mailbox Sent: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: Precache for UID=1077 failed: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) (attempted to index 871 messages between UIDs 179..1077) And while the logs don't seem to mention it, I guess that's also interfering with receiving mails, as postfix confirms getting the mail (though it complains about not being able to write to /var/log/dovecot/error.log, but I also don't know why it would need that so I'm currently not looking into it), but it dovecot never says it received it and also no new file is created in /maildirs/user/Maildir/cur/. I have issues with some plugins. I have in 20-imap.conf and 15-lda.conf inside mail_plugins "zlib = yes", but no zlib-related module can be found. Is there a different way to enable mail compression and decompression or did Debian just miss to enable that at compilation? I also have issues with the sieve plugin. I had it enabled in 15-lda.conf, 20-managesieve.conf, 20-imap.conf and 20-lmtp.conf. As I understand I don't need all of them. At least if I do I get a weird issue (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). So where exactly do I enable it? Also, I'd need help modifying something I put into 90-plugins.conf: plugin { # From elsewhere to Junk folder imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/sieve/global/learn-spam.sieve # From Junk folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Junk imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/sieve/global/learn-ham.sieve sieve_pipe_bin_dir = /etc/dovecot/sieve/global sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_plugins = sieve_imapsieve sieve_extprograms # Compression zlib_save_level = 4 # 1..9 zlib_save = zstd or bz2, If this config entry missing, compression is disabled. } but when I do it that way I get the error "doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-plugin.conf line 9: Unknown section name: plugin". I do have this in 90-sieve.conf: mailbox Spam { # From elsewhere to Spam folder sieve_script report-spam { type = before cause = copy path = /etc/dovecot/sieve/global/learn-spam.sieve } } # From Spam folder to elsewhere imapsieve_from Spam { sieve_script report-ham { type = before cause = copy path = /etc/dovecot/sieve/global/learn-ham.sieve } } (currently commented out), but I have no idea how exactly I fold the old config into the new one. Most of the config is already migrated, but how do I make sure that learn-spam-sieve is only running when something is moved to Junk, while learn-ham.sieve is executed when something is being moved from Junk, except when it's moved into Trash? And what exactly do I do with the last 5 configs? Sorry for the long message, but the new config scheme is a bit too different for me to understand it right away. Best regards Richard Hi, I've just migrated our mail server from Debian 12 to 13. With this, dovecot was upgraded to v2.4. I was previously aware of the new config schema, but it seems the documentation wasn't enough to make the transition that smooth. I'm encountering several issues where I'd need some assistance: I have issues with message sizes not fitting: Jan 22 19:16:04 imap(user)<82612><thWtCP5I7OuGPXzg>: Error: Mailbox INBOX: UID 31518: Deleting corrupted cache record: Broken virtual size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769006028.M895618P2636851.mail,S=21001,W=21465:2,S): FETCH BODY[] got too little data: 11619 vs 21465 Jan 22 19:16:05 imap(user)<82614><Oy+wCP5I/OuGPXzg>: Error: Mailbox INBOX: UID 31517: Deleting corrupted cache record: Broken physical size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769002524.M378861P2632916.mail,S=229241,W=232394:2,S) failed: Cached message size larger than expected (229241 > 149967, box=INBOX, UID=31517) I have set maildir_broken_filename_sizes = yes in 10-mail.conf, which I expected to prevent this, but is seemingly doesn't really. Do I have to purge some cache? Also something similar happens when sending mail: Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: fts-flatcurve: fts-flatcurve(Sent): Could not write message data: uid=1075; InvalidArgumentError: Term too long (> 245): B)l**5y**h**^H1gg^W^**^O**o**]s**qE**^Elkhv/**g^Cok3**)**{^Ft^Cm**b**lw,**1l^B**^[u^Mb*\**u**b**n[f**j**w;**r**y7+**e*qu**^L^\**x^L**f**(`**xfkw**<**a3**x5rv^G^L)**#zhh^B_7w/ztl}^Q.**1**5a**/**q**^M**^C^_^**"^Dd**j_**o**"x^Dya*_^_n Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: Deleting corrupted cache record: Broken physical size in mailbox Sent: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: Precache for UID=1077 failed: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) (attempted to index 871 messages between UIDs 179..1077) And while the logs don't seem to mention it, I guess that's also interfering with receiving mails, as postfix confirms getting the mail (though it complains about not being able to write to /var/log/dovecot/error.log, but I also don't know why it would need that so I'm currently not looking into it), but it dovecot never says it received it and also no new file is created in /maildirs/user/Maildir/cur/. I have issues with some plugins. I have in 20-imap.conf and 15-lda.conf inside mail_plugins "zlib = yes", but no zlib-related module can be found. Is there a different way to enable mail compression and decompression or did Debian just miss to enable that at compilation? I also have issues with the sieve plugin. I had it enabled in 15-lda.conf, 20-managesieve.conf, 20-imap.conf and 20-lmtp.conf. As I understand I don't need all of them. At least if I do I get a weird issue (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). So where exactly do I enable it? Also, I'd need help modifying something I put into 90-plugins.conf: plugin { # From elsewhere to Junk folder imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = [1]file:/etc/dovecot/sieve/global/learn-spam.sieve # From Junk folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Junk imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = [2]file:/etc/dovecot/sieve/global/learn-ham.sieve sieve_pipe_bin_dir = /etc/dovecot/sieve/global sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_plugins = sieve_imapsieve sieve_extprograms # Compression zlib_save_level = 4 # 1..9 zlib_save = zstd or bz2, If this config entry missing, compression is disabled. } but when I do it that way I get the error "doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-plugin.conf line 9: Unknown section name: plugin". I do have this in 90-sieve.conf: mailbox Spam { # From elsewhere to Spam folder sieve_script report-spam { type = before cause = copy path = /etc/dovecot/sieve/global/learn-spam.sieve } } # From Spam folder to elsewhere imapsieve_from Spam { sieve_script report-ham { type = before cause = copy path = /etc/dovecot/sieve/global/learn-ham.sieve } } (currently commented out), but I have no idea how exactly I fold the old config into the new one. Most of the config is already migrated, but how do I make sure that learn-spam-sieve is only running when something is moved to Junk, while learn-ham.sieve is executed when something is being moved from Junk, except when it's moved into Trash? And what exactly do I do with the last 5 configs? Sorry for the long message, but the new config scheme is a bit too different for me to understand it right away. Best regards Richard References Visible links 1. file://etc/dovecot/sieve/global/learn-spam.sieve 2. file://etc/dovecot/sieve/global/learn-ham.sieve

2 2

Public mailboxes with ACLs
by lukas＠email.it 22 Jan '26

22 Jan '26

Hi! I am setting up a new dovecot server in order to replace my old one. I am migrating from 2.3.6 to 2.4.1. I knew it would have been difficult but I didn't think so much. At the moment I am stuck in converting my configuration of Public mailboxes with ACLs. Even if I carefully checked the documentation, I do not understand clearly some point. My server has 2 Public Mailboxes that should be seen r/w by some user, read only by some other, not seen at all by all the others. Folders created in the Public Mailboxes need to have the same access privileges as the parent Public Mailbox. In 2.3 I set up a global ACL file containing the list of all privileges (some lines like "MAILBOX_NAME* user=USERNAME lrs" with the privileges of each user for the two mailboxes and their content) and it worked like a charm. I cannot get the same in 2.4. What I understand from dovecot 2.4 docs -correct me if I am wrong- is: - the global ACL file (and folder) is gone, deprecated; - I need to create a file in each folder shared in the public folder; - I need to enable "acl_driver = vfile" in 90-acl.conf. If I configure this way, it seems to work but I need to create a dovecot-acl file in every folder existing in the Public Mailbox... Given that the file is the same for every folder (since I do not need different privileges in my environment), should I really waste all of this time? Please, can you tell me if I am misunderstanding this argument? The dovecot 2.4 choice for this feature is really this or I am missing something? There is definitely no way to have something like the 2.3 global ACL file? Thank for help and patience. Bye Lukas

3 7

Configuration problem user quota
by Ruud Baart 21 Jan '26

21 Jan '26

Hi, I'm doing a migration from dovecot 2.3 to 2.4. I can't find why the user quota is not respected. In my case in version 2.3 the user quota where read from LDAP: user_attrs = mailBase=home,mailMessageStore=mail,dovecotQuota=quota_rule=*:storage=%$ I can't find how I can configure this in 2.4. The documentation refers to "quota_rule" but how and where? In 2.4 I have: userdb ldap { userdb_use_worker = yes userdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) fields { home = %{ldap:mailBase} mail = %{ldap:mailMessageStore} mail_path = %{ldap:mailMessageStore} quota_storage_size = %{ldap:dovecotQuota} } } quota "User quota" { storage_size = 5G warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } The global quota works (set on 5Gb). The command doveadm -D quota get -u <user> shows: Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 21 13:53:34 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Jan 21 13:53:34 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): Started userdb lookup Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb: Connecting Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Client connected (fd=9) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): auth input: user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): auth USER input: user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): Finished userdb lookup (username=user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail_path=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Effective uid=118, gid=125, home=/vmail/intern/user Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: open(/proc/self/io) failed: Permission denied (euid=118(vmail) egid=125(vmail) missing +r perm: /proc/self/io) Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: maildir++: root=/vmail/intern/user/Maildir, index=, indexpvt=, control=, inbox=/vmail/intern/user/Maildir, alt= Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: quota-count: quota_over_status check: quota_over_mask unset - skipping Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Mailbox INBOX: Mailbox opened Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: User session is finished Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Disconnected: Connection closed (fd=9) Quota name Type Value Limit % User quota STORAGE 9116042 5242880 173 User quota MESSAGE 60188 - 0 -- Cordialement, *R.J. Baart * Hi, I'm doing a migration from dovecot 2.3 to 2.4. I can't find why the user quota is not respected. In my case in version 2.3 the user quota where read from LDAP: user_attrs = mailBase=home,mailMessageStore=mail,dovecotQuota=quota_rule=*:storage=%$ I can't find how I can configure this in 2.4. The documentation refers to "quota_rule" but how and where? In 2.4 I have: userdb ldap { userdb_use_worker = yes userdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) fields { home = %{[1]ldap:mailBase} mail = %{[2]ldap:mailMessageStore} mail_path = %{[3]ldap:mailMessageStore} quota_storage_size = %{[4]ldap:dovecotQuota} } } quota "User quota" { storage_size = 5G warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } The global quota works (set on 5Gb). The command doveadm -D quota get -u <user> shows: Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 21 13:53:34 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Jan 21 13:53:34 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 doveadm([5]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([6]user(a)domain.xx): Started userdb lookup Jan 21 13:53:34 doveadm([7]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb: Connecting Jan 21 13:53:34 doveadm([8]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Client connected (fd=9) Jan 21 13:53:34 doveadm([9]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): auth input: [10]user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm([11]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([12]user(a)domain.xx): auth USER input: [13]user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm([14]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([15]user(a)domain.xx): Finished userdb lookup ([16]username=user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G) Jan 21 13:53:34 doveadm([17]user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm([18]user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail_path=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm([19]user(a)domain.xx)<229340><>: Debug: Added userdb setting: quota_storage_size=10G Jan 21 13:53:34 doveadm([20]user(a)domain.xx): Debug: Effective uid=118, gid=125, home=/vmail/intern/user Jan 21 13:53:34 doveadm([21]user(a)domain.xx): Debug: open(/proc/self/io) failed: Permission denied (euid=118(vmail) egid=125(vmail) missing +r perm: /proc/self/io) Jan 21 13:53:34 doveadm([22]user(a)domain.xx): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes Jan 21 13:53:34 doveadm([23]user(a)domain.xx): Debug: maildir++: root=/vmail/intern/user/Maildir, index=, indexpvt=, control=, inbox=/vmail/intern/user/Maildir, alt= Jan 21 13:53:34 doveadm([24]user(a)domain.xx): Debug: quota-count: quota_over_status check: quota_over_mask unset - skipping Jan 21 13:53:34 doveadm([25]user(a)domain.xx): Debug: Mailbox INBOX: Mailbox opened Jan 21 13:53:34 doveadm([26]user(a)domain.xx): Debug: User session is finished Jan 21 13:53:34 doveadm([27]user(a)domain.xx): Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Disconnected: Connection closed (fd=9) Quota name Type Value Limit % User quota STORAGE 9116042 5242880 173 User quota MESSAGE 60188 - 0 -- Cordialement, R.J. Baart References Visible links 1. file:///tmp/tmp_2m1p1xn/ldap:mailBase 2. file:///tmp/tmp_2m1p1xn/ldap:mailMessageStore 3. file:///tmp/tmp_2m1p1xn/ldap:mailMessageStore 4. file:///tmp/tmp_2m1p1xn/ldap:dovecotQuota 5. mailto:user@domain.xx 6. mailto:user@domain.xx 7. mailto:user@domain.xx 8. mailto:user@domain.xx 9. mailto:user@domain.xx 10. mailto:user@domain.xx 11. mailto:user@domain.xx 12. mailto:user@domain.xx 13. mailto:user@domain.xx 14. mailto:user@domain.xx 15. mailto:user@domain.xx 16. mailto:username=user@domain.xx 17. mailto:user@domain.xx 18. mailto:user@domain.xx 19. mailto:user@domain.xx 20. mailto:user@domain.xx 21. mailto:user@domain.xx 22. mailto:user@domain.xx 23. mailto:user@domain.xx 24. mailto:user@domain.xx 25. mailto:user@domain.xx 26. mailto:user@domain.xx 27. mailto:user@domain.xx

2 1

default_login_user setting is not honored in 2.4.x
by dovecot＠freakout.de 21 Jan '26

21 Jan '26

i have in my dovecot.conf: default_login_user = www when i start dovecot: Starting mail server ...doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull after adding dovenull user to /etc/passwd _AND_ leaving "default_login_user = www" in the dovecot.conf file everything is working fine. With 2.3.x user www worked.

2 1

Upgrade problems from Dovecot 2.3 to 2.4
by Gordon Dickens 21 Jan '26

21 Jan '26

I have attempted to upgrade my 2.3 installation to 2.4 but it will not allow my users to login closing the connections as authentication failures. My 2.3 installation has worked for many years and I simply attempted to make the changes that the dovecot documentation says are necessary to get 2.4 to work. I am running dovecot alongside Exim using mysql for the user addresses and passwords. Does anybody have any ideas as to why authentication is not working? Thanks in advance!.... Here is my dovecot.conf file: # *** REQUIRED *** Dovecot config and storage versions dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.2 passdb sql { query = SELECT crypt as password FROM users WHERE username = '%{user}' AND (type = 'local' OR type = 'piped'); } userdb sql { query = SELECT pop as home, uid, gid FROM users WHERE username =dovecot: auth: Fatal: auth-cache: SELECT crypt as password FROM users WHERE username = '%u' AND (type = 'local' OR type = 'piped');: Cache key must contain at least one variable '%{user}'; } sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { user = exim4u password = SECRET dbname = exim4u } protocols { imap = yes pop3 = yes } protocol imap { mail_max_userip_connections = 50 } protocol pop3 { pop3_uidl_format = %{uid}%{uidvalidity} } service auth { user = dovecot } ssl = required ssl_server_cert_file = /etc/pki/tls/exim_tls/exim.cert ssl_server_key_file = /etc/pki/tls/exim_tls/exim.key ssl_server_dh_file = /etc/dovecot/dh.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384: ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384

2 3

Replication and upgrade
by Francis Augusto Medeiros-Logeay 20 Jan '26

20 Jan '26

Hi, I have used Dovecot for about seven years, and I have a two server configuration with replication between them, mostly for redundancy and backup. I have by chance read that replication is gone with 2.4.0. I use the packages that come with ubuntu, so I feel I have to be careful with upgrading there. I read also that I can keep the functionality by using a replication plugin. My question is: do I need to compile dovecot myself to use the plugin, or can I simply install it ? Is there any guide for people like me who needs to keep replication? Best, Francis

2 2

Help regarding Postfix and Dovecot SASL
by Christophe Lohr 19 Jan '26

19 Jan '26

Hello, Please excuse my naive question. I am trying to understand how "service auth" is supposed to work between Postfix and Dovecot. (https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html) Here is my test setup: - dovecot and postfix talking in lmtpd (via unix_listener /var/spool/postfix/private/dovecot-lmtp) - dovecot and postfix talking in sasl (via unix_listener /var/spool/postfix/private/auth) - "bob" and "alice" are virtual users of the virtual domain "my_domain.org" - passwd-file (plain) is /etc/dovecot/passwd Now, postrfix receive (by smtp) an email From: bob(a)my_domain.org To: alice(a)my_domain.org Postfix validate the domain according to its config (main.cf: virtual_mailbox_domains=my_domain.org) Then, it queries dovecot about these users via sasl: and that's where it fails! Here are logs from postfix: 2026-01-16T14:28:55.829532+01:00 pc-serveur postfix/qmgr[25055]: CA20D880486: from=<bob(a)my_domain.org>, size=9988, nrcpt=1 (queue active) 2026-01-16T14:28:55.831365+01:00 pc-serveur postfix/lmtp[25080]: CA20D880486: to=<alice(a)my_domain.org>, relay=pc-serveur.my_domain.org[private/dovecot-lmtp], delay=0, delays=0/0/0/0, dsn=5.1.1, status=bounced (host pc-serveur.tp-reseaux.enstb.org[private/dovecot-lmtp] said: 550 5.1.1 <alice(a)my_domain.org> User doesn't exist: alice(a)my_domain.org (in reply to RCPT TO command)) Here are logs from dovecot: Jan 16 14:28:55 lmtp(25081): Info: Connect from local Jan 16 14:28:55 auth: Debug: conn unix:/run/dovecot/auth-userdb (pid=25081,uid=118): Server accepted connection (fd=24) Jan 16 14:28:55 auth: Debug: master in: USER 1 bob(a)my_domain.org protocol=lmtp Jan 16 14:28:55 auth(bob7): Debug: passwd-file: Performing userdb lookup Jan 16 14:28:55 auth(bob7): Debug: passwd-file: lookup: user=bob7 file=/etc/dovecot/passwd Jan 16 14:28:55 auth(bob7): Info: passwd-file: unknown user Jan 16 14:28:55 auth(bob7): Debug: passwd-file: Finished userdb lookup Jan 16 14:28:55 auth: Debug: userdb out: NOTFOUND 1 Jan 16 14:28:55 lmtp(25081): Info: Disconnect from local: Logged out (state=READY) Jan 16 14:28:55 lmtp(25081): Info: Connect from local Jan 16 14:28:55 auth: Debug: master in: USER 2 alice(a)my_domain.org protocol=lmtp Jan 16 14:28:55 auth(alice7): Debug: passwd-file: Performing userdb lookup Jan 16 14:28:55 auth(alice7): Debug: passwd-file: lookup: user=alice7 file=/etc/dovecot/passwd Jan 16 14:28:55 auth(alice7): Info: passwd-file: unknown user Jan 16 14:28:55 auth(alice7): Debug: passwd-file: Finished userdb lookup Jan 16 14:28:55 auth: Debug: userdb out: NOTFOUND 2 Jan 16 14:28:55 lmtp(25081): Info: Disconnect from local: Logged out (state=READY) So, what's wrong? It seems to me that Dovecot receives a SASL request for the user "bob(a)my_domain.org", but only does a lookup for "bob", without the domain. Isn't it? So, why? What can I do? Best regards, Christophe

7 20

IMAP with Dovecot: Kerberos/GSSAPI in LAN only
by r.barclay＠habmalnefrage.de 19 Jan '26

19 Jan '26

Hi, I'm setting up a new IMAPS server using Dovecot 2.4 at the moment. I'd like my network internal users to authenticate using GSSAPI. The server is also exposed to the Internet for smart phone email access. I want to offer PLAIN login only for external users as they can't be legitimate internal Kerberos users. (Just as an additional layer of security.) Would this approach work? service imap-login { inet_listener imaps_external { port = 1993 ssl = yes auth_mechanisms = plain login } inet_listener imaps_internal { port = 7993 ssl = yes auth_mechanisms = plain login gssapi } } Then I'd allow only port 1993 externally and keep port 7993 for the LAN. Thank you for your advice! Reg

3 2

2.4.2 breaks big-endian builds
by Noah Meyerhans 19 Jan '26

19 Jan '26

From the Debian s390 build log, no merging parent is NULL ............................................ : ok no merging parent sent to stats ...................................... : ok no merging parent timestamp differs .................................. : ok merge events parent NULL ............................................. : ok merge events parent sent to stats .................................... : ok skip empty parents ................................................... : ok merge events and skip empty parents .................................. : ok parent updated after send ............................................ : ok large event id ....................................................... : ok merge events global .................................................. : ok 0 / 10 tests failed test-master-service-settings.c:472: Assert(#16) failed: strstr(error, tests[i].error) != NULL test-master-service-settings: Error: Failed to parse configuration: Settings block doesn't end with NUL at offset 70 test-master-service-settings.c:472: Assert(#19) failed: strstr(error, tests[i].error) != NULL test-master-service-settings: Error: Failed to parse configuration: Settings block doesn't end with NUL at offset 84 master_service_settings_read() - binary corruption ................... : FAILED 1 / 1 tests failed make[4]: *** [Makefile:958: check-local] Error 1 make[4]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src/lib-master' make[3]: *** [Makefile:806: check-am] Error 2 make[3]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src/lib-master' make[2]: *** [Makefile:604: check-recursive] Error 1 make[2]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src' make[1]: *** [Makefile:739: check-recursive] Error 1 make[1]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1' The build failure was introduced with commit 41bd7a502 ("lib-settings, config: Use native CPU endianess in binary config file"). The build is successful at the previous commit, but fails at that commit. I haven't yet determined whether the failure is with the code itself or the test. Full build log is available at https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=s390x&ver=1%3A2… noah

2 2

Re: Issue upgrading from 2.3.x to 2.4.1 when changing the mail driver from mbox to dbox
by Michael Slusarz 18 Jan '26

18 Jan '26

> On 01/16/2026 10:50 AM MST actionmystique via dovecot <dovecot(a)dovecot.org> wrote: > > I followed all the requirements detailed in https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html, but there seems to be an issue on my side configuring correctly the Mailbox locations. > In 10-mail.conf, I changed the mail driver from: > mail_driver = mbox --> mail_driver = dbox > I thought that would be sufficient but apparently, it is not the case. Changing mailbox format requires migration. See https://doc.dovecot.org/latest/core/admin/migration.html michael > All updated configurations are: > dovecot -n > # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf > # Pigeonhole version 2.4.1-4 (0a86619f) > # OS: Linux 6.17.0-8-generic x86_64 Ubuntu 25.10 > # Hostname: <hostname> > dovecot_config_version = 2.4.1 > auth_debug = yes > auth_debug_passwords = yes > auth_mechanisms = plain > auth_verbose = yes > auth_verbose_passwords = sha1 > dovecot_storage_version = 2.4.1 > fts_autoindex = yes > fts_autoindex_max_recent_msgs = 999 > fts_search_add_missing = yes > log_debug = category=ssl > log_timestamp = "%Y-%m-%d %H:%M:%S " > mail_driver = dbox > mail_home = /home/%{user|username} > mail_inbox_path = /var/mail/%{user} > mail_path = %{home}/mail > mail_privileged_group = mail > protocols = imap lmtp > ssl = required > ssl_cipher_list = <some list> > ssl_curve_list = <some list> > ssl_min_protocol = TLSv1.3 > passdb pam { > driver = pam > fields { > allow_nets = <nets> > } > result_failure = return-fail > result_internalfail = return-fail > result_success = return-ok > skip = never > } > userdb passwd { > } > 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 virtual/All { > special_use = "\\All" > } > } > service imap-login { > inet_listener imap { > port = 143 > listen = 127.0.0.1 [::1] > } > inet_listener imaps { > port = 993 > ssl = yes > listen = * [::] > } > } > service pop3-login { > inet_listener pop3 { > } > inet_listener pop3s { > } > } > service submission-login { > inet_listener submission { > } > } > service lmtp { > inet_listener lmtp { > port = 8024 > listen = 127.0.0.1 ::1 > } > } > service imap { > } > service pop3 { > } > service submission { > } > service auth { > unix_listener auth-userdb { > } > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > service auth-worker { > } > service dict { > unix_listener dict { > } > } > ssl_server { > ca_file = <path> > cert_file = <path> > key_file = <path> > prefer_ciphers = server > request_client_cert = yes > require_crl = no > } > ssl_client { > ca_dir = /etc/ssl/certs > require_valid_cert = yes > } > protocol lmtp { > auth_username_format = %{user | username} > mail_plugins = quota sieve > postmaster_address = <email> > } > > In mail.err, I get multiple error messages such as: > Error: Mailbox INBOX: open() failed with file /var/mail/<user>/dovecot.index.log: Not a directory > of course, because /var/mail/<user> is not a folder but a file containing all the received mails. > > So, in /var/mail, I have one file per user, plus one user.lock.sav, and also some weird files such as mu8xTBeL, muaBkJQL... belonging to one of the user. > > How should I configure dbox? > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Issue upgrading from 2.3.x to 2.4.1 when changing the mail driver from mbox to dbox
by actionmystique＠gmail.com 16 Jan '26

16 Jan '26

I followed all the requirements detailed in https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html, but there seems to be an issue on my side configuring correctly the Mailbox locations. In 10-mail.conf, I changed the mail driver from: mail_driver = mbox --> mail_driver = dbox I thought that would be sufficient but apparently, it is not the case. All updated configurations are: dovecot -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.0-8-generic x86_64 Ubuntu 25.10 # Hostname: <hostname> dovecot_config_version = 2.4.1 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain auth_verbose = yes auth_verbose_passwords = sha1 dovecot_storage_version = 2.4.1 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes log_debug = category=ssl log_timestamp = "%Y-%m-%d %H:%M:%S " mail_driver = dbox mail_home = /home/%{user|username} mail_inbox_path = /var/mail/%{user} mail_path = %{home}/mail mail_privileged_group = mail protocols = imap lmtp ssl = required ssl_cipher_list = <some list> ssl_curve_list = <some list> ssl_min_protocol = TLSv1.3 passdb pam { driver = pam fields { allow_nets = <nets> } result_failure = return-fail result_internalfail = return-fail result_success = return-ok skip = never } userdb passwd { } 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 virtual/All { special_use = "\\All" } } service imap-login { inet_listener imap { port = 143 listen = 127.0.0.1 [::1] } inet_listener imaps { port = 993 ssl = yes listen = * [::] } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } } service lmtp { inet_listener lmtp { port = 8024 listen = 127.0.0.1 ::1 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { ca_file = <path> cert_file = <path> key_file = <path> prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_dir = /etc/ssl/certs require_valid_cert = yes } protocol lmtp { auth_username_format = %{user | username} mail_plugins = quota sieve postmaster_address = <email> } In mail.err, I get multiple error messages such as: Error: Mailbox INBOX: open() failed with file /var/mail/<user>/dovecot.index.log: Not a directory of course, because /var/mail/<user> is not a folder but a file containing all the received mails. So, in /var/mail, I have one file per user, plus one user.lock.sav, and also some weird files such as mu8xTBeL, muaBkJQL... belonging to one of the user. How should I configure dbox?

1 0

Is dovecot CE 2.4.x supported with 32bit compile?
by dovecot＠freakout.de 16 Jan '26

16 Jan '26

these compiler messages make me nervous: test-event-filter.c:1006:53: warning: integer overflow in expression of type 'long int' results in '-694967296' [-Woverflow] 1006 | { "field = 1hours", 60L * 60 * 1000 * 1000, TRUE },

2 1

issue with quota warning using separate namespace quotas
by Andreas Oster 15 Jan '26

15 Jan '26

Hello everyone, I am currently trying to implement quota warnings for two separate namespaces (INBOX, MailArchive). The individual quota values for these namespaces are derived from ldap, which is working fine. However since adding the quota_warning configuration error messages appear in the logs: Error: quota-count: Filter quota_warning=warn-95 unexpectedly not found (invalid userdb or -o override settings?) Error: quota-count: Filter quota_warning=ma-warn-95 unexpectedly not found (invalid userdb or -o override settings?) The relevant configuration parameters from my config: quota_storage_size = 1G userdb ldap { fields { quota/ma_quota/storage_size = %{ldap:quota1} quota_storage_size = %{ldap:quota2} } } namespace subscriptions { mailbox_subscriptions_filename = subscriptions hidden = yes list = no prefix = subscriptions = yes } namespace inbox { inbox = yes prefix = INBOX/ subscriptions = no quota user_quota { name = User Quota 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} } } quota_warning warn-under { quota_storage_percentage = 100 threshold = under execute quota-warning { args = below %{user} } } } mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Sent { auto = subscribe special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } mailbox Spam { auto = subscribe special_use = "\\Junk" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { auto = subscribe special_use = "\\Trash" quota_storage_percentage = 110 } } namespace MailArchive { mail_driver = maildir mail_index_path = /var/mail/indexes/mailarchive/%{user} mail_path = /var/mail/mailarchive/%{user}/Maildir list = children prefix = MailArchiv/ subscriptions = no type = private quota ma_quota { name = MailArchive Quota quota_warning ma-warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning ma-warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } quota_warning ma-warn-under { quota_storage_percentage = 100 threshold = under execute quota-warning { args = below %{user} } } } mailbox "Archived Mails" { auto = subscribe special_use = "\\Archive" } } } service quota-warning { executable = script /var/mail/scripts/quota-warning.sh user = vmail unix_listener quota-warning { } } Does anyone have an idea what could be causing this behavior ? Thank you very much for your kind help. Andreas

1 0

Dovecot 2.4.2: How to fix maildir incoming mails going to cur/ instead of new/
by Andy Baugh 13 Jan '26

13 Jan '26

Add the following to dovecot.conf if you use maildir: # Disable the maildir breaking default behavior of # mail_attachment_detection_options, as setting ANY flag forces you out of new/ # and into cur/ mail_attachment_detection_options = ..and voila, maildir works as it previously did. This is *hinted* to in the migration guide document, as the old default value was shown as blank in the table, but I didn't figure it out till reading through the source code to find what was adding the 'a' flag to all incoming mails (thus forcing them out of new, as any flag does this). Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com

2 2

How should virtual users update their password?
by vwoloszczuk＠tutanota.com 13 Jan '26

13 Jan '26

Hi, I now have my email system working with virtual users, using a passwd-file for passdb. Now I am at the stage where I would like to change my password and possibly add other virtual users for my friends, who should be able to add/change their password without my involvement. I had a look at the IMAP RFCs but didn't see any sort of "change password" instruction. I also looked at the Dovecot docs but didn't see any article which covered this. What is the recommended/suggested way to do this? Is there a way to do with within the MDA/IMAP ecosystem or is it required to have an external solution e.g. entering the new password on a webpage? Thanks, Viktor Hi, I now have my email system working with virtual users, using a passwd-file for passdb. Now I am at the stage where I would like to change my password and possibly add other virtual users for my friends, who should be able to add/change their password without my involvement. I had a look at the IMAP RFCs but didn't see any sort of "change password" instruction. I also looked at the Dovecot docs but didn't see any article which covered this. What is the recommended/suggested way to do this? Is there a way to do with within the MDA/IMAP ecosystem or is it required to have an external solution e.g. entering the new password on a webpage? Thanks, Viktor

4 3

BUG-Report: mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) second attempt!
by Klaus Tachtler 13 Jan '26

13 Jan '26

Hello everyone, Problem info: An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log > 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) > 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: > 45 sql_driver = mysql > 46 > 47 mysql db.idmz.tachtler.net { > 48 host = db.idmz.tachtler.net > 49 port = 3306 > 50 user = postfixuser > 51 password = geheim > 52 dbname = postfix > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA > 58 } WITHOUT the following line, a database connections is possible and works as expected: > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

1 0

Re: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Stephen Callaghan 12 Jan '26

12 Jan '26

Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped) Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped)

2 1

Lazy expunge does not work as previously after upgrade from Dovecot 2.3 to 2.4.1
by Peter Milesson 11 Jan '26

11 Jan '26

Hi folks, I upgraded an IMAP server from Dovecot 2.3 to 2.4.1 (Debian 13). I have used the lazy expunge plugin for many years, and after upgrade, it was impossible to get it working as previously. After many trials I got it working sort of, but not as previously. The mail location and driver is the following: mail_home = /data/vmail/%{user | username} mail_driver = sdbox mail_path = ~/dbox Previously I had the following structure ~/dbox (user's mailboxes) ~/expunged (user's expunged emails) After upgrade I had to resort to store expunged messages in the inbox namespace in the hidden folder .EXPUNGED, instead of in a separate structure under ~/expunged. This is something I sincerely dislike, as I want expunged messages separate. Now, when messages are expunged, Dovecot no longer obeys the structure of the mailboxes, and puts all expunged messages in the .EXPUNGED folder. Previously the structure of the ~/expunged folder was a copy of the inbox namespace, but now it is just a large garbage bag. This is really a breaking change, and very unfortunate. I had a retention period of 90 days for expunged messages, mainly as a forensic tool. It has been of great help in correcting users that do not follow company guidelines, and opened insecure/infected archives, even if it's strictly prohibited. It has also rescued whole folder structures with sub folders on several occasions, when the users have inadvertently deleted a main folder, and then emptied trash. Now all expunged messages are stored in one big mess, which is much harder to analyze, and I assume, almost impossible to recover to the original state, if that would be needed. I would like to ask, if it is at all possible to get the equivalent of the previous behavior, and in that case, what the configuration would look like. Any help would be very appreciated. Best regards, Peter

1 0

mail-crypt transition from Dovecot 2.3 to 2.4
by m＠maltris.org 11 Jan '26

11 Jan '26

In Dovecot 2.3 I had used the following query: password_query = \ SELECT USER.user, USER.host, \ SECRET.password, SECRET.public_key AS mail_crypt_global_public_key, SECRET.private_key AS mail_crypt_global_private_key \ FROM USER \ WHERE USER.user = '%Lu' This worked fine, enabling encryption and decryption properly. For Dovecot 2.4 this does not work anymore. Example from LMTP: Dec 11 15:02:59 lmtp(975838): Info: lmtp-server: conn unix:pid=975905,uid=113 [1]: rcpt user(a)test.de: <Ti6aNxPPOmne4w4APAc66w>: Failed to send message to <user(a)test.de> at server:24: 451 4.2.0 <user(a)test.de> get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled (1/1 at 12 ms) I tried to adapt it to Dovecot 2.4 per the documentation, ending up with this: query = \ SELECT \ USER.user, USER.host, \ SECRET.password, \ concat('inline:', SECRET.public_key) AS crypt_global_public_key_file, \ 'main' AS crypt_global_private_key, \ concat('inline:', SECRET.private_key) AS 'crypt_global_private_key/main/crypt_private_key_file' \ FROM USER \ WHERE USER.user = '%{user | lower}' Still the error message: get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled Additionally I tried without the "inline:" prefix, because without, doveadm mailbox cryptokey list would return a "no such file or directory error" trying to treat the key as a filename. With the "inline:" prefix it returns nothing except a warning: Warning: mailbox cryptokey list: Nothing was matched. Use -U or specify mask? What is the right way to proceed here?

2 2

Created DokuWiki entries for the migration from Dovecot 2.3 to 2.4.
by Klaus Tachtler 10 Jan '26

10 Jan '26

Hello everyone, Over the past few weeks, I have migrated from Dovecot 2.3 to 2.4 and documented this in my DokuWiki. I do not claim that this is complete, nor is it an all-encompassing description. It includes a configuration for Dovecot 2.3 and the respective migration to Dovecot 2.4. I implemented the following configurations: Dovecot ArchLinux Dovecot ArchLinux - SSL/TLS Dovecot ArchLinux - SASL Dovecot ArchLinux - Quotas Dovecot ArchLinux - Mail-Log-Schreibung Dovecot ArchLinux - Zlib-Komprimierung Dovecot ArchLinux - SQL Dovecot ArchLinux - SQL - Quota: SQL Dovecot ArchLinux - Sieve (Pigeonhole) Dovecot ArchLinux - Shares Dovecot ArchLinux - Master-User The DokuWiki entries are in German, but I think the code examples speak for themselves, and if necessary, a translation program can also be used. The Dokuwiki and my implementations can be accessed at the following link: https://dokuwiki.tachtler.net/doku.php?id=index#imap-server_dovecot_imap-se… The documentation was created using the Archlinux operating system, but can certainly be ported to other Linux distributions. I hope someone else might find my notes useful too? Best regards, Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

3 3

Problems building from source under Trixie
by William Silverstein 09 Jan '26

09 Jan '26

I am running Debian Trixie. I try building the, but the configuration fails: I tried building with: ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 \ --with-ldap I get configure: error: cannot build with MySQL support: Neither MySQL (mysqlclient) nor MariaDB library (libmariadb) found. But I did install libldb-dev. I also installed libldap2-dev liblz4-dev But when I do: EXPAT_CFLAGS=/usr/include EXPAT_LIBS=/lib/x86_64-linux-gnu \ LZ4_CFLAGS=/usr/include LZ4_LIBS=/usr/lib/x86_64-linux-gnu \ ZLIB_CFLAGS=/usr/include ZLIB_LIBS=/lib/x86_64-linux-gnu \ MARIADB_LIBS=/usr/lib/x86_64-linux-gnu MARIADB_CFLAGS=/usr/include/mariadb \ ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 It configures, them fails in the build. I got some LZ4_DEPRECATED("use LZ4_compress_default() instead") LZ4LIB_API int LZ4_compress (const char* src, char* dest, int srcSize); I get a bunch of linker errors: /usr/bin/ld: ./.libs/libcompression.a(istream-lz4.o): in function `i_stream_lz4_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-lz4.c:192:(.text+0x619): undefined reference to `LZ4_decompress_safe' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_init': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:324:(.text+0x1d): undefined reference to `inflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:46:(.text+0xa8): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_reset': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x168): undefined reference to `inflateEnd' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x3a7): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:264:(.text+0x97f): undefined reference to `inflate' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:220:(.text+0xa7f): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-lz4.o): in function `o_stream_lz4_compress': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-lz4.c:94:(.text+0x12f): undefined reference to `LZ4_compress' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:91:(.text+0x1ee): undefined reference to `deflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_create_zlib': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:412:(.text+0x339): undefined reference to `deflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_flush': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:281:(.text+0x577): undefined reference to `deflate' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_chunk': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:213:(.text+0x83b): undefined reference to `deflate' Any suggestions? Thanks. -- William G. Silverstein, Esq. 8383 Wilshire Blvd. Suite 630. Beverly Hills, CA 90211

2 1

Error: userdb: client doesn't have lookup permissions for this user
by vwoloszczuk＠tutanota.com 09 Jan '26

09 Jan '26

Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp(<user> <mailto:viktor@woloszcz.uk>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable.I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user.I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page:https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: [1]https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp([2]<user>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable. I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user. I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page: [3]https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor References Visible links 1. https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html 2. mailto:viktor@woloszcz.uk 3. https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html

2 3

how to use dovecot-lda with dovecot.crt?
by Matthias Bodenbinder 09 Jan '26

09 Jan '26

Hi, I have a self signed certificate for dovecot: > [root@rakete] /etc/dovecot > # ll > insgesamt 12K > -rwxr-xr-x 1 root root 1,7K 2026-01-09@09:56 dovecot.conf > -rw-r----- 1 root root 1,4K 2026-01-09@09:54 dovecot.crt > -rw-r----- 1 root root 1,7K 2026-01-09@09:54 dovecot.key in dovecot.conf I have: ssl_server { cert_file = /etc/dovecot/dovecot.crt key_file = /etc/dovecot/dovecot.key } This works fine for the evolution email client. But when I want to use dovecot-lda as part of my getmail6 config I get a permission denied: # getmail --rcfile dogado-rc -n -v getmail version 6.19.10 Copyright (C) 1998-2025 Charles Cazabon and others. Licensed under GPL-2.0. SimpleIMAPSSLRetriever:bodenbinder_de_9@imap.dogado.net:993: Delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) [INBOX] msg 1/1 (1392 bytes), delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) 1 messages (1392 bytes) retrieved, 0 skipped dogado-rc has this delivery section: [destination] type = MDA_external path = /usr/lib/dovecot/dovecot-lda arguments = ("-d", "matthias") When I change ownership of the certificate files it works: # chown root:matthias /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key [root@rakete] /etc/dovecot # ll /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key -rw-r----- 1 root matthias 1,4K 2026-01-09@09:54 /etc/dovecot/dovecot.crt -rw-r----- 1 root matthias 1,7K 2026-01-09@09:54 /etc/dovecot/dovecot.key If I do not change permissions for dovecot.key I get a similar error for that file too. But can this be the solution? That would mean that I need to give read access to the crt/key file to every user who wants to use dovecot-lda. Is that correct? Matthias

2 2

Republish of dovecot 2.4.2 packages
by Aki Tuomi 08 Jan '26

08 Jan '26

Hi! Due to mistake in RHEL 10 packaging, we have republished packages for 2.4.2. Content is still the same, build number has increased by one. The important change is that there is now pigeonhole package for RHEL 10. You can find the packages at https://repo.dovecot.org/ as usual. Kind regards, Aki Tuomi

1 0

File system errors
by Jyrki Partanen 07 Jan '26

07 Jan '26

I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks! I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks!

4 4

Non Existent User Login Attempts
by Bryan Simmons 07 Jan '26

07 Jan '26

Log contains several messages from dovecot that are not clear to me exactly what is occurring, single example below. These appear to be login attempts for the same group of non existent user ids from various rip addresses. Am I interpreting these correctly and, if so, is there any issue with just ignoring them? dovecot: pop3-login: Disconnected: Connection closed (auth failed, 1 attempts in 0 secs): user=<non-existent-user(a)example.net>, rip=0.0.0.0 Thank you, Bryan

6 6

How can I use /etc/passwd auth for linux users and a passwd-file for virtual mailbox users?
by Ethan Merrill 06 Jan '26

06 Jan '26

Hello, I hope this is the right mailing list to send questions to. Please direct me where to go if it is not. Thanks. --- I am setting up a postfix/dovecot email server on a Debian 13 VPS. Dovecot is v2.4.1. I have thus far been able to successfully configure the server for smtp and imap support for my primary domain (we'll say `user(a)example.com` who is a linux user with a home folder). I have been even been able to configure postfix to have virtual mailboxes and aliases, and from ssh I can can even see that the mail gets delivered to the correct place. However, I am struggling to set up dovecot to authenticate a virtual mailbox user (we'll say `user(a)example.net` who only has a virtual mailbox). [This documentation page](https://doc.dovecot.org/2.4.2/core/config/auth/mutltiple.html) describes the process to configure multiple authentication databases. It describes being able to use multiple `passdb` and `userdb` sections in order to authenticate dovecot users. Based upon what it suggested, I tried this configuration: > ## Snippet from /etc/dovecot/dovecot.conf ## > passdb passwd-file { > # So example.net => /etc/dovecot/passwd/example.net > passwd_file_path = /etc/dovecot/passwd/%{user | domain} > } > # Fall thru to PAM for unix users > passdb pam { > } > > userdb passwd-file { > passwd_file_path = /etc/dovecot/passwd/%{user | domain} > } > # Fall thru to /etc/passwd for unix users > userdb passwd { > } > > ## Snippet from /etc/dovecot/passwd/example.net ## > support@example.net:$y$j9...hash...:800:800::/var/postfix/virtual/example.net/support:: This is the configuration I landed on that hypothetically checks multiple databases for authentication that allows at least `user(a)example.com` to still login with Thunderbird and do email stuff. However it does not authenticate `user(a)example.net`. The biggest difference between my config and the example is that they use a `sql` database while I am trying the `passwd-file` database. In principle this seems like it should work, unless I am understanding the dovecot docs or have made my passwd file incorrectly. I even tried reversing the order of `userdb` and `passdb` sections to see if it would help to no avail. [This thread](https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thre… seems to address a similar issue, and more or less has the same configuration setup suggested as the one in the snippet above. It's also from 2006 so the API looks kinda different from the current docs. [This thread](https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thre… is from 2013 addressing a similar issue, but despite again different API it translates to more or less what the snippet above shows. Here is the journalctl output from when I tried to login as `user(a)example.net`: > # journalctl -xeu dovecot | tail > Dec 29 11:38:19 example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown > Dec 29 11:38:19 example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user(a)example.net rhost=10.0.0.1 > Dec 29 11:38:28 example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown > Dec 29 11:38:28 example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user(a)example.net rhost=10.0.0.1 > Dec 29 11:41:19 example.com dovecot[4700]: imap-login: Login aborted: Inactivity (auth failed, 2 attempts in 180 secs) (auth_failed): user=<user(a)example.net>, method=LOGIN, rip=10.0.0.1, lip=10.0.0.2, TLS, session=<z8Tj3hlHkLxJMmuL> The last message referring to "Inactivity" is because at that point fail2ban blocked my IP, but before that it was consistent with results I have been getting. I'm at an absolute loss. I feel like I've trawled every doc I could find, every config file involved in the setup process, all the Stack Exchange answers that seem to exist. Honestly it baffles me to see that even what looks like the same setup as official documentation, it just doesn't... work? Can anybody point to me what is going wrong? Thanks for reading, ~ Ethan Merrill Hello, I hope this is the right mailing list to send questions to. Please direct me where to go if it is not. Thanks. --- I am setting up a postfix/dovecot email server on a Debian 13 VPS. Dovecot is v2.4.1. I have thus far been able to successfully configure the server for smtp and imap support for my primary domain (we'll say `user(a)example.com` who is a linux user with a home folder). I have been even been able to configure postfix to have virtual mailboxes and aliases, and from ssh I can can even see that the mail gets delivered to the correct place. However, I am struggling to set up dovecot to authenticate a virtual mailbox user (we'll say `user(a)example.net` who only has a virtual mailbox). [1]This documentation page describes the process to configure multiple authentication databases. It describes being able to use multiple `passdb` and `userdb` sections in order to authenticate dovecot users. Based upon what it suggested, I tried this configuration: ## Snippet from /etc/dovecot/dovecot.conf ## passdb passwd-file { # So [2]example.net => /etc/dovecot/passwd/example.net passwd_file_path = /etc/dovecot/passwd/%{user | domain} } # Fall thru to PAM for unix users passdb pam { } userdb passwd-file { passwd_file_path = /etc/dovecot/passwd/%{user | domain} } # Fall thru to /etc/passwd for unix users userdb passwd { } ## Snippet from /etc/dovecot/passwd/example.net ## [3]support@example.net:$y$j9...hash...:800:800::/var/postfix/virtual/example.net/support:: This is the configuration I landed on that hypothetically checks multiple databases for authentication that allows at least `user(a)example.com` to still login with Thunderbird and do email stuff. However it does not authenticate `user(a)example.net`. The biggest difference between my config and the example is that they use a `sql` database while I am trying the `passwd-file` database. In principle this seems like it should work, unless I am understanding the dovecot docs or have made my passwd file incorrectly. I even tried reversing the order of `userdb` and `passdb` sections to see if it would help to no avail. [4]This thread seems to address a similar issue, and more or less has the same configuration setup suggested as the one in the snippet above. It's also from 2006 so the API looks kinda different from the current docs. [5]This thread is from 2013 addressing a similar issue, but despite again different API it translates to more or less what the snippet above shows. Here is the journalctl output from when I tried to login as `user(a)example.net`: # journalctl -xeu dovecot | tail Dec 29 11:38:19 [6]example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown Dec 29 11:38:19 [7]example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot [8]ruser=user(a)example.net rhost=10.0.0.1 Dec 29 11:38:28 [9]example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown Dec 29 11:38:28 [10]example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot [11]ruser=user(a)example.net rhost=10.0.0.1 Dec 29 11:41:19 [12]example.com dovecot[4700]: imap-login: Login aborted: Inactivity (auth failed, 2 attempts in 180 secs) (auth_failed): user=<[13]user(a)example.net>, method=LOGIN, rip=10.0.0.1, lip=10.0.0.2, TLS, session=<z8Tj3hlHkLxJMmuL> The last message referring to "Inactivity" is because at that point fail2ban blocked my IP, but before that it was consistent with results I have been getting. I'm at an absolute loss. I feel like I've trawled every doc I could find, every config file involved in the setup process, all the Stack Exchange answers that seem to exist. Honestly it baffles me to see that even what looks like the same setup as official documentation, it just doesn't... work? Can anybody point to me what is going wrong? Thanks for reading, ~ Ethan Merrill References Visible links 1. This documentation page https://doc.dovecot.org/2.4.2/core/config/auth/mutltiple.html 2. http://example.net/ 3. mailto:support@example.net 4. This thread https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/VMXU2… 5. This thread https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/YO3DF… 6. http://example.com/ 7. http://example.com/ 8. mailto:ruser=user@example.net 9. http://example.com/ 10. http://example.com/ 11. mailto:ruser=user@example.net 12. http://example.com/ 13. mailto:user@example.net

6 10

Putting a file in a shared namespace causes Panic in quota.c
by Christopher V. 06 Jan '26

06 Jan '26

Dear all, I guess I found a bug. I'm currently testing a migration of my Debian based dovecot bare metal installation from 2.3.19 --> 2.4.1 I'm using shared mailboxes. My understanding from the documentation is: "Quota plugin considers shared namespaces against owner's quota" and "The quota limits are also taken from the userdb." The following setup leads to a "Panic: file quota.c": * Quota is defined per-user and defined in a MySQL Database (and looked up as part of userdb) * User A shares directory "Inbox/teilemich" with user B. * User B has full access rights (details see below) * User A has a quota of 100MB - currently using 60% * User B has a quota of 4GB - currently using 550MB * User A puts mail xyz in the shared directory --> works * User B puts mail abc in the shared directory --> error message (see below) and mail is not stored. Defining the following not-overwritable global quota > 550 MB eliminates the error message. Defining a global quota < 550 MB still leads to the error message. quota "User quota" { storage_size = 560M storage_grace = 10M } Defining an overwritable global quota that is > 550 MB still leads to the error message. quota_storage_size = 560M quota "User quota" { storage_grace = 10M } Can you please check, if this is a bug? If you need some details I'm happy to provide it. Also - I would be very grateful for a workaround / fix. Thanks for all the effort & Best regards, Christopher ----------------------------------------------------- Detailed error message: ==================== Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Panic: file quota.c: line 512 (quota_root_is_visible): assertion failed: (box->list->ns->type == MAIL_NAMESPACE_TYPE_SHARED) Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 i_panic[0x7fa1b4c655e6] -> #4 [unw_get_proc_name() failed: -10] -> #5 [unw_get_proc_name() failed: -10] -> #6 quota_test_alloc[0x7fa1b45a7850] -> #7 quota_try_alloc[0x7fa1b45aa4e0] -> #8 [unw_get_proc_name() failed: -10] -> #9 mailbox_save_finish[0x7fa1b508c7f0] -> #10 mail_storage_copy[0x7fa1b507e670] -> #11 [unw_get_proc_name() failed: -10] -> #12 [unw_get_proc_name() failed: -10] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 mailbox_move[0x7fa1b508cc10] -> #17 [unw_get_proc_name() failed: -10] -> #18 command_exec[0x55da1ef57080] -> #19 [unw_get_proc_name() failed: -10] -> #20 [unw_get_proc_name() failed: -10] -> #21 [unw_get_proc_name() failed: -10] -> #22 client_handle_input[0x55da1ef5d990] -> #23 client_input[0x55da1ef5ded0] -> #24 io_loop_call_io[0x7fa1b4d51710] -> #25 io_loop_handler_run_internal[0x7fa1b4d534b0] -> #26 io_loop_handler_run[0x7fa1b4d53640] -> #27 io_loop_run[0x7fa1b4d53820] -> #28 master_service_run[0x7fa1b4ca6330] -> #29 main[0x55da1ef48880] -> #30 [unw_get_proc_name() failed: -10] -> #31 __libc_start_main[0x7fa1b4e52ce0] -> #32 _start[0x55da1ef48f30] Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Fatal: master: service(imap): child 135441 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Output of "doveadm acl get -A inbox/teilemich": ======================================= Username ID Global Rights <user A> user=<user B> admin create delete expunge insert lookup post read write write-deleted write-seen Output of "doveconf -a": ==================== # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.57+deb13-cloud-amd64 x86_64 Debian 13.2 ext4 # Hostname: <Servername> # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 # NOTE: Send doveconf -n output instead when asking for help. acl_cache_ttl = 30 secs acl_defaults_from_inbox = no acl_driver = vfile acl_global_path = acl_globals_only = no acl_groups = acl_id = acl_ignore = no acl_rights = acl_user = %{master_user} apparmor_hats = auth_allow_cleartext = no auth_allow_weak_schemes = no auth_anonymous_username = anonymous auth_cache_negative_ttl = 180 seconds auth_cache_size = 1024 auth_cache_ttl = 180 seconds auth_cache_verify_password_with_worker = no auth_debug = no auth_debug_passwords = no auth_default_domain = <servername> auth_failure_delay = 2 secs auth_gssapi_hostname = auth_internal_failure_delay = 2 secs auth_krb5_keytab = auth_master_user_separator = auth_mechanisms = plain login auth_policy_check_after_auth = yes auth_policy_check_before_auth = yes auth_policy_hash_mech = sha256 auth_policy_hash_nonce = auth_policy_log_only = no auth_policy_reject_on_fail = no auth_policy_report_after_auth = yes auth_policy_request_attributes = auth_policy_server_api_header = auth_policy_server_url = auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %{user|lower} auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth charset_aliases = compress_bz2_block_size_100k = 9 compress_deflate_level = 6 compress_gz_level = 6 compress_zstd_level = 3 crypt_acl_require_secure_key_sharing = no crypt_global_public_key_file = crypt_private_key_file = crypt_private_key_name = crypt_private_key_password = crypt_user_key_curve = crypt_user_key_password = crypt_user_key_require_encrypted = no crypt_write_algorithm = aes-256-gcm-sha256 debug_log_path = default_client_limit = 1000 default_idle_kill_interval = 1 mins default_internal_group = dovecot default_internal_user = dovecot default_login_user = dovenull default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%{msgid}: %{message} dict_driver = dict_file_lock_method = dotlock dict_file_path = dict_map_expire_field = dict_map_key_field_name = dict_map_key_field_type = string dict_map_key_field_value = dict_map_ldap_filter = dict_map_pattern = dict_map_sql_table = dict_map_username_field = dict_map_value = dict_map_value_field_name = dict_map_value_field_type = string dict_name = dict_proxy_idle_timeout = 0 dict_proxy_name = dict_proxy_slow_warn = 5 secs dict_proxy_socket_path = dict dotlock_use_excl = yes doveadm_allowed_commands = doveadm_api_key = doveadm_password = doveadm_port = 0 doveadm_socket_path = doveadm-server doveadm_ssl = no doveadm_username = doveadm doveadm_worker_count = 0 dovecot_storage_version = 2.4.0 dsync_alt_char = _ dsync_commit_msgs_interval = 100 dsync_features = dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%{user} -U event_exporter_driver = log event_exporter_file_path = event_exporter_format = event_exporter_http_post_url = event_exporter_name = event_exporter_time_format = rfc3339 event_exporter_unix_connect_timeout = 250 ms event_exporter_unix_path = execute_args = execute_driver = unix execute_fork_path = execute_name = execute_tcp_host = execute_tcp_port = 0 execute_unix_socket_path = fifo_listener_group = fifo_listener_mode = 0600 fifo_listener_path = fifo_listener_type = fifo_listener_user = first_valid_gid = 1 first_valid_uid = 500 fs_compress_read_plain_fallback = no fs_compress_write_method = fs_crypt_read_plain_fallback = no fs_dict_value_encoding = raw fs_driver = fs_name = fs_posix_accurate_mtime = no fs_posix_fsync = yes fs_posix_lock_method = flock fs_posix_mode = 0600 fs_posix_prefix = fs_randomfail_ops = fs_sis_queue_path = fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_decoder_driver = fts_decoder_script_socket_path = fts_decoder_tika_url = fts_driver = fts_flatcurve_commit_limit = 500 fts_flatcurve_min_term_size = 2 fts_flatcurve_optimize_limit = 10 fts_flatcurve_rotate_count = 5000 fts_flatcurve_rotate_time = 5 secs fts_flatcurve_substring_search = no fts_header_excludes = fts_header_includes = fts_message_max_size = unlimited fts_search = yes fts_search_add_missing = yes fts_search_read_fallback = yes fts_search_timeout = 30 secs haproxy_timeout = 3 secs haproxy_trusted_networks = hostname = http_client_connect_timeout = 0 http_client_delete_request_max_attempts = 0 http_client_delete_request_timeout = 0 http_client_max_connect_attempts = 0 http_client_max_idle_time = 0 http_client_max_parallel_connections = 1 http_client_max_pipelined_requests = 1 http_client_proxy_password = http_client_proxy_socket_path = http_client_proxy_ssl_tunnel = yes http_client_proxy_url = http_client_proxy_username = http_client_rawlog_dir = http_client_read_request_max_attempts = 0 http_client_read_request_timeout = 0 http_client_request_absolute_timeout = 0 http_client_request_max_attempts = 1 http_client_request_max_redirects = 0 http_client_request_timeout = 1 mins http_client_write_request_max_attempts = 0 http_client_write_request_timeout = 0 http_server_max_client_idle_time = 0 http_server_max_pipelined_requests = 1 http_server_rawlog_dir = imap_acl_allow_anyone = no imap_capability = imap_client_workarounds = imap_fetch_failure = disconnect-immediately imap_hibernate_timeout = 5s imap_id_retain = no imap_id_send = imap_literal_minus = no imap_logout_format = in=%{input} out=%{output} deleted=%{deleted} expunged=%{expunged} trashed=%{trashed} hdr_count=%{fetch_hdr_count} hdr_bytes=%{fetch_hdr_bytes} body_count=%{fetch_body_count} body_bytes=%{fetch_body_bytes} imap_metadata = no imap_urlauth_host = imap_urlauth_logout_format = in=%{input} out=%{output} imap_urlauth_port = 143 imap_urlauth_stream_user = imap_urlauth_submit_user = imapc_cmd_timeout = 5 mins imapc_connection_retry_count = 1 imapc_connection_retry_interval = 1 secs imapc_connection_timeout_interval = 30 secs imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_max_line_length = unlimited imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_sasl_mechanisms = imapc_ssl = no imapc_user = %{owner_user} imapsieve_expunge_discarded = no imapsieve_from_name = imapsieve_url = import_environment = inet_listener_haproxy = no inet_listener_name = inet_listener_port = 0 inet_listener_reuse_port = no inet_listener_ssl = no inet_listener_type = info_log_path = instance_name = dovecot language_default = no language_filter_normalizer_icu_id = Any-Lower; NFKD; [: Nonspacing Mark :] Remove; NFC; [\x20] Remove language_filter_stopwords_dir = /usr/share/dovecot/stopwords language_filters = normalizer-icu snowball stopwords language_name = language_tokenizer_address_token_maxlen = 250 language_tokenizer_generic_algorithm = simple language_tokenizer_generic_explicit_prefix = no language_tokenizer_generic_token_maxlen = 30 language_tokenizer_generic_wb5a = no language_tokenizers = generic email-address last_login_key = # hidden, use -P to show it last_login_precision = s last_valid_gid = 0 last_valid_uid = 0 lazy_expunge_mailbox = lazy_expunge_only_last_instance = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To ldap_auth_dn = ldap_auth_dn_password = ldap_auth_sasl_authz_id = ldap_auth_sasl_mechanisms = ldap_auth_sasl_realm = ldap_base = ldap_debug_level = 0 ldap_deref = never ldap_max_idle_time = 0 ldap_scope = subtree ldap_starttls = no ldap_timeout = 30 secs ldap_uris = ldap_version = 3 listen = lmtp_add_received_header = yes lmtp_client_workarounds = lmtp_hdr_delivery_address = final lmtp_proxy = no lmtp_proxy_rawlog_dir = lmtp_rawlog_dir = lmtp_rcpt_check_quota = no lmtp_save_to_detail_mailbox = no lmtp_user_concurrency_limit = 0 lock_method = fcntl log_core_filter = log_debug = log_path = syslog log_timestamp = "%b %d %H:%M:%S " login_log_format = %{message}: %{elements} login_log_format_elements = user=<%{user}> method=%{mechanism} rip=%{remote_ip} lip=%{local_ip} mpid=%{mail_pid} %{secured} session=<%{session}> login_plugin_dir = /usr/lib/dovecot/modules/login login_plugins = login_proxy_max_disconnect_delay = 0 login_proxy_max_reconnects = 3 login_proxy_notify_path = proxy-notify login_proxy_rawlog_dir = login_proxy_timeout = 30 secs login_socket_path = login_source_ips = login_trusted_networks = lua_file = lua_settings = mail_access_groups = mail_alt_path = mail_always_cache_fields = mail_attachment_detection_options = mail_cache_fields = mail_chroot = mail_compress_write_method = mail_control_path = mail_debug = no mail_driver = Maildir mail_ext_attachment_min_size = 128 k mail_ext_attachment_path = mail_fsync = optimized mail_full_filesystem_access = no mail_gid = vmail mail_home = /var/spool/dovecot/%{user|domain}/%{user|username}/home mail_inbox_path = mail_index_path = mail_index_private_path = mail_log_cached_only = no mail_log_events = mail_log_fields = mail_log_prefix = "%{service}(%{user})<%{process:pid}><%{session}>: " mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = mail_nfs_index = no mail_nfs_storage = no mail_path = /var/spool/dovecot/%{user|domain}/%{user|username}/mail mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins { acl = yes quota = yes fts = yes fts_flatcurve = yes quota_clone = yes } mail_prefetch_count = 0 mail_privileged_group = mail mail_server_admin = mailto:admin@<servername> mail_server_comment = mail_shared_explicit_inbox = no mail_sort_max_read_count = 0 mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = vmail mail_utf8_extensions = no mail_volatile_path = mail_vsize_bg_after_count = 0 mailbox_auto = no mailbox_autoexpunge = 0 mailbox_autoexpunge_max_mails = 0 mailbox_comment = mailbox_directory_name_legacy = yes mailbox_list_index = yes mailbox_list_index_include_inbox = no mailbox_list_index_prefix = dovecot.list.index mailbox_list_index_very_dirty_syncs = no mailbox_list_layout = fs mailbox_list_storage_escape_char = mailbox_list_visible_escape_char = mailbox_name = mailbox_notify_status = no mailbox_special_use = maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_empty_new = no maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%{input}/%{output} managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k managesieve_notify_capability = managesieve_sieve_capability = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_read_locks = mbox_very_dirty_syncs = no mbox_write_locks = mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 10 M metric_description = metric_exporter = metric_exporter_include = metric_fields = metric_filter = metric_group_by_field = metric_group_by_method_discrete_modifier = metric_group_by_method_exponential_base = 10 metric_group_by_method_exponential_max_magnitude = 0 metric_group_by_method_exponential_min_magnitude = 0 metric_group_by_method_linear_max = 0 metric_group_by_method_linear_min = 0 metric_group_by_method_linear_step = 0 metric_group_by_method_method = discrete metric_name = mmap_disable = no mysql_client_flags = 0 mysql_connect_timeout = 5 secs mysql_connection_limit = 5 mysql_dbname = mysql_host = mysql_option_file = mysql_option_group = client mysql_password = mysql_port = 0 mysql_read_timeout = 30 secs mysql_ssl = no mysql_user = mysql_write_timeout = 30 secs namespace_alias_for = namespace_disabled = no namespace_hidden = no namespace_ignore_on_failure = no namespace_inbox = no namespace_list = yes namespace_name = namespace_order = 0 namespace_prefix = namespace_separator = namespace_subscriptions = yes namespace_type = private notify_status_value = {"messages":%{messages},"unseen":%{unseen}} oauth2_active_attribute = oauth2_active_value = oauth2_client_id = oauth2_client_secret = oauth2_fields = oauth2_force_introspection = no oauth2_grant_url = oauth2_introspection_mode = oauth2_introspection_url = oauth2_issuers = oauth2_openid_configuration_url = oauth2_scope = oauth2_send_auth_headers = no oauth2_tokeninfo_url = oauth2_use_worker_with_mech = no oauth2_username_attribute = email oauth2_username_validation_format = %{user} passdb_default_password_scheme = PLAIN passdb_deny = no passdb_driver = passdb_fields = passdb_fields_import_all = yes passdb_master = no passdb_mechanisms_filter = passdb_name = passdb_pam_failure_show_msg = no passdb_pam_max_requests = 100 passdb_pam_service_name = dovecot passdb_pam_session = no passdb_pam_setcred = no passdb_result_failure = continue passdb_result_internalfail = continue passdb_result_success = return-ok passdb_skip = never passdb_sql_query = passdb_sql_update_query = passdb_static_password = passdb_use_cache = yes passdb_use_worker = no passdb_username_filter = passwd_file_path = pop3_client_workarounds = pop3_delete_type = default pop3_deleted_flag = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%{top_count}/%{top_bytes}, retr=%{retr_count}/%{retr_bytes}, del=%{deleted_count}/%{deleted_bytes}, size=%{message_bytes} pop3_migration_all_mailboxes = no pop3_migration_ignore_extra_uidls = no pop3_migration_ignore_missing_uidls = no pop3_migration_mailbox = pop3_migration_skip_size_check = no pop3_migration_skip_uidl_cache = no pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %{uid | hex(8)}%{uidvalidity | hex(8)} pop3c_features = pop3c_host = pop3c_master_user = pop3c_password = pop3c_port = 110 pop3c_quick_received_date = no pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_verify = yes pop3c_user = %{user} postmaster_address = postmaster@%{user|domain|default(hostname)} process_shutdown_filter = protocols { imap = yes lmtp = yes sieve = yes } push_notification_driver = push_notification_name = push_notification_ox_cache_ttl = 1 mins push_notification_ox_url = push_notification_ox_user_from_metadata = no quota_clone_unset = no quota_driver = count quota_enforce = yes quota_exceeded_message = Quota exceeded (mailbox for user is full) quota_fs_message_limit = no quota_fs_mount_path = quota_fs_type = any quota_full_tempfail = yes quota_hidden = no quota_ignore = no quota_ignore_unlimited = no quota_imapc_mailbox_name = INBOX quota_imapc_root_name = quota_mail_size = unlimited quota_mailbox_count = unlimited quota_mailbox_message_count = unlimited quota_message_count = unlimited quota_message_percentage = 100 quota_name = quota_over_status_current = quota_over_status_lazy_check = no quota_over_status_mask = quota_status_nouser = REJECT Unknown user quota_status_overquota = 554 5.2.2 %{error} quota_status_success = OK quota_status_toolarge = quota_storage_extra = 0 quota_storage_grace = 10 M quota_storage_percentage = 100 quota_storage_size = 50M quota_warning_name = quota_warning_resource = storage quota_warning_threshold = over rawlog_dir = recipient_delimiter = + redis_db_id = 0 redis_expire = 0 redis_host = 127.0.0.1 redis_key_prefix = redis_password = redis_port = 6379 redis_request_timeout = 30 secs redis_socket_path = rejection_reason = Your message to <%{to}> was automatically rejected:%{literal('\r\n')}%{reason} rejection_subject = Rejected: %{subject} sendmail_path = /usr/sbin/sendmail service_chroot = service_client_limit = 0 service_drop_priv_before_exec = no service_executable = service_extra_groups = service_group = service_idle_kill_interval = 0 service_name = service_privileged_group = service_process_limit = 0 service_process_min_avail = 0 service_protocol = service_restart_request_count = unlimited service_type = service_user = service_vsz_limit = 0 shutdown_clients = yes sieve_duplicate_default_period = 12 hours sieve_duplicate_max_period = 2 days sieve_editheader_header_forbid_add = no sieve_editheader_header_forbid_delete = no sieve_editheader_header_name = sieve_editheader_max_header_size = 2 k sieve_enabled = yes sieve_environment = sieve_execute_bin_dir = sieve_execute_exec_timeout = 10 secs sieve_execute_input_eol = crlf sieve_execute_socket_dir = 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 editheader = no spamtest = yes mboxmetadata = yes virustest = yes } sieve_filter_bin_dir = sieve_filter_exec_timeout = 10 secs sieve_filter_input_eol = crlf sieve_filter_socket_dir = sieve_global_extensions = sieve_implicit_extensions = sieve_include_max_includes = 255 sieve_include_max_nesting_depth = 10 sieve_max_actions = 32 sieve_max_cpu_time = 0 sieve_max_redirects = 4 sieve_max_script_size = 1 M sieve_notify_mailto_envelope_from = sieve_pipe_bin_dir = sieve_pipe_exec_timeout = 10 secs sieve_pipe_input_eol = crlf sieve_pipe_socket_dir = sieve_plugin_dir = /usr/lib/dovecot/modules/sieve sieve_plugins = sieve_quota_script_count = 0 sieve_quota_storage_size = 0 sieve_redirect_duplicate_period = 43200 sieve_redirect_envelope_from = sieve_report_from = sieve_resource_usage_timeout = 1 hours sieve_script_active_path = sieve_script_bin_path = sieve_script_cause = sieve_script_driver = file sieve_script_ldap_filter = sieve_script_ldap_modified_attribute = sieve_script_ldap_script_attribute = sieve_script_name = sieve_script_path = sieve_script_precedence = unlimited sieve_script_storage = sieve_script_type = personal sieve_spamtest_score_max_header = sieve_spamtest_score_max_value = sieve_spamtest_status_header = sieve_spamtest_status_type = score sieve_spamtest_text_value = sieve_trace_addresses = no sieve_trace_debug = no sieve_trace_dir = sieve_trace_level = none sieve_user_email = sieve_user_log_path = sieve_vacation_check_recipient = yes sieve_vacation_default_period = 1 weeks sieve_vacation_default_subject = sieve_vacation_default_subject_template = sieve_vacation_max_period = 60 days sieve_vacation_min_period = 1 days sieve_vacation_send_from_recipient = no sieve_vacation_to_header_ignore_envelope = no sieve_vacation_use_original_recipient = no sieve_variables_max_scope_count = 255 sieve_variables_max_value_size = 4 k sieve_virustest_score_max_header = sieve_virustest_score_max_value = sieve_virustest_status_header = sieve_virustest_status_type = score sieve_virustest_text_value = sql_driver = mysql ssl = yes ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH:!AECDH:!RC4-SHA:!SHA1 ssl_cipher_suites = ssl_client_ca_dir = ssl_client_ca_file = ssl_client_cert_file = ssl_client_key_file = ssl_client_key_password = ssl_client_require_valid_cert = yes ssl_crypto_device = ssl_curve_list = ssl_min_protocol = TLSv1.2 ssl_options = ssl_server_alt_cert_file = ssl_server_alt_key_file = ssl_server_ca_file = ssl_server_cert_file = ssl_server_cert_username_field = commonName ssl_server_dh_file = ssl_server_key_file = ssl_server_key_password = ssl_server_prefer_ciphers = client ssl_server_request_client_cert = no ssl_server_require_crl = yes stats_writer_socket_path = stats-writer submission_add_received_header = yes submission_backend_capabilities = submission_client_workarounds = submission_host = submission_logout_format = in=%{input} out=%{output} submission_max_mail_size = 0 submission_max_recipients = 0 submission_relay_command_timeout = 5 mins submission_relay_connect_timeout = 30 secs submission_relay_host = submission_relay_master_user = submission_relay_max_idle_time = 29 mins submission_relay_password = submission_relay_port = 25 submission_relay_rawlog_dir = submission_relay_ssl = no submission_relay_ssl_verify = yes submission_relay_trusted = no submission_relay_user = submission_ssl = no submission_timeout = 30 secs syslog_facility = mail textcat_config_path = trash_priority = 0 unix_listener_group = unix_listener_mode = 0600 unix_listener_path = unix_listener_type = unix_listener_user = userdb_driver = userdb_fields = userdb_fields_import_all = yes userdb_name = userdb_result_failure = continue userdb_result_internalfail = continue userdb_result_success = return-ok userdb_skip = never userdb_sql_iterate_query = userdb_sql_query = userdb_static_allow_all_users = no userdb_use_cache = yes userdb_use_worker = no valid_chroot_dirs = verbose_proctitle = no version_ignore = no virtual_max_open_mailboxes = 64 welcome_wait = no mysql localhost { dbname = sys_mail password = # hidden, use -P to show it ssl = no user = sys_dovecot } userdb sql { iterate_query = SELECT username AS user FROM mailbox query = SELECT CONCAT('/var/spool/dovecot/',maildir,'mail') AS mail_path, CONCAT('/var/spool/dovecot/',maildir) AS home, 5000 AS uid, 5000 AS gid, CONCAT(quota,'B') AS quota_storage_size FROM mailbox WHERE username = '%{user|lower}' } passdb pam { default_password_scheme = CRYPT service_name = dovecot skip = authenticated } namespace inbox { inbox = yes separator = / type = private mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { auto = subscribe special_use = "\\Junk" } mailbox Trash { auto = subscribe special_use = "\\Trash" quota_storage_percentage = 110 } mailbox Sent { auto = subscribe special_use = "\\Sent" } mailbox "Sent Messages" { auto = no special_use = "\\Sent" } } namespace shared { mail_driver = maildir mail_index_path = /var/spool/dovecot/%{user|domain}/%{user|username}/sharedmailboxes/%{owner_user|domain}/%{owner_user|username} mail_path = /var/spool/dovecot/%{owner_user|domain}/%{owner_user|username}/mail list = children prefix = shared/$user/ separator = / type = shared } service imap-login { inet_listener imap { listen = 127.0.0.1 } inet_listener imaps { } } service lmtp { unix_listener lmtp { } } service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } } service auth-worker { user = $SET:default_internal_user } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = vmail mode = 0660 user = dovecot } } service imap { unix_listener imap-master { user = dovecot } } ssl_server { cert_file = /etc/letsencrypt/live/<Servername>.de/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/<Servername>.de/privkey.pem prefer_ciphers = server } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 30 mail_plugins { imap_sieve = yes imap_quota = yes imap_acl = yes imap_zlib = no } } protocol lmtp { auth_username_format = %{user | username | lower} mail_plugins { sieve = yes } } service managesieve-login { process_min_avail = 1 restart_request_count = 1 vsz_limit = 64M inet_listener sieve { port = 4190 listen = 127.0.0.1 } } service managesieve { process_limit = 1024 } protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536 } dict_server { dict mysql { driver = sql hostname = localhost sql_driver = mysql ssl = no dict_map priv/quota/storage { sql_table = quota2 username_field = username dict_map_value_field bytes { type = uint } } dict_map priv/quota/messages { sql_table = quota2 username_field = username dict_map_value_field messages { type = uint } } dict_map "shared/shared-boxes/user/$to/$from" { sql_table = user_shares dict_map_value_field dummy { } dict_map_key_field from_user { value = $from } dict_map_key_field to_user { value = $to } } dict_map "shared/shared-boxes/anyone/$from" { sql_table = anyone_shares dict_map_value_field dummy { } dict_map_key_field from_user { value = $from } } } } acl_sharing_map { dict proxy { name = mysql } } language en { filters = lowercase snowball english-possessive stopwords } language de { default = yes filters = snowball stopwords normalizer-icu } fts flatcurve { substring_search = yes } quota "User quota" { driver = count storage_grace = 10M quota_warning warn-100 { quota_storage_percentage = 100 execute quota-full { args = 100 %{user} } } 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 unix_listener quota-warning { user = vmail } } service quota-full { executable = script /usr/local/bin/quota-warning-full.sh unix_listener quota-full { user = vmail } } quota_clone { dict proxy { name = mysql } } sieve_script personal { active_path = /var/spool/dovecot/%{user|domain}/%{user|username}/sieve/.dovecot.sieve driver = file path = /var/spool/dovecot/%{user|domain}/%{user|username}/sieve } sieve_script default { driver = file name = default path = /var/spool/dovecot/sieve/default.sieve type = default } service indexer-worker { executable = /usr/bin/nice -n 10 /usr/lib/dovecot/indexer-worker process_limit = 1 user = vmail }

2 2

time diff miscalculation on 32-bit systems
by Andy Spiegl 06 Jan '26

06 Jan '26

Dear dovecot team, I believe I found a bug in dovecot on 32-bit systems. Dovecot version: 1:2.4.1+dfsg1-6 (Architecture: i386) Operating system: Linux lar 6.13.7-64+ #1 SMP PREEMPT Fri Mar 21 08:33:47 MEZ 2025 x86_64 GNU/Linux Distributor ID: Debian Description: Debian GNU/Linux 13 (trixie) Release: 13 Codename: trixie * What led up to the situation? Upgrade from 2.3.21.1 to 1:2.4.1 * What was the outcome of this action? Logs are flooded with messages "Warning: Time moved forward" * Problem Description: The function io_loop_get_wait_time in ioloop.c contains the line: ioloop->next_max_time.tv_sec = (1ULL << (TIME_T_MAX_BITS-1)) - 1; On 32-bit systems TIME_T_MAX_BITS is 31 such that the result of this calculation is 1073741823. Far from the intended "infinity" and even before "now". This leads to problems in the function io_loop_handle_timeouts_real: the calculation of the time difference between now and next_max_time is then something like -693628953 seconds which confuses dovecot and floods the logs with these warnings: Jan 02 17:43:43 lmtp(38364): Warning: Time moved forward 693630400.301863 seconds Jan 02 17:43:43 lmtp(38364): Warning: Time moved forward 693630400.304144 seconds Jan 02 17:45:43 lmtp(38364): Warning: Time moved forward 693630520.416053 seconds * Possible solution/workaround ? ioloop->next_max_time.tv_sec = INT_MAX; Thanks for your consideration, Andy

2 1

Missing dovecot-pigeonhole packages in official CE-2.4 repo for RHEL/Rocky Linux 10
by Mateusz Kiczela 06 Jan '26

06 Jan '26

Hello Dovecot Team, I am attempting to install Dovecot 2.4.2 on Rocky Linux 10 (RHEL 10 compatible) using the official repository found at: http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/ The Issue: Although the core Dovecot packages (dovecot, dovecot-imapd, etc.) are present, the Pigeonhole (Sieve/ManageSieve) packages are completely missing from the repository index. I have verified this by browsing the directory listing directly. Missing Packages: - dovecot-pigeonhole - dovecot-sieve - dovecot-managesieved Could you please check the build pipeline for RHEL/CentOS/Rocky Linux 10? It appears the Pigeonhole artifacts are not being published, and the base dependencies might need a rebuild against current EL10 libraries. Thank you for your support! Best regards. Mateusz Kiczela Hello Dovecot Team, I am attempting to install Dovecot 2.4.2 on Rocky Linux 10 (RHEL 10 compatible) using the official repository found at: [1]http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/ The Issue: Although the core Dovecot packages (dovecot, dovecot-imapd, etc.) are present, the Pigeonhole (Sieve/ManageSieve) packages are completely missing from the repository index. I have verified this by browsing the directory listing directly. Missing Packages: - dovecot-pigeonhole - dovecot-sieve - dovecot-managesieved Could you please check the build pipeline for RHEL/CentOS/Rocky Linux 10? It appears the Pigeonhole artifacts are not being published, and the base dependencies might need a rebuild against current EL10 libraries. Thank you for your support! Best regards. Mateusz Kiczela References Visible links 1. http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/

2 3

Getting Dovecot to coredump
by Washington Odhiambo 05 Jan '26

05 Jan '26

Can someone please give simple steps to make dovecot to coredump on Debian 12? After reading this: https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps - I am still not able to get it to work. I have been running dovecot from git (yes, I know I shouldn't!) until I updated today and then it would be killed by signal 11. I have so far installed the release versions and all is fine, but I'd like to ensure that in the future, I have the coredump working. -- 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] Can someone please give simple steps to make dovecot to coredump on Debian 12? After reading this: [1]https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps - I am still not able to get it to work. I have been running dovecot from git (yes, I know I shouldn't!) until I updated today and then it would be killed by signal 11. I have so far installed the release versions and all is fine, but I'd like to ensure that in the future, I have the coredump working. -- 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 '^$|^.*#' -\_(Tu)_/- :-) [How to ask smart questions: [2]http://www.catb.org/~esr/faqs/smart-questions.html] References Visible links 1. https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps 2. http://www.catb.org/~esr/faqs/smart-questions.html

2 3

dovecot-2.3.21.1 for Fedora 43
by John Fawcett 04 Jan '26

04 Jan '26

Hi I realize this may seem overly nostalgic, but I was wondering if anyone has successfully got dovecot-2.3.21.1 running on Fedora 43? I'm about to do an upgrade to Fedora 43 and I wanted to avoid doing a simultaneous upgrade to Dovecot 2.4 which is now the distro packaged version, since I have not yet converted my configuration. I managed to compile from source (after taking care of adding -licuuc to the linker flags when linking test-fts-filter). However running test-lib then fails on two tests. test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED and test-data-stack.c:191: Assert failed: a == b data-stack buffer interruption ....................................... : FAILED If instead I use a src rpm like the one from here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2651758 that includes fedora specific patches and try to rebuild it, it builds without the libicuuc issue, but then fails on one (different) test: Error: error:078C0102:common libcrypto routines::passed a null parameter test-hmac.c:275: Assert(#3) failed: memcmp(res->data, vec->okm, vec->okm_len) == 0 hkdf sha256 rfc5869 vectors .......................................... : FAILED My assumption as yet unverified is that the fedora specific patches are avoiding the two test errors iwhen using the unpatched source, but contribute to the error produced when using the patched source, though my test did not rule out environment differences between these two tests. John

2 2

Failed tests in core & pigeonhole git HEAD
by Patrick 02 Jan '26

02 Jan '26

Hi, Happy New Year! During make check of core git rev 6d6724bd529493c448d5aa02e70aee9aaff4f2c3 (from github) with mock a test fails with: <mock-chroot> sh-5.3# more test-suite.log ============================================ Dovecot 2.4.3: src/imap/test-suite.log ============================================ # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 System information (uname -a): Linux 6.17.12-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 13 05:06:24 UTC 2025 x8 6_64 Distribution information (/etc/os-release): NAME="Fedora Linux" VERSION="43 (Forty Three)" RELEASE_TYPE=stable ID=fedora VERSION_ID=43 VERSION_CODENAME="" PRETTY_NAME="Fedora Linux 43 (Forty Three)" ANSI_COLOR="0;38;2;60;110;180" .. contents:: :depth: 2 FAIL: test-imap-client-hibernate ================================ imap client hibernate: non-IDLE ...................................... : ok test-common.c:300: Assert failed: suppress == TRUE test-imap-client-hibernate: Error: Couldn't hibernate imap client: net_connect_unix(/builddir/build/BUILD/dovecot-2 .4.3-build/dovecot/.test/imap-client-hibernate-130478.fdf4a74f3b5b21f2/imap-hibernate) failed: File name too long imap client hibernate: socket not found .............................. : FAILED test-imap-client-hibernate: Fatal: net_listen_unix(/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/.test/imap-cli ent-hibernate-130478.fdf4a74f3b5b21f2/imap-hibernate) failed: File name too long FAIL test-imap-client-hibernate (exit status: 89) Pigeonhole git rev 7229ac65540889fc3e9658c4623eafc5a9952006 make check shows: make check-local make[1]: Entering directory '/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/dovecot-pigeonhole' rm -rf ./.test make[1]: Leaving directory '/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/dovecot-pigeonhole' testsuite: Fatal: execv(/usr/bin/doveconf) failed: No such file or directory make: *** [Makefile:1280: tests/testsuite.svtest] Error 84 Best, Patrick

1 0

Hello, i came here for Your help cant do a proper configuration of dovecot from 2.3.X to 2.4.1
by revolt2＠wp.pl 31 Dec '25

31 Dec '25

I would like to ask if someone could correct the configuration file for Dovecot dovecot.conf for version 2.4.1? Its the old file from 2.3.X but I'm sorry to say it doesn't work ;( https://pastebin.com/BjXuPEvv , and here is an dovecot-sql.conf file : https://pastebin.com/C4dFG2Zi If any further changes are needed, please let me know, I will adapt, I tried to understand the AI documentation but I couldn't, so we have to meet here,, Thank you in advance for your help

3 2

2.4 use a dictionary when receiving authentification requests
by info＠opdepc.nl 31 Dec '25

31 Dec '25

In conf.d/10-auth.conf I do: dict lookuptable { dict_name = lookuptable dict_driver = file dict_file_path = /etc/dovecot/mailtouserid.dict } auth_username_format = %{user | lower | dict:lookuptable/shared/ } But it seems the dictionary doesn't work here... it is skipped. Is this a bug, is it something that will be added lateron or do I do something wrong? My goal is to allow users to logon with their email address as username. Best wishes for 2026 to all! -Huibert.

2 4

quota_mailbox_message_count
by James 31 Dec '25

31 Dec '25

New for 2.4 is quota_mailbox_message_count. I have set limits for: quota_storage_size quota_message_count quota_mailbox_message_count Defaults in dovecot.conf and per user value from userdb sql. These are working proved by the rejection of test messages. 1. To monitor users' quotas one can run: doveadm quota get -A This lists values for Types STORAGE and MESSAGE. Is there a way to list mailbox_message_count values? It is per mailbox so might need a mailbox option on doveadm. doveadm-quota(1) shows -A and -u. 2. How does one send quota warning messages when quota_mailbox_message_count crosses thresholds? The documentation [1] has examples for quota_storage_size and quota_message_count but not quota_mailbox_message_count. I am missing quota_mailbox_message_percentage. Thank you. 1. Quota example: https://doc.dovecot.org/2.4.2/core/plugins/quota.html#example-configuration

2 2

Minor note about what seems like a behavior change with the 'user' field in passdb/userdb overrides
by Andy Baugh 30 Dec '25

30 Dec '25

Just finished fixing a bug with our setup where the "archive" pseudo-user we setup wasn't listing the correct dirs in IMAP yet would show their other mailboxes, folders, etc. just fine via `doveadm mailbox list`. Turns out the issue was that the 'user' field is more important on dovecot 2.4's IMAP implementation than on 2.3, but in ways that the documentation didn't really suggest to me. In both cases it says that it overrides the user, but what that means is different. On 2.3, it's mostly saying "act as if you are this user but with these other params we set in the user/passdb return" On 2.4.x, it is a straight up alias to another userdb/passdb return in IMAP's context, so any other params you override do not in fact get used. You can pretty quickly verify this with `doveadm user`/`doveadm auth lookup` calls; when your "override" user matches another user which has an entry reported back from your userdb/passdb, it just returns their data instead even if your auth source provided other data. What's odd to me is more that `doveadm mailbox list` worked "as expected" here, as everything else was consistent with 'user' being an aliasing trigger. I wound up fixing my bug by just no longer setting the 'user' variable for this archival psuedo-user, and instead relying on the (already set even on 2.3) uid/gid fields to make sure they didn't have permissions errors. Then things worked precisely how they did on 2.3. I only figured this out by accidentally making a new IMAP dir for the original user and then noticing that show up for the pseudo-user (I then scrutinized the userdb/passdb returns more carefully, then noticing the difference). Hopefully my tale helps others avoid the many hours of fruitless debugging I was doing before making that crucial mistake lol. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

1 0

Error I can't fix
by John Hill 27 Dec '25

27 Dec '25

Hello, I’m encountering a reproducible parsing issue in Dovecot 2.4 on Debian 13 (Trixie). Even when /etc/dovecot/conf.d/auth-sql.conf.ext contains a valid passdb block, Dovecot reports that the block is empty. Environment: - Debian 13 (Trixie) - Dovecot 2.4 (from Debian repository) - Clean install, no custom patches Error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/auth-sql.conf.ext line 1: passdb { } is missing section name Steps to reproduce: 1. Remove the file: rm -f /etc/dovecot/conf.d/auth-sql.conf.ext 2. Recreate it cleanly: cat > /etc/dovecot/conf.d/auth-sql.conf.ext <<'EOF' passdb { driver = sql args = /etc/dovecot/sql.conf.ext } userdb { driver = sql args = /etc/dovecot/sql.conf.ext } EOF 3. Verify the file contents: sed -n '1,20p' /etc/dovecot/conf.d/auth-sql.conf.ext | cat -A Output: passdb {$ driver = sql$ args = /etc/dovecot/sql.conf.ext$ }$ $ userdb {$ driver = sql$ args = /etc/dovecot/sql.conf.ext$ }$ 4. Run: doveconf Actual result: Dovecot still reports that the passdb block is empty, even though the file is valid. Expected result: Dovecot should accept the passdb block and load SQL authentication normally. Additional notes: - No BOM (ef bb bf) present. - No CRLF (^M) present. - No stray characters. - File is not a symlink. - No duplicate auth-sql.conf.ext files exist. - The include line in 10-auth.conf is correct. - The error persists even after full deletion and recreation of the file. This appears to be a parser or include-path issue in Dovecot 2.4. Any guidance or confirmation would be appreciated.

4 7

dovecot-optimize FTS Xapian Failed to open glass revision file for reading
by Torge Riedel 27 Dec '25

27 Dec '25

Dears, from time to time (no regular frequency) I get the following error: /etc/cron.daily/dovecot-optimize: doveadm(account(a)domain.de): Error: FTS Xapian: Optimize (6) /var/vmail/mailboxes/domain.de/account/index/xapian-indexes/db_<longhex>/iamglass: Failed to open glass revision file for reading The reason is the file "iamglass" is owned by "root", when I change this back to "vmail" the error disappears for a while. I do not find the cause why this sometimes changes. And it is only this file, where the ownership changes. The content of /etc/cron.daily/dovecot-optimize is: #!/bin/sh doveadm fts optimize -A I welcome any help / hint, thanks and kind regards Torge

1 0

mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings)
by Klaus Tachtler 26 Dec '25

26 Dec '25

Hello everyone, Problem info: An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: 45 sql_driver = mysql 46 47 mysql db.idmz.tachtler.net { 48 host = db.idmz.tachtler.net 49 port = 3306 50 user = postfixuser 51 password = geheim 52 dbname = postfix 53 ssl = yes 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem 55 ssl_client_cert_file = /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem 56 ssl_client_key_file = /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem 57 ssl_cipher_list = DHE-RSA-AES256-SHA 58 } WITHOUT the following line, a database connections is possible and works as expected: 53 ssl = yes 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem 55 ssl_client_cert_file = /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem 56 ssl_client_key_file = /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

1 0

Rootless docker image missing /usr/bin/sleep causing health check to not work
by saturos+dove＠gmail.com 23 Dec '25

23 Dec '25

Hello! I was attempting to set up health checking as in the Health Checking document [1]. But it seems that the rootless image is missing the sleep command, which prints the error: dovecot[16633]: Dec 22 22:05:04 health-check: Error: /dovecot/libexec/dovecot/health-check.sh: 31: sed: not found Reproduction: $ podman run --rm -it index.docker.io/dovecot/dovecot:latest-dev which sleep /usr/bin/sleep $ podman run --rm -it index.docker.io/dovecot/dovecot:latest-root which sleep /usr/bin/sleep $ podman run --rm -it index.docker.io/dovecot/dovecot:latest which sleep $ Set up healthchecking on 5001. With latest: $ echo -e "PING\n" | nc -v localhost 5001 Connection to localhost (::1) 5001 port [tcp/*] succeeded! $ With latest-dev: $ echo -e "PING\n" | nc -v localhost 5001 Connection to localhost (::1) 5001 port [tcp/*] succeeded! PONG and the error log above is generated. Version: $ podman run --rm -it index.docker.io/dovecot/dovecot:latest dovecot --version 2.4.2 (0962ed2104) [1] https://doc.dovecot.org/2.4.2/core/config/health_check.html

2 1

quota_mail_size question
by Marcel Menzel 22 Dec '25

22 Dec '25

Hello List, I've enabled the quota_mail_size parameter to match what I've set in Postfix, but it seems to me that this parameter has no effect. Currently set to quota_mail_size = 104857600B (with or without the suffix does not matter in my case as both won't work), but connecting to the LMTP socket does not seem to advertise SIZE: # socat /run/dovecot/lmtp readline 220 mail-fra01 Hello there LHLO test 250-mail-fra01 250-8BITMIME 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-SMTPUTF8 250 STARTTLS quit 221 2.0.0 Bye Also looking at IMAP logs on clients, APPENDLIMIT also does not seem to get advertised there. Quota itself seems to work fine via userdb, also via the IMAP quota extension as my clients report the usage. Thanks, Marcel doveconf -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-hardened1-1-hardened x86_64 # Hostname: mail-fra01 dovecot_config_version = 2.4.2 auth_verbose = yes dovecot_storage_version = 2.4.2 first_valid_uid = 8 fts_autoindex = yes hostname = mail-fra01 imap4rev2_enable = yes last_valid_uid = 8 lmtp_rcpt_check_quota = yes login_greeting = Hello there mail_driver = maildir mail_gid = mail mail_home = /var/vmail/%{user | domain}/%{user | username} mail_path = ~/ mail_plugins { quota = yes quota_clone = yes notify = yes virtual = yes fts = yes fts_xapian = yes } mail_server_admin = mailto:marcel@menzel.de mail_server_comment = hi mail_uid = mail mail_utf8_extensions = yes mailbox_list_storage_escape_char = \ mailbox_list_utf8 = yes passdb_default_password_scheme = SHA256-CRYPT protocols { imap = yes pop3 = yes sieve = yes lmtp = yes } quota_mail_size = 104857600B quota_status_nouser = DUNNO sieve_global_extensions { vnd.dovecot.pipe = yes vnd.dovecot.environment = yes } sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins { sieve_imapsieve = yes sieve_extprograms = yes } sieve_redirect_envelope_from = recipient sql_driver = pgsql ssl = required ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305 ssl_curve_list = X448:X25519:P-256 ssl_options = no_ticket submission_host = 127.0.0.1:25 verbose_proctitle = yes protocol imap { imap_hibernate_timeout = 10 secs imap_idle_notify_interval = 29 mins imap_metadata = yes mail_max_userip_connections = 50 mail_plugins { imap_quota = yes imap_sieve = yes last_login = yes } } protocol pop3 { mail_plugins { last_login = yes } } protocol sieve { mail_plugins { last_login = yes } } protocol lmtp { mail_plugins { sieve = yes push_notification = yes } postmaster_address = postmaster@%{user | domain} } service lmtp { user = mail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service auth-worker { user = $SET:default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = dovecot mode = 0660 user = mail } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } } service indexer-worker { vsz_limit = 8 G } maildir { very_dirty_syncs = yes } mail_attribute { dict file { path = %{home}/dovecot-attributes } } fts xapian { } language en { default = yes } language de { } namespace inbox { inbox = yes separator = / mailbox Archive { auto = subscribe special_use = "\\Archive" } mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { fts_autoindex = no auto = subscribe autoexpunge = 30 days special_use = "\\Junk" } mailbox Sent { special_use = "\\Sent" } mailbox Trash { fts_autoindex = no auto = subscribe autoexpunge = 120 days special_use = "\\Trash" quota_storage_extra = 100M } } pgsql mcl { parameters { dbname = mail host = 10.10.3.2 password = <redacted> port = 6432 sslmode = disable user = mail } } userdb sql { iterate_query = SELECT username AS user FROM mailbox; query = SELECT CONCAT(quota, 'B') AS quota_storage_size FROM mailbox WHERE username = '%{user | lower}' LIMIT 1; } passdb sql { query = SELECT username AS user, password, allow_nets FROM mailbox WHERE username = '%{user | lower}' AND active = true LIMIT 1; } ssl_server { cert_file = /etc/ssl/private/dovecot.crt.pem key_file = /etc/ssl/private/dovecot.pk.pem prefer_ciphers = server } ssl_client { ca_dir = /etc/ssl/certs } sieve_script default { name = default path = /var/vmail/global.sieve type = default } sieve_script personal { active_path = /var/vmail/%{user | domain}/%{user | username}/dovecot.sieve path = /var/vmail/%{user | domain}/%{user | username}/sieve type = personal } mailbox Spam { sieve_script spam { cause = copy append path = /usr/lib/dovecot/sieve-pipe/report-spam.sieve type = before } } imapsieve_from Spam { sieve_script ham { cause = copy append path = /usr/lib/dovecot/sieve-pipe/report-ham.sieve type = before } } quota "User quota" { } quota_clone { dict proxy { name = quota_clone_sql } } dict_server { dict quota_clone_sql { driver = sql sql_driver = pgsql dict_map priv/quota/messages { sql_table = quota2 username_field = username dict_map_value_field messages { } } dict_map priv/quota/storage { sql_table = quota2 username_field = username dict_map_value_field bytes { } } } }

2 1

2.4.2 post login core dump when trash plugin is enabled
by Aragon Gouveia 22 Dec '25

22 Dec '25

Hi, docker run --rm --name dovecot -e USER_PASSWORD=test123 -v dovecot_mail:/srv/vmail -v ~aragon/dovetest/local.conf:/etc/dovecot/conf.d/local.conf -p 110:31110 -p 143:31143 --ulimit core=-1 dovecot/dovecot:latest-dev Dec 16 00:49:57 master: Info: Dovecot v2.4.2 (0962ed2104) starting up for imap, pop3, lmtp, sieve Dec 16 00:50:08 pop3-login: Info: Logged in: user=<test>, method=PLAIN, rip=172.17.0.1, lip=172.17.0.2, mpid=16, secured, session=<m5/SGwdGHNKsEQAB> Dec 16 00:50:08 pop3(test)<16><m5/SGwdGHNKsEQAB>: Fatal: master: service(pop3): child 16 killed with signal 11 (core dumped) Contents of ~aragon/dovetest/local.conf: mail_plugins { quota = yes trash = yes } protocols = imap pop3 lmtp sieve login_trusted_networks = 172.16.0.0/15 # telnet localhost 110 Trying ::1... Connected to localhost. Escape character is '^]'. +OK [XCLIENT] Dovecot ready. user test +OK pass test123 +OK Logged in. Connection closed by foreign host. dovecot-sysreport uploaded to https://limewire.com/d/PLgit#mrIN2Wx73J Is this sufficient info? Regrettably no debug symbols in the Docker builds, unless I missed something. Thank you in advance. Regards, Aragon

2 2

Sieve regex behavior
by Luca Weiss 22 Dec '25

22 Dec '25

Hi, I'm having troubles lately with a Sieve script of mine: require "fileinto"; require "mailbox"; require "regex"; if header :regex "Subject" "\\[.*PATCH.*\\]" { fileinto :create "Inbox.Patches"; } This should move all patches with "[PATCH]" or "[RFC PATCH v3]" into this Inbox subfolder, I'm pretty sure this version worked flawlessly in the past but since a couple of weeks ago it's not working with some emails. Debugging this, with manually editing mail files, I came to this discovery. That one mail matches and it's getting moved to the correct folder: Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: qcm6490-shift-otter: A Adding one more character leads to it not getting moved: Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: qcm6490-shift-otter: Ad Does anybody have an explanation for this why this broke, and how to fix either Dovecot/Pigeonhole or my Sieve script? I've already lost hours trying to figure this out and I'm not getting any wiser... Regards Luca

4 3

Error after power failure
by Doug Hardie 22 Dec '25

22 Dec '25

My mail server lost power and now I am having issues with dsync for one user. Here is the command and output: mail# doveadm backup -u doug remote:sermons dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: /var/mail/home_mail/doug/Maildir/dovecot.index: Couldn't set transaction log view (seq 295..297): Missing middle file seq=296 (between 295..297, we have seqs 295,297): Not found from .log.2: File is already open dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: Failed to read transaction log for mailbox INBOX dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: Remote command returned error 75: ssh sermons doveadm dsync-server -udoug -U How do I fix this issue? Thanks, -- Doug

2 1

Pigeonhole managesieve-login panic
by revsuine 19 Dec '25

19 Dec '25

Hi folks, I'm getting a ``` Dec 19 16:18:07 managesieve-login: Panic: file client.c: line 350 (managesieve_client_input_next_cmd): assertion failed: (args != NULL) Dec 19 16:18:07 auth: Debug: conn unix:login (pid=7390,uid=91) [2]: Disconnected: Connection closed (fd=20) Dec 19 16:18:07 managesieve-login: Fatal: master: service(managesieve-login): child 7390 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) ``` When trying to connect to MANAGESIEVE using [sieve-connect][1]. The command I'm using is ``` sieve-connect -s revsuine.xyz -u pid1 --passwordfd=5 5<<<"$(command to get pass here)" ``` This command was working previously (within the past year), though I don't remember which versions of Dovecot/Pigeonhole I tried it on. sieve-connect has not been updated recently, so there aren't any changes in sieve-connect that would've caused this. I'm attaching the files generated by `dovecot-sysreport` which includes my `dovecot -n`. Server OS is Alpine Linux 3.23.2. ~revsuine [1]: https://github.com/philpennock/sieve-connect

1 0

Attachments corrupted by sieve "redirect" action
by Michael Orlitzky 18 Dec '25

18 Dec '25

We got a report today from one of our customers that they are unable to "redirect" mail with attachments off-site. At first I was skeptical, because sieve does not mess with the message body... but sure enough, it's easy to reproduce: 1. Create a new address (mailbox) 2. Create a single sieve "redirect" filter for that address, pointing to my own mailbox 3. Send it a message with an attachment 4. An attachment is visible on the message that arrives, but it is corrupt For example: $ cat hello.original.txt Hello, world! but $ cat hello.attached.txt (it's empty). Sending a JPEG image is a bit more enlightening: $ /bin/ls -l *jpg -rw------- 1 mjo mjo 337119 Dec 18 11:15 image.attached.jpg -rw-r--r-- 1 mjo mjo 337173 Dec 18 11:13 image.original.jpg So something _is_ sent, but the start of the file is corrupt. Looking at it in a hex editor, it's only the first few lines that are messed up. This is with dovecot 2.4.2, but notably, we are using zlib compression: mail_plugins = mail_compress mail_compress_write_method = gz I'm curious if anyone else can reproduce this? Redirecting via sieve is not common, so this isn't an emergency, but obviously it is preferable to have it working.

2 1

Imap-login bind errors after upgrading dovecot from 2.3 to 2.4
by onyeibo 18 Dec '25

18 Dec '25

Greetings I updated the OS in a VPS blindly and broke the mail service. I had set up this service over four years ago and never had issues with upgrades until recently. I realized the gravity of my mistake after dovecot refused to start. Version 2.4.1 had arrived and I am in so much trouble. So far, I have adapted the configuraton files to 2.4 standards. "doveadm auth test user" tells me that the authentication is working fine. I am able to view old mails via doveadm. However, I get nothing new from mail clients. The maillog tells me that mails are getting queued (why?). I see status=sent (250.2.0.0) in some transactions, but that is the extent of success. However, I still get a nagging error message (see the end of this mail). dovecot -n # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.11-300.fc43.x86_64 x86_64 Fedora release 43 (Forty Three) dovecot_config_version = 2.4.1 auth_debug = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 first_valid_uid = xxxx mail_driver = maildir mail_home = /home/mails/%{user | domain}/%{user | username} mail_path = %{home}/Maildir mail_privileged_group = mail passdb_default_password_scheme = BLF-CRYPT protocols { imap = yes lmtp = yes sieve = yes } sql_driver = pgsql ssl = required ssl_cipher_list = PROFILE=SYSTEM pgsql localhost { parameters { dbname = postfix password = xxxxxxx user = postfix } } passdb sql {n query = SELECT username AS user, password FROM mailbox WHERE username = '%{user}' AND active='1' } userdb sql { query = SELECT '/home/mails/' || maildir AS home, xxxx as uid, xxxx as gid FROM mailbox WHERE username = '%{user}' AND active = '1' } namespace inbox { inbox = yes mailbox Drafts { auto = create special_use = "\\Drafts" } mailbox Junk { auto = create special_use = "\\Junk" } mailbox Trash { auto = create special_use = "\\Trash" } mailbox Sent { auto = create special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service lmtp { executable = lmtp -L process_min_avail = 5 user = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_server { cert_file = /etc/letsencrypt/live/xxxxxxx.com/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/xxxxxxx.com/privkey.pem prefer_ciphers = server } protocol lmtp { info_log_path = /var/log/lmtp/dovecot-lmtp.log mail_plugins { sieve = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve} I did adjust an entry in postfix (master.cf). I switched from dovecot-lda to dovecot-lmtp. LDA was throwing permission errors when accessing the cert file. Most reference materials recommended LMTP because its processes already have the required privileges. So ... master.cf (postfix)dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -a ${original_recipient} -d ${user}@${nexthop}# maillog errors Dec 16 22:16:29 xxxxxxx.com dovecot[139456]: master: Error: bind(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 xxxxxxx.com dovecot[139456]: master: Fatal: Failed to create per-PID unix_listener %{pid}: net_listen_unix(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 xxxxxxx.com dovecot[809]: master: Error: service(imap-login): command startup failed, throttling for 2.000 secsDec 16 22:16:29 xxxxxxx.com dovecot[139216]: imap-login: Fatal: master: service(imap-login): child 139456 returned error 89 (Fatal failure) What am I missing? Regards Onyeibo Greetings I updated the OS in a VPS blindly and broke the mail service. I had set up this service over four years ago and never had issues with upgrades until recently. I realized the gravity of my mistake after dovecot refused to start. Version 2.4.1 had arrived and I am in so much trouble. So far, I have adapted the configuraton files to 2.4 standards. "doveadm auth test user" tells me that the authentication is working fine. I am able to view old mails via doveadm. However, I get nothing new from mail clients. The maillog tells me that mails are getting queued (why?). I see status=sent (250.2.0.0) in some transactions, but that is the extent of success. However, I still get a nagging error message (see the end of this mail). dovecot -n # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.11-300.fc43.x86_64 x86_64 Fedora release 43 (Forty Three) dovecot_config_version = 2.4.1 auth_debug = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 first_valid_uid = xxxx mail_driver = maildir mail_home = /home/mails/%{user | domain}/%{user | username} mail_path = %{home}/Maildir mail_privileged_group = mail passdb_default_password_scheme = BLF-CRYPT protocols { imap = yes lmtp = yes sieve = yes } sql_driver = pgsql ssl = required ssl_cipher_list = PROFILE=SYSTEM pgsql localhost { parameters { dbname = postfix password = xxxxxxx user = postfix } } passdb sql {n query = SELECT username AS user, password FROM mailbox WHERE username = '%{user}' AND active='1' } userdb sql { query = SELECT '/home/mails/' || maildir AS home, xxxx as uid, xxxx as gid FROM mailbox WHERE username = '%{user}' AND active = '1' } namespace inbox { inbox = yes mailbox Drafts { auto = create special_use = "\\Drafts" } mailbox Junk { auto = create special_use = "\\Junk" } mailbox Trash { auto = create special_use = "\\Trash" } mailbox Sent { auto = create special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service lmtp { executable = lmtp -L process_min_avail = 5 user = vmail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_server { cert_file = /etc/letsencrypt/live/xxxxxxx.com/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/xxxxxxx.com/privkey.pem prefer_ciphers = server } protocol lmtp { info_log_path = /var/log/lmtp/dovecot-lmtp.log mail_plugins { sieve = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve } I did adjust an entry in postfix (master.cf). I switched from dovecot-lda to dovecot-lmtp. LDA was throwing permission errors when accessing the cert file. Most reference materials recommended LMTP because its processes already have the required privileges. So ... master.cf (postfix) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -a ${original_recipient} -d ${user}@${nexthop}# maillog errors Dec 16 22:16:29 [1]xxxxxxx.com dovecot[139456]: master: Error: bind(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 [2]xxxxxxx.com dovecot[139456]: master: Fatal: Failed to create per-PID unix_listener %{pid}: net_listen_unix(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 [3]xxxxxxx.com dovecot[809]: master: Error: service(imap-login): command startup failed, throttling for 2.000 secs Dec 16 22:16:29 [4]xxxxxxx.com dovecot[139216]: imap-login: Fatal: master: service(imap-login): child 139456 returned error 89 (Fatal failure) What am I missing? Regards Onyeibo References Visible links 1. http://xxxxxxx.com/ 2. http://xxxxxxx.com/ 3. http://xxxxxxx.com/ 4. http://xxxxxxx.com/

4 9

Bug Report: authCacheFlush HTTP API crashes with assertion failure
by Yurii Krainiuk 17 Dec '25

17 Dec '25

*## Title* authCacheFlush HTTP API crashes with assertion failure - type mismatch between API schema and implementation *## Dovecot Version* 2.4.2 *## Component* doveadm HTTP API *## Description* The authCacheFlush command via doveadm HTTP API causes a server crash with an assertion failure. The HTTP API schema declares the user parameter as array type, but the internal implementation (doveadm_cmd_param_str) expects string type, causing a type mismatch assertion failure. *## Steps to Reproduce* 1. Send any authCacheFlush request to doveadm HTTP API: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":"username(a)domain.com"},"tag1"]]' \ http://localhost:8080/doveadm/v1 2. Or with user as array (matching the declared schema): bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":["username(a)domain.com"]},"tag1"]]' \ http://localhost:8080/doveadm/v1 3. Or without any parameters: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{},"tag1"]]' \ http://localhost:8080/doveadm/v1 *## Expected Result* Auth cache should be flushed and API returns success response like: json [["doveadmResponse",[{"entries":1}],"tag1"]] *## Actual Result* Server crashes with empty reply (HTTP connection closed). The doveadm process is killed with signal 6 (SIGABRT). *## Error Log* Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) Error: Raw backtrace: #0 test_subprocess_fork[0x7362eb54a570] -> #1 backtrace_append[0x7362eb54a820] -> #2 backtrace_get[0x7362eb54a9c0] -> #3 e_info[0x7362eb556370] -> #4 i_syslog_fatal_handler[0x7362eb5564b0] -> #5 i_panic[0x7362eb474f28] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7362eb4e6a00] -> #8 io_loop_call_io[0x7362eb572510] -> #9 io_loop_handler_run_internal[0x7362eb5743a0] -> #10 io_loop_handler_run[0x7362eb574540] -> #11 io_loop_run[0x7362eb574740] -> #12 master_service_run[0x7362eb4bc640] -> #13 main[0x64c4233d74f0] -> #14 __libc_init_first[0x7362eb02a150] -> #15 __libc_start_main[0x7362eb02a200] -> #16 _start[0x64c4233d76e0] Fatal: master: service(doveadm): child 2302469 killed with signal 6 (core dumped) *## API Schema (from GET /doveadm/v1)* The API endpoint reports the following schema for authCacheFlush: json { "command": "authCacheFlush", "parameters": [ {"name": "socketPath", "type": "string"}, {"name": "user", "type": "array"} ] } *## Analysis* The API schema declares user as array, but line 120 in doveadm-cmd-parse.c calls doveadm_cmd_param_str() which asserts param->type == CMD_PARAM_STR. This type mismatch causes the crash. The relevant assertion in source code: c // doveadm-cmd-parse.c:120 assertion failed: (param->type == CMD_PARAM_STR) *## Note* - The CLI command doveadm auth cache flush <user> works correctly - Only the HTTP API is affected - All authentication methods (X-Dovecot-API header, Basic Auth) produce the same crash - The crash occurs regardless of whether parameters are provided or not *## Workaround* Currently no workaround via HTTP API. Must use CLI directly or via SSH. *## Environment* - OS: Linux (Ubuntu/Debian) - Dovecot: 2.4.2 - doveadm HTTP API enabled on port 8080 ## Title authCacheFlush HTTP API crashes with assertion failure - type mismatch between API schema and implementation ## Dovecot Version 2.4.2 ## Component doveadm HTTP API ## Description The authCacheFlush command via doveadm HTTP API causes a server crash with an assertion failure. The HTTP API schema declares the user parameter as array type, but the internal implementation (doveadm_cmd_param_str) expects string type, causing a type mismatch assertion failure. ## Steps to Reproduce 1. Send any authCacheFlush request to doveadm HTTP API: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":"[1]username(a)domain.com"},"tag1"]]' \ [2]http://localhost:8080/doveadm/v1 2. Or with user as array (matching the declared schema): bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":["[3]username(a)domain.com"]},"tag1"]]' \ [4]http://localhost:8080/doveadm/v1 3. Or without any parameters: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{},"tag1"]]' \ [5]http://localhost:8080/doveadm/v1 ## Expected Result Auth cache should be flushed and API returns success response like: json [["doveadmResponse",[{"entries":1}],"tag1"]] ## Actual Result Server crashes with empty reply (HTTP connection closed). The doveadm process is killed with signal 6 (SIGABRT). ## Error Log Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) Error: Raw backtrace: #0 test_subprocess_fork[0x7362eb54a570] -> #1 backtrace_append[0x7362eb54a820] -> #2 backtrace_get[0x7362eb54a9c0] -> #3 e_info[0x7362eb556370] -> #4 i_syslog_fatal_handler[0x7362eb5564b0] -> #5 i_panic[0x7362eb474f28] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7362eb4e6a00] -> #8 io_loop_call_io[0x7362eb572510] -> #9 io_loop_handler_run_internal[0x7362eb5743a0] -> #10 io_loop_handler_run[0x7362eb574540] -> #11 io_loop_run[0x7362eb574740] -> #12 master_service_run[0x7362eb4bc640] -> #13 main[0x64c4233d74f0] -> #14 __libc_init_first[0x7362eb02a150] -> #15 __libc_start_main[0x7362eb02a200] -> #16 _start[0x64c4233d76e0] Fatal: master: service(doveadm): child 2302469 killed with signal 6 (core dumped) ## API Schema (from GET /doveadm/v1) The API endpoint reports the following schema for authCacheFlush: json { "command": "authCacheFlush", "parameters": [ {"name": "socketPath", "type": "string"}, {"name": "user", "type": "array"} ] } ## Analysis The API schema declares user as array, but line 120 in doveadm-cmd-parse.c calls doveadm_cmd_param_str() which asserts param->type == CMD_PARAM_STR. This type mismatch causes the crash. The relevant assertion in source code: c // doveadm-cmd-parse.c:120 assertion failed: (param->type == CMD_PARAM_STR) ## Note - The CLI command doveadm auth cache flush <user> works correctly - Only the HTTP API is affected - All authentication methods (X-Dovecot-API header, Basic Auth) produce the same crash - The crash occurs regardless of whether parameters are provided or not ## Workaround Currently no workaround via HTTP API. Must use CLI directly or via SSH. ## Environment - OS: Linux (Ubuntu/Debian) - Dovecot: 2.4.2 - doveadm HTTP API enabled on port 8080 References Visible links 1. mailto:username@domain.com 2. http://localhost:8080/doveadm/v1 3. mailto:username@domain.com 4. http://localhost:8080/doveadm/v1 5. http://localhost:8080/doveadm/v1

2 1

mTLS ldap auth failure against openldap + TLSVerifyClient: demand
by Patrick Laimbock 16 Dec '25

16 Dec '25

Hi, I'm trying to setup up a Dovecot/Postfix/OpenLDAP combo on a Fedora 43 aarch64 box with the following versions: dovecot-2.4.2 from https://src.fedoraproject.org/rpms/dovecot/tree/rawhide and rebuilt for F43 at https://copr.fedorainfracloud.org/coprs/patrickl/dovecot/ postfix-3.10.3 openldap-2.6.10 openssl-3.5.4 Problem: I can't seem to make Dovecot (lmtp) establish a mTLS connection with the slapd server. Postfix works fine when using /etc/postfix/ldap-aliases.cf etc to get info from the slapd server which demands that the client sends a certificate due to olcTLSVerifyClient: demand. This is with a self-signed CA, intermediate CA and client & server certificates. Dovecot journalctl error: lmtp(92847): Error: lmtp-server: conn unix:pid=92846,uid=89 [1]: rcpt patrick@<domain>: Failed to lookup user patrick@<domain>: Internal error occurred. Refer to server log for more information. # doveadm log errors Dec 15 22:35:41.655525 Error: auth: ldap(ldaps://<FQDN>:636): Connection lost to LDAP server, reconnecting <snipped many more of the same message> Slapd error: TLS trace: SSL_accept:before SSL initialization <snip> TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL3 alert write:fatal:unknown TLS trace: SSL_accept:error in error TLS: can't accept: error:0A0000C7:SSL routines::peer did not return a certificate. TLS accept failure error=-1 id=1178, closing conn=1178 fd=15 closed (TLS negotiation failure) It seems that Dovecot does not send its client certificate to the slapd server when asked? Perhaps due to a config error? Example with postfix where the client cert is sent and mTLS succeeds: # postmap -q info@<domain> ldap:/etc/postfix/ldap-aliases.cf TLS trace: SSL_accept:before SSL initialization TLS trace: SSL_accept:before SSL initialization SSL_accept:SSLv3/TLS read SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS certificate verification: depth: 2, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 1, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 0, err: 0, subject: /CN=postfix-ldap, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA TLS trace: SSL_accept:TLSv1.3 read client compressed certificate TLS trace: SSL_accept:SSLv3/TLS read certificate verify TLS trace: SSL_accept:SSLv3/TLS read finished TLS trace: SSL_accept:SSLv3/TLS write session ticket TLS trace: SSL_accept:SSLv3/TLS write session ticket conn=1000 fd=13 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.3 tls_cipher=TLS_AES_256_GCM_SHA384 Dovecot config # dovecot -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-300.fc43.aarch64 aarch64 Fedora release 43 (Forty Three) # Hostname: <FQDN> # 5 default setting changes since version 2.4.1 dovecot_config_version = 2.4.1 auth_mechanisms = plain dovecot_storage_version = 2.4.1 first_valid_uid = 1000 ldap_auth_dn = cn=dovecot,dc=hosted,dc=ldap ldap_auth_dn_password = # hidden, use -P to show it ldap_uris = ldaps://<FQDN> log_debug = category=ssl mail_driver = sdbox mail_gid = vmail mail_home = /var/mail/virtual/%{user | domain}/%{user | username} mail_path = ~/mail mail_uid = vmail protocols { imap = yes lmtp = yes } ssl = required ssl_cipher_list = PROFILE=SYSTEM ssl_cipher_suites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 ssl_min_protocol = TLSv1.3 namespace inbox { inbox = yes separator = / } ssl_server { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/kronos.laimbock.nl.crt key_file = /etc/pki/dovecot/private/kronos.laimbock.nl_nopass.key.crt prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/dovecot-ldap.crt key_file = /etc/pki/dovecot/private/dovecot-ldap_nopass.key.crt require_valid_cert = yes } protocol !smtp { auth_ssl_require_client_cert = yes } passdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap default_password_scheme = CRYPT fields { user = %{ldap:mail} } bind = yes filter = (&(objectClass=person)(mail=%{user})) } userdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap fields { user = %{ldap:mail} } filter = (&(objectClass=person)(uid=%{user})) } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } The dovecot_ca_bundle.pem is created with # cat subca.crt ca.crt > dovecot_ca_bundle.pem The RootCA is imported into the trust store via: # cp ca.crt /etc/pki/ca-trust/source/anchors/ # update-ca-trust extract The public certificates live in /etc/pki/dovecot/certs: lrwxrwxrwx. 1 root root 16 Dec 15 15:49 1c2dd8a4.0 -> dovecot-ldap.crt lrwxrwxrwx. 1 root root 22 Dec 15 15:49 8dafd16f.0 -> <FQDN>.crt lrwxrwxrwx. 1 root root 9 Dec 15 20:15 d18284cf.0 -> subca.crt -rw-r--r--. 1 root root 773 Dec 12 21:21 dhparam -rw-r--r--. 1 root root 3456 Dec 15 21:34 dovecot_ca_bundle.pem -rw-r--r--. 1 root root 1586 Dec 15 20:15 dovecot-ldap.crt -rw-r--r--. 1 root root 1655 Dec 15 20:15 <FQDN>.crt -rw-r--r--. 1 root root 1850 Dec 15 20:15 subca.crt The private keys live in /etc/pki/dovecot/private: -rw-------. 1 root root 1704 Dec 15 20:15 dovecot-ldap_nopass.key.crt -rw-------. 1 root root 1704 Dec 15 20:15 <FQDN>_nopass.key.crt SELinux: there are no AVCs in /var/log/audit/audit.log but to make sure I ran: # restorecon -v -F -R /etc/dovecot # restorecon -v -F -R /etc/pki/doveecot With setenforce 0 no change in results. The slapd config: dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /run/openldap/slapd.args olcPidFile: /run/openldap/slapd.pid olcPasswordCryptSaltFormat: $6$%s olcLogLevel: 1023 # cat subca.crt ca.crt > slapd_ca_bundle.pem olcTLSCACertificateFile: /etc/openldap/certs/slapd_ca_bundle.pem olcTLSCertificateFile: /etc/openldap/certs/<FQDN>.crt olcTLSCertificateKeyFile: /etc/openldap/certs/<FQDN>_nopass.key.crt olcTLSCipherSuite: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 olcTLSVerifyClient: demand olcTLSCRLCheck: none I would appreciate any hints what I missed, what to read, where to look, etc If you need more info I'll be happy to provide. Thanks! Cheers, Patrick

1 0

mTLS ldap auth failure against openldap + TLSVerifyClient: demand
by Patrick Laimbock 16 Dec '25

16 Dec '25

Hi, I'm trying to setup up a Dovecot/Postfix/OpenLDAP combo on a Fedora 43 aarch64 box with the following versions: dovecot-2.4.2 from https://src.fedoraproject.org/rpms/dovecot/tree/rawhide and rebuilt for F43 at https://copr.fedorainfracloud.org/coprs/patrickl/dovecot/ postfix-3.10.3 openldap-2.6.10 openssl-3.5.4 Problem: I can't seem to make Dovecot (lmtp) establish a mTLS connection with the slapd server. Postfix works fine when using /etc/postfix/ldap-aliases.cf etc to get info from the slapd server which demands that the client sends a certificate due to olcTLSVerifyClient: demand. This is with a self-signed CA, intermediate CA and client & server certificates. Dovecot journalctl error: lmtp(92847): Error: lmtp-server: conn unix:pid=92846,uid=89 [1]: rcpt patrick@<domain>: Failed to lookup user patrick@<domain>: Internal error occurred. Refer to server log for more information. # doveadm log errors Dec 15 22:35:41.655525 Error: auth: ldap(ldaps://<FQDN>:636): Connection lost to LDAP server, reconnecting <snipped many more of the same message> Slapd error: TLS trace: SSL_accept:before SSL initialization <snip> TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL3 alert write:fatal:unknown TLS trace: SSL_accept:error in error TLS: can't accept: error:0A0000C7:SSL routines::peer did not return a certificate. TLS accept failure error=-1 id=1178, closing conn=1178 fd=15 closed (TLS negotiation failure) It seems that Dovecot does not send its client certificate to the slapd server when asked? Config error? Example with postfix where this succeeds: # postmap -q info@<domain> ldap:/etc/postfix/ldap-aliases.cf TLS trace: SSL_accept:before SSL initialization TLS trace: SSL_accept:before SSL initialization SSL_accept:SSLv3/TLS read SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS certificate verification: depth: 2, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 1, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 0, err: 0, subject: /CN=postfix-ldap, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA TLS trace: SSL_accept:TLSv1.3 read client compressed certificate TLS trace: SSL_accept:SSLv3/TLS read certificate verify TLS trace: SSL_accept:SSLv3/TLS read finished TLS trace: SSL_accept:SSLv3/TLS write session ticket TLS trace: SSL_accept:SSLv3/TLS write session ticket conn=1000 fd=13 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.3 tls_cipher=TLS_AES_256_GCM_SHA384 Dovecot config # dovecot -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-300.fc43.aarch64 aarch64 Fedora release 43 (Forty Three) # Hostname: <FQDN> # 5 default setting changes since version 2.4.1 dovecot_config_version = 2.4.1 auth_mechanisms = plain dovecot_storage_version = 2.4.1 first_valid_uid = 1000 ldap_auth_dn = cn=dovecot,dc=hosted,dc=ldap ldap_auth_dn_password = # hidden, use -P to show it ldap_uris = ldaps://<FQDN> log_debug = category=ssl mail_driver = sdbox mail_gid = vmail mail_home = /var/mail/virtual/%{user | domain}/%{user | username} mail_path = ~/mail mail_uid = vmail protocols { imap = yes lmtp = yes } ssl = required ssl_cipher_list = PROFILE=SYSTEM ssl_cipher_suites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 ssl_min_protocol = TLSv1.3 namespace inbox { inbox = yes separator = / } ssl_server { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/kronos.laimbock.nl.crt key_file = /etc/pki/dovecot/private/kronos.laimbock.nl_nopass.key.crt prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/dovecot-ldap.crt key_file = /etc/pki/dovecot/private/dovecot-ldap_nopass.key.crt require_valid_cert = yes } protocol !smtp { auth_ssl_require_client_cert = yes } passdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap default_password_scheme = CRYPT fields { user = %{ldap:mail} } bind = yes filter = (&(objectClass=person)(mail=%{user})) } userdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap fields { user = %{ldap:mail} } filter = (&(objectClass=person)(uid=%{user})) } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } The dovecot_ca_bundle.pem is created with # cat subca.crt ca.crt > dovecot_ca_bundle.pem The RootCA is imported into the trust store via: # cp ca.crt /etc/pki/ca-trust/source/anchors/ # update-ca-trust extract The public certificates live in /etc/pki/dovecot/certs: lrwxrwxrwx. 1 root root 16 Dec 15 15:49 1c2dd8a4.0 -> dovecot-ldap.crt lrwxrwxrwx. 1 root root 22 Dec 15 15:49 8dafd16f.0 -> <FQDN>.crt lrwxrwxrwx. 1 root root 9 Dec 15 20:15 d18284cf.0 -> subca.crt -rw-r--r--. 1 root root 773 Dec 12 21:21 dhparam -rw-r--r--. 1 root root 3456 Dec 15 21:34 dovecot_ca_bundle.pem -rw-r--r--. 1 root root 1586 Dec 15 20:15 dovecot-ldap.crt -rw-r--r--. 1 root root 1655 Dec 15 20:15 <FQDN>.crt -rw-r--r--. 1 root root 1850 Dec 15 20:15 subca.crt The private keys live in /etc/pki/dovecot/private: -rw-------. 1 root root 1704 Dec 15 20:15 dovecot-ldap_nopass.key.crt -rw-------. 1 root root 1704 Dec 15 20:15 <FQDN>_nopass.key.crt SELinux: there are no AVCs in /var/log/audit/audit.log but to make sure I ran: # restorecon -v -F -R /etc/dovecot # restorecon -v -F -R /etc/pki/doveecot With setenforce 0 no change in results. The slapd config: dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /run/openldap/slapd.args olcPidFile: /run/openldap/slapd.pid olcPasswordCryptSaltFormat: $6$%s olcLogLevel: 1023 # cat subca.crt ca.crt > slapd_ca_bundle.pem olcTLSCACertificateFile: /etc/openldap/certs/slapd_ca_bundle.pem olcTLSCertificateFile: /etc/openldap/certs/<FQDN>.crt olcTLSCertificateKeyFile: /etc/openldap/certs/<FQDN>_nopass.key.crt olcTLSCipherSuite: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 olcTLSVerifyClient: demand olcTLSCRLCheck: none I would appreciate any hints what I missed, what to read, where to look, etc If you need more info I'll be happy to provide. Thanks! Cheers, Patrick

1 0

Why doesn't Dovecot documentation specify which files to edit?
by n4ch0 13 Dec '25

13 Dec '25

I've noticed that the official Dovecot documentation frequently omits crucial information about which specific files should be modified when configuring different functionalities. Concrete examples: In the LMTP integration guide with Postfix (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-l…) It indicates to modify the socket configuration, but doesn't specify in which file this modification should be made In the quota plugin documentation (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota) It requests enabling the quota module, but doesn't mention the corresponding configuration file I managed to achieve the configuration I wanted but it took more time than it should have. My question: I understand that Dovecot uses a modular configuration system and that technically I can place directives in any file. However, wouldn't it be clearer and more efficient if the documentation followed an established order and specified recommended locations? For example: "Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf" Is there a technical reason why the documentation deliberately avoids recommending specific files, or does it simply assume that users already know these conventions? Is there a general guide about Dovecot's configuration file structure and best practices for organizing them? Thanks!

5 6

Dovecot crash after waking up from sleep
by Peter Psenak 13 Dec '25

13 Dec '25

Hi, I'm experiencing a dovecot crash every time my PC wakes up from sleep. Is this a know issues? # 2.4.0 (daeb6bc59c): /opt/homebrew/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) # OS: Darwin 25.1.0 arm64 File system: APFS Dec 11 22:24:20 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Dec 11 22:24:20 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102dc35f4 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102dc3738 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102dd0b64 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102dcf614 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102dcf5e0 fatal_handler_real + 0 -> 5 dovecot 0x0000000102b1a8fc master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102dcf794 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102e24ce0 event_callback.cold.1 + 0 -> 8 libdovecot.0.dylib 0x0000000102de61c4 io_loops_timeouts_update + 308 -> 9 \libdovecot.0.dylib 0x0000000102e24668 io_loop_handle_timeouts.cold.1 + 20 -> 10 libdovecot.0.dylib 0x0000000102de49b8 io_loop_handle_timeouts + 560 -> 11 libdovecot.0.dylib 0x0000000102de6e64 io_loop_handler_run_internal + 388 -> 12 libdovecot.0.dylib 0x0000000102de4f00 io_loop_handler_run + 220 -> 13 libdovecot.0.dylib 0x0000000102de4e04 io_loop_run + 88 -> 14 libdovecot.0.dylib 0x0000000102d4ec3c master_service_run + 28 -> 15 dovecot 0x0000000102b1a224 main + 2944 -> 16 dyld 0x000000019ff4dd54 start + 7184 thanks, Peter

2 1

Re: Why doesn't Dovecot documentation specify which files to edit?
by Michael Slusarz 12 Dec '25

12 Dec '25

See, e.g., https://doc.dovecot.org/2.4.2/core/config/quick.html#tldr-i-just-want-dovec… michael > On 12/11/2025 3:29 PM MST Chad Wallace via dovecot <dovecot(a)dovecot.org> wrote: > > > I think the configuration layout you're seeing may be provided by your > distribution (Debian, RedHat, etc.). In the original release provided > by Dovecot, I only see a single config file: dovecont.conf.in > > Also, it is quite easy to find which file has certain types of > configuration: > > $ grep -ri lmtp /etc/dovecot > > > On Thu, 11 Dec 2025 20:47:44 +0000 > n4ch0 via dovecot <dovecot(a)dovecot.org> wrote: > > > I've noticed that the official Dovecot documentation frequently omits > > crucial information about which specific files should be modified > > when configuring different functionalities. Concrete examples: > > > > In the LMTP integration guide with Postfix > > (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-l…) > > > > It indicates to modify the socket configuration, but doesn't specify > > in which file this modification should be made > > > > > > In the quota plugin documentation > > (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota) > > > > It requests enabling the quota module, but doesn't mention the > > corresponding configuration file > > > > > > > > I managed to achieve the configuration I wanted but it took more time > > than it should have. My question: I understand that Dovecot uses a > > modular configuration system and that technically I can place > > directives in any file. However, wouldn't it be clearer and more > > efficient if the documentation followed an established order and > > specified recommended locations? For example: > > > > "Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" > > "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf" > > > > Is there a technical reason why the documentation deliberately avoids > > recommending specific files, or does it simply assume that users > > already know these conventions? Is there a general guide about > > Dovecot's configuration file structure and best practices for > > organizing them? > > > > Thanks! > > _______________________________________________ > > dovecot mailing list -- dovecot(a)dovecot.org > > To unsubscribe send an email to dovecot-leave(a)dovecot.org > > > > -- > Chad Wallace > Software Developer | The Lodging Company® > P: +1 250 869 4931 ext. 251 > TF: +1 888 676 9977 > E: cwallace(a)lodgingcompany.com > W: www.lodgingcompany.com > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Migration of the Maildir standard from Dovecot 2.3 to Dovecot 2.4
by byteme＠linuxmaker.net 10 Dec '25

10 Dec '25

Hello everyone, I have a Dovecot 2.3 installation on a Debian 12 Linux system that is being upgraded to Dovecot 2.4. The server hosts many domains with numerous email accounts. Users had created folder structures containing many received and sent emails, following the Maildir standard as "dot-prefixed folders." When switching to Dovecot 2.4, all these emails and folders are no longer visible. This is what it looks like on the old system: root@mx1 /var/vmail/example.com/systemmails # ll -a insgesamt 256 drwx------ 14 vmail vmail 4096 3. Nov 09:15 . drwx------ 15 vmail vmail 4096 6. Apr 2021 .. drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Archive drwx------ 2 vmail vmail 86016 27. Okt 12:19 cur -rw------- 1 vmail vmail 0 15. Sep 2018 dovecot-acl-list -rw------- 1 vmail vmail 1080 29. Okt 06:50 dovecot.index -rw------- 1 vmail vmail 23400 30. Okt 01:36 dovecot.index.cache -rw------- 1 vmail vmail 10600 30. Okt 01:41 dovecot.index.log -rw------- 1 vmail vmail 6627 26. Aug 09:56 dovecot.index.thread -rw------- 1 vmail vmail 24 20. Apr 2024 dovecot-keywords -rw------- 1 vmail vmail 1256 3. Nov 09:05 dovecot.list.index -rw------- 1 vmail vmail 5156 3. Nov 09:15 dovecot.list.index.log -rw------- 1 vmail vmail 672 15. Jul 16:45 dovecot.mailbox.log -rw------- 1 vmail vmail 1781 30. Okt 01:36 dovecot-uidlist -rw------- 1 vmail vmail 8 15. Jul 16:45 dovecot-uidvalidity -r--r--r-- 1 vmail 1002 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a3 -r--r--r-- 1 vmail vmail 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a5 drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Drafts drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.Fail2ban drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.vzdump drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Junk drwx------ 2 vmail vmail 36864 30. Okt 01:36 new drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Quarantine drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Sent drwx------ 3 vmail vmail 4096 3. Dez 06:25 sieve -rw------- 1 vmail vmail 70 15. Jul 16:45 subscriptions drwx------ 2 vmail vmail 4096 2. Nov 16:41 tmp drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Trash This should be preserved so that users don't notice the system upgrade. Dovecot 2.4 works quite differently in this regard. What solution is there for migrating both the namespace and the existing emails to Dovecot 2.4? Thank you for your suggestions ByteMe

5 21

compilation build fail
by Franck Bourdonnec 10 Dec '25

10 Dec '25

Hello, I'm used to build Dovecot since a long time without any problem. Last one 2.3.21 With 2.4.2 I get a compiler error !!! CC unix-socket-create.lo CC unlink-directory.lo CC unlink-old-files.lo CC unichar.lo CC unicode-data-types.lo CC unicode-data-tables.lo CC unicode-data.lo CC unicode-transform.lo unicode-transform.c:211:1: error: initializer element is not constant static const size_t uni_hangul_n_count = uni_hangul_v_count * uni_hangul_t_count; ^ unicode-transform.c:212:1: error: initializer element is not constant static const uint16_t uni_hangul_l_end = uni_hangul_l_base + uni_hangul_l_count; ^ unicode-transform.c:213:1: error: initializer element is not constant static const uint16_t uni_hangul_v_end = uni_hangul_v_base + uni_hangul_v_count; ^ unicode-transform.c:214:1: error: initializer element is not constant static const uint16_t uni_hangul_t_end = uni_hangul_t_base + uni_hangul_t_count; ^ Makefile:1684: recipe for target 'unicode-transform.lo' failed make[4]: *** [unicode-transform.lo] Error 1 make[4]: Leaving directory '/data/users/root/dovecot-2.4.2/src/lib' Makefile:1333: recipe for target 'all' failed I know my system is old, Opensuse Leap 42.3. Perhaps something missing , not tested ? /* * Hangul syllable (de)composition */ static const uint16_t uni_hangul_s_base = 0xac00; static const uint16_t uni_hangul_l_base = 0x1100; static const uint16_t uni_hangul_v_base = 0x1161; static const uint16_t uni_hangul_t_base = 0x11a7; static const size_t uni_hangul_l_count = 19; static const size_t uni_hangul_v_count = 21; static const size_t uni_hangul_t_count = 28; static const size_t uni_hangul_n_count = uni_hangul_v_count * uni_hangul_t_count; static const uint16_t uni_hangul_l_end = uni_hangul_l_base + uni_hangul_l_count; static const uint16_t uni_hangul_v_end = uni_hangul_v_base + uni_hangul_v_count; static const uint16_t uni_hangul_t_end = uni_hangul_t_base + uni_hangul_t_count; static const uint16_t uni_hangul_s_end = 0xD7A4; Franck !DSPAM:69384f6f6071731448408!

3 2

Permission denied errors loading configuration in 2.4.1 (running utilities as unprivileged user)
by Jason J.G. White 09 Dec '25

09 Dec '25

I noticed the following after upgrading from 2.3 to 2.4.1: if I run various Dovecot utilities as an unprivileged user, they attempt to load the entire Dovecot configuration. The configuration loading then fails with a "fatal" permission denied error while trying to access the x.509 private key, which is accessible only to root for security reasons. Example: try running sievec as a normal user to compile a Sieve script. This should work, but it doesn't for the aforementioned reason. I'm not asking for help here, as I can work around it, but I would like to make sure it's on the bug list, if not fixed already.

1 0

auth: Fatal: master: service(auth): child N killed with signal 11
by alexey＠*.com 08 Dec '25

08 Dec '25

Hello there, Got a server powered by "AlmaLinux 9.7 (Moss Jungle Cat)" with Dovecot 2.4.2 compiled from sources by directadmin with the following options: ./configure \ --with-ldap=yes \ --with-pam=yes \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --without-icu Dovecot crashes and no IMAP auth is possible on the server Got this only from dumped core: Reading symbols from /usr/libexec/dovecot/auth... (No debugging symbols found in /usr/libexec/dovecot/auth) [New LWP 3855978] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/dovecot/auth'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 (gdb) bt #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 #1 0x000055da11c889bb in auth_sasl_instance_init () #2 0x000055da11c6eb9e in ?? () #3 0x000055da11c6f4ed in auths_preinit () #4 0x000055da11c6d245 in ?? () #5 0x000055da11c6d8a0 in main () (gdb) info threads Id Target Id Frame * 1 Thread 0x7f6636273ac0 (LWP 3855978) 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 (gdb) thread apply all bt Thread 1 (Thread 0x7f6636273ac0 (LWP 3855978)): #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 #1 0x000055da11c889bb in auth_sasl_instance_init () #2 0x000055da11c6eb9e in ?? () #3 0x000055da11c6f4ed in auths_preinit () #4 0x000055da11c6d245 in ?? () #5 0x000055da11c6d8a0 in main () (gdb) thread apply all bt full Thread 1 (Thread 0x7f6636273ac0 (LWP 3855978)): #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #1 0x000055da11c889bb in auth_sasl_instance_init () No symbol table info available. #2 0x000055da11c6eb9e in ?? () No symbol table info available. #3 0x000055da11c6f4ed in auths_preinit () No symbol table info available. #4 0x000055da11c6d245 in ?? () No symbol table info available. #5 0x000055da11c6d8a0 in main () No symbol table info available. (gdb) Have no issue with Dovecot 2.4.1 Kindly advice. Regards, Alex.

2 2

Can't get Dovecot working with Exim
by Christopher Curzio 07 Dec '25

07 Dec '25

Hello everyone. I'm in the process of migrating my mail server to Debian running exim4 and dovecot. I was previously using exim4 and dovecot on Slackware and I moved the configs over, however I can't get dovecot working with exim on the new system. These configs worked fine previously. I did have to make some minor changes, but overall everything is mostly the same as it was. dovecot config: https://pastebin.com/Hrhj6xeb exim config: https://pastebin.com/bAQ9mTJb No matter what I do, I'm getting this when mail is received: dovecot_delivery transport output: Can't open log file /var/log/dovecot/deliver-error.log: Permi ssion denied I've tried everything, even going as far as setting permissions on /var/log/dovecot to a+rwx recursive (solely as a test) but I still get the same message. Help getting this working would be greatly appreciated since I've exhausted my own knowledge trying to wrench it into submission. Thanks. Hello everyone. I'm in the process of migrating my mail server to Debian running exim4 and dovecot. I was previously using exim4 and dovecot on Slackware and I moved the configs over, however I can't get dovecot working with exim on the new system. These configs worked fine previously. I did have to make some minor changes, but overall everything is mostly the same as it was. dovecot config: [1]https://pastebin.com/Hrhj6xeb exim config: [2]https://pastebin.com/bAQ9mTJb No matter what I do, I'm getting this when mail is received: dovecot_delivery transport output: Can't open log file /var/log/dovecot/deliver-error.log: Permi ssion denied I've tried everything, even going as far as setting permissions on /var/log/dovecot to a+rwx recursive (solely as a test) but I still get the same message. Help getting this working would be greatly appreciated since I've exhausted my own knowledge trying to wrench it into submission. Thanks. References Visible links 1. https://pastebin.com/Hrhj6xeb 2. https://pastebin.com/bAQ9mTJb

6 12

Issues with mail_crypt plugin: per-user encryption with keys from LDAP
by luis.neapolis＠gmail.com 06 Dec '25

06 Dec '25

Hi everyone, I am trying to configure Dovecot's mail_crypt plugin to support per-user encryption, with public and private keys stored in LDAP and retrieved via userdb. My Goal: 1) Each user has their own key pair (public/private) stored in LDAP. 2) Incoming emails should be encrypted via LMTP using the user’s public key. 3) Users should be able to read emails via IMAP/Webmail using their private key, which is password-protected (the user’s login password). Current situation: 1) Using global keys (same key for all users) works fine: LMTP encrypts emails and users can read them correctly. 2) When trying to use per-user keys, I get encryption errors in IMAP, because Dovecot seems to require the private key even during LMTP, even though only the public key should be needed for encryption. Typical error: lmtp(…): Failed to initialize user: mail_crypt_plugin: main: crypt_private_key_password unset, no password to decrypt the key file Example configuration (LDAP userdb): crypt_user_key_require_encrypted = yes userdb ldap { driver = ldap ldap_filter = (&(objectClass=MailClass) (mail=%{user})) result_internalfail = continue-ok fields { quota_storage_size = %{ldap:quota|default('5')}G mail_home = %{ldap:homeDirectory} crypt_global_public_key_file=inline:%{ldap:CryptoGlobalPubKey|default("")} crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:CryptoGlobalPrivKey|default('')} crypt_private_key_password=%{password} } } Questions / help requested: 1) Is it possible to configure mail_crypt so that LMTP can encrypt emails using only the user’s public key, without needing the private key? 2) What is the correct way to use per-user keys with password-protected private keys? 3) Are there any working examples of mail_crypt configurations using LDAP as the source for per-user keys? I am fully aware that LMTP needs the private key of the user even if LMTP doesn't use, but during LMTP session the user password is not available. Version: 2.4.2-1 (0962ed2104) Thanks in advance for any guidance!

1 0

Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Thomas 03 Dec '25

03 Dec '25

Hello, I'm new to dovecot and greet everyone! I come from courier-imap and updated my imap server now to dovecot-2.4.2. All user directories and files were copied 1:1. In some cases, I now receive the following message in logfiles: 2025-11-28 15:20:52.184760182 Nov 28 15:20:52 imap(Email_address_hidden)<2297539><zNQfVqhEx98l90IK>: Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f8eb793ab09] -> libdovecot.so.0(backtrace_get+0x22) [0x7f8eb793ac42] -> libdovecot.so.0(+0x1493fc) [0x7f8eb79493fc] -> libdovecot.so.0(+0x149491) [0x7f8eb7949491] -> libdovecot.so.0(+0x6bde2) [0x7f8eb786bde2] -> lib95_imap_sieve_plugin.so(+0x49b7) [0x7f8eb74bb9b7] -> lib95_imap_sieve_plugin.so(+0x7c8b) [0x7f8eb74bec8b] -> libdovecot-storage.so.0(index_mail_free+0xe) [0x7f8eb7cb4c9e] -> lib95_imap_sieve_plugin.so(+0x6ef5) [0x7f8eb74bdef5] -> libdovecot-storage.so.0(mail_free+0x1a) [0x7f8eb7c29bca] -> libdovecot-storage.so.0(+0xf5c52) [0x7f8eb7cc7c52] -> libdovecot-storage.so.0(mail_index_transaction_commit_full+0x8c) [0x7f8eb7ce11ec] -> libdovecot-storage.so.0(index_transaction_commit+0xf2) [0x7f8eb7cc81f2] -> libdovecot-storage.so.0(+0xcff1e) [0x7f8eb7ca1f1e] -> lib95_imap_sieve_plugin.so(+0x8576) [0x7f8eb74bf576] -> lib15_notify_plugin.so(+0x368f) [0x7f8eb7bc668f] -> lib10_quota_plugin.so(+0xd99d) [0x7f8eb74d999d] -> libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x79) [0x7f8eb7c3bac9] -> imap(+0x1762b) [0x562bf69c462b] -> imap(command_exec+0xa4) [0x562bf69d3334] -> imap(+0x24180) [0x562bf69d1180] -> imap(+0x24214) [0x562bf69d1214] -> imap(+0x2449b) [0x562bf69d149b] -> imap(client_handle_input+0x1c5) [0x562bf69d1675] -> imap(client_input+0x73) [0x562bf69d1c33] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f8eb7960187] -> libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f8eb79618ba] -> libdovecot.so.0(io_loop_handler_run+0x51) [0x7f8eb7960231] -> libdovecot.so.0(io_loop_run+0x48) [0x7f8eb7960408] -> libdovecot.so.0(master_service_run+0x19e) [0x7f8eb78b011e] 2025-11-28 15:20:52.940692672 Nov 28 15:20:52 imap(Email_address_hiddene)<2297539><zNQfVqhEx98l90IK>: Fatal: master: service(imap): child 2297539 killed with signal 6 (core dumped) If I filter for "Panic" now I see: 2025-11-28 15:20:52.183676628 Nov 28 15:20:52 imap(Email_address_hidden)<2297539><zNQfVqhEx98l90IK>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Panic repeats up to several times. In moment of crash I can find lots [# of repeats] of copies of ONE mail file in users .Trash/tmp dir. Original mail file also in e.g. INBOX/cur Please tell me wht's going on here. I checked all permission, dirs and so on. CentOS 10 s/qmail dovecot-2.4.2 dovecot-pigeonhole-2.4.2 Regards, Thomas

2 3

Defining "INBOX" in mdbox context from ldap
by Florian Lohoff 03 Dec '25

03 Dec '25

Hi, i am in the middle of converting a handful of 2.3 installations to 2.4 and while at it i fail to see a point on how to define what the INBOX is in the mdbox/ldap context. So right now i am transferring the attributes from LDAP like this (iredmail schema) fields { user=%{ldap:mail} home=%{ldap:storageBaseDirectory} mail_driver=%{ldap:MailMessageStore | index(':', 0)} mail_path=%{ldap:mailMessageStore | index(':', 1)} quota_storage_size=%{ldap:mailQuota} } I fail to find the syntax for "mail_inbox_path" - In maildir its obvious. I tried various things but it mainly failed on me. I now removed it completely from the config which it seems makes the dbox/mdbox driver assume a sane default of "INBOX". But i am still wondering how do i configure the INBOX. I'd like to fetch that information from LDAP as i think i still have a handful of Maildir/mdbox mix installations. Flo -- Florian Lohoff f(a)zz.de Any sufficiently advanced technology is indistinguishable from magic.

1 0

Re: Dovecot 2.4.1 with mbox format
by "Tóth Attila" 02 Dec '25

02 Dec '25

Hi Bill, 2025.December 1.(H) 23:56 időpontban Bill Steinberg via dovecot ezt írta: > Hello again, > I didn't fully read the section in the documentation about using the > mbox > format. There is a setting, mail_inbox_path = /var/mail/%{user} to > specify > the iNBOX location for mails that are stored in /var/mail. > After setting mail_inbox_path I did initially have an issue about > dovecot > being able to write dotlock files, which was noted in the > documentation. I > was able to fix by adding users to the group "mail". > I am using these settings in the new server now: > > mail_driver = mbox > > mail_path = ~/mail > > mail_inbox_path = /var/mail/%{user} > > mail_index_path = ~/mail/index > > mail_control_path = ~/mail/control I'm struggling with the same setup as yourself. Sendmail delivers mails under /var/spool/mail/username and mail user agents were fetching the incoming mail from there and put them under /home/username/mail. This has been fine for ages - I have to say decades now. While 2.3 created files/directories in the name of the current user under ~/mail, 2.4 tries to write as mail:mail and therefore gets denied, since the user directories are owned by username:users and obviously have no permissions for other users. This change of behaviour is unacceptable in my opinion and 2.4 should also act in the name of the actual user. If some of the files would be owned by mail:mail and others by username:users: that would be a mess and the user would not be able to read contents using other user agents (for e.g. alpine) or make a backup of their own emails using an arbitrary tool or script of their own. For this reason I downgraded back to 2.3, because I have no time to dig deeper into this and reintroduce the mechanism granting current user access rights - running certain processes under proper conditions. Bill: how do you achieve that dovecot creates and writes files in users home directories in the name of the current user? Back in the good old 2.3 days I had this in the config and everything just worked as expected: mail_location = mbox:~/mail/:INBOX=/var/spool/mail/%u In case of the new 2.4 version I was unsuccessful with the following: mail_driver = mbox mail_path = /home/%{user}/mail mail_inbox_path = /var/spool/mail/%{user} server dovecot: imap(user)<48978><1LgipBQ3LO1/AAAB>: Error: mkdir(/home/user/mail/.imap) failed: Permission denied (euid=8(mail) egid=12(mail) missing +x perm: /home/user/mail, dir owned by 1000:100 mode=0700) Although I haven't specified mail_index_path and mail_control_path as you, I wouldn't expect this to make any difference regarding user rights. I'm aware, that mbox is deprecated, but still: this is a regression from my point of view. So how about user rights in your case Bill? Thanks: Dwokfur > > On Dec 1, 2025, at 10:18AM, Bill Steinberg via dovecot > <dovecot(a)dovecot.org> wrote: > Hello, > I'm attempting to upgrade a mbox format based dovecot server to the > latest > 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot > server > I'm attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in > the > user's ~/mail location For example Sent, Trash, Drafts, ... In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u",so when a client connects to the > dovecot > server their sendmail based mbox /var/mail isn't visible. Additionally mbox folders directly under a user's ~/mail iike Sent, > Trash, > Drafts are not visible either. > The new 2.4.1 dovecot server creates a folder named "inbox" under > ~/mail > as well as an .imap directory which contains directories that > appear > to > correspond to the folders at the top level along with other dovecot > based > files. > Can you describe how I would make the seamail delivered mail in > /var/spool > as well as a users top level mbox folders accessible in the new > dovecot > mbox structures? > Thanks in advance for any help, > -Bill > ====================================== > Dovecot config > ====================================== > > dovecot_config_version = 2.4.1 > > dovecot_storage_version = 2.4.1 > > protocols { > > imap = yes > > lmtp = yes > > } > > mail_driver = mbox > > mail_home = /home/%{user} > > mail_path = ~/mail > > mbox_write_locks = fcntl > > namespace inbox { > > inbox = yes > > separator = / > > } > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org >

3 4

Dovecot 2.4.1 with mbox format
by Bill Steinberg 02 Dec '25

02 Dec '25

Hello, I’m attempting to upgrade a mbox format based dovecot server to the latest 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot server I’m attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in the user’s ~/mail location For example Sent, Trash, Drafts, … In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u”,so when a client connects to the dovecot server their sendmail based mbox /var/mail isn’t visible. Additionally mbox folders directly under a user’s ~/mail iike Sent, Trash, Drafts are not visible either. The new 2.4.1 dovecot server creates a folder named “inbox” under ~/mail as well as an .imap directory which contains directories that appear to correspond to the folders at the top level along with other dovecot based files. Can you describe how I would make the seamail delivered mail in /var/spool as well as a users top level mbox folders accessible in the new dovecot mbox structures? Thanks in advance for any help, -Bill ====================================== Dovecot config ====================================== dovecot_config_version = 2.4.1 dovecot_storage_version = 2.4.1 protocols { imap = yes lmtp = yes } mail_driver = mbox mail_home = /home/%{user} mail_path = ~/mail mbox_write_locks = fcntl namespace inbox { inbox = yes separator = / } Hello, I'm attempting to upgrade a mbox format based dovecot server to the latest 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot server I'm attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in the user's ~/mail location For example Sent, Trash, Drafts, ... In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u",so when a client connects to the dovecot server their sendmail based mbox /var/mail isn't visible. Additionally mbox folders directly under a user's ~/mail iike Sent, Trash, Drafts are not visible either. The new 2.4.1 dovecot server creates a folder named "inbox" under ~/mail as well as an .imap directory which contains directories that appear to correspond to the folders at the top level along with other dovecot based files. Can you describe how I would make the seamail delivered mail in /var/spool as well as a users top level mbox folders accessible in the new dovecot mbox structures? Thanks in advance for any help, -Bill ====================================== Dovecot config ====================================== dovecot_config_version = 2.4.1 dovecot_storage_version = 2.4.1 protocols { imap = yes lmtp = yes } mail_driver = mbox mail_home = /home/%{user} mail_path = ~/mail mbox_write_locks = fcntl namespace inbox { inbox = yes separator = / }

1 1

managesieve-crash on 2.4.2
by Bjoern Franke 29 Nov '25

29 Nov '25

Hi, while trying to connect with "sieve-connect", managesieve crashed: Nov 25 14:21:08 mail.schafweide.org dovecot[440904]: managesieve-login: Panic: file client.c: line 350 (managesieve_client_input_next_cmd): assertion failed: (args != NULL) Nov 25 14:21:08 mail.schafweide.org systemd-coredump[440938]: [🡕] Process 440934 (managesieve-log) of user 74 dumped core. Stack trace of thread 440934: #0 0x000079c6cfa9890c n/a (libc.so.6 + 0x9890c) #1 0x000079c6cfa3e3a0 raise (libc.so.6 + 0x3e3a0) #2 0x000079c6cfa2557a abort (libc.so.6 + 0x2557a) #3 0x000079c6cfe5ffff n/a (libdovecot.so.0 + 0x5ffff) #4 0x000079c6cff4f095 n/a (libdovecot.so.0 + 0x14f095) #5 0x000079c6cfe5feb6 i_panic (libdovecot.so.0 + 0x5feb6) #6 0x000062e017df80de n/a (/usr/lib/dovecot/managesieve-login + 0x30de) #7 0x000062e017df8887 n/a (/usr/lib/dovecot/managesieve-login + 0x3887) #8 0x000079c6cff681f4 io_loop_call_io (libdovecot.so.0 + 0x1681f4) #9 0x000079c6cff6a2db io_loop_handler_run_internal (libdovecot.so.0 + 0x16a2db) #10 0x000079c6cff6a397 io_loop_handler_run (libdovecot.so.0 + 0x16a397) #11 0x000079c6cff6a599 io_loop_run (libdovecot.so.0 + 0x16a599) #12 0x000079c6cfeabce1 master_service_run (libdovecot.so.0 + 0xabce1) #13 0x000079c6d02f4350 login_binary_run (libdovecot-login.so.0 + 0x14350) #14 0x000079c6cfa27635 n/a (libc.so.6 + 0x27635) #15 0x000079c6cfa276e9 __libc_start_main (libc.so.6 + 0x276e9) #16 0x000062e017df8405 n/a (/usr/lib/dovecot/managesieve-login + 0x3405) ELF object binary architecture: AMD x86-64 Nov 25 14:21:08 mail.schafweide.org dovecot[440904]: managesieve-login: Fatal: master: service(managesieve-login): child 440934 killed with signal 6 (core dumped) I'm using dovecot/pigeonhole 2.4.2 on Arch. Regards Bjoern

3 7

"Mailbox attribute iteration failed": error running doveadm sync
by jamie＠mayfirst.org 29 Nov '25

29 Nov '25

I'm running doveadm sync to sync a remote mailbox over ssh (the remote server is running 2.3.13) with a local mailbox (the local server is running 2.4.1). I get the following errors: Error: brain M: Exporting mailbox INBOX failed: Mailbox attribute iteration failed: Internal error occurred. Refer to server log for more information. [2025-11-15 19:25:32] Error: cmd sync: Remote command returned error 75: ssh root(a)mailstore002.mayfirst.org doveadm dsync-server -u jamie-test dsync-server Does anyone have suggestions on how to fix? Also, any tips on how to increase logging verbosity would be great - I'm not getting anything in the logs. Here is the full transcript of the errors. Thanks for any suggestions! jamie Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Nov 15 19:28:47 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Nov 15 19:28:47 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Nov 15 19:28:47 Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Nov 15 19:28:47 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Nov 15 19:28:47 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Nov 15 19:28:47 Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: userdb lookup(jamie-test): Started userdb lookup Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=43923,uid=0): Client connected (fd=9) Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=43923,uid=0): auth input: jamie-test system_groups_user=jamie-test uid=1002 home=/home/users/jamie-test gid=100 Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: userdb lookup(jamie-test): auth USER input: jamie-test system_groups_user=jamie-test uid=1002 home=/home/users/jamie-test gid=100 Nov 15 19:28:47 doveadm(jamie-test)<46454><>: Debug: auth-master: userdb lookup(jamie-test): Finished userdb lookup (username=jamie-test system_groups_user=jamie-test uid=1002 home=/home/users/jamie-test gid=100) Nov 15 19:28:47 doveadm(jamie-test): Debug: Effective uid=1002, gid=100, home=/home/users/jamie-test Nov 15 19:28:47 doveadm(jamie-test): Debug: open(/proc/self/io) failed: Permission denied (euid=1002(jamie-test) egid=100(users) missing +r perm: /proc/self/io) Nov 15 19:28:47 doveadm(jamie-test): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes Nov 15 19:28:47 doveadm(jamie-test): Debug: maildir++: root=/home/users/jamie-test/Maildir, index=, indexpvt=, control=, inbox=/home/users/jamie-test/Maildir, alt= Nov 15 19:28:47 doveadm(jamie-test): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no Nov 15 19:28:47 doveadm(jamie-test): Debug: none: root=/home/users/jamie-test/Maildir, index=, indexpvt=, control=, inbox=/home/users/jamie-test/Maildir, alt= Nov 15 19:28:47 doveadm(jamie-test): Debug: brain M: Namespace inbox has path /home/users/jamie-test/Maildir Nov 15 19:28:47 doveadm(jamie-test): Debug: Mailbox INBOX: Mailbox opened Nov 15 19:28:47 doveadm(jamie-test): Debug: Mailbox INBOX: Mailbox opened Nov 15 19:28:47 doveadm(jamie-test): Debug: Namespace inbox: Using permissions from /home/users/jamie-test/Maildir: mode=0700 gid=default Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX guid=c06cb11ffc3b2e667cee07009334e653 uid_validity=1669914524 uid_next=1 subs=no last_change=0 last_subs=0 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Spam guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Sent guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Archive guid=e42d3631a91ba85ef96f00000df6ea83 uid_validity=1586118770 uid_next=1 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Archives guid=693e80288e6e8b5e153300000df6ea83 uid_validity=1586118767 uid_next=1 subs=no last_change=0 last_subs=0 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Drafts guid=60042a30bf3e5e64d44f15001890bc3b uid_validity=1669914525 uid_next=1 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Junk guid=387dc412e591b0683b3b34009334e653 uid_validity=1714306055 uid_next=1 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Keep Forever guid=99b2cc1be0826d61f07e00000df6ea83 uid_validity=1586118773 uid_next=1 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Local mailbox tree: INBOX.Trash guid=a8494334bf3e5e64d44f15001890bc3b uid_validity=1669914528 uid_next=1 subs=yes last_change=0 last_subs=1763215050 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX guid=c06cb11ffc3b2e667cee07009334e653 uid_validity=1669914524 uid_next=561 subs=no last_change=0 last_subs=0 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Spam guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1683898047 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Sent guid=00000000000000000000000000000000 uid_validity=0 uid_next=0 subs=yes last_change=0 last_subs=1683898047 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Drafts guid=60042a30bf3e5e64d44f15001890bc3b uid_validity=1669914525 uid_next=1 subs=yes last_change=0 last_subs=1683898047 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Trash guid=a8494334bf3e5e64d44f15001890bc3b uid_validity=1669914528 uid_next=1 subs=yes last_change=0 last_subs=1683898047 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Archive guid=e42d3631a91ba85ef96f00000df6ea83 uid_validity=1586118770 uid_next=1 subs=yes last_change=0 last_subs=1763213508 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Archives guid=693e80288e6e8b5e153300000df6ea83 uid_validity=1586118767 uid_next=1 subs=no last_change=0 last_subs=0 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Junk guid=387dc412e591b0683b3b34009334e653 uid_validity=1714306055 uid_next=1 subs=yes last_change=0 last_subs=1763213508 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree: INBOX.Keep Forever guid=99b2cc1be0826d61f07e00000df6ea83 uid_validity=1586118773 uid_next=1 subs=yes last_change=0 last_subs=1763213508 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree deletion: guid=dcb7483819278b5e7a5a00000df6ea83 type=mailbox timestamp=1763214618 name= local update=not found Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree deletion: guid=e05fa533bf3e5e64d44f15001890bc3b type=mailbox timestamp=1763214618 name= local update=not found Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree deletion: guid=c30776db7d3c7eaa71cdf47ee8a11926 type=dir timestamp=1763214618 name=INBOX.Sent local update=marked as deleted Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Remote mailbox tree deletion: guid=edfa9436de94e7fff67418728a00db1d type=dir timestamp=1763214618 name=INBOX.Spam local update=marked as deleted Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX: local=c06cb11ffc3b2e667cee07009334e653/0/1, remote=c06cb11ffc3b2e667cee07009334e653/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Archive: local=e42d3631a91ba85ef96f00000df6ea83/0/1, remote=e42d3631a91ba85ef96f00000df6ea83/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Archives: local=693e80288e6e8b5e153300000df6ea83/0/1, remote=693e80288e6e8b5e153300000df6ea83/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Drafts: local=60042a30bf3e5e64d44f15001890bc3b/0/1, remote=60042a30bf3e5e64d44f15001890bc3b/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Junk: local=387dc412e591b0683b3b34009334e653/0/1, remote=387dc412e591b0683b3b34009334e653/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Keep Forever: local=99b2cc1be0826d61f07e00000df6ea83/0/1, remote=99b2cc1be0826d61f07e00000df6ea83/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Sent: local=00000000000000000000000000000000/0/0, remote=00000000000000000000000000000000/0/2: Directory rename branch not found Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Spam: local=00000000000000000000000000000000/0/0, remote=00000000000000000000000000000000/0/2: Directory rename branch not found Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Mailbox INBOX.Trash: local=a8494334bf3e5e64d44f15001890bc3b/0/1, remote=a8494334bf3e5e64d44f15001890bc3b/0/1: Mailboxes are equal Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: Mailbox INBOX: Mailbox opened Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Syncing mailbox c06cb11ffc3b2e667cee07009334e653: UIDNEXT changed: 1 -> 561 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: doveadm-sieve: Iterating Sieve mailbox attributes Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: Pigeonhole version 2.4.1-4 (0a86619f) initializing Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: storage personal: file: Storage path '/home/users/%u/.sieve' not found Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: storage personal: file: Failed to normalize active script directory (path=/home/users/%u): Part of the path does not exist (yet) Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: storage personal: file: Using active Sieve script path: /home/users/%u/.dovecot.sieve Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: storage personal: file: Using script storage path: /home/users/%u/.sieve Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: sieve: storage personal: file: Using permissions from defaults: mode=0700 gid=-1 Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Error: brain M: Exporting mailbox INBOX failed: Mailbox attribute iteration failed: Internal error occurred. Refer to server log for more information. [2025-11-15 19:28:47] Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: brain M: Import mailbox INBOX: Saved UIDs: Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Error: cmd sync: Remote command returned error 75: ssh root(a)mailstore002.mayfirst.org doveadm dsync-server -u jamie-test dsync-server Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: User session is finished Nov 15 19:28:47 dsync-local(jamie-test)<esqfB2/UGGl2tQAAVqcyLg>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=43923,uid=0): Disconnected: Connection closed (fd=9)

2 2

"doveadm quota get" performance hit after enablig flat-curve plugin for mail account with 1.3k subfolders
by grabsoon＠gmail.com 28 Nov '25

28 Nov '25

Hello I have some performance problem with doveadm quota get -u user@domain after migrating from 2.3.21 to 2.4.1 and enabling fts-flatcurve plugin for mail account with 1330 folders and subfolders. Quota on 2.3.21 was stored in maildirsize. After upgrading dovecot to 2.4.2 quota driver is set to count When I run doveadm quota get -u user@domain command it takes about 15 minutes. Mail account quota is used about 6.7GB and about 10k messeges. Doveadm process use 100% CPU when it try to count quota values. When I run command doveadm with "strace" to trace callbacks it looks like: 14:51:00.577061 newfstatat(AT_FDCWD, "/maildovecot/*******/Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714", {st_mode=S_IFDIR|0700, st_size=4096, ...}, 0) = 0 14:51:00.577295 openat(AT_FDCWD, "/maildovecot/*******/Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714", O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 13 14:51:00.577680 rmdir("/maildovecot/*******/Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714") = -1 ENOTEMPTY (Directory not empty) 14:51:00.577765 rmdir("/maildovecot/*******/Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714") = -1 ENOTEMPTY (Directory not empty) 14:51:00.577847 rmdir("/maildovecot/*******/Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714") = -1 ENOTEMPTY (Directory not empty) 14:51:00.577929 rmdir("/maildovecot/*******Maildir/Foldery przechowywania/Zakupy/drogerie/rossmann/fts-flatcurve/index.714") = -1 ENOTEMPTY (Directory not empty) or 14:33:44.529146 newfstatat(AT_FDCWD, "/maildovecot//******//Maildir/Foldery przechowywania/programy lojalnosciowe/vitay/fts-flatcurve/cur", 0x7fff0d9cf270, 0) = -1 ENOENT (No such file or directory) and it loops 2374 times grep fts-flatcurve strace_quota | grep rossmann | wc -l 2374 My configuration: quota "User quota" { driver = count quota_storage_grace = 10M quota_mail_size = 50M quota_message_count = 1500000 quota_warning warn-80-storage { quota_storage_percentage = 80 quota_warning_resource = storage quota_warning_threshold = over execute quota-warning { args = 80 size %{user} %{userdb:quota_storage_size} } } quota_warning warn-90-storage { quota_storage_percentage = 90 quota_warning_resource = storage quota_warning_threshold = over execute quota-warning { args = 90 size %{user} %{userdb:quota_storage_size} } } quota_warning warn-90-message { quota_message_percentage = 95 quota_warning_resource = message quota_warning_threshold = over execute quota-warning { args = 90 inodes } } } service quota-warning { executable = script /dovecot/bin/quota.sh user = mail unix_listener quota-warning { user = mail } } cat conf.d/90-fts.conf language_tokenizers = generic email-address language_tokenizer_generic_algorithm = simple language_filters = lowercase snowball stopwords fts_autoindex = yes fts_autoindex_max_recent_msgs = 100 fts_message_max_size = 20M fts_driver = flatcurve fts_decoder_driver = script fts_decoder_script_socket_path = decode2text service decode2text { executable = script /dovecot/bin/attachment2text.sh unix_listener decode2text { mode = 0666 user = dovecot group = dovecot } } fts_header_excludes { Authentication-Results = yes Received = yes DKIM-* = yes X-* = yes Comments = yes Date = yes Message-ID = yes Received = yes } mailbox TRASH { fts_autoindex = no } mailbox SPAM { fts_autoindex = no } mailbox confirmed-spam { fts_autoindex = no } mailbox confirmed-ham { fts_autoindex = no } language en { default = yes filters = lowercase snowball english-possessive stopwords } fts flatcurve { commit_limit = 500 min_term_size = 2 optimize_limit = 10 rotate_count = 5000 rotate_time = 5s substring_search = no } My questions are: Why "doveadm quota get" tries to open "fts-flatcurve" directories and tries to find "cur" or "ndex.714" directory? Is there any options to exclude all "fts-flatcurve" directories from quota ? Do you observe performance hit for mail accounts with many folders and subfolders after enabling fts-flatcurve?

1 0

Sieve default script configuration
by Bernard 27 Nov '25

27 Nov '25

Hello, Using Dovecot v2.4.1 (Devuan stable), I am facing difficulties debugging what is wrong with my configuration. Here is the error: Error: sieve: file storage: Performing t_readlink() on active sieve symlink '(null)' failed: readlink() failed: Bad address Error: sieve: Failed to access active Sieve script in parsonal storage 'default': Internal error occurred. Refer to server log for more information. [2025-11-13 19:08:48] (temporary failure) This happens on the mailbox which has no personal Sieve file in its personal directory, hence falling back to the default sieve configured that way: sieve_script default { type = default name = default driver = file path = /etc/sieve/ } /etc/sieve contains: drwxr-xr-x 2 root root 4096 Nov 13 18:57 /etc/sieve/ -rw-r--r-- 1 root root 2209 Aug 19 2021 default.sieve -rw-r--r-- 1 root root 2276 Nov 13 18:57 default.svbin I read: - https://doc.dovecot.org/2.4.2/installation/upgrade/2.3-to-2.4.html#converte… converting sieve_default to a sieve_script block with type = default - https://doc.dovecot.org/2.4.2/core/plugins/sieve.html#script-storage-type-d… doveadm sieve list -A returns: vmail default ACTIVE doveadm sieve get -A default returns the sieve file contents /etc/sieve was previously belonging to vmail:vmail. Switching to root:root did not yield any change. Moreover, running sievec on the default.sieve file with vmail:vmail permissions yielded default.svbin with root:root ownership. The error message is cryptic to me: what is this symlink problem? Cheers, Bernard Rosset

3 13

issue getting unseen count from a mailbox
by Louis-David Mitterrand 26 Nov '25

26 Nov '25

Hi, I'm using wmbiff to monitor my imap mailboxes with a script that polls every minute: eval "ssh $WMHOST \"doveadm mailbox status -u ldm 'messages unseen' $(printf %q "$WMBOX")\" 2>/dev/null" |\ awk -F'[ =]' '{old=$3; new=$5} END {print old, new+0}' |\ { read old new; if [ $new -gt 0 ] ;then echo $new new; else echo $old; fi; } If I haven't polled the mailbox before with mutt or another MUA then only the total message count will be returned, however if I peek at the mailbox with a MUA (without looking at any message) then the script returns the new message count. How can I have dovecot (2.4.1 debian) always return the unseen message count in any case? Thanks,

1 0

imap_id_log for 2.4.1
by Adrian M 26 Nov '25

26 Nov '25

Hello, I was using imap_id_log to log user-agent in 2.3, but this seems to be replaced in 2.4 by imap_id_received, however I am unable to find any example how this is supposed to be configured. Please help me clarify this. Hello, I was using imap_id_log to log user-agent in 2.3, but this seems to be replaced in 2.4 by imap_id_received, however I am unable to find any example how this is supposed to be configured. Please help me clarify this.

3 3

Problem migrating some users from old to new dovecot server with doveadm backup
by Javier Miguel Rodríguez 26 Nov '25

26 Nov '25

Hello This is my setup: * Old server: RHEL 7 x64, dovecot 2.3.13 from dovecot RPM repo * New Server: RHEL 9 x64, dovecot-2.3.16-15.el9.x86_64 (rhel rpm) I am migrating several thousand mailboxes with doveadm backup, >99% worked, but 3 of them fail: doveadm(mbejdom)<KlUSFVAuEGnASxcAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) doveadm(mportcal)<rFRoEw0zEGl+XBcAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) doveadm(agalmun)<1l2fMZFoEWnoGhgAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) When I enable debug in doveadm backup this is what I get in one of them: Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: Mailbox ELAICH: Recreated /buzones/indices_correo/18/c4/mportcal/mailboxes/ELAICH/dovecot.index (file_seq=3) because: .log read 20380..8244 > rewrite_min_log_bytes 8192 Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) Nov 13 06:21:00 doveadm(304593): Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(304593): Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(304593): Debug: auth-master: conn unix:/var/run/dovecot//auth-userdb (pid=303177,uid=0): Disconnected: Connection closed (fd=9) In the old server I get this log: Nov 13 06:00:33 myserver dovecot: doveadm: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 (backtrace_append+0x42) [0x7f51347cc4c2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f51347cc5ce] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf262e) [0x7f51347d962e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf26d1) [0x7f51347d96d1] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f513472bea8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x114376) [0x7f51347fb376] -> /usr/lib64/dovecot/libdovecot.so.0(+0x1143cb) [0x7f51347fb3cb] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_create_dynamic+0x15) [0x7f51347cedc5] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_mailbox_export_init+0xa40) [0x56263eacc600] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_sync_mailbox_open+0x47c) [0x56263eac13ac] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_slave_recv_mailbox+0x285) [0x56263eac23e5] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_run+0x292) [0x56263eabf932] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x46f61) [0x56263eabff61] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x5bb9f) [0x56263ead4b9f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f51347f1775] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f51347f310b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f51347f1879] -> /usr/lib64/dovecot/libdovecot.so.0 (io_loop_run+0x38) [0x7f51347f1ab8] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x29ceb) [0x56263eaa2ceb] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x2b8c7) [0x56263eaa48c7] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x42bc4) [0x56263eabbbc4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f51347f1775] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f51347f310b] -> /usr/lib64/dovecot/libdovecot.so.0 (io_loop_handler_run+0x59) [0x7f51347f1879] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f51347f1ab8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f513475d493] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](main+0x1fc) [0x56263ea94a3c] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5134039555] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x1bb02) [0x56263ea94b02] I have tried doveadm force-resync but still get the same error. What can I do to troubleshoot what is happening? I attach doveconf -n output of the old server: auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_worker_max_count = 5500 base_dir = /var/run/dovecot/ default_client_limit = 5000 default_process_limit = 6500 disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it imap_capability = +XLIST imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags imap_id_log = * imap_max_line_length = 92 k lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_attribute_dict = file:/indices_correo/%2.26Hn/%2.200Hn/%n/dovecot-attributes mail_fsync = never mail_gid = entrega mail_home = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario mail_location = mdbox:/buzones_primarios/%2.26Hn/%2.200Hn/%n:ALT=/buzones_secundarios/%2.26Hn/%2.200Hn/%n:INDEX=/indices_correo/%2.26Hn/%2.200Hn/%n:ITERINDEX mail_log_prefix = "%s(%u)<%{session}>: " mail_max_userip_connections = 2500 mail_plugins = " zlib acl quota virtual" mail_uid = entrega 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 mdbox_rotate_interval = 1 days mdbox_rotate_size = 60 M namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox SPAM { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/usuario_maestro.txt driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile lda_mailbox_autosubscribe = yes quota = dict:Cuota de usuario::file:/indices_correo/cuotas/%n quota_rule2 = Trash:storage=+10%% quota_warning = storage=90%% aviso_cuota 90 %u sieve = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario/dovecot.sieve sieve_dir = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario/sieve/ sieve_max_redirects = 20 zlib_save = gz zlib_save_level = 1 } pop3_no_flag_updates = yes protocols = pop3 imap sieve service anvil { client_limit = 25000 } service auth { client_limit = 32000 unix_listener auth-master { user = entrega } unix_listener auth-userdb { user = entrega } user = root } service aviso_cuota { executable = script /usr/local/bin/quota-warning.sh unix_listener aviso_cuota { mode = 0666 } user = entrega } service config { process_min_avail = 4 } service doveadm { inet_listener { port = 12354 } } service imap-login { executable = /usr/libexec/dovecot/imap-login group = dovenull process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service imap { executable = /usr/libexec/dovecot/imap process_limit = 8000 process_min_avail = 12 vsz_limit = 1 G } service managesieve-login { executable = /usr/libexec/dovecot/managesieve-login inet_listener sieve { port = 2000 } process_limit = 2000 vsz_limit = 1 G } service managesieve { executable = /usr/libexec/dovecot/managesieve process_limit = 5000 } service pop3-login { executable = /usr/libexec/dovecot/pop3-login process_limit = 5000 process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service pop3 { executable = /usr/libexec/dovecot/pop3 process_limit = 5000 } service stats { fifo_listener stats-mail { mode = 0600 user = entrega } } ssl_cert = </etc/pki/tls/certificado.pem ssl_cipher_list = ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 64 k } protocol lda { hostname = mydomain.tldr info_log_path = log_path = mail_fsync = optimized mail_plugins = sieve zlib quota virtual postmaster_address = me(a)mydomain.tldr syslog_facility = mail } protocol imap { imap_metadata = yes mail_plugins = zlib quota imap_quota virtual } protocol pop3 { mail_plugins = zlib quota virtual pop3_enable_last = yes pop3_uidl_format = %g } Regards Javier Hello This is my setup: o Old server: RHEL 7 x64, dovecot 2.3.13 from dovecot RPM repo o New Server: RHEL 9 x64, dovecot-2.3.16-15.el9.x86_64 (rhel rpm) I am migrating several thousand mailboxes with doveadm backup, >99% worked, but 3 of them fail: doveadm(mbejdom)<KlUSFVAuEGnASxcAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) doveadm(mportcal)<rFRoEw0zEGl+XBcAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) doveadm(agalmun)<1l2fMZFoEWnoGhgAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) When I enable debug in doveadm backup this is what I get in one of them: Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: Mailbox ELAICH: Recreated /buzones/indices_correo/18/c4/mportcal/mailboxes/ELAICH/dovecot.index (file_seq=3) because: .log read 20380..8244 > rewrite_min_log_bytes 8192 Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:20:59 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(mportcal)<mIcAIbtqFWnRpQQAVKmH5w>: Error: read(myserver) failed: EOF (last sent=mailbox, last recv=mailbox) Nov 13 06:21:00 doveadm(304593): Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(304593): Debug: dict(file)<mportcal>: Waiting for dict to finish pending operations Nov 13 06:21:00 doveadm(304593): Debug: auth-master: conn unix:/var/run/dovecot//auth-userdb (pid=303177,uid=0): Disconnected: Connection closed (fd=9) In the old server I get this log: Nov 13 06:00:33 myserver dovecot: doveadm: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 (backtrace_append+0x42) [0x7f51347cc4c2] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f51347cc5ce] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf262e) [0x7f51347d962e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf26d1) [0x7f51347d96d1] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7f513472bea8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x114376) [0x7f51347fb376] -> /usr/lib64/dovecot/libdovecot.so.0(+0x1143cb) [0x7f51347fb3cb] -> /usr/lib64/dovecot/libdovecot.so.0(buffer_create_dynamic+0x15) [0x7f51347cedc5] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_mailbox_export_init+0xa40) [0x56263eacc600] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_sync_mailbox_open+0x47c) [0x56263eac13ac] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_slave_recv_mailbox+0x285) [0x56263eac23e5] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](dsync_brain_run+0x292) [0x56263eabf932] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x46f61) [0x56263eabff61] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x5bb9f) [0x56263ead4b9f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f51347f1775] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f51347f310b] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x59) [0x7f51347f1879] -> /usr/lib64/dovecot/libdovecot.so.0 (io_loop_run+0x38) [0x7f51347f1ab8] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x29ceb) [0x56263eaa2ceb] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x2b8c7) [0x56263eaa48c7] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x42bc4) [0x56263eabbbc4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7f51347f1775] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12b) [0x7f51347f310b] -> /usr/lib64/dovecot/libdovecot.so.0 (io_loop_handler_run+0x59) [0x7f51347f1879] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f51347f1ab8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f513475d493] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](main+0x1fc) [0x56263ea94a3c] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f5134039555] -> dovecot/doveadm-server [192.168.10.62 mportcal slave_recv_mailbox](+0x1bb02) [0x56263ea94b02] I have tried doveadm force-resync but still get the same error. What can I do to troubleshoot what is happening? I attach doveconf -n output of the old server: auth_cache_negative_ttl = 10 secs auth_cache_size = 10 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_worker_max_count = 5500 base_dir = /var/run/dovecot/ default_client_limit = 5000 default_process_limit = 6500 disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it imap_capability = +XLIST imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags imap_id_log = * imap_max_line_length = 92 k lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_attribute_dict = [1]file:/indices_correo/%2.26Hn/%2.200Hn/%n/dovecot-attributes mail_fsync = never mail_gid = entrega mail_home = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario mail_location = mdbox:/buzones_primarios/%2.26Hn/%2.200Hn/%n:ALT=/buzones_secundarios/%2.26Hn/%2.200Hn/%n:INDEX=/indices_correo/%2.26Hn/%2.200Hn/%n:ITERINDEX mail_log_prefix = "%s(%u)<%{session}>: " mail_max_userip_connections = 2500 mail_plugins = " zlib acl quota virtual" mail_uid = entrega 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 mdbox_rotate_interval = 1 days mdbox_rotate_size = 60 M namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox SPAM { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } passdb { args = /etc/usuario_maestro.txt driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } plugin { acl = vfile lda_mailbox_autosubscribe = yes quota = dict:Cuota de usuario::[2]file:/indices_correo/cuotas/%n quota_rule2 = Trash:storage=+10%% quota_warning = storage=90%% aviso_cuota 90 %u sieve = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario/dovecot.sieve sieve_dir = /buzones_primarios/%2.26Hn/%2.200Hn/%n/home_usuario/sieve/ sieve_max_redirects = 20 zlib_save = gz zlib_save_level = 1 } pop3_no_flag_updates = yes protocols = pop3 imap sieve service anvil { client_limit = 25000 } service auth { client_limit = 32000 unix_listener auth-master { user = entrega } unix_listener auth-userdb { user = entrega } user = root } service aviso_cuota { executable = script /usr/local/bin/quota-warning.sh unix_listener aviso_cuota { mode = 0666 } user = entrega } service config { process_min_avail = 4 } service doveadm { inet_listener { port = 12354 } } service imap-login { executable = /usr/libexec/dovecot/imap-login group = dovenull process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service imap { executable = /usr/libexec/dovecot/imap process_limit = 8000 process_min_avail = 12 vsz_limit = 1 G } service managesieve-login { executable = /usr/libexec/dovecot/managesieve-login inet_listener sieve { port = 2000 } process_limit = 2000 vsz_limit = 1 G } service managesieve { executable = /usr/libexec/dovecot/managesieve process_limit = 5000 } service pop3-login { executable = /usr/libexec/dovecot/pop3-login process_limit = 5000 process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service pop3 { executable = /usr/libexec/dovecot/pop3 process_limit = 5000 } service stats { fifo_listener stats-mail { mode = 0600 user = entrega } } ssl_cert = </etc/pki/tls/certificado.pem ssl_cipher_list = ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:RC4:HIGH:!MD5:!aNULL:!EDH ssl_min_protocol = TLSv1.2 userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } verbose_proctitle = yes protocol sieve { managesieve_implementation_string = dovecot managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 64 k } protocol lda { hostname = mydomain.tldr info_log_path = log_path = mail_fsync = optimized mail_plugins = sieve zlib quota virtual postmaster_address = [3]me(a)mydomain.tldr syslog_facility = mail } protocol imap { imap_metadata = yes mail_plugins = zlib quota imap_quota virtual } protocol pop3 { mail_plugins = zlib quota virtual pop3_enable_last = yes pop3_uidl_format = %g } Regards Javier References Visible links 1. file://indices_correo/%2.26Hn/%2.200Hn/%n/dovecot-attributes 2. file://indices_correo/cuotas/%n 3. mailto:me@mydomain.tldr

2 2

dovecot Build on macOS Fails With "No rule to make target `-L/opt/local/lib', needed by `test-regex'"
by Steven Smith 25 Nov '25

25 Nov '25

I’m trying to update the MacPorts dovecot to version 2.4.2. The build uses the standard calls './configure ; make all’, with standard build flags LDFLAGS='-L/opt/local/lib …' I get this build error, which makes it appear that the Makefile in ./src/lib-regex is creating a incorrect target from the build flags. > :info:build Making all in lib-regex > :info:build make[3]: Entering directory `/opt/local/var/macports/build/dovecot-f6decbdd/work/dovecot-2.4.2/src/lib-regex' > :info:build make[3]: *** No rule to make target `-L/opt/local/lib', needed by `test-regex'. Stop. The cause of this is that the Makefile ./src/lib-regex/Makefile incorrectly includes the library path option -L/opt/local/lib as a library dependency: > LIBICU_LIBS = -L/opt/local/lib -licui18n -licuuc > LIBOBJS = > LIBPCRE_CFLAGS = > LIBPCRE_LIBS = -L/opt/local/lib -lpcre2-32 > LIBS = > LIBSODIUM_CFLAGS = > LIBSODIUM_LIBS = -L/opt/local/lib -lsodium I'm trying to update the MacPorts dovecot to version 2.4.2. The build uses the standard calls './configure ; make all', with standard build flags LDFLAGS='-L/opt/local/lib ...' I get this build error, which makes it appear that the Makefile in ./src/lib-regex is creating a incorrect target from the build flags. :info:build Making all in lib-regex :info:build make[3]: Entering directory `/opt/local/var/macports/build/dovecot-f6decbdd/work/dovecot-2.4.2/src/lib-regex' :info:build make[3]: *** No rule to make target `-L/opt/local/lib', needed by `test-regex'. Stop. The cause of this is that the Makefile ./src/lib-regex/Makefile incorrectly includes the library path option -L/opt/local/lib as a library dependency: LIBICU_LIBS = -L/opt/local/lib -licui18n -licuuc LIBOBJS = LIBPCRE_CFLAGS = LIBPCRE_LIBS = -L/opt/local/lib -lpcre2-32 LIBS = LIBSODIUM_CFLAGS = LIBSODIUM_LIBS = -L/opt/local/lib -lsodium

1 0

Fresh mailbox missing directories tmp/new/cur
by Andreas Pflug 24 Nov '25

24 Nov '25

My configuration is this: mail_driver = maildir mail_path=/mailboxes/%{user} mailbox_list_layout=fs mailbox_directory_name=mbxInternal After connecting to Dovecot with Thunderbird for the first time, the following directory structure is created: ./dovecot.index.log ./Trash ./Trash/mbxInternal ./Trash/mbxInternal/dovecot.index.cache ./Trash/mbxInternal/cur ./Trash/mbxInternal/dovecot-uidlist ./Trash/mbxInternal/new ./Trash/mbxInternal/tmp ./Trash/mbxInternal/dovecot.index.log ./Trash/mbxInternal/dovecot-keywords ./dovecot.mailbox.log ./dovecot-uidvalidity ./subscriptions ./dovecot-uidvalidity.69245ab1 ./dovecot.list.index.log ./dovecot-uidlist Trying to copy a mail (using thunderbird) to the Trash will succeed, but trying to copy to INBOX gives the error Error: Mailbox INBOX: open(/mailboxes/me/tmp/1763990412.M635852P115610.mailstore) failed: No such file or directory which isn't surprising, the tmp/cur/new directories aren't there. After creating a subfolder, I have ./tmp ./dovecot.mailbox.log ./dovecot-uidvalidity ./INBOX ./INBOX/subfolder ./INBOX/subfolder/mbxInternal ./INBOX/subfolder/mbxInternal/new ./INBOX/subfolder/mbxInternal/cur ./INBOX/subfolder/mbxInternal/dovecot-uidlist ./INBOX/subfolder/mbxInternal/dovecot.index.log ./INBOX/subfolder/mbxInternal/tmp ./cur ./subscriptions ./dovecot.list.index.log ./Junk ./Junk/mbxInternal ./Junk/mbxInternal/cur ./Junk/mbxInternal/ ./new all directories are there as expected, and copying to INBOX works as well. Tested with Dovecot 2.4.1 (Debian13) and Thunderbird 140.5 NB: with mailbox_directory_name and mailbox_list_layout unset, cur/new/tmp directories are created immediately. Regards Andreas

1 0

multiple passdbs on 2.4.1
by Lou Duchez 24 Nov '25

24 Nov '25

I recently upgraded from 2.3 to 2.4.1, a little unwillingly (thanks Fedora), and I've almost got 2.4.1 working on my failover mail server. The failover server's job is, if the main mail server is inaccessible, mail gets delivered to the failover instead. Then the main server will retrieve mail from the failover server when it can. This has worked very well for many years. The way I implemented it was, I had two passdb's on the failover server: one for ordinary users who might need to access the failover server directly (login and password required), and one so that the main mail server could grab mail from the failover server (no password required). This broke when I went to 2.4.1; now, no matter what I do, Dovecot honors only one of the passdbs. Here is the configuration as it stands now. The intention is that, if the user properly authenticates with the first passdb, they're authenticated and the second passdb isn't consulted. But if the user doesn't authenticate with the first passdb, Dovecot moves on to the second passdb. # the passdb for normal users to check their mail on the failover server passdb passwd-file { passwd_file_path = /vmail/Maildir/passwdfile passdb_result_success = return-ok passdb_result_failure = continue-fail } # the passdb for the main server to grab mail from the failover server passdb passwd-file { passwd_file_path = /vmail/Maildir/passwdfile passdb_skip = authenticated fields { nopassword = yes allow_nets = xxx.xxx.xxx.xxx/32 } passdb_result_success = return-ok passdb_result_failure = return-fail } As things stand now, Dovecot always moves on to the second passdb and authenticates the user, or not, according to the outcome of the second passdb. The outcome of the first passdb does not seem to matter. Curiously, if I comment out the second passdb, the first passdb authenticates users as expected. I've tried all kinds of gyrations with passdb_result_success and passdb_result_failure, and none of them seem to work. The options I have there right now are, to the best of my knowledge, the ones that best match the flow I want to be seeing. There's a chance there's a bug in 2.4.1, but I bet I'm doing something wrong. What am I doing wrong?

3 7

Migrate deliver conf from 2.3 to 2.4 help and get panic
by Barry Scott 21 Nov '25

21 Nov '25

I'm trying to migrate my dovecot config from Fedora 42's dovecot-2.3.21.1-5.fc42.x86_64 to Fedora 43's dovecot-2.4.1-6.fc43.x86_64. I use this command to run the LDA via deliver.sh: ---- #!/bin/sh exec /usr/libexec/dovecot/deliver -c $HOME/fetchmail/barry(a)barrys-emacs.org/dovecot-deliver-rc -e "$@" ---- It's called from a procmail script like this: ---- LDA="$HOME/fetchmail/$MAILACCOUNT/deliver.sh" :0 * ^List-Id:.*<dovecot.dovecot.org> | $LDA -m "Others.Dovecot" ---- The dovecot-deliver-rc that I use for 2.3 is ---- log_path = /home/barry-mail/fetchmail/barry(a)barrys-emacs.org/logs/deliver.log protocol lda { postmaster_address = barry(a)barrys-emacs.org mail_location = maildir:~/Maildir lda_mailbox_autocreate = yes } ---- But for 2.4 that config is invalid. For 2.4 I iterated to this: ---- dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 protocol lda { postmaster_address = barry(a)barrys-emacs.org lda_mailbox_autocreate = yes log_path = /home/barry-mail/fetchmail/barry(a)barrys-emacs.org/logs/deliver.log mail_driver = maildir mail_home = /home/barry-mail mail_path = /home/barry-mail/Maildir } ---- But that crashed /usr/libexec/dovecot/deliver ---- Panic: file mailbox-list.c: line 1163: unreached Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x40) [0x7efe1a0f8320] libdovecot.so.0(backtrace_get+0x2f) [0x7efe1a0f846f] libdovecot.so.0(+0x101322) [0x7efe1a101322] libdovecot.so.0(+0x101365) [0x7efe1a101365] libdovecot.so.0(+0x2ad0f) [0x7efe1a02ad0f] libdovecot.so.0(+0x2b062) [0x7efe1a02b062] libdovecot-storage.so.0(+0x13dd5) [0x7efe1a28cdd5] libdovecot-storage.so.0(+0x6bfcc) [0x7efe1a2e4fcc] libdovecot-storage.so.0(mail_storage_create+0x504) [0x7efe1a2b56b4] libdovecot-storage.so.0(raw_storage_create_from_set+0x1ab) [0x7efe1a31672b] deliver(main+0x800) [0x557e6bbab6a0] libc.so.6(+0x35b5) [0x7efe19e0f5b5] libc.so.6(__libc_start_main+0x88) [0x7efe19e0f668] deliver(_start+0x25) [0x557e6bbac0e5] ---- Is the config for 2.4 in principle correct? Where do I report the crash? Barry

2 1

control and index
by Marek Greško 21 Nov '25

21 Nov '25

Hello, I just upgraded my server from Fedora 42 to Fedora 43 and found out there is an upgrade to dovecot 2.4 which requires completely new config. I am in doubt how I should convert it. My main issue is now hot co convert this line: mail_location = maildir:/var/maildir/%u:INDEX=/var/dovecot-index/%u:CONTROL=/var/dovecot-control/%u I am uncertain whether the first part should look like: mail_home = /var/maildir/ mail_driver = maildir mail_path = /var/maildir/%{user} But I am completely lost how to convert INDEX and CONTROL section. Could someone help me in this matter? Thanks Marek Hello, I just upgraded my server from Fedora 42 to Fedora 43 and found out there is an upgrade to dovecot 2.4 which requires completely new config. I am in doubt how I should convert it. My main issue is now hot co convert this line: mail_location = maildir:/var/maildir/%u:INDEX=/var/dovecot-index/%u:CONTROL=/var/dovecot-control/%u I am uncertain whether the first part should look like: mail_home = /var/maildir/ mail_driver = maildir mail_path = /var/maildir/%{user} But I am completely lost how to convert INDEX and CONTROL section. Could someone help me in this matter? Thanks Marek

3 3

control and index
by Marek Greško 20 Nov '25

20 Nov '25

Hello, I just upgraded my server from Fedora 42 to Fedora 43 and found out there is an upgrade to dovecot 2.4 which requires completely new config. I am in doubt how I should convert it. My main issue is now hot co convert this line: mail_location = maildir:/var/maildir/%u:INDEX=/var/dovecot-index/%u:CONTROL=/var/dovecot-control/%u I am uncertain whether the first part should look like: mail_home = /var/maildir/ mail_driver = maildir mail_path = /var/maildir/%{user} But I am completely lost how to convert INDEX and CONTROL section. Could someone help me in this matter? Thanks Marek Hello, I just upgraded my server from Fedora 42 to Fedora 43 and found out there is an upgrade to dovecot 2.4 which requires completely new config. I am in doubt how I should convert it. My main issue is now hot co convert this line: mail_location = maildir:/var/maildir/%u:INDEX=/var/dovecot-index/%u:CONTROL=/var/dovecot-control/%u I am uncertain whether the first part should look like: mail_home = /var/maildir/ mail_driver = maildir mail_path = /var/maildir/%{user} But I am completely lost how to convert INDEX and CONTROL section. Could someone help me in this matter? Thanks Marek

2 10

folders in folders
by Marek Greško 20 Nov '25

20 Nov '25

Hello, after upgrade of the dovecot to 2.4.1 version my folders in folders stopped working. For example I had folder work and subfolder done. When accessing folder work everything is working, but after accessing inner folder done, I get error in kmail: A000210 NO Character not allowed in mailbox name: '.' ( 0.001 + 0.000 secs ) . [ CANNOT ] When I look into disk structure on disk, the folder name is .work.done. It seems new version of dovecot does not allow the . in the name. How could I fix this? Thanks Marek Hello, after upgrade of the dovecot to 2.4.1 version my folders in folders stopped working. For example I had folder work and subfolder done. When accessing folder work everything is working, but after accessing inner folder done, I get error in kmail: A000210 NO Character not allowed in mailbox name: '.' ( 0.001 + 0.000 secs ) . [ CANNOT ] When I look into disk structure on disk, the folder name is .work.done. It seems new version of dovecot does not allow the . in the name. How could I fix this? Thanks Marek

3 4

ee key too small
by Marek Greško 20 Nov '25

20 Nov '25

Hello, after upgrading from Fedora 42 to Fedora 43 the dovecot got upgraded to version 2.4. I tweaked the configuration, dovecot starts, but when client is trying to connect to imap, I get: imap-login: Error: Failed to initialize SSL connection: Couldn't initialize SSL server context: Can't load SSL certificate (ssl_server_cert_file setting): error:0A00018F:SSL routines ::ee key too small: I tried replacing 2048 bits RSA with 4096 bits RSA, I tried to not use the dh.pem file (I read somewhere it is not neede any more), I deleted /var/lib/dovecot/ssl-parameters.dat file, but still the same error. Where should I look next? My ssl config: ssl = required #ssl_server_dh_file = /etc/dovecot/dh.pem ssl_server { #ssl_server_dh_file = /etc/dovecot/dh.pem ssl_server_cert_file = /somewhere/dovecot.pem ssl_server_key_file = /somewhere/dovecot.pem prefer_ciphers = server } ssl_min_protocol = TLSv1.2 ssl_cipher_list = PROFILE=SYSTEM #ssl_verify_client_cert = no #ssl_prefer_server_ciphers = no Thanks Marek Hello, after upgrading from Fedora 42 to Fedora 43 the dovecot got upgraded to version 2.4. I tweaked the configuration, dovecot starts, but when client is trying to connect to imap, I get: imap-login: Error: Failed to initialize SSL connection: Couldn't initialize SSL server context: Can't load SSL certificate (ssl_server_cert_file setting): error:0A00018F:SSL routines ::ee key too small: I tried replacing 2048 bits RSA with 4096 bits RSA, I tried to not use the dh.pem file (I read somewhere it is not neede any more), I deleted /var/lib/dovecot/ssl-parameters.dat file, but still the same error. Where should I look next? My ssl config: ssl = required #ssl_server_dh_file = /etc/dovecot/dh.pem ssl_server { #ssl_server_dh_file = /etc/dovecot/dh.pem ssl_server_cert_file = /somewhere/dovecot.pem ssl_server_key_file = /somewhere/dovecot.pem prefer_ciphers = server } ssl_min_protocol = TLSv1.2 ssl_cipher_list = PROFILE=SYSTEM #ssl_verify_client_cert = no #ssl_prefer_server_ciphers = no Thanks Marek

5 24

TLS cipher preference - yes or no or both?
by Edmund Lodewijks 20 Nov '25

20 Nov '25

Hello list, In the latest Dovecot docs I read: > For TLSv1.3 server ciphers should not longer be preferred: > > ssl_server_prefer_ciphers = client Source: https://doc.dovecot.org/2.4.2/core/config/ssl.html I am not so much wondering why TLS 1.3 should no longer have server preference enabled; I am wondering HOW one can set server preference to 'yes' for TLS <= 1.2, and to 'no' for TLS 1.3+. If this is not possible, which setting would be preferred? Would setting it to 'yes' break something with TLS 1.3, or would it be safe to leave it on 'yes' despite the docs (here, I suppose, I am asking for a bit of clarification on the 'why' of this change)? Thank you for enlightening me! Kind regards, Edmund -- Edmund Lodewijks <edmund(a)proteamail.com> TZ: UCT+2 / GMT+2

1 0

[PATCH] doc: dovecot.conf is 644 file permission, not 755
by Xiao Pan 20 Nov '25

20 Nov '25

Use INSTALL_DATA instead of INSTALL in doc/Makefile.am to install dovecot.conf with 644 instead of 755 file permission. After the patch, after ./autogen.sh and ./configure, doc/Makefile shows dovecot.conf is correclty installed with INSTALL_DATA which is `/usr/bin/install -c -m 644` instead of INSTALL which is `/usr/bin/install -c`. More info about INSTALL_DATA see `info make`. Signed-off-by: Xiao Pan <xyz(a)flylightning.xyz> --- doc/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Makefile.am b/doc/Makefile.am index 87b52dbe46..845e70e2db 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -26,7 +26,7 @@ all-local: stamp-man install-data-hook: $(INSTALL) -d $(DESTDIR)$(sysconfdir)/dovecot test -e $(DESTDIR)$(sysconfdir)/dovecot/dovecot.conf || \ - $(INSTALL) dovecot.conf $(DESTDIR)$(sysconfdir)/dovecot/dovecot.conf + $(INSTALL_DATA) dovecot.conf $(DESTDIR)$(sysconfdir)/dovecot/dovecot.conf install-data-local: $(MKDIR_P) $(DESTDIR)$(docdir); \ -- 2.52.0

1 3

inet_listener_address unimplemented
by Allan Zhang 18 Nov '25

18 Nov '25

Hello, I was hoping to use inet_listener_address to specify different listening addresses for IMAP (143) and IMAPS (993). It looks like inet_listener_address appears in the documentation[1] but is unimplemented[2]. 1. https://doc.dovecot.org/2.4.2/core/config/service.html#inet_listener_address 2. https://github.com/dovecot/core/blob/13ac9959a3c399e8a9d53f40f7858109dc0801… Best, Allan

2 2

Devocot-lda help please
by Jászberényi Szabolcs 17 Nov '25

17 Nov '25

Dear All! I have a strange error after upgrading from Debian Bookworm (12) to Debian Trixie (13). The server was lunched more than 10 years ago, so there are countless possible issues. Motherboard: ASUS P8B-E Series CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz Architecture: x64 Memory: 32GB (4 pcs of Kingston 9965525-058.A00LF) Disk: 2 pcs SSD in software RAID1 for / (root filesystem) and 2 pcs HDD with software RAID1 for /home Filesystems: ext4 The server will be soon replaced, but I need working configuration ASAP. After tweeking everything is working, but every time I am sending az email I have a Undelivered Mail Returned to Sender that has an error message: Command died with status 159: "/usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" -d "$USER"". Command output: Bad system call Tried to remove the -f and -a paramteres, but everithing is the same, only the command varies dependent on the config. Postfix in main.cf: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" -d "$USER" # ls -l /usr/lib/dovecot/dovecot-lda -rwxr-sr-x 1 root mail 27024 okt 23 16.01 /usr/lib/dovecot/dovecot-lda The server has winbind configured thru nsswitch, so every other program uses pam for user authentication and paramteres. Postfix has LDAP configured. Can anyone point out what I am missing? I found that dovecot-lda is producing the error, but nothing in dovecot's logs. Postfix shows the error in mail.log, but nothing other than this. If I run the program manually it asks for only the -d parameter, nothing more. Before this version I had only the -f and -a paramteres, no -d. It was working, but now it only works if I set it up with -d. I have attached the sysreports output. Waiting for help! Best regards: -- Tisztelettel: Jászberényi Szabolcs Rendszergazda Győr, PÁGISZ <https://www.pagisz.hu/> Mobil: +36704157707 Dear All! I have a strange error after upgrading from Debian Bookworm (12) to Debian Trixie (13). The server was lunched more than 10 years ago, so there are countless possible issues. Motherboard: ASUS P8B-E Series CPU: Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz Architecture: x64 Memory: 32GB (4 pcs of Kingston 9965525-058.A00LF) Disk: 2 pcs SSD in software RAID1 for / (root filesystem) and 2 pcs HDD with software RAID1 for /home Filesystems: ext4 The server will be soon replaced, but I need working configuration ASAP. After tweeking everything is working, but every time I am sending az email I have a Undelivered Mail Returned to Sender that has an error message: Command died with status 159: "/usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" -d "$USER"". Command output: Bad system call Tried to remove the -f and -a paramteres, but everithing is the same, only the command varies dependent on the config. Postfix in main.cf: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" -d "$USER" # ls -l /usr/lib/dovecot/dovecot-lda -rwxr-sr-x 1 root mail 27024 okt 23 16.01 /usr/lib/dovecot/dovecot-lda The server has winbind configured thru nsswitch, so every other program uses pam for user authentication and paramteres. Postfix has LDAP configured. Can anyone point out what I am missing? I found that dovecot-lda is producing the error, but nothing in dovecot's logs. Postfix shows the error in mail.log, but nothing other than this. If I run the program manually it asks for only the -d parameter, nothing more. Before this version I had only the -f and -a paramteres, no -d. It was working, but now it only works if I set it up with -d. I have attached the sysreports output. Waiting for help! Best regards: -- Tisztelettel: Jaszberenyi Szabolcs Rendszergazda Gyo"r, [1]PAGISZ Mobil: +36704157707 References Visible links 1. https://www.pagisz.hu/

2 1

doveadm -A finds non existent users
by Kippels, Julian 14 Nov '25

14 Nov '25

Hi, I am trying to iterate through all users using "doveadm sieve list -A" and I am seeing a lot of messages like this one: doveadm(someuser): Info: User no longer exists, skipping When I do "doveadm sieve list -u someuser" I get the following: doveadm(someuser): Error: User doesn't exist I have defined LDAP as my userdb and "someuser" is not present in the LDAP anymore. Where does doveadm -A get this user from and how can I clean this up? Thanks Julian

3 3

authentication back-ends - go to specific one?
by lejeczek 13 Nov '25

13 Nov '25

Hi guys. Is it possible to tell *dovecot* to authenticate with a specific back-end for a given domain? If it would not the only back-end a given account of a specific domain would try, then it would be the first back-end such account would try to auth against - possible? many thanks, L. Hi guys. Is it possible to tell dovecot to authenticate with a specific back-end for a given domain? If it would not the only back-end a given account of a specific domain would try, then it would be the first back-end such account would try to auth against - possible? many thanks, L.

2 1

after upgrade to 2.4 I get passwd-file: Password mismatch
by Helmut K. C. Tessarek 11 Nov '25

11 Nov '25

I upgraded dovecot from 2.3 to 2.4 today and all of a sudden I get an authentication error: passwd-file: Password mismatch My config looks like this: passdb pam { driver = pam } passdb passwd-file { driver = passwd-file auth_username_format = %{user | username} passwd_file_path = /etc/dovecot/alternate/passwd skip = authenticated } I haven't changed the /etc/dovecot/alternate/passwd in ages and its contents look similar to: user:$6$blablablagfsgfsgfsgsbfssfslongbase64stringhere Just earlier today (on 2.3) I was able to login just fine with the alternate password for my user. Did I misconfigure dovecot or are $6$ type passwords no longer supported. Here's the debug output: 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: pam: Finished passdb lookup 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: passwd-file: Performing passdb lookup 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: passwd-file: lookup: user=userhere file=/etc/dovecot/alternate/passwd 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: passwd-file: Finished passdb lookup 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: Auth request finished 2025-11-10 05:44:58 +0100auth(userhere,server-ip-here,sasl:plain)<VrJZMTZD7rtcKosF>: Debug: delaying auth failure Any idea what might be going on? Cheers, K. C.

2 4

Panic: file mail-user.c: line 185 (mail_user_deinit): assertion failed: ((*user)->refcount == 1)
by Szőts Ákos 10 Nov '25

10 Nov '25

Hi everyone, When I'm running a force-resync on my mailbox, it crashes. Unfortunately, after the crash, it left multiple new FTS mailboxes. Command: doveadm -D force-resync -u user(a)domain.ext '*' Error message: doveadm: Debug: Mailbox INBOX/fts-flatcurve/current.1756202040958990: Mailbox opened doveadm: Error: Mailbox INBOX: FTS optimize failed doveadm: Error: cmd force-resync: Forcing a resync on mailbox INBOX failed: FTS optimize failed doveadm: Panic: file mail-user.c: line 185 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) doveadm: Error: Raw backtrace: #0 fatal_handler_real[0x7f7fcd996190] -> #1 default_fatal_handler[0x7f7fcd996260] -> #2 i_panic[0x7f7fcd8b5407] -> #3 mail_user_deinit.cold[0x7f7fcdc5720e] -> #4 doveadm_mail_next_user[0x55b93b0c16b0] -> #5 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55b93b0c33d0] -> #6 doveadm_cmdline_run[0x55b93b0d76e0] -> #7 doveadm_cmdline_try_run[0x55b93b0d7ee0] -> #8 main[0x55b93b0b0d10] -> #9 __libc_start_call_main[0x7f7fcd50827e] -> #10 __libc_start_main_alias_2[0x7f7fcd50833e] -> #11 _start[0x55b93b0b1320] Backtrace: #0 __pthread_kill_implementation(threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007f7fcd57ae33in __pthread_kill_internal(threadid=<optimized out>, signo=6) at pthread_kill.c:89 #2 0x00007f7fcd51f7b6in __GI_raise(sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007f7fcd50634bin __GI_abort() at abort.c:77 #4 0x00007f7fcd8b5575in default_fatal_finish(type=LOG_TYPE_PANIC, status=0) at ../lib/failures.c:461 #5 fatal_handler_real(ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:473 #6 0x00007f7fcd996283in default_fatal_handler(ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:481 #7 0x00007f7fcd8b54d7in i_panic(format=format@entry=0x7f7fcdd3eac8 "file %s: line %d (%s): assertion failed: (%s)") at ../lib/failures.c:526 #8 0x00007f7fcdc57237in mail_user_deinit(user=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/lib-storage/mail-user.c:185 #9 mail_user_deinit(user=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/lib-storage/mail-user.c:183 #10 0x000055b93b0c18f2in doveadm_mail_next_user(ctx=0x55b93ed9dfb8, error_r=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:505 #11 0x000055b93b0c35e7in doveadm_mail_cmd_exec(ctx=0x55b93ed9dfb8, wildcard_user=0x0) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:705 #12 doveadm_cmd_ver2_to_mail_cmd_wrapper(cctx=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:1034 #13 0x000055b93b0d7dd7in doveadm_cmdline_run(argc=<optimized out>, argv=0x55b93ed69840, cctx=cctx@entry=0x55b93ed90fa8) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-cmd-parse.c:451 #14 0x000055b93b0d7f8cin doveadm_cmdline_try_run(cmd_name=cmd_name@entry=0x55b93ed6987c "force-resync", argc=<optimized out>, argv=<optimized out>, cctx=cctx@entry=0x55b93ed90fa8) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-cmd.c:160 #15 0x000055b93b0b101din main(argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm.c:406 Unfortunately, this interrupted run left many new mailboxes in place: $ doveadm mailbox list -u user(a)domain.ext Junk Drafts Drafts/fts-flatcurve Drafts/fts-flatcurve/current.1756201209435330 Drafts/fts-flatcurve/index.5092 Trash Trash/fts-flatcurve Trash/fts-flatcurve/current.1756242793225435 Trash/fts-flatcurve/index.5401 Trash/Junk Trash/Junk/fts-flatcurve Trash/Junk/fts-flatcurve/index.6279 Trash/Junk/fts-flatcurve/current.1756366793619309 Interestingly, a short ago I deleted the Junk mailbox with "doveadm mailbox delete -e Junk". Trash/Junk was never a thing. Version: 2.4.2 In case FTS config is useful: mail_plugins { fts = yes fts_flatcurve = yes quota = yes virtual = yes } fts flatcurve { substring_search = yes } fts_autoindex = yes language en { default = yes } language de { } language_tokenizers = generic email-address Ákos Hi everyone, When I'm running a force-resync on my mailbox, it crashes. Unfortunately, after the crash, it left multiple new FTS mailboxes. Command: doveadm -D force-resync -u [1]user(a)domain.ext '*' Error message: doveadm: Debug: Mailbox INBOX/fts-flatcurve/current.1756202040958990: Mailbox opened doveadm: Error: Mailbox INBOX: FTS optimize failed doveadm: Error: cmd force-resync: Forcing a resync on mailbox INBOX failed: FTS optimize failed doveadm: Panic: file mail-user.c: line 185 (mail_user_deinit): assertion failed: ((*user)->refcount == 1) doveadm: Error: Raw backtrace: #0 fatal_handler_real[0x7f7fcd996190] -> #1 default_fatal_handler[0x7f7fcd996260] -> #2 i_panic[0x7f7fcd8b5407] -> #3 mail_user_deinit.cold[0x7f7fcdc5720e] -> #4 doveadm_mail_next_user[0x55b93b0c16b0] -> #5 doveadm_cmd_ver2_to_mail_cmd_wrapper[0x55b93b0c33d0] -> #6 doveadm_cmdline_run[0x55b93b0d76e0] -> #7 doveadm_cmdline_try_run[0x55b93b0d7ee0] -> #8 main[0x55b93b0b0d10] -> #9 __libc_start_call_main[0x7f7fcd50827e] -> #10 __libc_start_main_alias_2[0x7f7fcd50833e] -> #11 _start[0x55b93b0b1320] Backtrace: #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007f7fcd57ae33 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89 #2 0x00007f7fcd51f7b6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007f7fcd50634b in __GI_abort () at abort.c:77 #4 0x00007f7fcd8b5575 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at ../lib/failures.c:461 #5 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:473 #6 0x00007f7fcd996283 in default_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:481 #7 0x00007f7fcd8b54d7 in i_panic (format=format@entry=0x7f7fcdd3eac8 "file %s: line %d (%s): assertion failed: (%s)") at ../lib/failures.c:526 #8 0x00007f7fcdc57237 in mail_user_deinit (user=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/lib-storage/mail-user.c:185 #9 mail_user_deinit (user=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/lib-storage/mail-user.c:183 #10 0x000055b93b0c18f2 in doveadm_mail_next_user (ctx=0x55b93ed9dfb8, error_r=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:505 #11 0x000055b93b0c35e7 in doveadm_mail_cmd_exec (ctx=0x55b93ed9dfb8, wildcard_user=0x0) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:705 #12 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-mail.c:1034 #13 0x000055b93b0d7dd7 in doveadm_cmdline_run (argc=<optimized out>, argv=0x55b93ed69840, cctx=cctx@entry=0x55b93ed90fa8) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-cmd-parse.c:451 #14 0x000055b93b0d7f8c in doveadm_cmdline_try_run (cmd_name=cmd_name@entry=0x55b93ed6987c "force-resync", argc=<optimized out>, argv=<optimized out>, cctx=cctx@entry=0x55b93ed90fa8) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm-cmd.c:160 #15 0x000055b93b0b101d in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dovecot-2.4.2/src/doveadm/doveadm.c:406 Unfortunately, this interrupted run left many new mailboxes in place: $ doveadm mailbox list -u [2]user(a)domain.ext Junk Drafts Drafts/fts-flatcurve Drafts/fts-flatcurve/current.1756201209435330 Drafts/fts-flatcurve/index.5092 Trash Trash/fts-flatcurve Trash/fts-flatcurve/current.1756242793225435 Trash/fts-flatcurve/index.5401 Trash/Junk Trash/Junk/fts-flatcurve Trash/Junk/fts-flatcurve/index.6279 Trash/Junk/fts-flatcurve/current.1756366793619309 Interestingly, a short ago I deleted the Junk mailbox with "doveadm mailbox delete -e Junk". Trash/Junk was never a thing. Version: 2.4.2 In case FTS config is useful: mail_plugins { fts = yes fts_flatcurve = yes quota = yes virtual = yes } fts flatcurve { substring_search = yes } fts_autoindex = yes language en { default = yes } language de { } language_tokenizers = generic email-address Akos References Visible links 1. mailto:user@domain.ext 2. mailto:user@domain.ext

2 3

doveadm sync: Both source and destination mail_path and mail_index_path point to same directory
by Szőts Ákos 09 Nov '25

09 Nov '25

Hi everyone, When I'm trying to synchronise my e-mails from a backup with doveadm sync, I get an error. Doveadmin sync command: doveadm -D sync -1 -f -a "Virtual/All" -R -u user(a)example.net -n inbox mdbox:/var/spool/mail/example.net/user_backup Error message: dsync: Error: cmd sync: Both source and destination mail_path and mail_index_path point to same directory: /var/spool/mail/example.net/user//mail/mailboxes (name space inbox { mail_path } is set explicitly?) Relevant config section: namespace inbox { separator = / inbox = yes # "home" is set in userdb mail_path = %{home}/mail mail_index_path = %{home}/index/inbox mailbox ... { ... } mailbox ... { ... } } mail_driver = mdbox According to the config, the two directories are explicitly set to be different. I verified and they exist and they are not symlinks. Do you know what causes this issue? Version: 2.4.2 Thank you, Ákos Hi everyone, When I'm trying to synchronise my e-mails from a backup with doveadm sync, I get an error. Doveadmin sync command: doveadm -D sync -1 -f -a "Virtual/All" -R -u [1]user(a)example.net -n inbox mdbox:/var/spool/mail/example.net/user_backup Error message: dsync: Error: cmd sync: Both source and destination mail_path and mail_index_path point to same directory: /var/spool/mail/example.net/user//mail/mailboxes (name space inbox { mail_path } is set explicitly?) Relevant config section: namespace inbox { separator = / inbox = yes # "home" is set in userdb mail_path = %{home}/mail mail_index_path = %{home}/index/inbox mailbox ... { ... } mailbox ... { ... } } mail_driver = mdbox According to the config, the two directories are explicitly set to be different. I verified and they exist and they are not symlinks. Do you know what causes this issue? Version: 2.4.2 Thank you, Akos References Visible links 1. mailto:user@example.net

2 2

Using full email address as login
by Alex 07 Nov '25

07 Nov '25

Hi, I'm using dovecot-2.3.21.1 on fedora42. It seems that increasingly remote clients are only supporting the full email address as the login ID instead of just the username. One such example is Apollo.io, an AI sales platform that uses IMAP to connect to a remote server to send and receive emails. The documentation I've found on this appears to be deprecated or incomplete. Do I want to look for "shared namespace" documentation? Currently, emails are stored in /var/spool/mail/username. Does this need to change to something like /var/spool/domain.com/username? I'll also need to change postfix to use username(a)domain.com with sasl, I believe? Here is my current dovecot.conf. Ideas greatly appreciated. # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21.1 (49005e73) # OS: Linux 6.17.6-200.fc42.x86_64 x86_64 Fedora release 42 (Adams) # Hostname: orion.example.com auth_mechanisms = plain xoauth2 oauthbearer auth_verbose = yes default_vsz_limit = 1500 M mail_gid = mail mail_home = mail/ mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_max_userip_connections = 500 mail_plugins = " listescape acl" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = 68.195.111.42 port = 993 } process_min_avail = 6 service_count = 0 } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 } inet_listener pop3s { port = 995 } } ssl_cert = </etc/letsencrypt/example-fullchain.pem ssl_cipher_list = ALL:!LOW:!EXP:!aNULL:!RC4::!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } Thanks, Alex Hi, I'm using dovecot-2.3.21.1 on fedora42. It seems that increasingly remote clients are only supporting the full email address as the login ID instead of just the username. One such example is Apollo.io, an AI sales platform that uses IMAP to connect to a remote server to send and receive emails. The documentation I've found on this appears to be deprecated or incomplete. Do I want to look for "shared namespace" documentation? Currently, emails are stored in /var/spool/mail/username. Does this need to change to something like /var/spool/[1]domain.com/username? I'll also need to change postfix to use [2]username(a)domain.com with sasl, I believe? Here is my current dovecot.conf. Ideas greatly appreciated. # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21.1 (49005e73) # OS: Linux 6.17.6-200.fc42.x86_64 x86_64 Fedora release 42 (Adams) # Hostname: [3]orion.example.com auth_mechanisms = plain xoauth2 oauthbearer auth_verbose = yes default_vsz_limit = 1500 M mail_gid = mail mail_home = mail/ mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_max_userip_connections = 500 mail_plugins = " listescape acl" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { address = 68.195.111.42 port = 993 } process_min_avail = 6 service_count = 0 } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 } inet_listener pop3s { port = 995 } } ssl_cert = </etc/letsencrypt/example-fullchain.pem ssl_cipher_list = ALL:!LOW:!EXP:!aNULL:!RC4::!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd } Thanks, Alex References Visible links 1. http://domain.com/username 2. mailto:username@domain.com 3. http://orion.example.com/

3 3

2.4.2 upgrade oddity
by Andy Baugh 06 Nov '25

06 Nov '25

Howdy y'all, I noticed something odd with the userdb/passdb processing past the 2.4.2 CVE fix, etc. -- namely that the prefixing you previously needed to do to userdb returns, etc. when you set a cache_key is no longer necessary and in fact harmful. It is worth mentioning, as after looking into this a bit and realizing that it "should have been obvious" to me that this would have been the case. That said I didn't make the logical leap till doveadm screamed at me about it during mailbox creation after upgrade (can't very well do `doveadm mailbox create -s -u user(a)domain.test INBOX.spam` when your userdb returns `${CACHE_KEY}_mailbox/INBOX/spam/...` for the relevant config values, etc.). TL;DR: disabling the cache = do NOT prefix any userdb/passdb returns in accordance with cache_key you set. This is true for lua passdb/authdb or any other authdb, not just passwd/oauth2. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

2 2

doveadm sync issue
by Dan Whitehouse 06 Nov '25

06 Nov '25

Hi, I am running Dovecot on Debian trixie (dovecot-core/stable,now 1:2.4.1+dfsg1-6 amd64). Under the previous version, which I believe was 2.3, I was able to run a sync script with the following syntax: doveadm sync -u <user> remote:<user>@<host.tld> This worked very well and I was able to sync my mail. Having upgraded, this syntax produces the following error: dsync-server: invalid option -- ‘U' Error: doveadm: Unexpected or incomplete option: -U Even though my script doesn’t pass “-U” explicitly I believe that it is passed internally: https://github.com/dovecot/core/blob/main/src/doveadm/doveadm-settings.c#L1… core/src/doveadm/doveadm-settings.c at main · dovecot/core github.com Confusingly the online help still displays: doveadm dsync-server —help doveadm dsync-server [-r <rawlog path>] [-T <timeout secs>] [-U] Here we can see that the “-U” option (despite all the above) appears to have been removed from the code: https://github.com/dovecot/core/commit/4c04e4c30fd4817a8b0e11d04d9681173f69… global: Remove replicator · dovecot/core@4c04e4c github.com I have added the following to /etc/dovecot/local.conf: dsync_remote_cmd = "ssh -l%{login} %{host} doveadm dsync-server -u%{user}” (Note that I override the “-U”) and sync once again works properly. Many thanks for your attention, Dan Whitehouse

4 3

Dovecot upgrade from 2.3.x to 2.4.x: and mailbox_alias plugin
by Gerhard Wiesinger 06 Nov '25

06 Nov '25

Hello, Regarding dovecot upgrade from 2.3.x to 2.4.x and mailbox_alias plugin: I've already converted my config and scripts but I'm still missing this config change: plugin { mailbox_alias_old = Spam mailbox_alias_new = Junk } I saw in the link https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html mailbox-alias plugin Depending on the use case, replacement may be the mailbox_special_use mailbox setting and/or Sieve filters. Any ideas what's the best alternative? Another question, is the following correct: mail_home = /home/vmail/%n mail_location = maildir:~/Maildir => mail_home = /home/vmail/%{user | username} mail_driver = maildir mail_path = ~/Maildir mail_inbox_path = ~/Maildir (Especially mail_inbox_path, I don't have a ".INBOX" directory currently, I guess .INBOX is now default. How to deal with this?) Thnx. Ciao, Gerhard

2 4

Build failure due to non-constant initializers in unicode-transform.c
by adesh＠backuply.com 05 Nov '25

05 Nov '25

When building Dovecot 2.4.2 on modern compilers (GCC ≥ 5, Clang, or any C99/C11-compliant environment), the build fails in src/lib/unicode-transform.c due to the use of non-constant initializers in static const global variables. The affected lines define Hangul composition constants using other const variables instead of compile-time constants, which is not allowed in standard C99 and later. error log: unicode-transform.c:211:1: error: initializer element is not constant static const size_t uni_hangul_n_count = uni_hangul_v_count * uni_hangul_t_count; ^ unicode-transform.c:212:1: error: initializer element is not constant static const uint16_t uni_hangul_l_end = uni_hangul_l_base + uni_hangul_l_count; ^ unicode-transform.c:213:1: error: initializer element is not constant static const uint16_t uni_hangul_v_end = uni_hangul_v_base + uni_hangul_v_count; ^ unicode-transform.c:214:1: error: initializer element is not constant static const uint16_t uni_hangul_t_end = uni_hangul_t_base + uni_hangul_t_count; ^ This issue prevents building Dovecot 2.4.x on modern systems without non-standard compiler flags, breaking out-of-the-box builds on up-to-date Linux distributions.

2 2

configuration fails at the last hurdle
by demo＠manx.net 04 Nov '25

04 Nov '25

as a newbie suddenly requiring a mail server the configuration of dovecot and postfix is proving elusive. if i get one element working another fails. i think it would help readers if i supply my status report and ask for suggestions as to how to ensure a remote client can access the mail just delivered from another remote in addition for mutt to see the mail on the sever. cat <<EOF > ~/mailserver-status.txt 📨 Mail Server Status – Ryzen2 (Ubuntu 25.10) Objective: To host email services independently, replacing Manx Telecom’s legacy offering. Rationale: Manx Telecom has been acquired by Jersey Telecom, with plans to charge £65 per annum per email address. This migration aims to preserve autonomy and reduce costs. ✅ Current Achievements - Mail Receipt Confirmed: Mail addressed to jsm(a)mckenzietrust.com (a domain owned by us) is successfully received via encrypted POP3S (port 995) using both Thunderbird and OpenSSL. - Maildir Workflow Operational: Messages arrive in Maildir/new and are moved every minute to Maildir/cur via a cron job. They are accessible locally using mutt. - SSL Layer Functional: POP3S handshake completes successfully, confirming certificate and encryption setup is sound. ⚠️ Known Issues - Remote Access Fails Silently: Thunderbird and OpenSSL clients connect but cannot retrieve messages from Maildir/cur or new. No errors are returned—access appears to die silently. - Dovecot Configuration Fragility: Any attempt to explicitly define mail_location in config files (e.g., 10-mail.conf) causes Dovecot to crash on startup. This behavior is consistent across both Ubuntu 25.04 and 25.10 builds. It is imperative not to attempt location overrides, as recovery requires reverting to a clean config state. - Post-Reboot Regression: Remote access was briefly functional but failed after a system reboot triggered by a firmware update. This suggests a state-dependent or ephemeral config success. 🧭 Configuration Notes - Dovecot and Postfix Versions: Packages from Ubuntu 25.04 were manually installed and locked to prevent auto-updates. This avoids compatibility issues with newer builds. - POP3S Listener Enabled: The following stanza is active in 10-master.conf: service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } - SSL Configuration: ssl = yes ssl_server_cert_file = /etc/dovecot/private/dovecot.pem ssl_server_key_file = /etc/dovecot/private/dovecot.key These paths are valid and readable by root. 🧱 Constraints and Priorities - No Urgency: At least one month is available for debugging and refinement. - Web Server Stability Is Critical: The live web server must remain uninterrupted, as it hosts the McKenzie Trust’s public-facing structure. - Outbound Mail Deliverability: The domain currently uses DDNS. Without a PTR record, outbound mail from Ryzen2 may be rejected. A fixed IP or relay forwarding will be required. 🧩 Next Steps - Investigate mailbox visibility for remote clients—likely a permissions or UID mapping issue. - Consider enabling auth-master socket for privileged access if needed. - Explore relay options or static IP acquisition to ensure outbound mail acceptance. EOF regards jsm

5 6

doveadm sync -1 -R only downloads Inbox but not Sent Items
by r.barclay＠habmalnefrage.de 02 Nov '25

02 Nov '25

Hi, When my free mail provider mailbox runs out of free space, I have my local Dovecot server one-way sync that free mail mailbox and then I delete the contents of the free mail mailbox. So I can archive my emails in an "offline archive". Initially, I used "doveadm backup", but later always used: doveadm -Dv sync -u offline(a)example.org -1 -f -R imapc: At large, this works. But only during the first "backup" the "Sent" folder was synced as well. Nowdays, it only downloads the Inbox, but not my Sent Items. I tried adding the "-N" parameter, but that said: "Fatal: -N parameter requires syncing with remote host" I'm on Debian 12 and Dovecot 2.3.x: 1:2.3.19.1+dfsg1-2.1+deb12u1 amd64. What could I check or try? And one more question: To better understand the debug output: What is "brain M" and "brain S"? Yours, Reg

1 0

Dovecot 2.4.0: Error with Oauth2 login after successful introspection
by sukanyamorbale＠gmail.com 31 Oct '25

31 Oct '25

Hello, I upgraded Dovecot from version 2.3.21 to 2.4.0. In version 2.3.21, I encountered issues with OAuth2 authentication that had worked correctly in earlier releases. Specifically, the active_attribute check was failing, even though Keycloak was sending the active value as true. After upgrading to Dovecot 2.4.0, the active attribute is now validated successfully, and token introspection completes as expected. However, I am now encountering the following error: 2025-10-30 14:43:41.438 Oct 30 13:43:41 auth: Panic: file expansion-statement.c: line 30 (var_expand_execute_stmt): assertion failed: (value != NULL) 2025-10-30 14:43:41.444 Oct 30 13:43:41 auth-worker(354): Debug: conn unix:auth-worker (pid=113,uid=101): Disconnected: Connection closed (fd=-1) 2025-10-30 14:43:41.443 Oct 30 13:43:41 auth: Error: Raw backtrace: #0 test_subprocess_fork[0x7f03870fc510] -> #1 backtrace_append[0x7f03870fc7c0] -> #2 backtrace_get[0x7f03870fc960] -> #3 event_filter_match_iter_init[0x7f0387106bc0] -> #4 i_syslog_fatal_handler[0x7f0387106d00] -> #5 i_panic[0x7f0387033c8e] -> #6 [unw_get_proc_name() failed: -10] -> #7 var_expand_program_execute[0x7f0387070460] -> #8 settings_file_get[0x7f0387083550] -> #9 settings_parse_keyidx_value_nodup[0x7f0387085660] -> #10 settings_parse_keyidx_value_nodup[0x7f0387085d70] -> #11 settings_parse_keyidx_value_nodup[0x7f0387087180] -> #12 settings_get[0x7f03870877b0] -> #13 auth_worker_auth_request_new[0x558c60949050] -> #14 auth_worker_auth_request_new[0x558c609496e0] -> #15 oauth2_json_tree_build[0x7f03870432f0] -> #16 oauth2_json_tree_build[0x7f03870433d0] -> #17 oauth2_request_parse_json[0x7f03870435a0] -> #18 http_client_request_callback[0x7f0387091ee0] -> #19 http_client_connection_lost_peer[0x7f0387094850] -> #20 http_client_peer_connection_failure[0x7f038709a090] -> #21 io_loop_call_io[0x7f0387122780] -> #22 io_loop_handler_run_internal[0x7f0387123aa0] -> #23 io_loop_handler_run[0x7f0387123c40] -> #24 io_loop_run[0x7f0387123e40] -> #25 master_service_run[0x7f0387075720] -> #26 main[0x558c60931e80] -> #27 __libc_init_first[0x7f0386dc9150] -> #28 __libc_start_main[0x7f0386dc9200] -> #29 _start[0x558c609323d0] Here is my current dovecot.conf. dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 protocols = imap pop3 lmtp auth_mechanisms { oauthbearer = yes xoauth2 = yes } oauth2 { introspection_url = https://client-name:client-key@iam.keyclock-url.com/auth/realms/realm-name/… introspection_mode = post active_attribute = active active_value = true username_attribute = preferred_username } userdb static { fields { uid = vmail gid = vmail home = /home/vmail/%{user | domain}/%{user | username} } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { mode = 0600 user = postfix group = postfix } } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service auth-worker { user = vmail } log_debug = category=auth auth_verbose = yes auth_debug_passwords = yes mail_driver = maildir mail_home = /home/vmail/%{user | domain}/%{user | username} mail_path = ~ ssl_server_cert_file = /etc/ssl/private/vmail.crt ssl_server_key_file = /etc/ssl/private/vmail.key ssl_server_dh_file = /etc/dovecot/dh.pem mail_debug = yes log_path = /dev/stdout info_log_path = /dev/stdout debug_log_path = /dev/stdout Regards, Sukanya Morbale

1 0

Panic with FTS_BACKEND_FLAG_TOKENIZED_INPUT and virtual mailboxes: file index-search-result.c: line 132
by markus-dovecot＠doits.de 31 Oct '25

31 Oct '25

Originally posted and debugged here: https://github.com/slusarz/dovecot-fts-flatcurve/issues/66 I have to following panic with fts flatcurve enabled: ``` Panic: file index-search-result.c: line 132 (index_search_result_update_flags): assertion failed: (result->search_args->args == &search_arg) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x46) [0x74e9890a2846] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x74e9890a2962] -> /usr/lib/dovecot/libdovecot.so.0(+0x10d81b) [0x74e9890af81b] -> /usr/lib/dovecot/libdovecot.so.0(+0x10d8b7) [0x74e9890af8b7] -> /usr/lib/dovecot/libdovecot.so.0(+0x5e2e2) [0x74e9890002e2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x518a4) [0x74e9891d38a4] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x274e) [0x74e988bf8a9e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x5c) [0x74e9891eff9c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x39) [0x74e9891f0039] -> dovecot/imap(cmd_select_full+0x1df) [0x62354bd8326f] -> dovecot/imap(command_exec+0xa4) [0x62354bd8b444] -> dovecot/imap(+0x22392) [0x62354bd89392] -> dovecot/imap(+0x22444) [0x62354bd89444] -> dovecot/imap(client_handle_input+0x1bd) [0x62354bd8989d] -> dovecot/imap(client_input+0x74) [0x62354bd89e64] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x74e9890c603d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13a) [0x74e9890c77aa] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x74e9890c60e4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x74e9890c62a0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x74e989036ad7] -> dovecot/imap(main+0x570) [0x62354bd7ad20] -> /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x74e988c29d90] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x74e988c29e40] -> dovecot/imap(_start+0x25) [0x62354bd7ade5] ``` It happens when accessing virtual folder with filters like this: ``` something-*/excep-dev* header x-abc-exception "1" ``` The error happens on subsequent access of the folder: - Removing dovecot.index{,.log} files allows to access the virtual folder again - dovecot.index gets recreated on access and the folder can be accessed multiple times - Marking an e-mail read triggers the error, though! Now each next access raises the error - Removing dovecot.index{,.log} restores access again and the e-mails are still marked as read (so this information is not lost), until the next e-mail is marked as read: then the folder cannot be accessed again Slusarz debugged the backtrace and wrote a detailed description at https://github.com/slusarz/dovecot-fts-flatcurve/issues/66#issuecomment-229… which I'll quote here: > This is not a flatcurve bug - it is a bug within Dovecot's indexing/fts handling. > > (Detailed debug below, so that core team can understand the problem.) > > As discussed above, this bug is triggered with virtual mailboxes on subsequent accesses. The initial access will work fine; the assert crash only happens when the Dovecot lib-storage index code reads the indexes created for the virtual mailboxes. > > `index_search_result_update_appends()` in lib-storage/index/index-search-result.c > > * Inside this function, a "temporary search parameter to limit the search only to the new messages" is added to the mail search args. Later, it is checked that the mail_search args points to this same search parameter after the search is executed. It is this assert check that is failing, because the mail args is changing during the course of the search. > > * `i_assert(result->search_args->args == &search_arg);` > > > The search args are being altered in plugins/fts/fts-search.args.c, `fts_search_args_expand()`. Specifically, in that function, either `fts_search_args_expand_language_top_level()` or `fts_search_args_expand_tree()` is being called, which can replace the current args parameter with a new pointer. > > `fts_search_args_expand()` is being called in plugins//fts/fts-search.c by `fts_search_try_lookup()` when the FTS backend has the FTS_BACKEND_FLAG_TOKENIZED_INPUT flag set. Flatcurve has this flag set. > > This flag is defined in plugins/fts/fts-api-private.h. Comments say: > > ``` > /* Tokenize all the input. update_build_more() will be called a single > directly indexable token at a time. Searching will modify the search > args so that lookup() sees only tokens that can be directly > searched. */ > ``` > > Thus, the comments explicitly say the search args will be modified if this flag is set. This modification is incompatible with the assert check in `index_search_result_update_appends()`, which requires that the search args not be modified. > > The core team will have to determine whether this behavior is correct, or if the assert check is invalid. You can find some more discussion at https://github.com/slusarz/dovecot-fts-flatcurve/issues/66, but I think the most important part (the very detailed analysis from Slusarz, thanks again!) might be enough to understand and maybe fix the problem. Relevant information about the mail system: ``` # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.5.0-45-generic x86_64 Ubuntu 22.04.4 LTS [...] namespace { location = virtual:~/virtual:LAYOUT=maildir++ prefix = _/ separator = / } [...] plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared fts = flatcurve fts_autoindex = yes fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball stopwords fts_languages = de en fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=30 fts_tokenizers = generic email-address sieve = file:~/sieve;active=~/.dovecot.sieve } [...] ``` I can provide more information if you need. Thanks for looking into it!

2 3

Segfault (null pointer dereference) in mail_index_unset_fscked
by Марк Коренберг 31 Oct '25

31 Oct '25

Dovecot 2.3.21.1 (d492236fa0) Reduced sources: int mdbox_storage_rebuild(struct mdbox_storage *storage) { struct mdbox_map_atomic_context *atomic; atomic = mdbox_map_atomic_begin(storage->map); mdbox_map_atomic_unset_fscked(atomic); <---- atomic here is NULL according to gdb bt } struct mdbox_map_atomic_context *mdbox_map_atomic_begin(struct mdbox_map *map) { struct mdbox_map_atomic_context *atomic; atomic = i_new(struct mdbox_map_atomic_context, 1); atomic->map = map; <------- would fall here if atomic was NULL. but it does not. return atomic; } Seems memory corruption happens somewhere. Happy to help if you say how. -------------- Some tracebacks: #0 mail_index_unset_fscked (t=0x0) at ../lib-index/mail-index-transaction-update.c:1331 #1 0x00007fb99b0b1eb0 in mdbox_storage_rebuild (storage=<optimized out>) at index/dbox-multi/mdbox-storage-rebuild.c:1001 #2 0x00007fb99b0b2925 in mdbox_mailbox_close (box=0x56448dda4158) at index/dbox-multi/mdbox-storage.c:201 #3 0x00007fb99b08f3ba in mailbox_close (box=0x56448dda4158) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1642 #4 mailbox_close (box=box@entry=0x56448dda4158) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1633 #5 0x00007fb99b0946ef in mailbox_free (_box=_box@entry=0x7ffe965912a0) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1662 #6 0x0000564463d53a63 in imap_client_close_mailbox (client=client@entry=0x56448dd91ce8) ------ #0 mail_index_unset_fscked (t=0x0) at ../lib-index/mail-index-transaction-update.c:1331 #1 0x00007fed23455eb0 in mdbox_storage_rebuild (storage=<optimized out>) at index/dbox-multi/mdbox-storage-rebuild.c:1001 #2 0x00007fed23456925 in mdbox_mailbox_close (box=0x558f04a98ed8) at index/dbox-multi/mdbox-storage.c:201 #3 0x00007fed234333ba in mailbox_close (box=0x558f04a98ed8) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1642 #4 mailbox_close (box=box@entry=0x558f04a98ed8) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1633 #5 0x00007fed234386ef in mailbox_free (_box=_box@entry=0x7ffc98e15758) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1662 #6 0x00007fed22a4b2fc in quota_count_mailbox (root=0x558f04a73700, ns=0x558f04a4c7d0, vname=0x7fed23523807 "INBOX", bytes=<optimized out>, ------------- #0 mail_index_unset_fscked (t=0x0) at ../lib-index/mail-index-transaction-update.c:1331 #1 0x00007f8b661a2eb0 in mdbox_storage_rebuild (storage=<optimized out>) at index/dbox-multi/mdbox-storage-rebuild.c:1001 #2 0x00007f8b661a3925 in mdbox_mailbox_close (box=0x55690db6dec8) at index/dbox-multi/mdbox-storage.c:201 #3 0x00007f8b661803ba in mailbox_close (box=0x55690db6dec8) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1642 #4 mailbox_close (box=box@entry=0x55690db6dec8) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1633 #5 0x00007f8b661856ef in mailbox_free (_box=<optimized out>) at /usr/src/debug/dovecot-2.3.21.1-1.fc41.x86_64/src/lib-storage/mail-storage.c:1662 #6 0x00007f8b657a72fc in _Unwind_SetGRValue (context=<optimized out>, index=229799824, val=161) at ../../../libgcc/unwind-dw2.c:329 ------------ -- Segmentation fault

5 10

dovecot-2.4.2 pigeonhole make check failure
by Eray Aslan 31 Oct '25

31 Oct '25

Running make check for pigeonhole-2.4.2 fails: $ ./configure --with-dovecot=../dovecot-2.4.2 --with-managesieve \ && make \ && make check [...] make[2]: Leaving directory '/tmp/dovecot/dovecot-pigeonhole-2.4.2/doc' make[1]: Leaving directory '/tmp/dovecot/dovecot-pigeonhole-2.4.2/doc' /bin/sh ./update-version.sh . . testsuite: Fatal: execv(/usr/local/bin/doveconf) failed: No such file or directory make: *** [Makefile:1261: tests/testsuite.svtest] Error 84 This seems to be the result of commit 8b9295d. Do we now require a dovecot installation (or at least a working doveconf binary) for running tests for pigeonhole or is there a workaround I am missing? Thank you -- Eray

1 1

Dovecot and Pigeonhole v2.4.2 released
by Aki Tuomi 31 Oct '25

31 Oct '25

Hi! We are pleased to release version 2.4.2 of Dovecot and Pigeonhole. Important notice that we are adding new dependency of libpcre2 in this release to implement support for regular expressions in more safe manner. This release adds support for Debian Trixie and Red Hat Enterprise Linux 10, and removes support for Debian Bullseye and Red Hat Enterprise Linux 8. https://dovecot.org/releases/2.4/dovecot-2.4.2.tar.gz https://dovecot.org/releases/2.4/dovecot-2.4.2.tar.gz.sig https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot -- Dovecot NEWS * CVE-2025-30189: Passdb oauth2 (not oauth2 mechanism), passdb passwd, passdb bsdauth, and userdb passwd drivers would cause users to be cached with same cache key when auth cache was enabled. * auth: Remove proxy_always field. * config: Change settings history parsing to use python3. * doveadm: Print table formatter - Print empty values as "-". * imapc: Propagate remote error codes properly. * lda: Default mail_home=$HOME environment if not using userdb lookup * lib-dcrypt: Salt for new version 2 keys has been increased to 16 bytes. * lib-dregex: Add libpcre2 based regular expression support to Dovecot, if the library is missing, disable all regular expressions. This adds libpcre2-32 as build dependency. * lib-oauth2: jwt - Allow nbf and iat to point 1 second into future. * lib: Replace libicu with our own unicode library. Removes libicu as build dependency. * login-common: If proxying fails due to remote having invalid SSL cert, don't reconnect. + auth: Add ssl_client_cert_fp and ssl_client_cert_pubkey_fp fields, see https://doc.dovecot.org/latest/core/summaries/settings.html#ssl_peer_certif… for more information. + config: Add support for $SET:filter/path/setting. + config: Improve @group includes to work with overwriting their settings. + doveadm kick: Add support for kicking multiple usernames + doveadm mailbox status: Add support for deleted status item. + imap, imap-client: Add experimental partial IMAP4rev2 support. + imap: Implement support for UTF8=ACCEPT for APPEND + lib-oauth2, oauth2: Add oauth2_token_expire_grace setting. + lmtp: lmtp-client - Support command pipelining. + login-common: Support local/remote blocks better. + master: accept() unix/inet connections before creating child process to handle it. This reduces timeouts when child processes are slow to spawn themselves. - SMTPUTF8 was accepted even when it wasn't enabled. - auth, *-login: Direct logging with -L parameter was not working. - auth: Crash occured when OAUTH token validation failed with oauth2_use_worker_with_mech=yes. - auth: Invalid field handling crashes were fixed. - auth: ldap - Potential crash could happen at deinit. - auth: mech-gssapi - Server sending empty initial response would cause errors. - auth: mech-winbind - GSS-SPNEGO mechanism was erroneously marked as not accepting NUL. - config: Multiple issues with $SET handling has been fixed. - configure: Building without LDAP didn't work. - doveadm: If source user didn't exist, a crash would occur. - imap, pop3, submission, imap-urlauth: USER environment usage was broken when running standalone. - imap-hibernate: Statistics would get truncated on unhibernation. - imap: "SEARCH MIMEPART FILENAME ENDS" command could have accessed memory outside allocated buffer, resulting in a crash. - imapc: Fetching partial headers would cause other cached headers to be cached empty, breaking e.g. imap envelope responses when caching to disk. - imapc: Shared namespace's INBOX mailbox was not always uppercased. - imapc: imapc_features=guid-forced GUID generation was not working correctly. - lda: USER environment was not accepted if -d hasn't been specified. - lib-http: http-url - Significant path percent encoding through parse and create was not preserved. This is mainly important for Dovecot's Lua bindings for lib-http. - lib-settings: Crash would occur when using %variables in SET_FILE type settings. - lib-storage: Attachment flags were attempted to be added for readonly mailboxes with mail_attachment_flags=add-flags. - lib-storage: Root directory for unusable shared namespaces was unnecessarily attempted to be created. - lib: Crash would occur when config was reloaded and logging to syslog. - login-common: Crash might have occured when login proxy was destroyed. - sqlite: The sqlite_journal_mode=wal setting didn't actually do anything. - Many other bugs have been fixed. -- Pigeonhole NEWS * lib-sieve: Use new regular expression library in core. * managesieve: Add default service_extra_groups=$SET:default_internal_group. + lib-sieve: Add support for "extlists" extension. + lib-sieve: regex - Allow unicode comparator. - lib-sieve-tool: sieve-tool - All sieve_script settings were overriden. - lib-sieve: storage: dict: sieve_script_dict filter was missing from settings. - sieve-ldap-storage: Fix compile without LDAP.

4 4

dovecot-2.4.2 lua5-1 build failure
by Eray Aslan 31 Oct '25

31 Oct '25

Hi, Building dovecot-2.4.2 fails to build against lua5-1: $ ./configure --with-lua [...] checking for lua5.1 >= 5.1 lua5.1 != 5.2... yes configure: using library lua5.1 checking for lua_newstate... yes checking for luaL_setfuncs... no checking for luaL_setmetatable... no checking for lua_isinteger... no checking for lua_resume... yes checking for lua_seti... no checking for lua_tointegerx... no checking for lua_yieldk... no [...] $ make [...] CC dlua-iostream.lo dlua-iostream.c:16:28: error: field 'stream' has incomplete type 16 | struct luaL_Stream stream; | ^~~~~~ dlua-iostream.c: In function 'dlua_o_write': dlua-iostream.c:68:24: error: implicit declaration of function 'luaL_tolstring'; did you mean 'lua_tolstring'? [-Wimplicit-function-declaration] 68 | vec.iov_base = luaL_tolstring(L, 2, &vec.iov_len); | ^~~~~~~~~~~~~~ | lua_tolstring dlua-iostream.c:68:22: error: assignment to 'const void *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 68 | vec.iov_base = luaL_tolstring(L, 2, &vec.iov_len); | ^ dlua-iostream.c:73:24: error: implicit declaration of function 'luaL_fileresult'; did you mean 'luaL_pushresult'? [-Wimplicit-function-declaration] 73 | return luaL_fileresult(L, 0, o_stream_get_name(stream->os)); | ^~~~~~~~~~~~~~~ | luaL_pushresult make[3]: *** [Makefile:786: dlua-iostream.lo] Error 1 Same configure and make commands succeed when run against lua5-4. Not sure if this was intentional as we still check for >= lua5-1 != lua5-2 in m4/want_lua.m4 Thanks -- Eray

2 1

dovecot_config_version 2.4.2 -> error
by Genes Lists 30 Oct '25

30 Oct '25

Hi I would expect this to track the current version (i.e. 2.4.2) - would be good to accept 2.4.2 and later versions as they are released: doveconf line 9: Invalid dovecot_config_version: Currently supported versions are: 2.4.0 2.4.1 0.0.0 -- Gene

3 13

USER_PASSWORD environment variable
by Hendrik Friedel 30 Oct '25

30 Oct '25

Hello, can you tell me, where to find documentation on the USER_PASSWORD environment variable? I do not find how to specify more than one user. Thanks and best regards, Hendrik

2 1

lmtp server disconnects upon "RCPT TO" with internal error message
by rmfuhrer＠optonline.net 30 Oct '25

30 Oct '25

I've got a dovecot 2.4.1 instance (from the DockerHub official image) in a test Docker container on MacOS, running both IMAPS and LMTP. The IMAPS service is behaving normally, including the SSL negotiation, so I'm sure my cert (from LetsEncrypt) are kosher. I want to use fetchmail to deliver emails via LTMP, and fetchmail seems to connect to LMTP but doesn't succeed in delivering any emails. I tried the following experiment to manually craft an mail-delivery interaction with LMTP, but the connection suddenly closed right after the server sees the "RCPT TO", with an odd internal SSL error: $ openssl s_client -showcerts -connect 127.0.0.1:31024 ... <SSL negotiation diagnostics> ... Secure Renegotiation IS NOT supported ... 220 104b6de64916 Dovecot ready. LHLO test.mydomain.net 250-104b6de64916 250-8BITMIME 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-PIPELINING 250 SMTPUTF8 MAIL FROM:<someuser(a)somedomain.net> 250 2.1.0 OK RCPT TO:<myuser(a)mydomain.net> RENEGOTIATING 8204750656:error:1404C042:SSL routines:ST_OK:called a function you should not call:/AppleInternal/Library/BuildRoots/4ff29661-3588-11ef-9513-e2437461156c/Library/Caches/com.apple.xbs/Sources/libressl/libressl-3.3/ssl/ssl_lib.c:2435: $ Note that during SSL negotiation, the client notes that "Secure Renegotiation IS NOT supported". Not sure whether that's relevant, but I do see "RENEGOTIATING" just before the fatal (?) error. FWIW, the recipient "myuser(a)mydomain.net" really exists on the Dovecot server; I have a mail client that connects to the IMAP service and successfully authenticates as that user. The relevant LMTP portion of the Dovecot logs looks like this: Oct 29 14:02:38 lmtp(7270): Info: Connect from 192.168.65.1 Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x10, ret=1: before SSL initialization Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: before SSL initialization Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=-1: before SSL initialization Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: before SSL initialization Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: TLSv1.3 write encrypted extensions Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: TLSv1.3 write server certificate verify Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write finished Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=-1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=-1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=-1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=-1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: TLSv1.3 early data Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS read finished Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x20, ret=1: SSLv3/TLS write session ticket Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket Oct 29 14:02:38 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL: where=0x2002, ret=1: SSL negotiation finished successfully Oct 29 14:03:14 lmtp(7270): Debug: lmtp-server: conn 192.168.65.1:36620 [1]: SSL alert: close notify Oct 29 14:03:14 lmtp(7270): Info: Disconnect from 192.168.65.1: Connection closed (state=MAIL FROM) I've searched around and not found anything useful (in fact, hardly anything at all) about the above-cited error. Clues, anyone?

2 2

2.4.2: "make check" fails without json & lpeg Lua modules
by Thomas Zajic 29 Oct '25

29 Oct '25

Hi, Basically $SUBJECT. If you run "make check" after a successful build, it will fail unless you have the Lua modules "json" and "lpeg" installed. Not a huge problem, I got them from https://github.com/harningt/luajson and https://www.inf.puc-rio.br/~roberto/lpeg/, but as this sees to be a new thing with 2.4.2 I thought I'd give you a heads-up. HAND Thomas

1 0