- dovecot - dovecot.org

Verifying LDAP configuration from command line ?
by BuzzSaw Code 14 Jun '25

14 Jun '25

Dovecot version : 2.3.x - using RedHat build Years ago I had a Dovecot install that was setup to perform certificate based authentication for clients that worked well - part of that setup was creating a passdb that pointed to a flat file that contained entries like this: cool.joe.c:{PLAIN}::::::username=cooljc and the passdb definition looked like this: passdb { driver = passwd-file args = scheme=plain /etc/dovecot/users.external skip = authenticated mechanisms = EXTERNAL default_fields = uid=vmail gid=vmail nopassword=1 } That worked and we had a cron job that would build that users.external file and keep it up to date. Now, a few years down the road, I've setup a new Dovecot server that is working wonderfully but I'd like to add the same functionality but also use a direct LDAP query instead of managing a flat file to maintain the list of users. I have another passdb entry that is using LDAP that works great for username/password auth, but I'd like to test what I think is a proper LDAP configuration specific for this passdb, But for the life of me I can't find out how to test the configuration file without having to actually update my dovecot configuration to use it. I'm looking for something like the Postfix 'postmap' tool that I can provide my configuration file for the LDAP lookup, give a username input to and it will show me the results from the configuration, including the return values. Is there such a tool ? Or do I have to setup a test server, add it to the config, and debug it ? Sorry if this is FAQ or dumb question - I've been reading documentation on the official Dovecot site looking for the answer but I'm either missing it or I'm reading the wrong docs.

4 3

FreeBSD deployment
by Eugene R 07 Jun '25

07 Jun '25

Hello! I am planning a migration of the Postfix/Dovecot mail system to a new FreeBSD server. In recent years, I have come to prefer the official ports/packages installations; however, the FreeBSD port of Dovecot is still at 2.3.21 which is substantially different from the current upstream 2.4.1. I have no problems with installing from sources (have been doing that for a long time) but I wonder what is the recommended approach with regard to the installation and configuration paths. I would prefer to follow the standard conventions and eventually switch to the ports-based install once it catches up, with minimal disruption and reconfiguration. Thank you in advance Eugene

4 4

GSSAPI authentication for sieve
by Paul Zirnik 05 Jun '25

05 Jun '25

Hi all, I try to get GSSAPI working for sieve. I already found there was an issue with GSSAPI in dovecot 2.4 and applied the patch from this thread https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/MWCLQ… With the patch GSSAPI now works for imap. I do test this with "imtest" from cyrus tools imat@speedy:~> imtest -v -p 143 -u imat -m GSSAPI manitou.disconnected.homeip.net S: * OK [CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS LOGINDISABLED AUTH=GSSAPI] Dovecot ready. C: A01 AUTHENTICATE GSSAPI YIIDIgYJKoZIhvcSAQICAQBuggMRMIIDDaADAgEFoQMCAQ6iBwMFACAAAACjggIaYYICFjCCAhKgAwIBBaEZGxdESVNDT05ORUNURUQuSE9NRUlQLk5FVKIyMDCgAwIBA6EpMCcbBGltYXAbH21hbml0b3UuZGlzY29ubmVjdGVkLmhvbWVpcC5uZXSjggG6MIIBtqADAgESoQMCAQKiggGoBIIBpFcei+vGql9tb5TpNjKFgdKAo7p1IiSW8DXPJR2GkCrHVrm0LdtsUaky4zOCskwEQkLURA8CuxM5HGmXT38O56434VTStpRHWZx7Xu43UHHJpOjdf76YYqnIA7WEk76QQyUpnO3hQWCEwyAPf1GhQKGDWCosHEuvn3jNE8t8fWmnRtWSgr35w5GD9OHsYKwca14yUruNU/qfVL9I41bjiFcJ1FFjMyVa/+ogghBm4jDoiFTV7vB8WYpx8Vuuev0d48TZDqv7Kf5/G8TgH3bc59VLjCemLAzTjOQ4mZxTXBEh9OpibKPUozRd266ao7dAD4OHMWNORXKqWl/Ch0iC7q/QEg/qY7E0dm7wqMDROrzmaxWW8p5+y69AbjwylsgivknVcTmbQjVnGGvniDLTke8O6CvqeIum/uUli2FyBmSUt8kVju1GIfoysFP8BEu6gDXdbcsG2XbuoTvfzLyJNT7eomILhF9nZI1vFariqF3TJLo14/L4OCG05RrAH3o8kHTkUMz8rrZj5y0yzfQqlME66yBRezRRSccrrD5AWdHzRMvw26SB2TCB1qADAgESooHOBIHLTo7UMx+G8Q+Ly+Mmj35JBfLm+SWeCV1YGcJQ8O1hI6F3pKh4fMjx5L9v4v4NzbDWpZ8YlQtSBcDgyebiZjHaeqGf4bIcOaGyzfor3DhAn0q0n0Zx/SKJiTJuT9eT0pHwb/yaT9MzOZTP6C5HuXgxUN/2Po2qNwkzaU5gOH+sOYu6Y0AKoKGlkIQHejzns70FehWRn8wBbu8T9+8zKRU0qmBQXnqg/C10pSW7EUVD37VPhY0kLY6SB77KS/8aguWWC3OVAfw6bcAXVVM= S: + YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvzFWfR5FTOl77CqiMZ7qWR4I6JqXdi0JbIG4xTYJNYvQSsvxAxyfEiGINTMW5QytlcMvfiJpTj0U2Fd3Hr/MzLcCeCRwJ9jTg8m2E1ZgpmzmpXzl7xGq+MRIvetu3Wdgxum+ZQ8jPS1obTnI1Vh7I C: S: + BQQF/wAMAAAAAAAAHJz31AH///+2dWHfKNY/6f01FUw= C: BQQE/wAMAAAAAAAABI42iwEAAABpbWF0C53m6npnJwjAfaEu S: A01 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE REPLACE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW SPECIAL-USE STATUS=SIZE SAVEDATE COMPRESS=DEFLATE INPROGRESS NOTIFY LITERAL+] Logged in Authenticated. Security strength factor: 0 C: Q01 LOGOUT * BYE Logging out Q01 OK Logout completed (0.001 + 0.000 secs). Connection closed. When i try to use "sivtest" from cyrus tools, this does hang and it looks like sievtest is still waiting for some data imat@speedy:~> sivtest -v -p 4190 -u imat -m GSSAPI manitou.disconnected.homeip.net S: "IMPLEMENTATION" "Dovecot Pigeonhole" S: "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include body variables enotify environment mailbox date index ihave duplicate mime foreverypart extracttext" S: "NOTIFY" "mailto" S: "SASL" "GSSAPI" S: "STARTTLS" S: "VERSION" "1.0" S: OK "Dovecot ready." C: AUTHENTICATE "GSSAPI" {1076+} YIIDIwYJKoZIhvcSAQICAQBuggMSMIIDDqADAgEFoQMCAQ6iBwMFACAAAACjggIbYYICFzCCAhOgAwIBBaEZGxdESVNDT05ORUNURUQuSE9NRUlQLk5FVKIzMDGgAwIBA6EqMCgbBXNpZXZlGx9tYW5pdG91LmRpc2Nvbm5lY3RlZC5ob21laXAubmV0o4IBujCCAbagAwIBEqEDAgECooIBqASCAaTS89GNFHQk6FCilKJkEP8Xl27g/A8b1T0pxGwipjYBug0+bprqG0xJucYaULvqi1PnTI+A6WJesi2434B+L0WAv1sdWhI60SpmmfnsZPD8uqbJmZEFMj9bQnS4VbNgduhEA+pgYp85q0PcP3I5DcMeypIC7rk2hv15qYnVSYhND/P3tOANikXc5JB3cWnnPc79gRW+Ozi75waihMIv7C3UvllUtb2tTUKqdGwz2D9/BT3e1ZfcueaWznhXmzieh4dHZyqvbm4UVVUuc4paI1QMUrImy6zEfXjEH0O8dbZN3FbiKjCdP7E/zFtd6PkWaI0lgk8qGP1JqaFtGgqo+EcDEgyh4DoTRuNGGJp7n1zmQGkgIHzsUNR+SydUhWijdWJSegeIrGsZ4/s8YZupdxpC8g1qComP0+holawe9/iAnCxmRNGrNXDSRnL8wMaVAgm7t0SrBUSOm/YHKZSlHpMIWw438Dp/FdWwuCm2jA5pTksRbzmpS9fguMwp65bX0xh/a0NkI2VWJfwUmgqws3LRv1WHsn2FB/k+w55oOMboOtO3SCCkgdkwgdagAwIBEqKBzgSBy9PZObV0yc813IAR4TwEzPtKepfhzLvT0vFekCieE0sCu7jig2m+bpKt1IbIngs+hiztVx4TXYJu/UjH8UKNYct7xFWAOamuh/Fp4AnTBQXxieMM9TGZsiot7NzH75kRUY6SifNYYbz579wBAMbPzId5n2NVdp2blEpaCDKhMdZf/AQqUj3eFbafs5ociy4cOfmQSNuW7hY4KpQ0JU0cdWQyh0+Xl+fE9tz1ctmRoTA4WIF3U1UcwB0CPxlFxlw6cW+OAP0mlWqJE5Yx S: "YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvEb5fwEVTKq3wm3xJawxEVD9Ngdz3tmzW5a8wJAh9lSRYSE0aJS97LvUtT1mWqZTFx5AZMJGfM7KpcbmJc3cOkVhe5lTUQDir58n1RywkyWYM6RvKd1Vzeonxt/AyJi7rN1CMR9VIh2KZUItIsz1y" here it hangs until timeout. May 24 10:10:36 manitou dovecot[45007]: auth(imat@disconnected.homeip.net,192.168.42.24,sasl:gssapi)<mh73Nt01+OHAqCoY>: Request timed out waiting for client to continue authentication (150 secs) May 24 10:11:06 manitou dovecot[45007]: managesieve-login: Login aborted: Inactivity during authentication (client didn't finish SASL auth, 1 attempts in 180 secs) (auth_waiting_client): user=<>, method=GSSAPI, rip=192.168.42.24, lip=192.168.42.42, session=<mh73Nt01+OHAqCoY> and sievtest does end with this S: BYE "Disconnected for inactivity during authentication." base64 decoding error Authentication failed. generic failure Security strength factor: 0 Connection closed. The "base64 decoding error" probably is unrelated as it does try to decode the "S: BYE .....". I also tested with other sieve clients, none does work (however different issues reported), while all tested imap clients do work. My guess is some small fix like the one from above is also needed for dovecot-pigeonhole. This is my used config manitou:~ # dovecot -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.14.6-1-default x86_64 # Hostname: manitou.disconnected.homeip.net # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_debug = yes auth_debug_passwords = yes auth_gssapi_hostname = manitou.disconnected.homeip.net auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain login gssapi dovecot_storage_version = 2.4.0 protocols { imap = yes lmtp = yes sieve = yes } protocol lmtp { auth_username_format = %{user | username} mail_plugins = sieve } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { } } namespace inbox { mail_driver = maildir mail_inbox_path = ~/Maildir/.INBOX mail_path = ~/Maildir inbox = yes separator = / } passdb pam { service_name = dovecot } userdb passwd { use_worker = yes } ssl_server { cert_file = /etc/ssl/servercerts/servercert.pem key_file = /etc/ssl/servercerts/serverkey.pem } service managesieve-login { } service managesieve { } sieve_script personal { active_path = ~/.dovecot.sieve path = ~/.sieve } What logs/infos are needed to dig into it ? thanks and regards, Tami

