- dovecot - dovecot.org

Bash automation for Dovecot
by Travis Bean 21 Apr '25

21 Apr '25

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

1 0

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

18 Apr '25

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

1 1

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

17 Apr '25

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

1 0

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

17 Apr '25

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

3 7

config help with sieve_script
by Genes Lists 17 Apr '25

17 Apr '25

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

2 2

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

16 Apr '25

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

1 1

Question about dovecot quota calculation
by Zakaria 16 Apr '25

16 Apr '25

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

1 0

Question about quota calculation
by Zakaria 16 Apr '25

16 Apr '25

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

1 0

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

16 Apr '25

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

2 2

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

15 Apr '25

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

3 2