- dovecot - dovecot.org

dovecot RHEL 10 packages
by burnzerog＠gmail.com 19 Aug '25

19 Aug '25

Hi, I see only RHEL 8 and 9 packages but not for RHEL 10 in repo.dovecot.org. Do you think it can be released soon? Thank you.

3 2

quota_clone + dict_file_path wound up being somewhat cumbersome on 2.4
by Andy Baugh 19 Aug '25

19 Aug '25

The quota_clone syntax is rather cumbersome in comparison to 2.3 when using a flat file dictionary. I found I needed to make a "bogus" config block first: quota_clone { dict file { path = ${userdb:mail_path}/dovecot-quota } } Bogus, as the code path which actually deals with that doesn't have the ${userdb:*} vars available (visible by stracing the dovecot process, and seeing it fail to make /dovecotquota for obvious reasons). That said, if you don't include *some* value, it will explode even when you provide the *correct* value via userdb unless you initialize quota clone earlier there in the config. In this case for the 'luser' user: quota_clone/dict/file/path: /home/luser/mail/dovecot-quota wound up being the param I needed in order to get that logged in the right place for that specific user. None of how to format this properly was remotely clear to me from the documentation when looking at the quota_clone page: https://doc.dovecot.org/main/core/config/dict.html#flat-files As such I made an educated guess after reading the quota_clone code and testing a few things out. This actually works, so I'm happy with it for now. Not sure what this means RE the documentation, as even though it's not exactly obvious, I clearly was able to piece it together for the most part just by reading other documentation pages which mentioned things like separating namespaces by slashes, etc. I don't know how to properly convey "hey here's the list of where all these vars are actually able to be set and not set," as there's clearly some context there that's missing unless you go digging in the code. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV 713-384-8831 andy.baugh(a)webpros.com www.webpros.com

1 0

On Dovecot 2.4, auth-legacy setting for the auth service appears to be no-op when using lua passdb
by Andy Baugh 19 Aug '25

19 Aug '25

So, I used https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html#exim-auth… to ensure exim still worked. Unfortunately, that doesn't seem to be the case. Sender verification, auth, etc. *will* fail until you specifically start sending back those old params as well as the updated ones. I am using lua for the passdb/userdb however, so presumably it's just not documented that this is an "exercise for the reader" when using lua. In particular you need to deliver the 'mail' and 'quota' fields as they previously existed (colon separated) alongside the new dovecot params. Hope this helps someone else out there. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

2 2

'duplicate listener' on port 465
by William David Edwards 17 Aug '25

17 Aug '25

Hi, When configuring SMTPS as described on https://doc.dovecot.org/main/core/config/submission.html#smtps, Dovecot says there is a 'duplicate listener'. MRE: ``` root@dovecot24-test:/etc/dovecot/conf.d# doveconf -n # 2.4.1-4+debian12 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4+debian12 (0a86619f) # OS: Linux 6.1.0-29-amd64 x86_64 Debian 12.11 # Hostname: dovecot24-test.cyberfusion.nl # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 protocols = submission service submission-login { inet_listener submission_465 { port = 465 } } doveconf: Error: duplicate listener: 465:* doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: duplicate listener: 465:* ``` Can anyone help me understand why this listener would be 'duplicate'? This setup worked on 2.3.21.1. Thanks! William David Edwards

2 1

Supporting both "username" to username@domain.com
by Alex 15 Aug '25

15 Aug '25