1 1

Dovecot 2.4. field lookup for sqlite_path?
by Brent Clark 04 Jun '25

04 Jun '25

Good day Guys Reading: https://doc.dovecot.org/2.4.1/core/config/auth/databases/sql.html#sqlite Im trying to do a field look up but I get the following error message Failed to parse configuration: Failed to expand sqlite_path setting variables: dom ain: No value to get domain from This is what I have passdb sql { query = SELECT name AS username, password FROM mailboxes WHERE name = '%{user | username}' sqlite_path = /usr/home/.mail/%{domain}/mailconf.sq3 } If I hard code the path, then the error message goes away Regards Brent Clark

2 2

Fatal: Couldn't load required plugin /usr/lib/dovecot/lib90_sieve_plugin.so: dlopen() failed: Error relocating /usr/lib/dovecot/lib90_sieve_plugin.so: mail_deliver_get_return_address: symbol not found
by paradoor 04 Jun '25

04 Jun '25

Hi there, I have a Postfix/Dovecot server which today I upgraded from Alpine Linux 3.21 to 3.22. In the process, Dovecot updated from 2.3.21 to 2.4.1, and I updated my Dovecot config accordingly. At least `doveconf -n` runs without any error, and I'm able to start and run Dovecot. For context, I am using a passwd file where I enter usernames and argon2id passwords manually, since it's just a small mail server where I am the only user. The setup was working fine with Dovecot 2.3.x, and I've sent and received lots of mail before the update. However, I noticed that I'm no longer able to authenticate to the server since doing all the updates. I thought, maybe I should make sure the passwd file is correct with my password, so I tried running `doveadm pw -s argon2id`. I then got the error: `Fatal: Couldn't load required plugin /usr/lib/dovecot/lib90_sieve_plugin.so: dlopen() failed: Error relocating /usr/lib/dovecot/lib90_sieve_plugin.so: mail_deliver_get_return_address: symbol not found` I assume this is the cause of the problem, ie Dovecot isn't able to authenticate as this error occurs when a login attempt is made (I think?). I am not sure if this is an Alpine packaging issue or a Dovecot user issue, but just in case it's a user issue that I can fix myself, I thought to post here and ask if people know if there's something I can do to resolve this. I'm also posting to the Alpine mailing list in the case of it being an Alpine packaging issue. I've attached the output of `doveconf -n`; let me know if it's preferable to put this in the body of the email and I can send a reply with it in the body. `dovecot --version` is `2.4.1-4 (7d8c0e5759)`. Example `/var/log/dovecot.conf` authentication attempt: May 31 21:50:41 auth: Debug: conn unix:login (pid=21015,uid=91) [1]: client in: AUTH 4 PLAIN protocol=imap final-resp-ok secured=tls session=ElBsg3U25ou51Zrs lip=93.113.25.226 rip=185.213.154.236 lport=993 rport=35814 ssl_ja3_hash=422b5eb1ed3e9bdf65e87a42ed96ba1f local_name=mail.revsuine.xyz resp=<hidden> May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Debug: passwd-file: Performing passdb lookup May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Debug: passwd-file: lookup: user=${user | username} file=/etc/dovecot/passwd May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Info: passwd-file: unknown user May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Debug: passwd-file: Finished passdb lookup May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Debug: Auth request finished May 31 21:50:41 auth(${user | username},185.213.154.236,sasl:plain)<ElBsg3U25ou51Zrs>: Debug: delaying auth failure May 31 21:50:43 auth: Debug: conn unix:login (pid=21015,uid=91) [1]: client passdb out: FAIL 4 user=${user | username} original_user=pid1 (The IP addresses are my public server IP address and a Mullvad VPN IP address, so not sensitive.) I'm using the same credentials and passwd file as before the update. Thanks in advance, appreciate any responses.

