- dovecot - dovecot.org

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