February 2025 - dovecot

auth_userdb_iterate
by Luigi Trovato 19 Feb '25

19 Feb '25

Hello, I have a doubt: is the lua function "auth_userdb_iterate" expected to always return the whole list of users no matter what, or it should evaluate if a specific virtual domain is provided as req argument and only list the users in that specific domain? And should the returned user list be in the format "username(a)domain.tld" or "username" ? -- Ciao, Luigi

1 1

lua API and returning reason and CONTACTADMIN
by Arkadiusz Miśkiewicz 19 Feb '25

19 Feb '25

Hello. Trying to pass reason response via lua by passing it at dovecot.auth.PASSDB_RESULT_USER_DISABLED like: function auth_password_verify(request, password) return dovecot.auth.PASSDB_RESULT_USER_DISABLED, "reason=custom_message" end function auth_userdb_lookup(request) return dovecot.auth.PASSDB_RESULT_OK, "uid=428671 gid=9726 home=/var/mail/existusertest" end function script_init() return 0 end function script_deinit() end Unfortunately returned result contains no custom message and also returns AUTHENTICATIONFAILED instead of CONTACTADMIN: NO [AUTHENTICATIONFAILED] Authentication failed. while I would expect something like: NO [CONTACTADMIN] custom_message: Any reason for such behaviour and how to get reason passed and proper CONTACTADMIN? Tests done on 2.3.21.1. passdb { driver = lua mechanisms = login plain args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } userdb { driver = lua args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 6

Can someone explain this to me, please?
by Ken Wright 19 Feb '25

19 Feb '25

The last time I checked my mail.log I found the following line: 2025-02-18T22:41:31.175798-05:00 grace dovecot: imap-login: Login aborted: Connection closed (auth failed, 1 attempts in 8 secs) (auth_failed): user=<wizard(a)koalatyworks.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<wTMBiHYu5pXAqAEB> Is this a password error or something more? Ken

2 1

Doveadm Backup
by Doug Hardie 18 Feb '25

18 Feb '25

I tried the backup again tonight. I am now getting a new error: mail# doveadm backup -f -u doug remote:checkout dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Warning: Deleting mailbox 'INBOX': UID=92440 GUID=1465118975.V4eI7cfa32M232845.mail is missing locally dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Error: Couldn't delete mailbox INBOX: INBOX can't be deleted. dsync-local(doug)<N0q9NI0xtGf4vgAAZU03Dg>: Error: Remote command returned error 65: ssh checkout doveadm dsync-server -udoug -U Anytime I run it now generates the same error messages. However on the backup machine the .cur directory is empty. I presume that is the INBOX referred to in the messages. All the other directories appear to be intact. -- Doug

2 3

2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'
by Bjoern Franke 18 Feb '25

18 Feb '25

Hi, I have the following (manage)sieve-related parts in my 2.4.0 config: within the namespace inbox: mailbox Junk { auto = subscribe autoexpunge = 14d sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.sieve } special_use { "\Junk" = yes } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } sieve_script personal { active_path = /data/mail/%{user}/dovecot.sieve driver = file path = /data/mail/%{user}/sieve } Accessing via managesieve fails: Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' But the sieve rules in general work. Regards Bjoern

2 2

Re: Userdb lookup problems
by Ken Wright 18 Feb '25

18 Feb '25