Hi, I'm using dovecot-2.3.21 on fedora40 and have configured it to use only usernames without domain when logging in. Now apparently the new Outlook (1.2025.617.000) no longer supports the ability to change username for IMAP. Now what? We have other users who are using older versions of Outlook and Thunderbird and webmail that still support this login method. How can I support both? Here is my dovecot info. # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # OS: Linux 6.12.6-100.fc40.x86_64 x86_64 Fedora release 40 (Forty) btrfs auth_mechanisms = plain login default_client_limit = 3000 default_process_limit = 4000 default_vsz_limit = 1 G dict { sql = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 209.216.XXX.60, 127.0.0.1 mail_gid = users mail_location = maildir:/home/%u/Maildir mail_max_userip_connections = 100 mail_plugins = " listescape last_login" mail_privileged_group = mail 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 } plugin { last_login_dict = proxy::sql last_login_key = # hidden, use -P to show it last_login_precision = ms sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = pop3 imap lmtp service anvil { client_limit = 12003 } service auth-worker { client_limit = 20000 } service auth { client_limit = 20000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 20 service_count = 0 vsz_limit = 1 G } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_ca = </var/www/example.com-443/ssl/DigiCertCA-2022.crt ssl_cert = </var/www/example.com-443/ssl/example-combined-2025.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } local_name example.com { ssl_cert = </var/www/example.com-443/ssl/example-combined-2025.crt ssl_key = # hidden, use -P to show it } local_name users.example1.com { ssl_cert = </etc/letsencrypt/example1-fullchain.pem ssl_key = # hidden, use -P to show it } We're also using postfix to support this basic sasl username when sending. smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous Hi, I'm using dovecot-2.3.21 on fedora40 and have configured it to use only usernames without domain when logging in. Now apparently the new Outlook (1.2025.617.000) no longer supports the ability to change username for IMAP. Now what? We have other users who are using older versions of Outlook and Thunderbird and webmail that still support this login method. How can I support both? Here is my dovecot info. # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # OS: Linux 6.12.6-100.fc40.x86_64 x86_64 Fedora release 40 (Forty) btrfs auth_mechanisms = plain login default_client_limit = 3000 default_process_limit = 4000 default_vsz_limit = 1 G dict { sql = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 209.216.XXX.60, 127.0.0.1 mail_gid = users mail_location = maildir:/home/%u/Maildir mail_max_userip_connections = 100 mail_plugins = " listescape last_login" mail_privileged_group = mail 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 } plugin { last_login_dict = proxy::sql last_login_key = # hidden, use -P to show it last_login_precision = ms sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = pop3 imap lmtp service anvil { client_limit = 12003 } service auth-worker { client_limit = 20000 } service auth { client_limit = 20000 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 20 service_count = 0 vsz_limit = 1 G } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_ca = </var/www/example.com-443/ssl/DigiCertCA-2022.crt ssl_cert = </var/www/example.com-443/ssl/example-combined-2025.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } local_name [1]example.com { ssl_cert = </var/www/example.com-443/ssl/example-combined-2025.crt ssl_key = # hidden, use -P to show it } local_name [2]users.example1.com { ssl_cert = </etc/letsencrypt/example1-fullchain.pem ssl_key = # hidden, use -P to show it } We're also using postfix to support this basic sasl username when sending. smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname broken_sasl_auth_clients = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous References Visible links 1. http://example.com/ 2. http://users.example1.com/

9 12

github: minimal dovecot 2.4 setup for testing in docker
by Rory Campbell-Lange 15 Aug '25

15 Aug '25

Hi Everyone I've made a simple dovecot.conf and accompanying users.db file suitable for running in Docker. At the moment this simply shows how to force the default domain using the "auth_default_domain" setting. I'm hoping this will be a helpful jumping off point if you need to upgrade your Dovecot config ... and want to test outside of production. Instructions and the minimal conf and db file are here: https://github.com/rorycl/dovecot-config Feel free to improve the setup by submitting a PR. If you'd like to add some other scenarios please also submit PRs. My suggested arrangement for that is in a directory named by feature, with a README.md, minimal conf file, support files (only if necessary) and log.txt showing the expected output. Cheers Rory

1 0

doveadm sync issue
by Dan Whitehouse 15 Aug '25

15 Aug '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

1 0

Sieve Scripts via SQL Dicts in Dovecot 2.4 not working?
by Niklas Meyer 15 Aug '25

15 Aug '25