3 6

Crash in imapd
by Peter Chubb 02 Jun '25

02 Jun '25

Hi Folks, I'm seeing imapd crash when an evolution user accesses her primary mailbox. She can see the mailbox perfectly well using thunderbird or Apple Mail on an iPad; just not from her evolution instance. Version is 2.4.1-4 (7d8c0e5759) The error is an assertion failure: Panic: file istream-header-filter.c: line 665 (i_stream_header_filter_snapshot_free): assertion failed: (snapshot->mstream->snapshot_pending) I'm running on Debian unstable in an LXC container, using the Debian packaged version of dovecot. Filesystem for INBOX (mbox format) is XFS; home directories are mounted via NFS. The backtrace in gdb is: #0 0x00007f996709e95c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f9967049cc2 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f99670324ac in abort () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007f9967265964 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007f9967333cb7 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007f99672656c0 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #6 0x00007f996725eab1 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #7 0x00007f9967345bdc in i_stream_snapshot_free () from /usr/lib/dovecot/libdovecot.so.0 #8 0x00007f9967345bdc in i_stream_snapshot_free () from /usr/lib/dovecot/libdovecot.so.0 #9 0x00007f9967345c6c in i_stream_unref () from /usr/lib/dovecot/libdovecot.so.0 #10 0x00007f996752bf99 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 #11 0x00007f996752c391 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 #12 0x00007f996752c64c in index_mail_get_special () from /usr/lib/dovecot/libdovecot-storage.so.0 #13 0x00007f99674a570e in mail_get_special () from /usr/lib/dovecot/libdovecot-storage.so.0 #14 0x000055fb1f1b298a in fetch_snippet (ctx=0x55fb4c044168, mail=0x55fb4c070e88, preview=0x55fb4c070230) at ./src/imap/imap-fetch-body.c:610 #15 0x000055fb1f1b7ce3 in imap_fetch_more_int (ctx=ctx@entry=0x55fb4c044168, cancel=false) at ./src/imap/imap-fetch.c:562 #16 0x000055fb1f1b7fbd in imap_fetch_more (ctx=0x55fb4c044168, cmd=0x55fb4c043e98) at ./src/imap/imap-fetch.c:617 #17 0x000055fb1f1ac1c8 in cmd_fetch (cmd=0x55fb4c043e98) at ./src/imap/cmd-fetch.c:382 #18 0x000055fb1f1b5124 in command_exec (cmd=cmd@entry=0x55fb4c043e98) at ./src/imap/imap-commands.c:208 #19 0x000055fb1f1bb650 in client_command_input (cmd=<optimized out>, cmd@entry=0x55fb4c043e98) at ./src/imap/imap-client.c:1271 #20 0x000055fb1f1bb6e6 in client_command_input (cmd=<optimized out>, cmd@entry=0x55fb4c043e98) at ./src/imap/imap-client.c:1341 #21 0x000055fb1f1bb97d in client_command_input (cmd=<optimized out>) at ./src/imap/imap-client.c:1305 #22 0x000055fb1f1bbb55 in client_handle_next_command (client=0x55fb4c042a68, remove_io_r=<synthetic pointer>) at ./src/imap/imap-client.c:1383 #23 client_handle_input (client=client@entry=0x55fb4c042a68) at ./src/imap/imap-client.c:1397 #24 0x000055fb1f1bbf47 in client_input (client=0x55fb4c042a68) at ./src/imap/imap-client.c:1441 #25 0x00007f996735177b in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 #26 0x00007f99673535ea in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 #27 0x00007f9967353694 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 #28 0x00007f9967353868 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 #29 0x00007f99672a6347 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 #30 0x000055fb1f1a6e27 in main (argc=<optimized out>, argv=<optimized out>) at ./src/imap/main.c:601 dovecot -n === # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.16-amd64 x86_64 Debian 13.0 # Hostname: wombat.chubb.wattle.id.au # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 first_valid_uid = 130 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes mail_access_groups = mail mail_driver = mbox mail_full_filesystem_access = yes mail_home = /home/%{user|username} mail_inbox_path = /var/mail/%{user} mail_index_path = /var/indices/%{user} mail_nfs_storage = yes mail_path = ~/Mail/ mail_privileged_group = mail protocols { imap = yes } ssl_cipher_list = EDH+CAMELLIA:EDH+aRSA:EECDH+aRSA+AESGCM:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH:+CAMELLIA256:+ECDHE-RSA-AES256-GCM-SHA384:+AES256:+CAMELLIA128:+AES128:+SSLv3:DES-CBC3-SHA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:RC4:!SEED:!ECDSA:CAMELLIA256-SHA:AES256-SHA:CAMELLIA128-SHA:AES128-SHA ssl_min_protocol = TLSv1 passdb pam { } userdb passwd { } namespace inbox { inbox = yes mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } mailbox Spam { special_use = "\\Junk" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service submission { } service auth { unix_listener auth-userdb { } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/dovecot/private/dovecot.pem key_file = /etc/dovecot/private/dovecot.key } passdb local { driver = pam } userdb local { driver = passwd } ---

2 1

Question about OSS-Fuzz
by 0xdeadtofu 01 Jun '25

01 Jun '25

Hello, I have been looking at the dovecot project in oss-fuzz [1] and I have noticed that the different fuzzers that are being built for dovecot do not have any sanitizer but UBSAN enabled. Normally, it's the default to fuzz with Address Sanitizer or Memory Sanitizer, so I was wondering, what is the reason for not enabling it? Kind Regards, Patrick Detering [1] https://github.com/google/oss-fuzz/tree/master/projects/dovecot

1 0

Help Translating Dovecot 2.3 Proxy Configuration to 2.4
by Brent Clark 31 May '25

31 May '25