On Mon, 2025-02-17 at 15:49 +0200, Timo Sirainen wrote: > On 16. Feb 2025, at 17.03, Ken Wright via dovecot > <dovecot(a)dovecot.org> wrote: > > mysql localhost { > > user = something > > password = MYPASSWORD > > dbname = something > > } > .. > > According to the logs, Dovecot isn't trying to connect using the > > user > > something, it's using the user dovecot. That's not the user for > > the > > database. > > The default mysql user is empty, not "dovecot". So it must be getting > "dovecot" user from somewhere in your config. Look at your "doveconf" > output - maybe the mysql_user gets overridden in some other config > file. Things to look at: > > doveconf mysql > doveconf | grep mysql > doveconf I went through every file in conf.d trying to find a mention of dovecot with no positive results. Then I tried the three things to look at you suggested, and got this: doveconf mysql: mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } doveconf | grep mysql: sql_driver = mysql mysql localhost { doveconf: # 2.4.0-2+ubuntu24.04 (daeb6bc59c): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0-2+ubuntu24.04 (1b2d5bb9) # OS: Linux 6.8.0-53-generic x86_64 Ubuntu 24.04.2 LTS ext4 # Hostname: localhost dovecot_config_version = 2.4.0 auth_mechanisms = auth_mechanisms { plain = yes login = yes } dovecot_storage_version = 2.4.0 mail_driver = maildir mail_gid = vmail mail_inbox_path = /var/vmail/%{user | domain}/%{user | username } mail_path = /var/vmail/%{user | domain }/%{user | username }/Maildir mail_uid = vmail mailbox_list_utf8 = yes passdb_default_password_scheme = ARGON2I protocols = protocols { imap = yes lmtp = yes sieve = yes } sql_driver = mysql ssl = required ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem prefer_ciphers = server } namespace inbox { mailbox Drafts { auto = create special_use = special_use { "\\Drafts" = yes } } mailbox Junk { auto = create special_use = special_use { "\\Junk" = yes } } mailbox Trash { auto = create special_use = special_use { "\\Trash" = yes } } mailbox Sent { auto = create special_use = special_use { "\\Sent" = yes } } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } passdb sql { query = SELECT username AS username, domain, password FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } userdb sql { iterate_query = SELECT username AS username, domain FROM mailbox query = SELECT mail_path, uid, gid FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } local 127.0.0.1 { local_name mailserver.example1.com { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem } } } local_name mail.example2.net { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mail.example2.net/fullchain.pem key_file = /etc/letsencrypt/live/mail.example2.net/privkey.pem } } } } I can't find anything indicating a database user 'dovecot.' Would you like to see the results of tail /var/log/mail.log? Ken On Mon, 2025-02-17 at 15:49 +0200, Timo Sirainen wrote: On 16. Feb 2025, at 17.03, Ken Wright via dovecot <dovecot(a)dovecot.org> wrote: mysql localhost { user = something password = MYPASSWORD dbname = something } .. According to the logs, Dovecot isn't trying to connect using the user something, it's using the user dovecot. That's not the user for the database. The default mysql user is empty, not "dovecot". So it must be getting "dovecot" user from somewhere in your config. Look at your "doveconf" output - maybe the mysql_user gets overridden in some other config file. Things to look at: doveconf mysql doveconf | grep mysql doveconf I went through every file in conf.d trying to find a mention of dovecot with no positive results. Then I tried the three things to look at you suggested, and got this: doveconf mysql: mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } doveconf | grep mysql: sql_driver = mysql mysql localhost { doveconf: # 2.4.0-2+ubuntu24.04 (daeb6bc59c): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0-2+ubuntu24.04 (1b2d5bb9) # OS: Linux 6.8.0-53-generic x86_64 Ubuntu 24.04.2 LTS ext4 # Hostname: localhost dovecot_config_version = 2.4.0 auth_mechanisms = auth_mechanisms { plain = yes login = yes } dovecot_storage_version = 2.4.0 mail_driver = maildir mail_gid = vmail mail_inbox_path = /var/vmail/%{user | domain}/%{user | username } mail_path = /var/vmail/%{user | domain }/%{user | username }/Maildir mail_uid = vmail mailbox_list_utf8 = yes passdb_default_password_scheme = ARGON2I protocols = protocols { imap = yes lmtp = yes sieve = yes } sql_driver = mysql ssl = required ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem prefer_ciphers = server } namespace inbox { mailbox Drafts { auto = create special_use = special_use { "\\Drafts" = yes } } mailbox Junk { auto = create special_use = special_use { "\\Junk" = yes } } mailbox Trash { auto = create special_use = special_use { "\\Trash" = yes } } mailbox Sent { auto = create special_use = special_use { "\\Sent" = yes } } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } passdb sql { query = SELECT username AS username, domain, password FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } userdb sql { iterate_query = SELECT username AS username, domain FROM mailbox query = SELECT mail_path, uid, gid FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } local 127.0.0.1 { local_name mailserver.example1.com { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem } } } local_name mail.example2.net { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mail.example2.net/fullchain.pem key_file = /etc/letsencrypt/live/mail.example2.net/privkey.pem } } } } I can't find anything indicating a database user 'dovecot.' Would you like to see the results of tail /var/log/mail.log? Ken