Hello everyone, I am currently working on porting the Dovecot 2.4 configuration from the latest 2.3 version. During this process, I encountered issues with the Sieve filters, particularly those related to SQL dict mappings. The previous (2.3) configuration looked like this and worked: |map { pattern = priv/sieve/name/$script_nametable = sieve_before username_field = username value_field = idfields { script_name = $script_name} } map { pattern = priv/sieve/data/$idtable = sieve_before username_field = username value_field = script_data fields { id= $id} } | This resulted in the following SQL queries on the MySQL server: |2025-08-1511:01:29.237511SELECTid FROMsieve_after WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'2025-08-1511:01:29.236416SELECTid FROMsieve_before WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'| As you can see, there are SQL mappings for |sieve_before| and |sieve_after|, alongside a local file loaded prior to the SQL settings, as they are user-based. In Dovecot 2.3, everything worked and the scripts were executed. In 2.4, however, they no longer run. I adapted the configuration for dict SQL mapping for Sieve filters according to the documentation: |dict_mappriv/sieve/name/$script_name{ sql_table= sieve_before username_field = username value_field id { } # The script name field in the table to querykey_fieldscript_name { value= $script_name} } dict_map priv/sieve/data/$id{ sql_table= sieve_before username_field = username value_field script_data { } key_fieldid { value= $id} } | This also results in the dict proxy querying the database with the same pattern as before: |2025-08-1511:11:47.175184SELECTid FROMsieve_after WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'2025-08-1511:11:47.172952SELECTid FROMsieve_before WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'2025-08-1511:11:47.155786SELECTid FROMsieve_after WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'2025-08-1511:11:47.136030SELECTid FROMsieve_before WHEREscript_name ='active'ANDusername ='frittenjonas(a)derlinkman.de'| However, unlike in 2.3, it now queries the DB twice. In the Sieve debug logs, I see the following: https://pastebin.com/PTKkLsDQ Notably: |Aug 1512:22:2443664c142e0a dovecot: lmtp(frittenjonas(a)derlinkman.de)<2407><mPFNN2AKn2hnCQAAhwrv7A>: Debug: Localdelivery failed: Temporarily unable toaccessnecessary Sieve scripts | This line concerns me. Here are the current Sieve script declarations: |sieve_script before{ type= beforedriver = file path= /var/vmail/sieve/global_sieve_before.sieve } sieve_script before2 { type= beforedriver = dict name= active dict proxy { name= sieve_before sieve_script_bin_path = /var/vmail/sieve_before_bindir } } sieve_script after{ type= afterdriver = file path= /var/vmail/sieve/global_sieve_after.sieve } sieve_script after2 { type= afterdriver = dict name= active dict proxy { name= sieve_after sieve_script_bin_path = /var/vmail/sieve_after_bindir } } # Personal scripts sieve_script personal { type= personal driver = file path= ~/sieve active_path = ~/.dovecot.sieve } | The dict proxy configuration, pointing to the dict_map SQL query above, looks like this: |dict sieve_after { driver = sql!include/etc/dovecot/sql/dovecot-dict-sql-sieve_after.conf } dict sieve_before { driver = sql!include/etc/dovecot/sql/dovecot-dict-sql-sieve_before.conf } | Thanks for your guidance. Kind regards Niklas Meyer Maintainer of the mailcow project Hello everyone, I am currently working on porting the Dovecot 2.4 configuration from the latest 2.3 version. During this process, I encountered issues with the Sieve filters, particularly those related to SQL dict mappings. The previous (2.3) configuration looked like this and worked: map { pattern = priv/sieve/name/$script_name table = sieve_before username_field = username value_field = id fields { script_name = $script_name } } map { pattern = priv/sieve/data/$id table = sieve_before username_field = username value_field = script_data fields { id = $id } } This resulted in the following SQL queries on the MySQL server: 2025-08-15 11:01:29.237511 SELECT id FROM sieve_after WHERE script_name = 'active' AND username = '[1]frittenjonas(a)derlinkman.de' 2025-08-15 11:01:29.236416 SELECT id FROM sieve_before WHERE script_name = 'active' AND username = '[2]frittenjonas(a)derlinkman.de' As you can see, there are SQL mappings for sieve_before and sieve_after, alongside a local file loaded prior to the SQL settings, as they are user-based. In Dovecot 2.3, everything worked and the scripts were executed. In 2.4, however, they no longer run. I adapted the configuration for dict SQL mapping for Sieve filters according to the documentation: dict_map priv/sieve/name/$script_name { sql_table = sieve_before username_field = username value_field id { } # The script name field in the table to query key_field script_name { value = $script_name } } dict_map priv/sieve/data/$id { sql_table = sieve_before username_field = username value_field script_data { } key_field id { value = $id } } This also results in the dict proxy querying the database with the same pattern as before: 2025-08-15 11:11:47.175184 SELECT id FROM sieve_after WHERE script_name = 'active' AND username = '[3]frittenjonas(a)derlinkman.de' 2025-08-15 11:11:47.172952 SELECT id FROM sieve_before WHERE script_name = 'active' AND username = '[4]frittenjonas(a)derlinkman.de' 2025-08-15 11:11:47.155786 SELECT id FROM sieve_after WHERE script_name = 'active' AND username = '[5]frittenjonas(a)derlinkman.de' 2025-08-15 11:11:47.136030 SELECT id FROM sieve_before WHERE script_name = 'active' AND username = '[6]frittenjonas(a)derlinkman.de' However, unlike in 2.3, it now queries the DB twice. In the Sieve debug logs, I see the following: [7]https://pastebin.com/PTKkLsDQ Notably: Aug 15 12:22:24 43664c142e0a dovecot: lmtp([8]frittenjonas(a)derlinkman.de)<2407><mPFNN2AKn2hnCQAAhwrv7A>: Debug: Local delivery failed: Temporarily unable to access necessary Sieve scripts This line concerns me. Here are the current Sieve script declarations: sieve_script before { type = before driver = file path = /var/vmail/sieve/global_sieve_before.sieve } sieve_script before2 { type = before driver = dict name = active dict proxy { name = sieve_before sieve_script_bin_path = /var/vmail/sieve_before_bindir } } sieve_script after { type = after driver = file path = /var/vmail/sieve/global_sieve_after.sieve } sieve_script after2 { type = after driver = dict name = active dict proxy { name = sieve_after sieve_script_bin_path = /var/vmail/sieve_after_bindir } } # Personal scripts sieve_script personal { type = personal driver = file path = ~/sieve active_path = ~/.dovecot.sieve } The dict proxy configuration, pointing to the dict_map SQL query above, looks like this: dict sieve_after { driver = sql !include /etc/dovecot/sql/dovecot-dict-sql-sieve_after.conf } dict sieve_before { driver = sql !include /etc/dovecot/sql/dovecot-dict-sql-sieve_before.conf } Thanks for your guidance. Kind regards Niklas Meyer Maintainer of the mailcow project References Visible links 1. mailto:frittenjonas@derlinkman.de 2. mailto:frittenjonas@derlinkman.de 3. mailto:frittenjonas@derlinkman.de 4. mailto:frittenjonas@derlinkman.de 5. mailto:frittenjonas@derlinkman.de 6. mailto:frittenjonas@derlinkman.de 7. https://pastebin.com/PTKkLsDQ 8. mailto:frittenjonas@derlinkman.de

1 0

Lots of problems with Dovecot 2.4
by sev+dovecot＠sev.monster 14 Aug '25

14 Aug '25

Hello all, I am trying to get Dovecot 2.4 running on Alpine Edge x86-64. But a myriad of problems have occurred that make it impossible to do so. First of all was the recent off-by-one bug that was recently fixed, which caused an unavoidable segfault on start under musl libc, which Alpine uses: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17050 Then, I saw that the shadow driver was removed, which necessitated the installation of PAM and my learning about it... I haven't needed it before, so I'd never used it. I guess I understand why the decision was made to use PAM, though I still don't like it. After resolving those issue, I've run into new ones: 1. The passwd userdb does not seem to work correctly. It is able to get the first user and its information correctly, but any attempts to look up any user after that will seemingly always use the information from the first matched user. Setting max auths to 1 so that the auth process is discarded afterwards does not seem to help. For example, if the first user to log in to Dovecot is bob, and then user joe logs in, the information returned from the passwd userdb will all be that of user bob, not joe. This continues for all subsequent userdb lookups until Dovecot is restarted, and a new userdb lookup is persisted. Changing to passwd-file instead works and does not experience this problem. 2. Why is the only available username field for the passwd driver %{passwd:system_groups_user}? I understand what the purpose of the field is based on the docs, but shouldn't more than this be exposed? The fields available through passwd are also not documented, and I had to read the source to find them out. This should either be documented or a more standard username field be additionally exposed as with other drivers. Can this field even be relied on to use as the username, if the driver otherwise worked? 3. It seems the Exim auth driver is no longer able to successfully authenticate with Dovecot 2.4 against Exim 4.98.2. It works fine in the last version of 2.3.21.1. Has the authentication framework changed along with the other modifications that 2.4 underwent? Has any effort been made with the Exim team to resolve any incompatibilities? Can I somehow diagnose this issue if it's otherwise supposed to work? 4. The ldap driver can no longer look up missing fields from LDAP users. Some (but not all) of my users have the rfc2307bis schema posixAccount supplemental objectClass, and as such contain the posixHome, uidNumber, and gidNumber attributes—but even if I specify a default value, if one of the attributes is not queryable for the returned user, the lookup errors out and the login fails. This is a regression/undocumented change from 2.3.x, where instead of erroring out, the default_fields value would be used. Based on my interpretation of the design goals for 2.4, I would imagine the default filter would ignore the missing attribute error and set the default value like default_fields used to, no? Or am I missing something? 5. passdb_ldap_filter is always required for the ldap passdb driver, even if passdb_ldap_bind is enabled. Not only does this go against the docs, but the value is unused and it doesn't matter what it's set to. This is a regression from 2.3.x. Overall I am very unimpressed by 2.4. It clearly needed a lot more time in the oven and much more thorough testing. Relevant minimal config from my working 2.3.21.1 install: auth_username_format = %Ln auth_mechanisms = plain login passdb { driver = shadow } userdb { driver = passwd override_fields = gid=mail home=/var/mail/%Ln } passdb { driver = ldap args = /etc/dovecot/ldap-passdb.conf.ext #uris = ldapi://%2frun%2fopenldap%2fslapd.sock #base = ou=accounts,dc=ldap #auth_bind = yes #auth_bind_userdn = uid=%Ln,ou=accounts,dc=ldap } userdb { driver = ldap default_fields = uid=mail gid=mail home=/var/mail/%Ln args = /etc/dovecot/ldap-userdb.conf.ext #uris = ldapi://%2frun%2fopenldap%2fslapd.sock #dn = cn=dovecot,dc=ldap #dnpass = "some pw" #base = ou=accounts,dc=ldap #iterate_filter = (objectClass=inetOrgPerson) #iterate_attrs = uid=username #user_filter = (&(objectClass=inetOrgPerson)(uid=%Ln)) #user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid } mail_location = maildir:/var/mail/%Ln mail_plugins = $mail_plugins virtual namespace inbox { inbox = yes mailbox INBOX { auto = subscribe } } namespace virtual { type = private separator = . prefix = "Search Folders." location = virtual:/etc/dovecot/virtual:INDEX=~/dovecot-virtual.cache:CONTROL=~/dovecot-virtual.cache:VOLATILEDIR=~/dovecot-virtual.cache # virtual/All/dovecot-virtual: #!INBOX #* #-Junk #-Junk* #-Spam #-Spam* #-Trash #-Trash* #-Deleted #-Deleted* #-Deleted Items #-Deleted Items* # all hidden = yes list = children subscriptions = no mailbox All { auto = subscribe special_use = \All comment = All messages, excluding Junk and Trash } } namespace virtual-user { type = private separator = . prefix = "User Search Folders." location = virtual:~/.virtual:INDEX=~/dovecot-virtual-user.cache:CONTROL=~/dovecot-virtual-user.cache:VOLATILEDIR=~/dovecot-virtual-user.cache:LAYOUT=maildir++ hidden = yes list = children subscriptions = no } service auth { unix_listener auth-userdb { # restrict userdb to dovecot user/group only instead of world read/write mode = 0660 user = $default_internal_user group = $default_internal_group } unix_listener auth-client { # give Exim access to native authentication mode = 0660 group = exim } } service auth-worker { # no need to run as root user = $default_internal_user # allow pam passdb to read /etc/shadow group = shadow } !include_try /usr/share/dovecot/protocols.d/*.conf protocol imap { mail_max_userip_connections = 25 } protocol pop3 { mail_max_userip_connections = 25 } Converted config for 2.4: dovecot_config_version = 2.4.1 dovecot_storage_version = 2.4.1 mail_home = /var/mail/%{user | username | lower } mail_driver = maildir mail_path = $SET:mail_home mail_plugins = virtual auth_username_format = %{user | username | lower } auth_mechanisms = plain login passdb pam { failure_show_msg = yes max_requests = 1 } userdb passwd-file { passwd_file_path = /etc/passwd fields { gid = mail } } # BUG: doesn't work right #userdb passwd { # fields { # gid = mail # } #} passdb ldap { ldap_uris = ldapi://%2frun%2fopenldap%2fslapd.sock ldap_connection_group = login ldap_base = ou=accounts,dc=ldap ldap_bind = yes ldap_bind_userdn = uid=%{user | username | lower },ou=accounts,dc=ldap # XXX: thought this wasnt needed with bind? ldap_filter = z } userdb ldap { ldap_uris = ldapi://%2frun%2fopenldap%2fslapd.sock ldap_auth_dn = cn=dovecot,dc=ldap ldap_auth_dn_password = "some pw" ldap_base = ou=accounts,dc=ldap ldap_filter = (&(objectClass=inetOrgPerson)(uid=%{user | username | lower })) fields { username = %{ldap:uid} # BUG: causes errors if rfc2307bis posixAccount objectClass is not set home = %{ldap:homeDirectory | default($SET:mail_home)} uid = %{ldap:uidNumber | default(mail)} gid = %{ldap:gidNumber | default(mail)} } ldap_iterate_filter = (objectClass=inetOrgPerson) iterate_fields { username = %{ldap:uid} } } namespace inbox { inbox = yes mailbox INBOX { auto = subscribe } } namespace virtual { type = private separator = . prefix = "Search Folders." mail_driver = virtual mail_path = /etc/dovecot/virtual # virtual/All/dovecot-virtual: #!INBOX #* #-Junk #-Junk* #-Spam #-Spam* #-Trash #-Trash* #-Deleted #-Deleted* #-Deleted Items #-Deleted Items* # all mail_index_path = ~/dovecot-virtual.cache mail_control_path = ~/dovecot-virtual.cache mail_volatile_path = ~/dovecot-virtual.cache hidden = yes list = children subscriptions = no mailbox All { auto = subscribe special_use = \All comment = All messages, excluding Junk and Trash } } namespace virtual-user { type = private separator = . prefix = "User Search Folders." mail_driver = virtual mail_path = ~/dovecot-virtual-user mail_index_path = ~/dovecot-virtual-user.cache mail_control_path = ~/dovecot-virtual-user.cache mail_volatile_path = ~/dovecot-virtual-user.cache mailbox_list_layout = Maildir++ hidden = yes list = children subscriptions = no } service auth { unix_listener auth-userdb { # restrict userdb to dovecot user/group only instead of world read/write mode = 0660 } unix_listener auth-client { # give Exim access to native authentication mode = 0660 group = exim } } service auth-worker { # no need to run as root user = $SET:default_internal_user # allow pam passdb to read /etc/shadow group = shadow } protocols = imap pop3 protocol imap { mail_max_userip_connections = 25 } protocol pop3 { mail_max_userip_connections = 25 } In addition to help with the noted issues, I'd also love if anyone more knowledgeable on Dovecot 2.4 could give any pointers on my config and if I could improve the translation in any way, given I have been fumbling around with it for weeks and am not really sure if my various decisions are correct. Best regards.

7 8

function 'dovecot_lua_notify_event_message_new' in my lua script when I use push_notification_lua_driver
by 3825634＠qq.com 14 Aug '25

14 Aug '25

I need to push a message notification to external system when they receive new emails from their mailbox，so I used the push_notification_lua plugin. My dovecot configuration file is as follows： plugin {     ....     push_notification_driver = dlog     push_notification_driver2 = lua:file=/etc/dovecot/custom-lua/push-notification.lua     push_lua_url = http://localhost:10421/internal/dovecot/email-notification/receive } protocol lda {     mail_plugins = $mail_plugins sieve last_login push_notification mail_lua push_notification_lua     .... } ============= I print the 'event' param's value log in function 'dovecot_lua_notify_event_message_new' in my lua script: function dovecot_lua_notify_event_message_new(ctx, event)   dovecot.i_info("lua-push: event=" .. cjson.encode(event)) end However, when I send a mail with multiple recivers, the notification event info seems to work abnormally. Sender: wangzx(a)hxtmailtest.avicnet.cn Receivers: zhaoqb(a)hxtmailtest.avicnet.cn , wangzx7110(a)hxtmailtest.avicnet.cn I found the two event object's field 'to_address' and 'to_display_name' value are same in /var/log/dovecot/lda.log. Please help me confirm if this is a bug? The log in /var/log/dovecot/lda.log like bellow: 2025-08-06T09:38:11.383536+08:00 hxtmailtest-server dovecot: lda(wangzx7110(a)hxtmailtest.avicnet.cn)<548522><EkAeFgOykmiqXggAfhwsfQ>: lua-push: event={"snippet":"test!!","date":1754444290,"keywords":{},"to_display_name":"Zhaoqb","uid":19,"subject":"test","from_display_name":"","to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","tz":480,"mailbox":"INBOX","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","from":"wangzx(a)hxtmailtest.avicnet.cn","message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>","uid_validity":1752827738,"flags":{},"from_address":"wangzx(a)hxtmailtest.avicnet.cn","name":"MessageNew"} 2025-08-06T09:38:11.423272+08:00 hxtmailtest-server dovecot: lda(zhaoqb(a)hxtmailtest.avicnet.cn)<548524><znZfFwOykmisXggAfhwsfQ>: lua-push: event={"subject":"test","mailbox":"INBOX","flags":{},"snippet":"test!!","from":"wangzx(a)hxtmailtest.avicnet.cn","date":1754444290,"from_address":"wangzx(a)hxtmailtest.avicnet.cn","keywords":{},"uid_validity":1752634929,"to_display_name":"Zhaoqb","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","name":"MessageNew","from_display_name":"","tz":480,"to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","uid":39,"message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>"} Thanks! 3825634(a)qq.com 3825634(a)qq.com I need to push a message notification to external system when they receive new emails from their mailbox**so I used the push_notification_lua plugin. My dovecot configuration file is as follows** plugin { .... push_notification_driver = dlog push_notification_driver2 = lua:file=/etc/dovecot/custom-lua/push-notification.lua push_lua_url = http://localhost:10421/internal/dovecot/email-notification/receive } protocol lda { mail_plugins = $mail_plugins sieve last_login push_notification mail_lua push_notification_lua .... } ============= I print the 'event' param's value log in function 'dovecot_lua_notify_event_message_new' in my lua script: function dovecot_lua_notify_event_message_new(ctx, event) dovecot.i_info("lua-push: event=" .. cjson.encode(event)) end However, when I send a mail with multiple recivers, the notification event info seems to work abnormally. Sender: wangzx(a)hxtmailtest.avicnet.cn Receivers: zhaoqb(a)hxtmailtest.avicnet.cn , wangzx7110(a)hxtmailtest.avicnet.cn I found the two event object's field 'to_address' and 'to_display_name' value are same in /var/log/dovecot/lda.log. Please help me confirm if this is a bug? The log in /var/log/dovecot/lda.log like bellow: 2025-08-06T09:38:11.383536+08:00 hxtmailtest-server dovecot: lda(wangzx7110(a)hxtmailtest.avicnet.cn)<548522><EkAeFgOykmiqXggAfhwsfQ>: lua-push: event={"snippet":"test!!","date":1754444290,"keywords":{},"to_display_name":"Zhaoqb","uid":19,"subject":"test","from_display_name":"","to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","tz":480,"mailbox":"INBOX","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","from":"wangzx(a)hxtmailtest.avicnet.cn","message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>","uid_validity":1752827738,"flags":{},"from_address":"wangzx(a)hxtmailtest.avicnet.cn","name":"MessageNew"} 2025-08-06T09:38:11.423272+08:00 hxtmailtest-server dovecot: lda(zhaoqb(a)hxtmailtest.avicnet.cn)<548524><znZfFwOykmisXggAfhwsfQ>: lua-push: event={"subject":"test","mailbox":"INBOX","flags":{},"snippet":"test!!","from":"wangzx(a)hxtmailtest.avicnet.cn","date":1754444290,"from_address":"wangzx(a)hxtmailtest.avicnet.cn","keywords":{},"uid_validity":1752634929,"to_display_name":"Zhaoqb","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","name":"MessageNew","from_display_name":"","tz":480,"to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","uid":39,"message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>"} Thanks! [1][IMG] [2]3825634(a)qq.com 3825634(a)qq.com References Visible links 1. https://wx.mail.qq.com/home/index?t=readmail_businesscard_midpage&nocheck=t… 2. https://wx.mail.qq.com/home/index?t=readmail_businesscard_midpage&nocheck=t…

2 4