Hi all, I'm in the process of upgrading from Dovecot 2.3 to 2.4 and would appreciate some help translating an existing configuration that uses a proxy lookup for user and password databases. Here's the relevant 2.3 configuration: |passdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } userdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } uri= proxy:/var/run/mail_directory_service/socket:somewhere password_key= passdb/%u user_key= userdb/%u iterate_disable= yes | This configuration was working fine in 2.3 to proxy user and password lookups to an external service via a Unix socket. However, Dovecot 2.4 has reworked configuration parsing, and this syntax no longer appears valid. I couldn’t find a direct equivalent in the 2.4 documentation. Could someone advise how this should be adapted for 2.4? What’s the correct way to specify the proxy: URI in 2.4? Are password_key and user_key still supported, or should I be using a different mechanism? Is iterate_disable = yes still relevant or required in this context? Any guidance, examples, or pointers to migration resources would be very helpful. Thanks in advance, Brent Clark Hi all, I'm in the process of upgrading from Dovecot 2.3 to 2.4 and would appreciate some help translating an existing configuration that uses a proxy lookup for user and password databases. Here's the relevant 2.3 configuration: passdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } userdb { driver =dict args =/etc/dovecot/dovecot-dict-auth.conf.ext } uri = proxy:/var/run/mail_directory_service/socket:somewhere password_key = passdb/%u user_key = userdb/%u iterate_disable = yes This configuration was working fine in 2.3 to proxy user and password lookups to an external service via a Unix socket. However, Dovecot 2.4 has reworked configuration parsing, and this syntax no longer appears valid. I couldn’t find a direct equivalent in the 2.4 documentation. Could someone advise how this should be adapted for 2.4? What’s the correct way to specify the proxy: URI in 2.4? Are password_key and user_key still supported, or should I be using a different mechanism? Is iterate_disable = yes still relevant or required in this context? Any guidance, examples, or pointers to migration resources would be very helpful. Thanks in advance, Brent Clark

6 11

Panic with FTS_BACKEND_FLAG_TOKENIZED_INPUT and virtual mailboxes: file index-search-result.c: line 132
by markus-dovecot＠doits.de 30 May '25

30 May '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 2

RE: dragging files into mail folders
by Marc 30 May '25

30 May '25

If I drag files in imap folders in outlook they will show up in eg roundcube/thunderbird as winmail.dat. So I guess this is just a microsoft thing. Would be nice if there were plugins that would add functionality that unwrapped these winmail.dat files. > > > If i Understood correctly you are looking for a software like > > roundcube or something right ?. > > Not necessarily, but would be a good start. Question is if the imap > allows to store these files directly. > > > > that offers ajax based GUI that allows > > you to drap and drop mails into folders. > > Files not mails. .jpg, .odt, .txt etc > > > > > > > > With exchange and outlook I was always used to sometimes drag files > > into mail folders. Is something like this available for imap? Or maybe > a > > dovecot extension? > > > > > > (obviously I am not looking for a solution to store them as > > attachments to mails) > > > _______________________________________________ > > > dovecot mailing list -- dovecot(a)dovecot.org > > > To unsubscribe send an email to dovecot-leave(a)dovecot.org

2 2

dragging files into mail folders
by Marc 28 May '25

28 May '25

With exchange and outlook I was always used to sometimes drag files into mail folders. Is something like this available for imap? Or maybe a dovecot extension? (obviously I am not looking for a solution to store them as attachments to mails)

1 0

Re: NAMESPACE empty when logging via haproxy but populated properly when logging directly
by dk+lists.dovecot.org＠7ns.eu 27 May '25

27 May '25

On 2025-05-22 17:41, dk+lists.dovecot.org(a)7ns.eu wrote: > > On 2025-05-22 16:55, Aki Tuomi via dovecot wrote: >>> >>> I see you a local 10.20.20.20 statement there, which changes how the >>> inbox prefix behaves, and I'm guessing (?) you are testing from >>> 10.20.20.20 as it's local, not remote. >>> >>> Which would explain why. >> >> Also to add a bit that the "local_ip" (not real_local_ip) gets updated >> with haproxy proxy protocol (when enabled), so it will remote >> haproxy's local IP. >> >> Aki >> > Wow. Thank you. It works. I mangled a IPs little bit before I send them > to mailist. All machines are in the same network. Client, Proxy, Server. > All in the same subnet. This is first time I see such problem with > server software and reverse proxy. Never seen similar problem. What > exactly this "local" statement do? Mail client is in the same network as > server, so after PROXY header is stripped, my mail client IP should be > seen by dovecot exactly the same, so shouldn't dovecot treat those > connections equally? oO > > Thank you again for tip Aki. > DK Hmm, now I am struggling with "local_name" filtering in haproxy environment. According to dovecot docs [1] it could potentially work with "send-proxy-v2-ssl" configured on proxy backend. However my dovecot filter does not work. Have the same problem I had with "local" filter. Dovecot does not recognize this connection and does not filter config for it properly. I tried "send-proxy-v2-ssl-cn". Still the same. I even enabled ssl on dovecot globally with "ssl=required" to be sure dovecot does not disable some ssl logic when "ssl=no". Still no go. Seems like dovecot does not get or use TLS/SNI info from haproxy. Does it even work in such environment? Is it supported? Or is this a bug or maybe my error? Any clues please? DK [1] https://doc.dovecot.org/2.4.1/core/config/haproxy.html#tls-forwarding

4 10

Sieve vnd.dovecot.config extension does not work when mail is delivered to lmtp inet_listener but works when delivered to lmtp unix_listener
by DK 27 May '25

27 May '25

Hello. I have a strange problem with sieve scripts vnd.dovecot.config extension processing on newest dovecot 2.3 and 2.4. When I deliver mail via lmtp unix_listener sieve script can get sieve_env_* variable with no problem. However when I deliver mail via lmtp inet_listener sieve script can not get the same sieve_env_* variable. I deliver mails from postfix to lmtp inet_listener directly (not via haproxy). The same postfix is used when testing lmtp unix_listener mail delivery which works. Any clues what could be the cause of such problem? DK

1 2

Thunderbird and Dovecot 2.4.0 Incompatibility
by Amit Chaudhari 27 May '25

27 May '25