1 0

Doveadm Backup
by Doug Hardie 18 Feb '25

18 Feb '25

I am using doveadm backup to backup the mail server's files for a specific user. This is a test environment for the backup machine. All it does is sit there until I run backup on the mail server. However, I am encountering an issue occasionally where backup throws the following message: Warning: Deleting mailbox 'Deleted Messages': UID=533920 already exists locally for a different mail: GUIDs don't match (1739791386.M526904P56414.checkout,S=2206,W=2264 vs 1739674845.M569094P6598.mail,S=6530202,W=6615064) At this point it stops and the indicated mailbox has been deleted. It is not always the same mailbox. I then have to run the backup again and wait for it to download the entire directory which takes a long time. I was hoping to use this approach for a frequently run backup, but it appears it is not feasible. Some mailboxes are large enough that a second backup would be initiated before the complete reload had completed. Can this be corrected? -- Doug

1 0

Question about push notification plugin
by Zakaria 17 Feb '25

17 Feb '25

Hi Dovecot Mailing List members, I just struggled to understand the plugin events and wondered if anyone can help on this. I wanted to capture the event when I mark message as not spam move event as well as when I move message to new folder event, I found MessageNew and MessageAppend, and couldnt figure out which one is responsible of the relevant event? Also, feedback to the dovecot dev team, it would great if we have push notification redis driver. Thanks in advance. Zakaria.

2 2

Re: Doveadm Backup Error
by Asai 17 Feb '25

17 Feb '25

Thank you, Timo, that fixed the problem. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: > On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: >> >> sieve_script personal { >> active_path = /vmail/%{user | domain }/%{user | username >> }/home/.dovecot.sieve >> driver = file >> path = /vmail/%{user | domain }/%{user | username }/home/sieve >> } > > Looks like %variables aren't really working right with Sieve / doveadm > combination. It gives an error: > > Error: sieve: sieve_file_storage settings: Failed to parse > configuration: Failed to expand sieve_script_path setting variables: > Unknown variable 'user' > > So for now the only way is to avoid %variables there - that simplifies > the config anyway: > > sieve_script personal { > active_path = ~/.dovecot.sieve > path = ~/sieve > } > Thank you, Timo, that fixed the problem. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: sieve_script personal { active_path = /vmail/%{user | domain }/%{user | username }/ home/.dovecot.sieve driver = file path = /vmail/%{user | domain }/%{user | username }/home/sieve } Looks like %variables aren't really working right with Sieve / doveadm combination. It gives an error: Error: sieve: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' So for now the only way is to avoid %variables there - that simplifies the config anyway: sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve }

1 0

Re: Doveadm Backup Error
by Asai 17 Feb '25

17 Feb '25

Thanks Timo, OK, I'll give that a try, I should point out that the Sieve filters are working as they should be for general delivery, outside of doveadm backup. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: > On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: >> >> sieve_script personal { >> active_path = /vmail/%{user | domain }/%{user | username >> }/home/.dovecot.sieve >> driver = file >> path = /vmail/%{user | domain }/%{user | username }/home/sieve >> } > > Looks like %variables aren't really working right with Sieve / doveadm > combination. It gives an error: > > Error: sieve: sieve_file_storage settings: Failed to parse > configuration: Failed to expand sieve_script_path setting variables: > Unknown variable 'user' > > So for now the only way is to avoid %variables there - that simplifies > the config anyway: > > sieve_script personal { > active_path = ~/.dovecot.sieve > path = ~/sieve > } > Thanks Timo, OK, I'll give that a try, I should point out that the Sieve filters are working as they should be for general delivery, outside of doveadm backup. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: sieve_script personal { active_path = /vmail/%{user | domain }/%{user | username }/ home/.dovecot.sieve driver = file path = /vmail/%{user | domain }/%{user | username }/home/sieve } Looks like %variables aren't really working right with Sieve / doveadm combination. It gives an error: Error: sieve: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' So for now the only way is to avoid %variables there - that simplifies the config anyway: sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve }

1 0