- dovecot - dovecot.org

Dovecot 2.4.0 local_name wildcard matching regression
by Julius Kriukas 19 Mar '25

19 Mar '25

Hi, Using a wildcard host name in the `local_name` filter no longer works in Dovecot 2.4.0. This is useful for wildcard certificates. Example `dovecot.conf`: ``` ssl_server_cert_file = /etc/dovecot/global.cert ssl_server_key_file = /etc/dovecot/global.key ssl_server_dh_file = /etc/dovecot/dh.pem ... local_name "*.example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } local_name "example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } ``` The configuration is tested with: ``` openssl s_client -connect mail.example.com:993 openssl s_client -connect example.com:993 ``` The first connection to mail.example.com fails because Dovecot uses the default `global.cert` file. The second test with the exact host name match works as expected. Dovecot uses the `example.com.cert` file. Similar to the previously reported multiple hosts on the same line discrepancy, it seems that the `doveconf` tool still has the wildcard matching support: ``` # doveconf -f local_name=mail.example.com ssl_server ssl_server { cert_file = /etc/dovecot/example.com.cert dh_file = /etc/dovecot/dh.pem key_file = /etc/dovecot/example.com.key } ``` Is there a new way to achieve the wildcard matching behaviour of the local_name filter in Dovecot 2.4.0? Thanks. -- Julius Kriukas

3 3

LDAP quota is ignored
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded from dovecot 2.3.x to 2.4.0. I converted the configuration files and all is ok, but there is this strange thing about quota. I have quota limit from LDAP: quota_storage_size = %{ldap:quota}G Value is correctly retrieved from LDAP, with "doveadm user user@domain": quota_storage_size 10G In configuration files of dovecot I have nothing about quota definitions. If I check in webmail I have undefined value. If I set manually in configuration files: quota "User quota" { storage_size = 1G } quota is correctly shown in webmail, but only with this default value. It appears it ignores values from ldap userdb. How can I debug this? Thanks.

2 2

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

2 3

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 18 Mar '25

18 Mar '25

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

1 0

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

1 0

Help: Configuration example conversion from 2.3 to 2.4 ?
by ollie＠ik.me 17 Mar '25

17 Mar '25

Hello ! Like many people who are posting here, I'm a bit in "trouble" to convert my actual v2.3 config that is perfectly functional to the new v2.4 I've read the doc, searched on this list and everywhere I could find something among search engine results, and I still can't figure out how to solve my problem. The lack of examples right now is probably what is blocking me, so.. can anyone here with sharp knowledge of v2.4 configuration "translate" this official v2.3 example into a working v2.4 example ? ( ref: https://doc.dovecot.org/2.3/configuration_manual/quota/quota_dict/ ) Server-based Dictionaries -------------------------------------- plugin { # SQL backend: quota = dict:User quota::proxy::sqlquota # Redis backend (v2.1.9+): quota = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota_rule = *:storage=10M:messages=1000 } dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } ============================ Example dovecot-dict-sql.conf.ext: -------------------------------------------------- connect = host=localhost dbname=mails user=sqluser password=sqlpass map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } Thanks a million times to whoever can do that ! :) Lon.

2 2

RFC header to plain address(es)
by Jochen Bern 15 Mar '25

15 Mar '25

This has got to be one of the most stupid questions I've ever asked online ... I have a need of a "helper function" that takes a string someone would "want to send an e-mail to", i.e., something like an RFC 5322 "address" token, as used in a "To:" header, and extract just the actual e-mail address(es) from it. (The capability to deal with lists of *several* recipients is likely optional.) I found a certain number of *libraries* for various programming languages that offer such a functionality¹, but I would prefer an executable from some run-of-the-mill Linux/UNIX package to be called by shell command. Considering that pretty much every MTA and MUA must contain such functionality (to construct an SMTP envelope for a mail to be sent), and then some (I looked into, e.g., procmail), I'm surprised that apparently none of them *expose* it. (I seem to remember that the original "sendmail -bt" came somewhat close at least ...) Does anyone have an idea what tool I could (ab)use for that purpose? ¹ Namely: -- parseaddr() for python https://documentation.help/Python-PEP/module-email.Utils.html -- maildrop for C https://www.courier-mta.org/maildrop/rfc822.html -- mail_parser for Rust https://docs.rs/mail-parser/latest/mail_parser/ -- address-rfc2822 for JavaScript https://www.npmjs.com/package/address-rfc2822 -- mailparse-rfc822-parse-addresses for PHP https://www.php.net/manual/en/function.mailparse-rfc822-parse-addresses.php -- mail-header-parse-address for LISP https://www.gnu.org/software/emacs/manual/html_node/emacs-mime/Interface-Fu… -- and I suppose you could try to stuff the syntax definition into some parser code generator, too https://www.rfc-editor.org/rfc/rfc5322#section-3.4 Thanks in advance, -- Jochen Bern Systemingenieur Binect GmbH

2 1

Build error without ldap support
by Lafiel 14 Mar '25

14 Mar '25

Hi. Cannot build Dovecot without LDAP support. Configure flags: --with-ldap=no Error: In file included from db-ldap-settings.c:9: ../../src/lib-ldap/ldap-settings-parse.h:4:10: fatal error: ldap.h: No such file or directory 4 | #include <ldap.h> | ^~~~~~~~ compilation terminated. make[3]: *** [Makefile:2138: auth-db-ldap-settings.o] Error 1 Dovecot version: 2.4.0 -- Best regards, Lafiel mailto:lafiel@elven.pw

3 4

Instructions for upgrading to a newer version returns 404
by Jose Celestino 14 Mar '25

14 Mar '25

Hi, https://doc.dovecot.org/2.4.0/installation/upgrading.html returns a 404. Best regards, José Celestino

3 2

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 13 Mar '25

13 Mar '25

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

1 0