I'm trying to setup a dovecot 2.4.0 imap server and have it work with Thunderbird. I'm able to connect/auth fine, however trying to save a message to a mailbox causes the connection to close. ``` Info: Disconnected: Too many invalid IMAP commands. in=744 out=2559 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 ``` It appears thunderbird's imap APPEND command is using syntax which dovecot doesn't like? I enabled raw logs and pasted them below: Downgrading to 2.3 resolves the issue, so it’s either a regression, or some config issue I’m not able to pinpoint. ``` 1738942430.025029 5 ID ("name" "Thunderbird" "version" "128.7.0") 1738942430.029320 6 ENABLE UTF8=ACCEPT 1738942430.033907 7 select "Drafts" 1738942430.039796 8 append "Drafts" (\Draft) UTF8 (~{726+} 1738942430.039796 Message-ID: <ea714f62-7186-4bcb-b709-007e39c6a9d6(a)example.com <mailto:ea714f62-7186-4bcb-b709-007e39c6a9d6@example.com>> 1738942430.039796 Date: Fri, 7 Feb 2025 10:33:49 -0500 1738942430.039796 MIME-Version: 1.0 1738942430.039796 User-Agent: Mozilla Thunderbird 1738942430.039796 Content-Language: en-US 1738942430.039796 To: sender(a)example.com <mailto:sender@example.com> 1738942430.039796 From: User Name <user(a)example.com <mailto:user@example.com>> 1738942430.039796 Subject: test 1738942430.039796 X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0; 1738942430.039796 attachmentreminder=0; deliveryformat=0 1738942430.039796 X-Identity-Key: id2 1738942430.039796 Fcc: imap://user%40example.com@192.168.115.203/Sent 1738942430.039796 Content-Type: text/html; charset=UTF-8 1738942430.039796 Content-Transfer-Encoding: 7bit 1738942430.039796 1738942430.039796 <!DOCTYPE html> 1738942430.039796 <html> 1738942430.039796 <head> 1738942430.039796 1738942430.039796 <meta http-equiv="content-type" content="text/html; charset=UTF-8"> 1738942430.039796 </head> 1738942430.039796 <body> 1738942430.039796 <p><br> 1738942430.039796 </p> 1738942430.039796 </body> 1738942430.039796 </html> 1738942430.039796 ) ``` ``` 1738942430.025188 * ID ("name" "Dovecot") 1738942430.025234 5 OK ID completed (0.001 + 0.000 secs). 1738942430.029390 * ENABLED UTF8=ACCEPT 1738942430.029418 6 OK Enabled (0.001 + 0.000 secs). 1738942430.035478 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) 1738942430.035531 * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. 1738942430.035559 * 0 EXISTS 1738942430.035585 * 0 RECENT 1738942430.035611 * OK [UIDVALIDITY 1738898190] UIDs valid 1738942430.035638 * OK [UIDNEXT 1] Predicted next UID 1738942430.035693 7 OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs). 1738942430.040007 8 BAD Error in IMAP command APPEND: Missing ')' (0.001 + 0.000 secs). 1738942430.040140 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040172 Date: BAD Error in IMAP command FRI,: Unknown command (0.001 + 0.000 secs). 1738942430.040233 MIME-Version: BAD Error in IMAP command 1.0: Unknown command (0.001 + 0.000 secs). 1738942430.040291 User-Agent: BAD Error in IMAP command MOZILLA: Unknown command (0.001 + 0.000 secs). 1738942430.040356 Content-Language: BAD Error in IMAP command EN-US: Unknown command (0.001 + 0.000 secs). 1738942430.040409 To: BAD Error in IMAP command sender(a)example.com <mailto:sender@example.com>: Unknown command (0.001 + 0.000 secs). 1738942430.040467 From: BAD Error in IMAP command USER: Unknown command (0.001 + 0.000 secs). 1738942430.040521 Subject: BAD Error in IMAP command TEST: Unknown command (0.001 + 0.000 secs). 1738942430.040574 X-Mozilla-Draft-Info: BAD Error in IMAP command INTERNAL/DRAFT;: Unknown command (0.001 + 0.000 secs). 1738942430.040638 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040666 X-Identity-Key: BAD Error in IMAP command ID2: Unknown command (0.001 + 0.000 secs). 1738942430.040720 Fcc: BAD Error in IMAP command: Invalid command name (0.001 + 0.000 secs). 1738942430.040746 Content-Type: BAD Error in IMAP command TEXT/HTML;: Unknown command (0.001 + 0.000 secs). 1738942430.040802 Content-Transfer-Encoding: BAD Error in IMAP command 7BIT: Unknown command (0.001 + 0.000 secs). 1738942430.040862 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040889 <!DOCTYPE BAD Error in IMAP command HTML>: Unknown command (0.001 + 0.000 secs). 1738942430.040966 <html> BAD Error in IMAP command: Invalid command name (0.001 + 0.000 secs). 1738942430.040991 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.041015 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.041032 * BYE Too many invalid IMAP commands. ```

5 7

Dovecot and pigeonhole/sieve without ldap
by ppn＠parhuet.fr 26 May '25

26 May '25

Hi, First of all, thanks for your work on this software overall. Since 2.4 dovecot/pigeonhole (2.4.1 gentoo here), it fails to build without ldap support. I've seen nothing that justifies this requirement so it seems like a bug/issue? Configure for dovecot : ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-dependency-tracking --disable-silent-rules --disable-static --docdir=/usr/share/doc/dovecot-2.4.1-r1 --htmldir=/usr/share/doc/dovecot-2.4.1-r1/html --with-sysroot=/ --libdir=/usr/lib64 --with-rundir=/run/dovecot --with-statedir=/var/lib/dovecot --with-moduledir=/usr/lib64/dovecot --disable-hardening --disable-rpath --with-bzlib --without-libbsd --with-libcap --with-icu --enable-experimental-mail-utf8 --without-sodium --without-cdb --without-gssapi --without-lua --without-ldap --without-flatcurve --without-lz4 --without-mysql --with-pam --without-pgsql --without-sqlite --without-solr --without-stemmer --without-systemd --without-textcat --without-libunwind --without-zstd --disable-static userdbs ........ : static prefetch passwd passwd-file : -ldap -sql Configure for pigeonhole : ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-dependency-tracking --disable-silent-rules --disable-static --docdir=/usr/share/doc/dovecot-2.4.1-r1 --htmldir=/usr/share/doc/dovecot-2.4.1-r1/html --with-sysroot=/ --libdir=/usr/lib64 --disable-static --localstatedir=/var --enable-shared --disable-hardening --with-dovecot=/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4 --without-ldap --without-managesieve script drivers . : file dict : -ldap Error : age/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-sasl -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/li b-dcrypt -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-program-client -I/var/tmp/portage/net-mail/dovecot-2. 4.1-r1/work/dovecot-2.4.1-4/src/lib-oauth2 -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-var-expand -I/var/t mp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-index -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1- 4/src/lib-storage -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-storage/list -I/var/tmp/portage/net-mail/dov ecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-storage/index -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-stora ge/index/raw -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-imap-storage -I/var/tmp/portage/net-mail/dovecot- 2.4.1-r1/work/dovecot-2.4.1-4/src/plugins/quota -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-ldap -I../../. ./.. -I../../../../src/lib-sieve -O2 -pipe -frecord-gcc-switches -flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -fa synchronous-unwind-tables -c sieve-ldap-storage.c -fPIC -DPIC -o .libs/sieve-ldap-storage.o In file included from sieve-ldap-storage.c:6: /var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-ldap/ldap-utils.h:4:10: fatal error: ldap.h: No such file or dir ectory 4 | #include <ldap.h> | ^~~~~~~~ compilation terminated. make[5]: *** [Makefile:607: sieve-ldap-storage.lo] Error 1 Regards, NicoP

3 12

lmtp user verification
by Christian H. Kuhn 26 May '25

26 May '25

Hi, after a new install and avoiding a lot of simple faults, i try to run my system postfix as smtpd, smtpds, and submission, and dovecot as imap and lmtp server. I can login to imap, and i can send via 587 with sasl authentification. So i think that most things are ok :-) What does NOT work is the local transport to my maildir. christian.kuhn(a)qno.de is not resolved to qno(a)qno.de but to qno(a)bywater.qno.de, and lmtp rejects that unverified user: 2025-05-25T18:13:25.431342+02:00 bywater postfix/smtpd[987726]: NOQUEUE: reject: RCPT from mail-lj1-f176.google.com[209.85.208.176]: 450 4.1.1 <qno(a)bywater.qno.de>: Recipient address rejected: unverified address: host bywater.qno.de[private/dovecot-lmtp] said: 550 5.1.1 <qno(a)bywater.qno.de> User doesn't exist: qno(a)bywater.qno.de (in reply to RCPT TO command) also mails to qno-anyextension(a)qno.de are rejected. I set recipient_delimiter to -, but it seems to be ignored by lmtp: 2025-05-25T15:24:10.147369+02:00 bywater postfix/smtpd[985952]: NOQUEUE: reject: RCPT from higher.littydate.com[104.244.79.41]: 450 4.1.1 <qno-planets(a)qno.de>: Recipient address rejected: unverified address: host bywater.qno.de[private/dovecot-lmtp] said: 550 5.1.1 <qno-planets(a)qno.de> User doesn't exist: qno-planets(a)qno.de (in reply to RCPT TO command); from=<webmaster(a)littydate.com> to=<qno-planets(a)qno.de> proto=ESMTP helo=<higher.littydate.com> postconf -n: (postfix 3.8.6) broken_sasl_auth_clients = yes compatibility_level = 3.6 content_filter = amavis:[127.0.0.1]:10024 default_database_type = cdb indexed = ${default_database_type}:${tabledir} inet_interfaces = 127.0.0.1, 65.21.136.15, [::1], [2a01:4f9:3b:25b0:9:6:1:e01] local_recipient_maps = mailbox_transport = lmtp:unix:private/dovecot-lmtp mydestination = $myhostname mydomain = qno.de myhostname = bywater.qno.de mynetworks = 127.0.0.0/8 65.21.136.15/32 [::1]/128 [2a01:4f9:3b:25b0:9:6:1:e01]/128 [2a01:4f8:171:b85:9:6:1:e01]/128 136.243.102.134/32 myorigin = $mydomain policyd-spf_time_limit = 3600 postscreen_access_list = permit_mynetworks postscreen_bare_newline_action = enforce postscreen_bare_newline_enable = no postscreen_dnsbl_action = enforce postscreen_dnsbl_reply_map = ${indexed}dnsbl_reply postscreen_dnsbl_sites = zusbyxqsairu6mu6ayyhstc3ua.zen.dq.spamhaus.net postscreen_dnsbl_threshold = 1 postscreen_non_smtp_command_action = enforce postscreen_non_smtp_command_enable = no postscreen_pipelining_action = enforce postscreen_pipelining_enable = no receive_override_options = no_address_mappings recipient_delimiter = - smtp_bind_address = 65.21.136.15 smtp_bind_address6 = 2a01:4f9:3b:25b0:9:6:1:e01 smtp_generic_maps = ${indexed}generic smtp_tls_exclude_ciphers = aNULL smtp_tls_loglevel = 1 smtp_tls_mandatory_ciphers = medium smtp_tls_mandatory_exclude_ciphers = RC4, MD5, SHA1 smtp_tls_security_level = may smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_required = yes smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unverified_recipient, check_policy_service unix:private/policyd-spf, reject_rbl_client zusbyxqsairu6mu6ayyhstc3ua.zen.dq.spamhaus.net, reject_rhsbl_reverse_client zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net, reject_rhsbl_helo zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net, reject_rhsbl_sender zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_tls_security_options = $smtpd_sasl_security_options smtpd_sasl_type = dovecot smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_tls_auth_only = yes smtpd_tls_eccert_file = /etc/letsencrypt/live/mail.qno.de/fullchain.pem smtpd_tls_eckey_file = /etc/letsencrypt/live/mail.qno.de/privkey.pem smtpd_tls_mandatory_ciphers = high smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5, SHA1 smtpd_tls_mandatory_protocols = >=TLSv1.2 smtpd_tls_received_header = yes smtpd_tls_security_level = may tabledir = ${config_directory}/tables.d/ virtual_alias_domains = $mydomain virtual_alias_maps = ${indexed}virtual virtual_gid_maps = static:5000 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = sk-koenig-tegel.de virtual_mailbox_maps = mysql:${tabledir}virtual_mailbox_maps.cf virtual_minimum_uid = 10000 virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_uid_maps = static:5000 doveconf -n: # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.8.0-60-generic x86_64 Ubuntu 24.04.2 LTS # Hostname: bywater.qno.de auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = yes listen = 65.21.136.15, 2a01:4f9:3b:25b0:9:6:1:c01 mail_debug = yes mail_location = maildir:~/Maildir 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 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 { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/imap2.qno.de/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes verbose_ssl = yes TIA QNo

2 3

Two instances on one machine — can they share indexes?
by dove＠redir.desz.cz 24 May '25

24 May '25

Hello, I (think I) need to run two instances of Dovecot on one machine (rationale below, if someone's interested). They access the same mail share (NFS, maildir), but the indexes are kept on local storage. One of them would also provide lmtp service to local MTA. For now I set the instances to keep indexes separate, in different directories, but I wonder, if they can share the indexes, to avoid unnecessary duplication? Of course, mmap_disable = yes, but would locking suffice? The platform is Linux (Devuan chimaera ATM, equivalet of Debian 11), filesystem - ext4, Dovecot version 2.3.13 (from distribution packages). Why? I have to provide different authentication methods to external IMAP clients and locally-running webmail; at first I hoped to make it via remote filter, but docs state that “auth settings currently only support the protocol filter”, so I had to come with some other idea. It _is_ possible that users would be logged in both via external mail client and webmail at the same time – and even if not, there's also lmtp, that can run at any moment. Sincerely, Bartosz Stępień

1 0

Guidance re doveadm sync full (-f) and stateful (-s)
by Georgios Kontaxis 24 May '25

24 May '25

Hi, I’m looking for guidance on how to use doveadm sync with flags -f (full synchronization) and -s. (stateful synchronization) After reading the doveadm-sync man page it seems one should do the following: (omitting -u -l -N flags for clarity) 1. First sync: doveadm sync -f 2. Second sync: doveadm sync -s “" > state 3. Subsequent infrequent syncs: doveadm sync -f 4. Subsequent frequent syncs: doveadm sync -s “$(<state)” > state (I’m assuming that before the first sync replica A has all the mailboxes and replica B has no mailboxes. I’m also assuming that the above commands are executed from replica A. The goal is to do master/master sync continuously.) Can you help me answer the following questions? a. Each time we execute (4) stateful sync after (3) full sync, is it correct to include previous state? b. What happens if we do: doveadm sync -f -s “” or doveadm sync -f -s “$(<state)” I think the replicator code does (b) in https://github.com/dovecot/core/blob/47349e24828be3ec7f591570e02c0b15ae26c6… and I’m not sure why. Overall, it would be good to have more examples in the man page demonstrating the various synchronization modes. Thanks, Georgios

1 0

Dovecot 2.4.1 userdb override for autoexpunge on specific mailbox
by Thomas Leuxner 24 May '25

24 May '25

Hi, I'm trying to override the autoexpunge setting for the "Deleted Messages" mailbox in the INBOX namespace. [...] mailbox "Deleted Messages" { autoexpunge = 2d special_use = "\\Trash" } doveconf -nF # mail_namespace :FILTER settings_filter_name="namespace/inbox" namespace_name=inbox namespace_type=private namespace_separator=/ namespace_prefix= namespace_inbox=yes namespace_hidden=no mailbox=INBOX Drafts Junk Deleted\_Messages Spam Sent Sent\_Messages The setting seems to be pulled from the userdb and matches the escaping above. It doesn't seem to alter the global "autoexpunge = 2d" setting for this user though. doveadm user -u tlx(a)leuxner.net userdb: tlx(a)leuxner.net user : tlx(a)leuxner.net home : /var/vmail/domains/leuxner.net/tlx uid : 5000 gid : 5000 quota_storage_size: 5G acl_groups: PublicMailboxAdmins namespace/inbox/mailbox/Deleted\_Messages/autoexpunge: 6h Regards Thomas

1 1

NAMESPACE empty when logging via haproxy but populated properly when logging directly
by dk+lists.dovecot.org＠7ns.eu 23 May '25

23 May '25

Hello there. I have a problem with newest dovecots (2.3 and 2.4). Dovecot server for some reason is not providing NAMESPACE via IMAP commands when logging via haproxy (rawlog provided below). Server config: inet_listener imap { port = 143 haproxy = yes } inet_listener imap0 { port = 1143 haproxy = no } When I login directly to dovecot server on port 1143 I get this response from server: 1747853284.039953 * NAMESPACE (("INBOX/" "/")) (("Shared/" "/")) (("Public/" "/")) 1747853284.039986 52 OK Namespace completed (0.001 + 0.000 secs). However when I login to the exact same dovecot server but via haproxy host on port 143 I get this response from server: 1747853284.076121 * NAMESPACE (("" "/")) NIL NIL 1747853284.076160 27 OK Namespace completed (0.001 + 0.000 secs). Tested on: - debian dovecot 2.3.21.1+dfsg1-1+b2 - debian dovecot 2.4.1+dfsg1-4 Could some dev look into it please? Clearly something is broken with dovecot haproxy listener. I just deployed dovecot 2.4 to check if it was fixed but the same problem exists there. Greets. dk Hello there. I have a problem with newest dovecots (2.3 and 2.4). Dovecot server for some reason is not providing NAMESPACE via IMAP commands when logging via haproxy (rawlog provided below). Server config: inet_listener imap { port = 143 haproxy = yes } inet_listener imap0 { port = 1143 haproxy = no } When I login directly to dovecot server on port 1143 I get this response from server: 1747853284.039953 * NAMESPACE (("INBOX/" "/")) (("Shared/" "/")) (("Public/" "/ ")) 1747853284.039986 52 OK Namespace completed (0.001 + 0.000 secs). However when I login to the exact same dovecot server but via haproxy host on port 143 I get this response from server: 1747853284.076121 * NAMESPACE (("" "/")) NIL NIL 1747853284.076160 27 OK Namespace completed (0.001 + 0.000 secs). Tested on: - debian dovecot 2.3.21.1+dfsg1-1+b2 - debian dovecot 2.4.1+dfsg1-4 Could some dev look into it please? Clearly something is broken with dovecot haproxy listener. I just deployed dovecot 2.4 to check if it was fixed but the same problem exists there. Greets. dk

4 6

Upgrade 2.3 to 2.4 - Dovecot cannot find user mailbox
by Cam Ellison 22 May '25

22 May '25

The system in question primarily sends emails to group members but also has a few virtual email accounts for officers. Usernames and passwords are looked up from a mysql (MariaDB) database. After the upgrade incoming mail now goes to a vmail account that Dovecot creates because it cannot match the email to the user for whom it is intended (there is no user 'vmail' in the system). Users can log in and read their mail and send mail, but any emails received since the change to 2.4 are understandably inaccessible. Below is the output from doveconf -n. Can anyone see what is wrong? # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.1.0-20-rt-686-pae i686 Debian 13.0 ext4 # Hostname: football.scasl.ca # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login base_dir = /var/run/dovecot/ dovecot_storage_version = 2.4.0 first_valid_gid = 5000 first_valid_uid = 5000 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = scasl.ca listen = * :: login_trusted_networks = 209.121.143.10/32 mail_debug = yes mail_driver = maildir mail_gid = 5000 mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir mail_privileged_group = vmail mail_uid = 5000 postmaster_address = postmaster(a)scasl.ca protocols { imap = yes } sql_driver = mysql dict quota { } mysql scasl.ca { dbname = scasl host = localhost password = # hidden, use -P to show it port = 3306 user = scasl } userdb sql { iterate_query = SELECT email_username AS username, domain FROM league query = SELECT CONCAT('/var/vmail/',email_username) AS home, 5000 AS uid, 5000 AS gid FROM league WHERE email_username = '%{user|username}' } passdb sql { default_password_scheme = BLF-CRYPT query = SELECT password FROM login WHERE ID IN (SELECT ID FROM league WHERE email_username='%{user|username}') } maildir { very_dirty_syncs = yes } namespace inbox { mail_driver = maildir mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir inbox = yes separator = / mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service submission-login { inet_listener submission { } } service lmtp { unix_listener lmtp { mode = 0666 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0666 } unix_listener auth-client { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } service stats { unix_listener stats-reader { group = vmail mode = 0666 } unix_listener stats-writer { group = vmail mode = 0666 } } ssl_server { cert_file = /etc/letsencrypt/live/scasl.ca/fullchain.pem key_file = /etc/letsencrypt/live/scasl.ca/privkey.pem } Cheers Cam The system in question primarily sends emails to group members but also has a few virtual email accounts for officers. Usernames and passwords are looked up from a mysql (MariaDB) database. After the upgrade incoming mail now goes to a vmail account that Dovecot creates because it cannot match the email to the user for whom it is intended (there is no user 'vmail' in the system). Users can log in and read their mail and send mail, but any emails received since the change to 2.4 are understandably inaccessible. Below is the output from doveconf -n. Can anyone see what is wrong? # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.1.0-20-rt-686-pae i686 Debian 13.0 ext4 # Hostname: football.scasl.ca # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login base_dir = /var/run/dovecot/ dovecot_storage_version = 2.4.0 first_valid_gid = 5000 first_valid_uid = 5000 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = scasl.ca listen = * :: login_trusted_networks = 209.121.143.10/32 mail_debug = yes mail_driver = maildir mail_gid = 5000 mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir mail_privileged_group = vmail mail_uid = 5000 postmaster_address = postmaster(a)scasl.ca protocols { imap = yes } sql_driver = mysql dict quota { } mysql scasl.ca { dbname = scasl host = localhost password = # hidden, use -P to show it port = 3306 user = scasl } userdb sql { iterate_query = SELECT email_username AS username, domain FROM league query = SELECT CONCAT('/var/vmail/',email_username) AS home, 5000 AS uid, 5000 AS gid FROM league WHERE email_username = '%{user|username}' } passdb sql { default_password_scheme = BLF-CRYPT query = SELECT password FROM login WHERE ID IN (SELECT ID FROM league WHERE email_username='%{user|username}') } maildir { very_dirty_syncs = yes } namespace inbox { mail_driver = maildir mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir inbox = yes separator = / mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service submission-login { inet_listener submission { } } service lmtp { unix_listener lmtp { mode = 0666 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0666 } unix_listener auth-client { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } service stats { unix_listener stats-reader { group = vmail mode = 0666 } unix_listener stats-writer { group = vmail mode = 0666 } } ssl_server { cert_file = /etc/letsencrypt/live/scasl.ca/fullchain.pem key_file = /etc/letsencrypt/live/scasl.ca/privkey.pem } Cheers Cam

2 2

Upgrade 2.3 to 2.4 - virtual mail - dovecot-lda flags ignored
by Cam Ellison 22 May '25

22 May '25

When running v2.3, Dovecot correctly identifies both recipient and domain when receiving mail from Debian exim4 via dovecot-lda, with no flags set. With v2.4, whether the flags are set or not, Dovecot throws error 75. If lda_mailbox_autocreate is set to yes, it creates the mailuser vmail and delivers to /var/vmail/vmail/INBOX. Users are able to log in and read email as before. doveadm user admin(a)example.ca output is: field value uid 5000 gid 5000 home /var/vmail/admin mail_path /var/vmail/admin/Maildir Here is the full printout of doveconf -n. # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.1.0-20-rt-686-pae i686 Debian 13.0 ext4 # Hostname: football.scasl.ca # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login base_dir = /var/run/dovecot/ dovecot_storage_version = 2.4.0 first_valid_gid = 5000 first_valid_uid = 5000 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = scasl.ca listen = * :: login_trusted_networks = 209.121.143.10/32 mail_debug = yes mail_driver = maildir mail_gid = 5000 mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir mail_privileged_group = vmail mail_uid = 5000 postmaster_address = postmaster(a)scasl.ca protocols { imap = yes } sql_driver = mysql mysql scasl.ca { dbname = scasl host = localhost password = # port = 3306 user = scasl } userdb sql { iterate_query = SELECT email_username AS username, domain FROM league query = SELECT CONCAT('/var/vmail/',email_username) AS home, 5000 AS uid, 5000 AS gid FROM league WHERE email_username = '%{user|username}' } passdb sql { default_password_scheme = BLF-CRYPT query = SELECT password FROM login WHERE ID IN (SELECT ID FROM league WHERE email_username='%{user|username}') } maildir { very_dirty_syncs = yes } namespace inbox { mail_driver = maildir mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir inbox = yes separator = / type = private mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service submission-login { inet_listener submission { } } service lmtp { unix_listener lmtp { mode = 0666 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0666 } unix_listener auth-client { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } service stats { unix_listener stats-reader { group = vmail mode = 0666 } unix_listener stats-writer { group = vmail mode = 0666 } } ssl_server { cert_file = /etc/letsencrypt/live/scasl.ca/fullchain.pem key_file = /etc/letsencrypt/live/scasl.ca/privkey.pem } protocol lda { mail_plugins = $mail_plugins } I assume I am missing a parameter that needs setting. Is it that, do I have something set incorrectly, or is it really a bug? Cheers Cam When running v2.3, Dovecot correctly identifies both recipient and domain when receiving mail from Debian exim4 via dovecot-lda, with no flags set. With v2.4, whether the flags are set or not, Dovecot throws error 75. If lda_mailbox_autocreate is set to yes, it creates the mailuser vmail and delivers to /var/vmail/vmail/INBOX. Users are able to log in and read email as before. doveadm user admin(a)example.ca output is: field value uid 5000 gid 5000 home /var/vmail/admin mail_path /var/vmail/admin/Maildir Here is the full printout of doveconf -n. # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.1.0-20-rt-686-pae i686 Debian 13.0 ext4 # Hostname: football.scasl.ca # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login base_dir = /var/run/dovecot/ dovecot_storage_version = 2.4.0 first_valid_gid = 5000 first_valid_uid = 5000 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = scasl.ca listen = * :: login_trusted_networks = 209.121.143.10/32 mail_debug = yes mail_driver = maildir mail_gid = 5000 mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir mail_privileged_group = vmail mail_uid = 5000 postmaster_address = postmaster(a)scasl.ca protocols { imap = yes } sql_driver = mysql mysql scasl.ca { dbname = scasl host = localhost password = # port = 3306 user = scasl } userdb sql { iterate_query = SELECT email_username AS username, domain FROM league query = SELECT CONCAT('/var/vmail/',email_username) AS home, 5000 AS uid, 5000 AS gid FROM league WHERE email_username = '%{user|username}' } passdb sql { default_password_scheme = BLF-CRYPT query = SELECT password FROM login WHERE ID IN (SELECT ID FROM league WHERE email_username='%{user|username}') } maildir { very_dirty_syncs = yes } namespace inbox { mail_driver = maildir mail_home = /var/vmail/%{user|username} mail_inbox_path = /var/vmail/%{user|username}/Maildir/INBOX mail_path = /var/vmail/%{user|username}/Maildir inbox = yes separator = / type = private mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { } } service submission-login { inet_listener submission { } } service lmtp { unix_listener lmtp { mode = 0666 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0666 } unix_listener auth-client { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } service stats { unix_listener stats-reader { group = vmail mode = 0666 } unix_listener stats-writer { group = vmail mode = 0666 } } ssl_server { cert_file = /etc/letsencrypt/live/scasl.ca/fullchain.pem key_file = /etc/letsencrypt/live/scasl.ca/privkey.pem } protocol lda { mail_plugins = $mail_plugins } I assume I am missing a parameter that needs setting. Is it that, do I have something set incorrectly, or is it really a bug? Cheers Cam

2 2

Re: Upgrade 2.3 to 2.4 - virtual mail - dovecot-lda flags ignored
by Cam Ellison 22 May '25

22 May '25

On 2025-05-21 14:11, Odhiambo Washington wrote: > Hi Cam, > > I suffered something similar during my migration and an old post > somewhere saved the day for me: https://skeletor.org.ua/?p=2497 > I hope it helps you too. > It was worth a try, and at least has changed the focus to Exim from Dovecot: the existing lookups for identifying user@domain in Exim are not working. What he has is not significantly different from my own setup. Thank you for the link Cam

1 1

Large Server with Dovecot
by Odhiambo Washington 21 May '25

21 May '25

Hello Admins, I have at hand a task to setup Dovecot (2.4.1) to handle about 10,000 mailboxes using IMAP/POP3. It's a migration from another system. The current total storage for the mailboxes is 350GB. I believe several Mail admins are managing such systems, and bigger. What do you recommend as the baseline for the optimization Dovecot engine itself? Assuming the storage is on SSD, is there something you recommend I add to the dovecot.configuration for fast access? Indexing? Anything else? How about the system specs - CPU/RAM? Thank you in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] Hello Admins, I have at hand a task to setup Dovecot (2.4.1) to handle about 10,000 mailboxes using IMAP/POP3. It's a migration from another system. The current total storage for the mailboxes is 350GB. I believe several Mail admins are managing such systems, and bigger. What do you recommend as the baseline for the optimization Dovecot engine itself? Assuming the storage is on SSD, is there something you recommend I add to the dovecot.configuration for fast access? Indexing? Anything else? How about the system specs - CPU/RAM? Thank you in advance. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart- questions.html]

1 0

prohibit subfolders under INBOX
by dentar＠fnsheppard.com 20 May '25

20 May '25

I know this is a n00b question but I've done my diligence... Is there a way (Maildir not MBOX) to ONLY prohibit creation of folders under INBOX e.g. no INBOX.Fred allowed, but the user MAY create subfolders under other folders, e.g. Fred.Barney? We've discovered that when people create INBOX.anything it causes Outlook to go insane.

1 0