- dovecot - dovecot.org

Sdbox/mdbox purge on Public folders
by luke+dovecot＠psy.io 15 Feb '26

15 Feb '26

Hi dovecot mailing list people, After having looked through the mailing list archives, tried various search engines & asked an LLM to hallucinate an answer all to no avail, I now pose the following question to you all: For a Dovecot 2.4 system that uses mail_driver = mdbox for regular mailboxes and also has a public namespace, how might I invoke the maintenance routine of `doveadm purge` against the m.1, m.2 ... m.N files under the mail_path location? Below is the snippet of what I have in the configuration files for the public namespace: namespace public { type = public separator = / prefix = Public/ mail_path = /var/spool/mail/Public mail_index_private_path = ~/public subscriptions = yes mailbox "communal" { auto = subscribe } } Since my dovecot instance is a self-hosted matter, I am in a position to move all mail data out of there, delete any left over storage files and change the mail_driver to Maildir, if that is the easiest way to manage the risk of dbox m file sprawl/growth. Best regards, Luke

2 1

Is there a lint utility for 2.4.x configuration?
by Steve Litt 14 Feb '26

14 Feb '26

Hi all, I use a local Dovecot IMAP server to store all my emails, which I access from either Claws-Mail or Evolution. On 7/7/2025 my email stopped working, a few hours of troubleshooting led to a Dovecot problem, a few more hours led to the 2.3 to 2.4 config file changes, and the next 3 days I went without email while trying to get a working 2.4. Finally I managed to downgrade back to 2.3.x and restore the config from backup, and didn't lose too many emails. I've waited 6 months for all the dust to settle, and now I'm going to try to make a test VM (Void Linux) with 2.4.x, using phony baloney data because I don't want to lose my email capabilities again. So my first question is this: Is there a lint utility for my configuration, so that I can cut down on experimenting with 50 different variables at once and reading conflicting documentation? Here's what I know so far about lint utilities: * I know doveconf -n and dovecot -n dump non-default settings, but I don't think they can detect syntax errors. * dovecot-sysreport doesn't seem to give me info about syntax errors. * None of the doveadm commands seem to check syntax. Thanks, SteveT Steve Litt http://444domains.com

2 3

My plan for a test Dovecot 2.4.2
by Steve Litt 14 Feb '26

14 Feb '26

Hi all, I need to thoroughly test Dovecot 2.4.2 on a Virtual Machine before upgrading my real machine. Please tell me whether you think this plan is good... I install Void Linux, my Daily Driver Distro, on a Qemu VM. I also install Dovecot and Claws-Mail. Then I copy part or all of my current (2.3.21.1 (d492236fa0)) maildir to the VM, and work until I can configure a Dovecot on the VM that serves IMAP only, SSL only (ssl = required on 2.3.x), such that Claws-Mail can read, search and delete messages on the VM just the same as on 2.3.21.1 on my daily driver. I'm using few or no Dovecot features other than using it as a Maildir driven IMAP server. Maildir is a must because I write to it from Procmail, and Procmail doesn't write every kind of mail storage. Does this sound like a good, safe way to test before upgrading? Thanks, SteveT Steve Litt http://444domains.com

1 0

Clean up of dovecot.index.pvt.log files
by Sad Clouds 14 Feb '26

14 Feb '26

Hello, I'm trying to understand how to clean up old dovecot.index.pvt.log files, which are used for per user private \Seen flags. Running "doveadm purge" does not seem to remove them. I have the following public namespace configured: namespace public { type = public separator = / prefix = Public/ inbox = no hidden = no mail_driver = mdbox mail_path = /data/mailstore/%{user|domain|lower}/mail_public/mdbox mail_index_private_path = ~/mdbox/Public.index.pvt # Enable user private \Seen flags list = yes subscriptions = no # Allow users in the 'admin' group to have complete control over the namespace acl group=admin { rights = lrwstipekxa } } The problem is - if the admin deletes a public folder, the old dovecot.index.pvt.log files forever remain in all of the users' home mailbox directories, like tombstones. I see two ways around it: 1. Attempt to store private index files in the original folder's mail path, so when the folder is deleted, all files underneath it are also deleted automatically: mail_path = %{mail_directory}/Public.index.pvt/%{user|domain|lower} However there appears to be no %{mail_directory} variable which would expand to mdbox/mailboxes/<folder_name>/dbox-Mails/ and even if there was one, with public folders, for every user subscribed to this folder, there would be a user-specific directory just for the private index file. This may not scale well with thousands of users. 2. Run a cron script to list all public folders and then compare ~/mdbox/Public.index.pvt directory of each user for stale private index files which refer to non-existent folders. This can probably be done efficiently with commands like find, awk and sed, but it feels a bit cumbersome and arcane. Can anyone suggest any other or better alternatives to solve this issue? Thanks.

1 0

shared mailbox on 2.3 - will I avoid concurrency (mailbox corruption) issues if both users are on the same server
by daniel.botting＠codethink.co.uk 13 Feb '26

13 Feb '26

Hi all, Currently we are running 2.3, with a plan to move to 2.4 later this year. Our current setup is two replicating servers, I have setup on my test servers a shared name space as this is a limited requirement at this time for an assistant to view their managers inbox. I had read here: https://doc.dovecot.org/2.3/configuration_manual/shared_mailboxes/cluster_s… For two or more servers Director is required because (taken from the docs): As mentioned in Director, you can’t have multiple servers accessing the same user at the same time or it will lead into trouble. This can become problematic with shared mailboxes, because two users who are sharing a folder may run in different servers. As this is a limited requirement at this time and we'll be migrating to 2.4 where Director has been removed (I read the Docs that there is an unsupported replacement) if I have both the manager and the assistant only accessing the managers inbox via the same server will I avoid concurrency issues (ie I presume mailbox corruption). Many thanks and have a nice weekend Daniel

1 1

Rebuilding missing index/paths
by Alain Perry 13 Feb '26

13 Feb '26

Hello, First of all, I'm sorry if this isn't the best place to ask for that kind of help, in which case I'd appreciate a pointer to any adequate asynchronous channel. ------------ Some context (skip to next horizontal line if you don't care): I'm happily self-hosting a few services at home. Some months ago I decided I needed to backup my emails to my NAS, in a way that would allow me to read or search them from a web browser as easily as I did with my "cloud" mailboxes. Since I didn't find a modern yet simple webmail that could directly read a Maildir storage, I finally bit the bullet and ran a dovecot container to copy my emails to (using imapsync). Since I opted for an IMAP server, I thought I didn't need to worry too much about the storage format and used the sdbox that (I believe) was the default. Backing up worked and searching worked and I was a happy person. I used my local webmail a couple of times to search for an old email, found it, thought this was a job well done that I wouldn't have to worry too much about anymore. Then, it stopped working. I honestly don't remember what I did around that time that might have broken things or caused a data loss, but IMAP clients couldn't access my emails anymore. Since I had other more urgent matters to address, I let that problem rot. Now that I have a bit more time, I decided to try again. ------------ My problem is that, while it is clear that some data is missing, I have no clue what that data is and how (if ?) I can rebuild it. The folder structure is there in /src/vmail/username/Mail/mailboxes. I do see index(.log) and dbox-Mails/u.* in the folders, so it does look like it conforms to the doc in this regard. However, the paths returned for the mailboxes by "doveadm mailbox path" all use guid's, and do not exist on the filesystem. I don't quite understand how it got to this point, nor what I should have lying around at those paths but I wonder if it is at all possible to rebuild them so I might regain access to my archives. Is there something I can do to recover my emails ? Thanks for reaching this point, and thank you for any help and/or pointers you might be able to provide. Regards,

2 2

fts-flatcurve change index location
by grabsoon＠gmail.com 12 Feb '26

12 Feb '26

hi is there any way to change location ONLY FOR flatcurve indexes all I want is to write fts-flatcurve directories outside ~/Maildir path I do not want to change location of: dovecot.list.index.log dovecot.mailbox.log dovecot-uidvalidity Only for flatcurve indexes. when i set mail_index_path = ~/Indexes all indexes are saved to this new location, not just flatcurve i'm afraid that changing mail_index_path value on production environment is very riski Thanks

2 1

Re: 2.4: fts flatcurve remove?
by Michael Slusarz 11 Feb '26

11 Feb '26

> On 02/10/2026 3:07 PM MST Bjoern Franke via dovecot <dovecot(a)dovecot.org> wrote: > > in the pre release docs > https://doc.dovecot.org/main/core/man/doveadm-fts.1.html#fts-flatcurve-remo… > > doveadm fts flatcurve remove > > was mentioned, but in https://doc.dovecot.org/2.4.2/ it's gone. ? https://doc.dovecot.org/2.4.2/core/man/doveadm-fts.1.html#fts-flatcurve-rem…

2 1

2.4: fts flatcurve remove?
by Bjoern Franke 11 Feb '26

11 Feb '26

Hi, in the pre release docs https://doc.dovecot.org/main/core/man/doveadm-fts.1.html#fts-flatcurve-remo… doveadm fts flatcurve remove was mentioned, but in https://doc.dovecot.org/2.4.2/ it's gone. So, how to remove the flatcurve data again? Simply a find ...--delete? Regards Bjoern

1 0

doveadm quota get issue in lcx container
by Kim Haverblad 09 Feb '26

09 Feb '26

Hi, I'm having some issues getting the quota plugin to work properly. Based on the error message, it looks like the plugin doesn't fully cooperate with Proxmox mount points for LXC containers. It appears to be referencing the secondary disk directly as /dev/nvme1n1p1, rather than the actual mount point inside the container. Here's the full error message: mlgate:/usr/lib/systemd/system# doveadm quota get -u [1]some(a)example.com doveadm([2]some(a)example.com): Error: Failed to get quota resource STORAGE: quota-fs: quotactl(Q_GETQUOTA, /dev/nvme1n1p1) failed: No such file or directory Are there any parameters that need to be adjusted to make this work, or is there an alternative plugin that would handle this setup better? //Kim

2 1

In an email client, tasks accumulate and are queued using the IMAP protocol
by Lafiel Elentari 08 Feb '26

08 Feb '26

Hello. By default, the email client uses 4 IMAP connections. However, tasks often hang, and changes to email statuses made via the web interface are not reflected in the client. I tried enabling imap-hibernate, which cleared the queue, but the issue with updating email statuses persisted. Is this a problem with the email client or the Dovecot server? -- Best regards, Lafiel Elentari mailto:lafiel@elven.pw

1 0

Configuring the Outbox folder in an email client
by Lafiel Elentari 08 Feb '26

08 Feb '26

Hello. The Bat! email client, when using the IMAP protocol, comes with three pre-defined folders: "Outbox," "Sent Mail," and "Trash." While setting up the "Sent Mail" and "Trash" folders is simple, configuring the "Outbox" folder may be less obvious. How should it be set up? Is it correct to designate the Drafts folder for this purpose? -- Best regards, Lafiel Elentari mailto:lafiel@elven.pw

1 0

doveadm sync panic
by Roberto Puzzanghera 07 Feb '26

07 Feb '26

I am experiencing a consistent panic while using doveadm sync on Dovecot v2.4.2. The panic occurs during a synchronization attempt between two servers. It appears that the sync panics when entering in a .Junk.Something folder. Any idea? I attach the log lines and my configuration Any help would be appreciated Roberto # doveadm -D sync -u postmaster@domain-tld tcp:10.0.0.24:12345 [...] Feb 06 22:39:46 doveadm(postmaster(a)domain.tld): Panic: file hash.c: line 252 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) Feb 06 22:39:46 doveadm(postmaster(a)domain.tld): Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x40) [0x7f7bba941860] -> libdovecot.so.0(backtrace_get+0x22) [0x7f7bba9419b2] -> libdovecot.so.0(+0x14fc12) [0x7f7bba94fc12] -> libdovecot.so.0(+0x14fc41) [0x7f7bba94fc41] -> libdovecot.so.0(+0x72375) [0x7f7bba872375] -> libdovecot.so.0(+0x732c3) [0x7f7bba8732c3] -> doveadm(dsync_mailbox_tree_build_name128_hash+0x9a) [0x55e5f58108ba] -> doveadm(dsync_mailbox_tree_fill+0x750) [0x55e5f5811bb0] -> doveadm(dsync_brain_mailbox_trees_init+0x192) [0x55e5f58055b2] -> doveadm(dsync_brain_master_init+0x191) [0x55e5f5801f51] -> doveadm(+0x3544b) [0x55e5f57e644b] -> doveadm(+0x3794e) [0x55e5f57e894e] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x244) [0x55e5f57e9684] -> doveadm(doveadm_cmdline_run+0x593) [0x55e5f57fd473] -> doveadm(doveadm_cmdline_try_run+0xba) [0x55e5f57fc67a] -> doveadm(main+0x2fd) [0x55e5f57dacfd] -> libc.so.6(__libc_start_main+0xcd) [0x7f7bba4fd03d] -> doveadm(_start+0x2a) [0x55e5f57db0ea] # doveconf -n # 2.4.2 (): /usr/local/dovecot/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.15.3 x86_64 Slackware 15.0 # Hostname: qt dovecot_config_version = 2.4.2 auth_allow_cleartext = yes auth_allow_weak_schemes = yes auth_default_domain = mydomain.tld auth_mechanisms = plain login auth_socket_path = ../../../var/run/dovecot/auth-userdb debug_log_path = /var/log/dovecot/dovecot.log default_login_user = vpopmail doveadm_password = # hidden, use -P to show it dovecot_storage_version = 2.4.2 first_valid_gid = 89 first_valid_uid = 89 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes hostname = mydomain.tld last_valid_gid = 89 last_valid_uid = 89 listen { * = yes :: = no } log_debug = category=mail log_path = /var/log/dovecot/dovecot.log mail_access_groups = 89 mail_driver = maildir mail_gid = 89 mail_path = ~/Maildir mail_plugins { notify = yes fts = no fts_solr = no quota = yes } mail_privileged_group = 89 mail_uid = 89 mailbox_list_validate_fs_names = no passdb_default_password_scheme = SHA512-CRYPT postmaster_address = postmaster(a)mydomain.tld protocols { imap = yes pop3 = yes sieve = yes } sendmail_path = /var/qmail/bin/sendmail sql_driver = mysql ssl_min_protocol = TLSv1.1 passdb sql { query = SELECT CONCAT(vpopmail.pw_name, '@', vpopmail.pw_domain) AS user, vpopmail.pw_passwd AS password, vpopmail.pw_dir AS userdb_home, 89 AS userdb_uid, 89 AS userdb_gid, CONCAT(REPLACE(SUBSTRING_INDEX(vpopmail.pw_shell, 'S', 1), 'NOQUOTA', '0'), 'B') AS userdb_quota_storage_size FROM vpopmail LEFT JOIN aliasdomains ON aliasdomains.alias='%{user | domain}' LEFT JOIN limits ON limits.domain='%{user | domain}' WHERE vpopmail.pw_name='%{user | username}' AND (vpopmail.pw_domain='%{user | domain}' OR vpopmail.pw_domain=aliasdomains.domain) AND ('%{local_port}'!='995' OR !(vpopmail.pw_gid & 2)) AND ('%{remote_ip}'!='10.0.0.4' OR !(vpopmail.pw_gid & 4)) AND ('%{remote_ip}'='10.0.0.4' OR '%{local_port}'!='993' OR !(vpopmail.pw_gid & 8)) AND ('%{remote_ip}'!='10.0.0.4' OR COALESCE(disable_webmail,0)!=1) AND ('%{remote_ip}'='10.0.0.4' OR COALESCE(disable_imap,0)!=1) } userdb prefetch { driver = prefetch } userdb sql { iterate_query = SELECT CONCAT(pw_name,'@',pw_domain) AS user FROM vpopmail query = SELECT vpopmail.pw_dir AS home, 89 AS uid, 89 AS gid, CONCAT(REPLACE(SUBSTRING_INDEX(vpopmail.pw_shell, 'S', 1), 'NOQUOTA', '0'), 'B') AS quota_storage_size FROM vpopmail WHERE vpopmail.pw_name='%{user | username}' AND vpopmail.pw_domain='%{user | domain}' } namespace inbox { inbox = yes mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { autoexpunge = 30d special_use = "\\Junk" } mailbox Junk.TeachSpam { auto = subscribe autoexpunge = 30d } mailbox Junk.TeachNotSpam { auto = subscribe autoexpunge = 30d } mailbox Trash { autoexpunge = 60d special_use = "\\Trash" quota_storage_extra = 100M } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } protocol !indexer-worker { mail_vsize_bg_after_count = 100 } maildir { broken_filename_sizes = yes } service imap-login { inet_listener imap { } inet_listener imaps { } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service imap { executable = imap postlogin } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login ../../etc/scripts/dovecot_postlogin.sh user = vpopmail unix_listener postlogin { group = vchkpw mode = 0660 user = vpopmail } } service auth { user = $SET:default_internal_user unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service auth-worker { user = $SET:default_internal_user } service stats { unix_listener stats-reader { group = vchkpw mode = 0660 user = vpopmail } unix_listener stats-writer { group = vchkpw mode = 0660 user = vpopmail } } protocol lda { mail_plugins { sieve = yes mail_log = yes } } protocol imap { mail_plugins { notify = yes mail_log = yes imap_sieve = yes imap_quota = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol pop3 { mail_plugins { notify = yes mail_log = yes } } language en { default = yes } quota "User quota" { driver = count storage_grace = 10M quota_warning overquota { quota_storage_percentage = 100 execute quota-warning { args = 100 %{user} } } quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-85 { quota_storage_percentage = 85 execute quota-warning { args = 85 %{user} } } } service quota-warning { executable = script ../../etc/scripts/quota-warning.sh user = vpopmail unix_listener quota-warning { group = vchkpw mode = 0660 user = dovenull } } sieve_script personal { active_path = ~/.sieve/dovecot.sieve driver = file path = ~/.sieve } sieve_script move-spam { cause = delivery path = /usr/local/dovecot/etc/sieve/move-spam.sieve type = before } mysql 10.0.0.112 { dbname = vpopmail_test password = # hidden, use -P to show it user = vpopmail_test } ssl_server { cert_file = /etc/ssl/certs/dovecot.pem key_file = /etc/ssl/private/dovecot.pem }

2 1

About mail_inbox_path and mail location
by Aki Tuomi 06 Feb '26

06 Feb '26

Hi! We've been noticing that many people are configuring mail_inbox_path. I assume that for most people this is because debian decided to include it in their default config, so that it would use /var/mail boxes for user INBOXes. If your inbox *does not* reside in some weird location, you should *not* set this setting to any value, instead you can either ensure it's commented out, or set to empty value. IN PARTICULAR, IT IS **NOT** REQUIRED SETTING. Setting it to some random weird value like '.' will just cause Problems, setting it to $MAIL_HOME/ or something else will just be either pointless or cause problems. Some most common conversions (please adjust to your environment) mail_home= /home/vmail/%u => mail_home = /home/vmail/%{user} mail_home = /home/vmail/%d/%u => mail_home = /home/vmail/%{user|domain}/%{user|username} or some variant of this. mail_location = maildir:~/ => mail_path = ~/ mail_driver = maildir mail_location = maildir:/var/srv/foo/%d/%u => mail_path = /var/srv/foo/%{user|domain}/%{user|username} mail_driver = maildir In addition you might want to convert INDEX=~/.index => mail_index_path=~/.index CONTROL=~/.control => mail_control_path=~/.control LAYOUT=fs => mailbox_list_layout=fs A minimal working config is mail_home=/home/vmail/%{user} mail_driver=maildir mail_path=~/maildir mail_uid=vmail mail_gid=vmail ## If you have settings like namespace other { location = maildir:/foo/bar } this converts into namespace other { mail_path = /foo/bar # optional, if this is matches your top level mail_driver = maildir } Hope this clears out some of the confusion. Aki

3 4

Pigeonhole 2.4.2 build failure: cannot find -ldovecot-ldap even without LDAP support
by adesh＠backuply.com 04 Feb '26

04 Feb '26

I'm building Pigeonhole 2.4.2 (fresh tarball from https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: > > CC ext-fileinto.lo > CC ext-reject.lo > ... > CC sieve.lo > CCLD libdovecot-sieve.la > /opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: cannot find -ldovecot-ldap > collect2: error: ld returned 1 exit status > make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1 NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no Confirmed no openldap-devel influencing detection (or temporarily removed) Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot.

1 0

How to let postfix use dovecot to check quotas for virtual aliases
by jerome＠jolimont.fr 04 Feb '26

04 Feb '26

Hi all. Receiving an email for an alias, I got those errors: <alias(a)domain.tld>Recipient address rejected: Unknown user; I realized this happened when postfix queries dovecot about user quota. Basically, what happens is that postfix queries dovecot using the virutal alias as name, not the virtual user. And since dovecot doesn't find a user under that name, it returns an error and postfix rejects the mail. ### Configuration I followed the docs at https://doc.dovecot.org/latest/core/plugins/quota.html when setting up the server. /etc/postfix/main.cf ``` smtpd_recipient_restrictions = check_policy_service unix:private/quota-status ``` /etc/dovecot/conf.d/90-quota.conf ``` service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { user = postfix } client_limit = 1 } ``` /etc/dovecot/conf.d/auth-sql.conf.ext ``` userdb sql { query = SELECT '/var/mail/vmail/'||maildir AS home, 110 AS uid, 113 AS gid, quota || 'B' AS quota_storage_size FROM mailbox WHERE username = '%{user}' iterate_query = SELECT username FROM mailbox } ``` ### Solution 1: modify user query This issue was reported and analyzed here: https://dovecot.dovecot.narkive.com/FtjhqCuU/postfix-aliases-with-quota-sta… and there: https://github.com/docker-mailserver/docker-mailserver/issues/2091 A comment (https://dovecot.dovecot.narkive.com/FtjhqCuU/postfix-aliases-with-quota-sta…) suggests to modify the SQL query to also look for aliases. I modified my query like so: ``` query = SELECT '/var/mail/vmail/'||maildir AS home, 110 AS uid, 113 AS gid, quota || 'B' AS quota_storage_size FROM mailbox JOIN alias ON mailbox.username = alias.goto WHERE alias.address = '%{user}'; ``` and it seemed to work. I mean, I can query user quota with an alias: doveadm quota get -u alias(a)domain.tld but the iterate query ignores aliases so doveadm quota get -A only lists users, not aliases (which is what I want) and I can't IMAP login using aliases (which is also what I want) since I didn't modify the password query either. I find this configuration slightly inconsistent: the user query returns aliases, not the iterate query. Is the user query really meant to return aliases as well? Also, I realized this query is broken for alias to multiple addresses. I'd get the following error: Recipient address rejected: Unknown user Surprisingly, it seems to only affect messages from an external source to an alias pointing to an external mailbox. Messages submitted locally (and perhaps messages sent to an alias to local destinations only, I'm not sure) were not affected. ### Solution 2: ignore aliases, it will fail later anyway On another server, I had this configuration: /etc/dovecot/conf.d $ vi 90-quota.conf (Don't put this in `plugin` on dovecot 2.4+.) ``` plugin { quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" } ``` The alias is unknown so the check returns DUNNO and postfix lets the message pass (postfix log read "delivered via spamassassin service") but then it fails at sieve stage when writing the message: sieve: msgid=<xxx>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) The result is what is expected: the message is rejected due to mailbox full. But I don't think it was intended to work this way. And since the message is quota-rejected at sieve stage, I could remove the `check_policy_service` line since it will be rejected for a virtual user (not alias) as well anyway. Right? ### Question What is the recommended configuration to let postfix use dovecot to check quotas for virtual aliases? I couldn't find documentation for this specific use case. Ideally, postfix would query using the resolved user, not the alias. Can this be achieved? Should I remove the check and rely on the fact that writing the message fails at a later step anyway? Thanks. (Question also posted on ServerFault: https://serverfault.com/questions/1197914/how-to-let-postfix-use-dovecot-to…)

3 3

Question about behavior I wound up patching 2.4 to fix
by Andy Baugh 03 Feb '26

03 Feb '26

Howdy, I had a complaint from RoundCube users that the maildir quotas weren't accurate when they logged in after something wound up deleting their maildirsize file on Dovecot 2.4. Since that does IMAP GETQUOTAROOT to fetch the info, I figured we're probably not triggering quota recalculation on maildir like we did on dovecot 2.3 (which doesn't seem to have this issue). Wound up writing a patch to src/plugins/imap-quota/imap-quota-plugin.c to add a hook into cmd_setquota which looks to see if imap_quota is enabled, and if so trigger maildir quota recalculation on IMAP login. This does work to solve the reported issue, but I'm ultimately more curious whether this could even be considered a regression, as per your own documentation for the quota plugin: > Once the maildirsize reaches 5120 bytes, the quota is recalculated and the file is recreated. This makes sure that if quota happens to be broken (e.g. externally deleted files) it won't stay that way forever. This suggests to me that the behavior I'm "fixing" a regression in is actually working "as designed." As such my question would be: Is there a good reason I *should not* be doing this? I would of course be happy to share this patch with the list, but I'm not going to bother if it's actually something the maintainers are not interested in due to it not being a good idea in the first place. Thanks, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

1 0

Unexpected Configuration Error `Unknown setting: ssl_server_cert_file`
by David Weingut 02 Feb '26

02 Feb '26

Hello, I upgraded from Debian 12 to 13 and thereby also from dovecot 2.3 to 2.4. Now I am facing a weird error in dovecot. The actual error is the following # doveconf -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 22: ssl_server_cert_file : Unknown setting: ssl_server_cert_file The corresponding entry in my config is ssl = yes ssl_server_cert_file = /etc/letsencrypt/live/example.com/fullchain.pem ssl_server_key_file = /etc/letsencrypt/live/example.com/privkey.pem I am sorry if I missed something in the archives but I did not find any similar posts. Is there something I am missing here and what would be further required to debug this? Best, David Hello, I upgraded from Debian 12 to 13 and thereby also from dovecot 2.3 to 2.4. Now I am facing a weird error in dovecot. The actual error is the following # doveconf -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 22: ssl_server_cert_file : Unknown setting: ssl_server_cert_file The corresponding entry in my config is ssl = yes ssl_server_cert_file = /etc/letsencrypt/live/example.com/fullchain.pem ssl_server_key_file = /etc/letsencrypt/live/example.com/privkey.pem I am sorry if I missed something in the archives but I did not find any similar posts. Is there something I am missing here and what would be further required to debug this? Best, David

2 3

Compiling Dovecot 2.4 on OpenBSD
by Joel Mawhorter 02 Feb '26

02 Feb '26

I'm writing to see if anyone has had success compiling Dovecot 2.4 on OpenBSD. I can't seem to find any documentation that lists prerequisites. At the moment, the 2.4.2 source tarball from the Dovecot site does not seem to compile on my OpenBSD 7.8 system and the error message is not very helpful. I'm unsure if this is just a problem of some required package not being installed. If anyone could point me to info to help move forward, I would appreciate that. Joel

6 19

How can these MBOX files on a Dovecot-based IMAP server be converted to PST for access in Outlook?
by Rawnie Dolgato 31 Jan '26

31 Jan '26

MBOX files stored on a Dovecot-based IMAP server cannot be accessed directly in Microsoft Outlook, because Outlook does not support the MBOX file format. Outlook works with PST files, so a conversion step is mandatory. While it is technically possible to convert MBOX files to EML and then import them into Outlook, this approach is impractical for real-world scenarios. It is time-consuming, difficult to manage, and not suitable when handling bulk mailboxes or large datasets, which is typically the case with server-level backups. For this reason, an MBOX to PST conversion tool (such as BitRecover MBOX to PST Converter) is recommended. It supports bulk MBOX data, preserves folder structure and metadata, and allows selective migration based on criteria like date, sender, or subject. The process runs 100% offline, ensuring data security, and works on Windows, macOS, and Linux, making it suitable for both single and multi-mailbox migrations.

2 1

Meaning of auth-worker disconnected message and relation to LMTP 451 errors on Ubuntu
by Kim Haverblad 31 Jan '26

31 Jan '26

Hi dovecot list, I’m troubleshooting an LMTP delivery issue with Dovecot and would appreciate clarification on the meaning and impact of the following log message, which appears repeatedly during delivery attempts: auth-worker(2961): Debug: conn unix:auth-worker (pid=2948,uid=107): Disconnected: Connection closed (fd=-1) *Environment* * OS: Ubuntu (latest LTS, fully up to date) * Dovecot: distribution package (current version for Ubuntu) * MTA: Postfix * Delivery: LMTP to Dovecot * User database: MySQL (userdb lookup succeeds) * Mail storage: Maildir * Quotas: enabled via userdb (quota_rule) *Context* * LMTP accepts the recipient and completes userdb lookup successfully. * The mailbox path, uid, gid, and quota are correctly returned. * Postfix later receives a 451 4.3.0 Temporary internal error after the DATA phase. * The above auth-worker ... Disconnected: Connection closed (fd=-1)message appears around the same time. *Questions* 1. Is this Disconnected: Connection closed (fd=-1) message expected/normal behavior for auth-worker processes once a lookup is complete? 2. Under what circumstances would this indicate a real problem versus a harmless connection teardown? 3. Could this message itself contribute to, or explain, LMTP 451 4.3.0 Temporary internal error responses? 4. Are there specific auth-worker, LMTP, or debug settings recommended to determine whether this disconnect is abnormal? So far, authentication and userdb lookups appear clean, and there are no explicit permission or quota errors logged, which makes it unclear whether this message is relevant to the delivery failure or simply informational. Any clarification on how to interpret this log entry — and how to confirm whether it is benign or problematic — would be greatly appreciated. Kind Regards, Kim Hi dovecot list, I'm troubleshooting an LMTP delivery issue with Dovecot and would appreciate clarification on the meaning and impact of the following log message, which appears repeatedly during delivery attempts: auth-worker(2961): Debug: conn unix:auth-worker (pid=2948,uid=107): Disconnected: Connection closed (fd=-1) Environment o OS: Ubuntu (latest LTS, fully up to date) o Dovecot: distribution package (current version for Ubuntu) o MTA: Postfix o Delivery: LMTP to Dovecot o User database: MySQL (userdb lookup succeeds) o Mail storage: Maildir o Quotas: enabled via userdb (quota_rule) Context o LMTP accepts the recipient and completes userdb lookup successfully. o The mailbox path, uid, gid, and quota are correctly returned. o Postfix later receives a 451 4.3.0 Temporary internal error after the DATA phase. o The above auth-worker ... Disconnected: Connection closed (fd=-1) message appears around the same time. Questions 1. Is this Disconnected: Connection closed (fd=-1) message expected/normal behavior for auth-worker processes once a lookup is complete? 2. Under what circumstances would this indicate a real problem versus a harmless connection teardown? 3. Could this message itself contribute to, or explain, LMTP 451 4.3.0 Temporary internal error responses? 4. Are there specific auth-worker, LMTP, or debug settings recommended to determine whether this disconnect is abnormal? So far, authentication and userdb lookups appear clean, and there are no explicit permission or quota errors logged, which makes it unclear whether this message is relevant to the delivery failure or simply informational. Any clarification on how to interpret this log entry -- and how to confirm whether it is benign or problematic -- would be greatly appreciated. Kind Regards, Kim

2 4

sieve auto-creation/subscription - Thunderbird cannot re-arrange folders
by listy 31 Jan '26

31 Jan '26

Hi guys. In Thunderbird auto-subscribed folders - in my case a path with sub-folders - cannot be moved around, meaning top-bottom order. Parent folders Thunderbird shows in cursive and sub-folders (targets for sieve fules) are shown "normal" It seems impossible to re-arrange top/parent folders - but every other folder, top or not, which is not auto created & auto subscribed, Thunderbird can move around as expected. Anybody seen, anybody knows this and knows a way to "fix" it? many thanks, L.

2 4

How can these MBOX files on a Dovecot-based IMAP server be accessed in Outlook?
by Rawnie Dolgato 31 Jan '26

31 Jan '26

MBOX files stored on a Dovecot-based IMAP server cannot be accessed directly in Microsoft Outlook, because Outlook does not support the MBOX file format. Outlook works with PST files, so a conversion step is mandatory. While it is technically possible to convert MBOX files to EML and then import them into Outlook, this approach is impractical for real-world scenarios. It is time-consuming, difficult to manage, and not suitable when handling bulk mailboxes or large datasets, which is typically the case with server-level backups. For this reason, an MBOX to PST conversion tool (such as BitRecover MBOX to PST Converter) is recommended. It supports bulk MBOX data, preserves folder structure and metadata, and allows selective migration based on criteria like date, sender, or subject. The process runs 100% offline, ensuring data security, and works on Windows, macOS, and Linux, making it suitable for both single and multi-mailbox migrations.

1 0

Subscriptions file broken in 2.4.x against 2.3.21 (V2)
by DaLiV 31 Jan '26

31 Jan '26

Hello! /eror at update from 2.3.21 to 2.4.2 / Maildir+ currently is broken. posix - so main hierarchy separator is "/" for file "subscriptions" in versions 2.4 lost possibility to recognize v2 format also as writes v1 instead with header V2 ... so all users will lost their subscriptions and must re-subscribe depsite in folder persist file in format V2 (tab separated) ... on subscribe that appends subscriptions delimeted with "/" namespace Public { type = public prefix = Public/ mail_driver = maildir mail_path = /var/mail/Public/%{auth_user|domain}/ mail_index_private_path = pvt.idx/Public mailbox_list_layout=fs separator = / subscriptions = no list = children } seems not taking in account separators and using "." instead of "/" slighlz debugged - in subsfile_set_subscribed - that gets on subscription for processing : "name"="Public/TEST" but "separator" = "." therefore splits not and decides that is version "0" ... so - somewhere deeper or possible need additional configuration Hello! eror at update from 2.3.21 to 2.4.2 Maildir+ currently is broken. posix - so main hierarchy separator is "/" for file "subscriptions" in versions 2.4 lost possibility to recognize v2 format also as writes v1 instead with header V2 ... so all users will lost their subscriptions and must re-subscribe depsite in folder persist file in format V2 (tab separated) ... on subscribe that appends subscriptions delimeted with "/" namespace Public { type = public prefix = Public/ mail_driver = maildir mail_path = /var/mail/Public/%{auth_user|domain}/ mail_index_private_path = pvt.idx/Public mailbox_list_layout=fs separator = / subscriptions = no list = children } seems not taking in account separators and using "." instead of "/" slighlz debugged - in subsfile_set_subscribed - that gets on subscription for processing : "name"="Public/TEST" but "separator" = "." therefore splits not and decides that is version "0" ... so - somewhere deeper or possible need additional configuration

1 0

New Member
by Jochen Becker 30 Jan '26

30 Jan '26

Hi all My name is Jochen and I have joined the list in order to get some first hand advice on my journey of migrating my SOHO mail server from 2.3 to 2.4. I set up my first server back in 2005 or so. OpenSuse and Cyrus IMAP. That went fine until all of a sudden, some 8 or 10 years ago, Suse no longer supported Cyrus directly. So I switched over to Dovecot and did not regret it. My current production server (OpenSuse Leap 16, Dovecot 2.4.2) is running fine after a recent migration. But the HW is ageing and disk usage is getting close to 80%. So I got new and larger HW. I run OpenSuse Leap 16.0 and Dovecot 2.4.2 on it. As I ran into unsurmountable problems there (could not move mail_path away from /var/mail), I decided to set up a test system under Ubuntu server 25.10. There I have got Dovecot running much better, but still, I ran into problems I could not solve for quite some time now. So here I am. I will start with questions about Dovecot on Ubuntu - my test system - because there I hope my mistakes are not as bad. Aki, thanks for taking me on board. Kind regards Jochen Mainz, Germany

2 1

Re: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Jeffrey Böhm 29 Jan '26

29 Jan '26

Hi, I’m seeing the same issue after upgrading to Dovecot 2.4.2. I reproduced it with both the Alpine Linux build and the official Dovecot Docker image referenced at [1]. In my case, the crash correlates strongly with iOS devices auto-deleting older messages from the Trash folder. As Christian described, it starts after a larger number of IMAP MOVE operations. Key finding: when I disable the imap_sieve extensions, the crashes stop. Personal Sieve rules continue to work as expected, so the problem appears to be specific to imap_sieve (or its interaction with frequent MOVE operations). > sieve_plugins { > sieve_imapsieve = no > } > > protocol imap { > mail_plugins { > imap_sieve = no > imap_filter_sieve = no > } > } My configuration with the enabled imap_sieve extension is located at [2]. Kind regards Jeff [1]: https://github.com/dovecot/docker [2]: https://github.com/jeboehm/docker-mailserver/blob/7433443ebd4af1c422cb4030c…

1 0

Migration to 2.4: Howto get the quota dict writing into a second DB
by volker.jaenisch＠inqbus.de 29 Jan '26

29 Jan '26

Dear Dovecot wizards! I have a question concerning the migration from 2.3.4 to 2.4.1. On 2.3.4 I had the following config dict { sql_store_user_quota = pgsql:/etc/dovecot/dovecot-sql-store-user_quota.conf } With /etc/dovecot/dovecot-sql-store-user_quota.conf: connect = host=127.0.0.1 port=5433 dbname=dddd user=uuuu password=pppp: map { pattern = priv/quota/storage table = fill_user username_field = username value_field = bytes } map { pattern = priv/quota/messages table = messages_user username_field = username value_field = messages } On 2.4.1 I tried dict_map priv/quota/storage { sql_table = emailaddress_fill username_field = emailaddress dict_map_value_field quota_bytes { type = uint } } dict fill { sql_driver = pgsql pgsql pg_mc2 { parameters { dbname = dddd host = hhhh password = ppppp user = uuuuu } } } But it is doing nothing. Am sure I am missing something here (I guess howto connect these config snippets). Any help appreciated. Cheers, Volker -- =========================================================== inqbus Scientific Computing GmbH Dr. Volker Jaenisch Hungerbichlweg 3 +49 (8860) 9222 7 92 86977 Burggen https://inqbus.de ===========================================================

4 8

Pigeonhole 2.4.2 build failure: cannot find -ldovecot-ldap even without LDAP support
by Adesh 29 Jan '26

29 Jan '26

Hi, I'm building Pigeonhole 2.4.2 (fresh tarball from https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: > _CC ext-fileinto.lo_ > _CC ext-reject.lo_ > _..._ > _CC sieve.lo_ > _CCLD libdovecot-sieve.la_ > _/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: > cannot find -ldovecot-ldap_ > _collect2: error: ld returned 1 exit status_ > _make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1_ NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: * make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no * Confirmed no openldap-devel influencing detection (or temporarily removed) * Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot. -- Thanks and Regards, Adesh Rane Hi, I'm building Pigeonhole 2.4.2 (fresh tarball from [1]https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.…) against Dovecot 2.4.2 compiled without LDAP support (--without-ldap during Dovecot configure, no libdovecot-ldap.so present). The build fails at linking libdovecot-sieve.la: CC ext-fileinto.lo CC ext-reject.lo ... CC sieve.lo CCLD libdovecot-sieve.la /opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: cannot find -ldovecot-ldap collect2: error: ld returned 1 exit status make[4]: *** [Makefile:757: libdovecot-sieve.la] Error 1 NEWS confirms the fix is included: - sieve-ldap-storage: Fix compile without LDAP. Steps tried: o make distclean && ./configure --with-dovecot=/usr/local/apps/dovecot --with-ldap=no o Confirmed no openldap-devel influencing detection (or temporarily removed) o Fresh source extract, no prior build artifacts Configure output shows LDAP as disabled (or paste relevant lines if different). Is there an additional flag needed, or is this a regression/edge case in 2.4.2? Any patch or workaround would be appreciated. System: RHEL-like (devtoolset-11/gcc 11), Dovecot prefix /usr/local/apps/dovecot. -- Thanks and Regards, Adesh Rane References Visible links 1. https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.2.tar.gz

1 0

Bug-Report config handling with named filters
by Patrick Cernko 27 Jan '26

27 Jan '26

Hello Dovecot devs, I think I found a bug in Dovecot's config handling. The semantic of e.g. ssl_server { cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem key_file = /etc/ssl/private/ssl-cert-snakeoil.key } in a config file is slightly different to ssl_server_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_server_key_file = /etc/ssl/private/ssl-cert-snakeoil.key If the directives are used in the second (flat) format, they can be overridden by doveadm (or the sieve* binaries), if the first (structured) version is used, they cannot be overridden. Even if the flat format is used in a "local" config file to override the default config as installed by the CE Debian package (which uses the structured), overriding the value of ssl_server_key_file on the doveadm cmdline is not possible. This prevents unprivileged users to use doveadm or the sieve* binaries as they cannot the tools will fail with an access error for the key file, even if the users knows and uses "-o ssl_server_key_file=''" or "-o ssl_server/key_file=''". I did not test overriding other settings in structured format, but I assume, that the issue is also present there. That means, settings that are specified in the structured format CANNOT be overridden with the "-o" cmdline option. I would like to ask you, to fix this issue in one of the next releases, please! Best regards, P.S.: It would be nice, if doveconf would also get a "-o" option to test overrides. -- Patrick Cernko <pcernko(a)mpi-klsb.mpg.de> +49 681 9325 5815 Joint Scientific IT and Technical Service Max-Planck-Institute für Informatik & Softwaresysteme

1 0

mountpoint.c:264:33: error: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration]
by Andrew Watkins 27 Jan '26

27 Jan '26

Hello, I am trying to build dovecot-2.4.2 on Solaris 11.4 with gcc 14.2 and getting the following error: CC module-dir.lo CC mountpoint.lo mountpoint.c: In function ‘mountpoint_iter_next’: mountpoint.c:264:33: error: implicit declaration of function ‘makedev’ [-Wimplicit-function-declaration] 264 | iter->mnt.dev = makedev(ent.ext.mnt_major, ent.ext.mnt_minor); | ^~~~~~~ *** Error code 1 The following command caused the error: echo " CC " mountpoint.lo;/bin/sh ../../libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -std=gnu11 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT mountpoint.lo -MD -MP -MF .deps/mountpoint.Tpo -c -o mountpoint.lo mountpoint.c make: Fatal error: Command failed for target `mountpoint.lo' Current working directory /var/tmp/dovecot-2.4.0/src/lib *** Error code 1 I have been using dovecot for a long time and haven't seen this before. I just checked and rebuilt dovecot-2.3.21 and had no problems. Any ideas? Thanks, Andrew Hello, I am trying to build dovecot-2.4.2 on Solaris 11.4 with gcc 14.2 and getting the following error: CC module-dir.lo CC mountpoint.lo mountpoint.c: In function `mountpoint_iter_next': mountpoint.c:264:33: error: implicit declaration of function `makedev' [-Wimplicit-function-declaration] 264 | iter->mnt.dev = makedev(ent.ext.mnt_major, ent.ext.mnt_minor); | ^~~~~~~ *** Error code 1 The following command caused the error: echo " CC " mountpoint.lo;/bin/sh ../../libtool --silent --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -std=gnu11 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -mfunction-return=keep -mindirect-branch=keep -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -MT mountpoint.lo -MD -MP -MF .deps/mountpoint.Tpo -c -o mountpoint.lo mountpoint.c make: Fatal error: Command failed for target `mountpoint.lo' Current working directory /var/tmp/dovecot-2.4.0/src/lib *** Error code 1 I have been using dovecot for a long time and haven't seen this before. I just checked and rebuilt dovecot-2.3.21 and had no problems. Any ideas? Thanks, Andrew

2 5

Blocking with RBLs
by Lefteris Tsintjelis 27 Jan '26

27 Jan '26

Hi, Is there a way to block with RBLs? I already have a really good and very trustworthy and accurate internal one that works extremely well and fast with my SMTP servers for years now. Is there a way to apply the same RBL to dovecot? Logs are really going crazy as they stopped with SMTP and started with IMAP for a while now since dovecot is wide open to these attacks. Anvil does not seem to do much here. I am looking for solutions other than fail2ban or anything similar to this. Lefteris

11 26

Possible Bug: Dovecot LDAP userdb search ignores DN template
by Esteban Heschung 25 Jan '26

25 Jan '26

Hello Dovecot Team, I am currently using *Dovecot 2.4.1* with *Windows Active Directory* via LDAPS (self-signed certificate). I have configured a *bind DN template* for authentication. Authentication works perfectly. However, when Dovecot tries to perform the *userdb lookup*, it seems to *ignore the DN template*. Instead, it attempts to perform a search using the *ldap_base and filter* I configured... According to the documentation, the *bind DN template should be sufficient*, and Dovecot should not need to perform this search. Additionally, if I *remove the ldap_base or filter fields*, Dovecot fails with an error and cannot perform the lookup at all. This results in doveadm user failing, even though authentication succeeds. Could this be a bug in the way Dovecot handles bind_userdn for LDAP userdb lookups? I would appreciate any guidance or confirmation on this behavior. Thank you for your help. Hello Dovecot Team, I am currently using Dovecot 2.4.1 with Windows Active Directory via LDAPS (self-signed certificate). I have configured a bind DN template for authentication. Authentication works perfectly. However, when Dovecot tries to perform the userdb lookup, it seems to ignore the DN template. Instead, it attempts to perform a search using the ldap_base and filter I configured... According to the documentation, the bind DN template should be sufficient, and Dovecot should not need to perform this search. Additionally, if I remove the ldap_base or filter fields, Dovecot fails with an error and cannot perform the lookup at all. This results in doveadm user failing, even though authentication succeeds. Could this be a bug in the way Dovecot handles bind_userdn for LDAP userdb lookups? I would appreciate any guidance or confirmation on this behavior. Thank you for your help.

3 5

YESCRYPT_COST_FACTOR=11 not working
by Matthias Bodenbinder 25 Jan '26

25 Jan '26

Hi, dovecot does not work with ENCRYPT_METHOD YESCRYPT and YESCRYPT_COST_FACTOR=11. I have tested with 2.4.2-4 and 2.3.21.1-4 on endeavouros. When changing YESCRYPT_COST_FACTOR to 11 in /etc/login.defs and recreacting the user password for my user and restarting the dovecot service I get: # doveadm auth test matthias Password: passdb: matthias auth failed extra fields: user=matthias When reverting the change to YESCRYPT_COST_FACTOR=5 it works again: # doveadm auth test matthias Password: passdb: matthias auth succeeded extra fields: user=matthias I have tested this back and forth. The culprit is definitely a high value for YESCRYPT_COST_FACTOR. A value of 7 is still good but a value of 9 or 11 fails. Matthias

4 11

Has anyone ever managed to link their AD to Dovecot?
by ByteWave 25 Jan '26

25 Jan '26

Are there any Dovecot configuration examples for linking an Active Directory? The documentation doesn't mention it, and my configuration only works for IMAP authentication; for some unknown reason, the user is then not found...

2 4

Question about mail_utf8_extensions on Dovecot 2.4
by Andy Baugh 25 Jan '26

25 Jan '26

Is there a reason this isn't enabled by default other than perhaps compatibility with very old systems/clients? This sounds like a pretty useful feature if I'm understanding it correctly, and there already were enough new breaking changes with 2.4 that I don't see much downside to making this the default behavior there. What am I missing? Thanks, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

3 4

Issue connecting Windows AD ↔ Dovecot via LDAPS
by heschung.esteban＠gmail.com 24 Jan '26

24 Jan '26

Hello, I’m trying to connect my Windows Active Directory to Dovecot 2.4.1 via LDAPS with a self-signed certificate. Authentication works correctly using the template method. I’m using a DN template for the bind DN. The ldap_base and passdb_ldap_filter field is present in my config because its required, otherwise it doen't work, maybe a internal requirement. Authentication succeeds, but sending mail fails. ldap_uris = ldaps://gr4.lan ldap_base = cn=Users,dc=gr4,dc=lan ssl_client_require_valid_cert = no # self-signed certificate passdb { driver = ldap passdb_ldap_filter = (objectClass=*) passdb_ldap_bind = yes bind_userdn = cn=%{user},cn=Users,dc=gr4,dc=lan } userdb { driver = static args = uid=vmail gid=vmail } So, the command doveadm auth test user@domain work but not doveadm user user@domain The issue in on Debian 13. Also i have print a doveadm -Dv user pol(a)gr4.lan root@deb13:/etc/dovecot/conf.d/ doveadm-Dv user pol(a)gr4.lan Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib1@_doveadm_acl plugin.so: undefined symbol: acl_user_moc ule (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/11b10_doveadm_quota_plugin.so: undefined symbol: quota_us er module (this is usually Intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/1ib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_ rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined syn bol: fts flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadn/libdoveadm_mail_crypt_plugin.so: undefined symbol: c rypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 24 18:51:29 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libie_doveadm_acl_plugin.so: undefined symb ol: acl user module (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Skipping nodule doveadm_quota_plugin, because diopen() failed: /usr/lib/dovecot/modules/doveadm/lib1(a)_doveadm_quota_plugin.so: undefined this message) symbol : quota_user_module (this is usually intentional, so just ignore Jan 24 18:51:29 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symb Fol: fts backend_rescan (this is usually intentional, so just ignore this message) Jan 24 18:51:29 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.s o: undefined symbol: fts flatcurve_user_module (this is usually intentional, so just ignore this message) Skipping module doveadm_mail_crypt plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: und Jan 24 18:51:29 Debug: ef ined symbol: crypt_acl_setting_parser info (this is usually intentional, so just ignore this message) // this is normal Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: userdb lookup (pol@gr4, lan): Started userdb lookup Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777>>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting Jan 24 18:51:29 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=e): Client connected (fd=9) Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=0): auth input: //why its empty ??? on passwd file its not Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>: Error: auth-master: userdb lookup(pol(a)gr4.lan): Auth USER Lookup failed //help ! Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777><>: Debug: auth-master: userdb lookup(polegr4.lan): auth USER Input: Jan 24 18:51:35 doveadm(pol(a)gr4.lan) <2777>>: Debug: auth-master: userdb lookup(pol(a)gr4.lan): Userdb lookup failed userdb lookup: Internal error occurred. Refer to server log for more information. Jan 24 18:51:35 Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=2693,uid=0): Disconnected: Connection closed (fd=9) field value Thank for help.

3 5

Help with migration to dovecot 2.4
by Richard 23 Jan '26

23 Jan '26

Hi, I've just migrated our mail server from Debian 12 to 13. With this, dovecot was upgraded to v2.4. I was previously aware of the new config schema, but it seems the documentation wasn't enough to make the transition that smooth. I'm encountering several issues where I'd need some assistance: I have issues with message sizes not fitting: Jan 22 19:16:04 imap(user)<82612><thWtCP5I7OuGPXzg>: Error: Mailbox INBOX: UID 31518: Deleting corrupted cache record: Broken virtual size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769006028.M895618P2636851.mail,S=21001,W=21465:2,S): FETCH BODY[] got too little data: 11619 vs 21465 Jan 22 19:16:05 imap(user)<82614><Oy+wCP5I/OuGPXzg>: Error: Mailbox INBOX: UID 31517: Deleting corrupted cache record: Broken physical size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769002524.M378861P2632916.mail,S=229241,W=232394:2,S) failed: Cached message size larger than expected (229241 > 149967, box=INBOX, UID=31517) I have set maildir_broken_filename_sizes = yes in 10-mail.conf, which I expected to prevent this, but is seemingly doesn't really. Do I have to purge some cache? Also something similar happens when sending mail: Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: fts-flatcurve: fts-flatcurve(Sent): Could not write message data: uid=1075; InvalidArgumentError: Term too long (> 245): B)l�5y�h�^H1gg^W^�^O�o�]s�ቄ�^Elkhv/�g^Cok3�)�{^Ft^Cm�b�lw,�1l^B�^[u^MbҾ\�u�b�n[f�j�w;�r�y7+�eȯqu�^L^\�x^L�f�(`�xfkw�<�ǣ�x5rv^G^L)�#zhh^B_7w/ztl}^Q.�1�5a�/�q�^M�^C^_^�"^Dd�j_�o�"x^Dya͘_^_n Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: Deleting corrupted cache record: Broken physical size in mailbox Sent: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: Precache for UID=1077 failed: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) (attempted to index 871 messages between UIDs 179..1077) And while the logs don't seem to mention it, I guess that's also interfering with receiving mails, as postfix confirms getting the mail (though it complains about not being able to write to /var/log/dovecot/error.log, but I also don't know why it would need that so I'm currently not looking into it), but it dovecot never says it received it and also no new file is created in /maildirs/user/Maildir/cur/. I have issues with some plugins. I have in 20-imap.conf and 15-lda.conf inside mail_plugins "zlib = yes", but no zlib-related module can be found. Is there a different way to enable mail compression and decompression or did Debian just miss to enable that at compilation? I also have issues with the sieve plugin. I had it enabled in 15-lda.conf, 20-managesieve.conf, 20-imap.conf and 20-lmtp.conf. As I understand I don't need all of them. At least if I do I get a weird issue (Error: Couldn't load required plugin /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol: mail_deliver_ctx_get_log_var_expand_table). So where exactly do I enable it? Also, I'd need help modifying something I put into 90-plugins.conf: plugin { # From elsewhere to Junk folder imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/sieve/global/learn-spam.sieve # From Junk folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Junk imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/sieve/global/learn-ham.sieve sieve_pipe_bin_dir = /etc/dovecot/sieve/global sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_plugins = sieve_imapsieve sieve_extprograms # Compression zlib_save_level = 4 # 1..9 zlib_save = zstd or bz2, If this config entry missing, compression is disabled. } but when I do it that way I get the error "doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-plugin.conf line 9: Unknown section name: plugin". I do have this in 90-sieve.conf: mailbox Spam { # From elsewhere to Spam folder sieve_script report-spam { type = before cause = copy path = /etc/dovecot/sieve/global/learn-spam.sieve } } # From Spam folder to elsewhere imapsieve_from Spam { sieve_script report-ham { type = before cause = copy path = /etc/dovecot/sieve/global/learn-ham.sieve } } (currently commented out), but I have no idea how exactly I fold the old config into the new one. Most of the config is already migrated, but how do I make sure that learn-spam-sieve is only running when something is moved to Junk, while learn-ham.sieve is executed when something is being moved from Junk, except when it's moved into Trash? And what exactly do I do with the last 5 configs? Sorry for the long message, but the new config scheme is a bit too different for me to understand it right away. Best regards Richard Hi, I've just migrated our mail server from Debian 12 to 13. With this, dovecot was upgraded to v2.4. I was previously aware of the new config schema, but it seems the documentation wasn't enough to make the transition that smooth. I'm encountering several issues where I'd need some assistance: I have issues with message sizes not fitting: Jan 22 19:16:04 imap(user)<82612><thWtCP5I7OuGPXzg>: Error: Mailbox INBOX: UID 31518: Deleting corrupted cache record: Broken virtual size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769006028.M895618P2636851.mail,S=21001,W=21465:2,S): FETCH BODY[] got too little data: 11619 vs 21465 Jan 22 19:16:05 imap(user)<82614><Oy+wCP5I/OuGPXzg>: Error: Mailbox INBOX: UID 31517: Deleting corrupted cache record: Broken physical size in mailbox INBOX: read(/maildirs/user/Maildir/cur/1769002524.M378861P2632916.mail,S=229241,W=232394:2,S) failed: Cached message size larger than expected (229241 > 149967, box=INBOX, UID=31517) I have set maildir_broken_filename_sizes = yes in 10-mail.conf, which I expected to prevent this, but is seemingly doesn't really. Do I have to purge some cache? Also something similar happens when sending mail: Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: fts-flatcurve: fts-flatcurve(Sent): Could not write message data: uid=1075; InvalidArgumentError: Term too long (> 245): B)l**5y**h**^H1gg^W^**^O**o**]s**qE**^Elkhv/**g^Cok3**)**{^Ft^Cm**b**lw,**1l^B**^[u^Mb*\**u**b**n[f**j**w;**r**y7+**e*qu**^L^\**x^L**f**(`**xfkw**<**a3**x5rv^G^L)**#zhh^B_7w/ztl}^Q.**1**5a**/**q**^M**^C^_^**"^Dd**j_**o**"x^Dya*_^_n Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: Deleting corrupted cache record: Broken physical size in mailbox Sent: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: UID 1077: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) Jan 22 19:26:53 indexer-worker(user)<88639><pobvLv5IOtqGPXzg:tyFvLuZrcmk/WgEApdA/4w>: Error: Mailbox Sent: Precache for UID=1077 failed: read(/maildirs/user/Maildir/.Sent/cur/1589821415.M621487P6382.mail,S=8285,W=8432:2,Sa) failed: Cached message size larger than expected (8285 > 3115, box=Sent, UID=1077) (attempted to index 871 messages between UIDs 179..1077) And while the logs don't seem to mention it, I guess that's also interfering with receiving mails, as postfix confirms getting the mail (though it complains about not being able to write to /var/log/dovecot/error.log, but I also don't know why it would need that so I'm currently not looking into it), but it dovecot never says it received it and also no new file is created in /maildirs/user/Maildir/cur/. I have issues with some plugins. I have in 20-imap.conf and 15-lda.conf inside mail_plugins "zlib = yes", but no zlib-related module can be found. Is there a different way to enable mail compression and decompression or did Debian just miss to enable that at compilation? I also have issues with the sieve plugin. I had it enabled in 15-lda.conf, 20-managesieve.conf, 20-imap.conf and 20-lmtp.conf. As I understand I don't need all of them. At least if I do I get a weird issue (Error: Couldn't load required plugin /usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol: mail_deliver_ctx_get_log_var_expand_table). So where exactly do I enable it? Also, I'd need help modifying something I put into 90-plugins.conf: plugin { # From elsewhere to Junk folder imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = [1]file:/etc/dovecot/sieve/global/learn-spam.sieve # From Junk folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Junk imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = [2]file:/etc/dovecot/sieve/global/learn-ham.sieve sieve_pipe_bin_dir = /etc/dovecot/sieve/global sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_plugins = sieve_imapsieve sieve_extprograms # Compression zlib_save_level = 4 # 1..9 zlib_save = zstd or bz2, If this config entry missing, compression is disabled. } but when I do it that way I get the error "doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-plugin.conf line 9: Unknown section name: plugin". I do have this in 90-sieve.conf: mailbox Spam { # From elsewhere to Spam folder sieve_script report-spam { type = before cause = copy path = /etc/dovecot/sieve/global/learn-spam.sieve } } # From Spam folder to elsewhere imapsieve_from Spam { sieve_script report-ham { type = before cause = copy path = /etc/dovecot/sieve/global/learn-ham.sieve } } (currently commented out), but I have no idea how exactly I fold the old config into the new one. Most of the config is already migrated, but how do I make sure that learn-spam-sieve is only running when something is moved to Junk, while learn-ham.sieve is executed when something is being moved from Junk, except when it's moved into Trash? And what exactly do I do with the last 5 configs? Sorry for the long message, but the new config scheme is a bit too different for me to understand it right away. Best regards Richard References Visible links 1. file://etc/dovecot/sieve/global/learn-spam.sieve 2. file://etc/dovecot/sieve/global/learn-ham.sieve

2 2

Public mailboxes with ACLs
by lukas＠email.it 22 Jan '26

22 Jan '26

Hi! I am setting up a new dovecot server in order to replace my old one. I am migrating from 2.3.6 to 2.4.1. I knew it would have been difficult but I didn't think so much. At the moment I am stuck in converting my configuration of Public mailboxes with ACLs. Even if I carefully checked the documentation, I do not understand clearly some point. My server has 2 Public Mailboxes that should be seen r/w by some user, read only by some other, not seen at all by all the others. Folders created in the Public Mailboxes need to have the same access privileges as the parent Public Mailbox. In 2.3 I set up a global ACL file containing the list of all privileges (some lines like "MAILBOX_NAME* user=USERNAME lrs" with the privileges of each user for the two mailboxes and their content) and it worked like a charm. I cannot get the same in 2.4. What I understand from dovecot 2.4 docs -correct me if I am wrong- is: - the global ACL file (and folder) is gone, deprecated; - I need to create a file in each folder shared in the public folder; - I need to enable "acl_driver = vfile" in 90-acl.conf. If I configure this way, it seems to work but I need to create a dovecot-acl file in every folder existing in the Public Mailbox... Given that the file is the same for every folder (since I do not need different privileges in my environment), should I really waste all of this time? Please, can you tell me if I am misunderstanding this argument? The dovecot 2.4 choice for this feature is really this or I am missing something? There is definitely no way to have something like the 2.3 global ACL file? Thank for help and patience. Bye Lukas

3 7

Configuration problem user quota
by Ruud Baart 21 Jan '26

21 Jan '26

Hi, I'm doing a migration from dovecot 2.3 to 2.4. I can't find why the user quota is not respected. In my case in version 2.3 the user quota where read from LDAP: user_attrs = mailBase=home,mailMessageStore=mail,dovecotQuota=quota_rule=*:storage=%$ I can't find how I can configure this in 2.4. The documentation refers to "quota_rule" but how and where? In 2.4 I have: userdb ldap { userdb_use_worker = yes userdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) fields { home = %{ldap:mailBase} mail = %{ldap:mailMessageStore} mail_path = %{ldap:mailMessageStore} quota_storage_size = %{ldap:dovecotQuota} } } quota "User quota" { storage_size = 5G warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } The global quota works (set on 5Gb). The command doveadm -D quota get -u <user> shows: Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 21 13:53:34 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Jan 21 13:53:34 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): Started userdb lookup Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb: Connecting Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Client connected (fd=9) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): auth input: user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): auth USER input: user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup(user(a)domain.xx): Finished userdb lookup (username=user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G) Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail_path=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm(user(a)domain.xx)<229340><>: Debug: Added userdb setting: quota_storage_size=10G Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Effective uid=118, gid=125, home=/vmail/intern/user Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: open(/proc/self/io) failed: Permission denied (euid=118(vmail) egid=125(vmail) missing +r perm: /proc/self/io) Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: maildir++: root=/vmail/intern/user/Maildir, index=, indexpvt=, control=, inbox=/vmail/intern/user/Maildir, alt= Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: quota-count: quota_over_status check: quota_over_mask unset - skipping Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: Mailbox INBOX: Mailbox opened Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: User session is finished Jan 21 13:53:34 doveadm(user(a)domain.xx): Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Disconnected: Connection closed (fd=9) Quota name Type Value Limit % User quota STORAGE 9116042 5242880 173 User quota MESSAGE 60188 - 0 -- Cordialement, *R.J. Baart * Hi, I'm doing a migration from dovecot 2.3 to 2.4. I can't find why the user quota is not respected. In my case in version 2.3 the user quota where read from LDAP: user_attrs = mailBase=home,mailMessageStore=mail,dovecotQuota=quota_rule=*:storage=%$ I can't find how I can configure this in 2.4. The documentation refers to "quota_rule" but how and where? In 2.4 I have: userdb ldap { userdb_use_worker = yes userdb_ldap_filter = (&(objectClass=PromptMailUser)(accountStatus=TRUE)(mailDeliveryaddress=%{user})) fields { home = %{[1]ldap:mailBase} mail = %{[2]ldap:mailMessageStore} mail_path = %{[3]ldap:mailMessageStore} quota_storage_size = %{[4]ldap:dovecotQuota} } } quota "User quota" { storage_size = 5G warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } The global quota works (set on 5Gb). The command doveadm -D quota get -u <user> shows: Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Jan 21 13:53:34 Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Jan 21 13:53:34 Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Jan 21 13:53:34 Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_fts_flatcurve_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_fts_flatcurve_plugin.so: undefined symbol: fts_flatcurve_user_module (this is usually intentional, so just ignore this message) Jan 21 13:53:34 Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: crypt_acl_setting_parser_info (this is usually intentional, so just ignore this message) Jan 21 13:53:34 doveadm([5]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([6]user(a)domain.xx): Started userdb lookup Jan 21 13:53:34 doveadm([7]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb: Connecting Jan 21 13:53:34 doveadm([8]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Client connected (fd=9) Jan 21 13:53:34 doveadm([9]user(a)domain.xx)<229340><>: Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): auth input: [10]user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm([11]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([12]user(a)domain.xx): auth USER input: [13]user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G Jan 21 13:53:34 doveadm([14]user(a)domain.xx)<229340><>: Debug: auth-master: userdb lookup([15]user(a)domain.xx): Finished userdb lookup ([16]username=user(a)domain.xx home=/vmail/intern/user mail=/vmail/intern/user/Maildir/ mail_path=/vmail/intern/user/Maildir/ quota_storage_size=10G) Jan 21 13:53:34 doveadm([17]user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm([18]user(a)domain.xx)<229340><>: Debug: Added userdb setting: mail_path=/vmail/intern/user/Maildir/ Jan 21 13:53:34 doveadm([19]user(a)domain.xx)<229340><>: Debug: Added userdb setting: quota_storage_size=10G Jan 21 13:53:34 doveadm([20]user(a)domain.xx): Debug: Effective uid=118, gid=125, home=/vmail/intern/user Jan 21 13:53:34 doveadm([21]user(a)domain.xx): Debug: open(/proc/self/io) failed: Permission denied (euid=118(vmail) egid=125(vmail) missing +r perm: /proc/self/io) Jan 21 13:53:34 doveadm([22]user(a)domain.xx): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes Jan 21 13:53:34 doveadm([23]user(a)domain.xx): Debug: maildir++: root=/vmail/intern/user/Maildir, index=, indexpvt=, control=, inbox=/vmail/intern/user/Maildir, alt= Jan 21 13:53:34 doveadm([24]user(a)domain.xx): Debug: quota-count: quota_over_status check: quota_over_mask unset - skipping Jan 21 13:53:34 doveadm([25]user(a)domain.xx): Debug: Mailbox INBOX: Mailbox opened Jan 21 13:53:34 doveadm([26]user(a)domain.xx): Debug: User session is finished Jan 21 13:53:34 doveadm([27]user(a)domain.xx): Debug: auth-master: conn unix:/run/dovecot//auth-userdb (pid=229336,uid=0): Disconnected: Connection closed (fd=9) Quota name Type Value Limit % User quota STORAGE 9116042 5242880 173 User quota MESSAGE 60188 - 0 -- Cordialement, R.J. Baart References Visible links 1. file:///tmp/tmp_2m1p1xn/ldap:mailBase 2. file:///tmp/tmp_2m1p1xn/ldap:mailMessageStore 3. file:///tmp/tmp_2m1p1xn/ldap:mailMessageStore 4. file:///tmp/tmp_2m1p1xn/ldap:dovecotQuota 5. mailto:user@domain.xx 6. mailto:user@domain.xx 7. mailto:user@domain.xx 8. mailto:user@domain.xx 9. mailto:user@domain.xx 10. mailto:user@domain.xx 11. mailto:user@domain.xx 12. mailto:user@domain.xx 13. mailto:user@domain.xx 14. mailto:user@domain.xx 15. mailto:user@domain.xx 16. mailto:username=user@domain.xx 17. mailto:user@domain.xx 18. mailto:user@domain.xx 19. mailto:user@domain.xx 20. mailto:user@domain.xx 21. mailto:user@domain.xx 22. mailto:user@domain.xx 23. mailto:user@domain.xx 24. mailto:user@domain.xx 25. mailto:user@domain.xx 26. mailto:user@domain.xx 27. mailto:user@domain.xx

2 1

default_login_user setting is not honored in 2.4.x
by dovecot＠freakout.de 21 Jan '26

21 Jan '26

i have in my dovecot.conf: default_login_user = www when i start dovecot: Starting mail server ...doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: default_login_user doesn't exist: dovenull after adding dovenull user to /etc/passwd _AND_ leaving "default_login_user = www" in the dovecot.conf file everything is working fine. With 2.3.x user www worked.

2 1

Upgrade problems from Dovecot 2.3 to 2.4
by Gordon Dickens 21 Jan '26

21 Jan '26

I have attempted to upgrade my 2.3 installation to 2.4 but it will not allow my users to login closing the connections as authentication failures. My 2.3 installation has worked for many years and I simply attempted to make the changes that the dovecot documentation says are necessary to get 2.4 to work. I am running dovecot alongside Exim using mysql for the user addresses and passwords. Does anybody have any ideas as to why authentication is not working? Thanks in advance!.... Here is my dovecot.conf file: # *** REQUIRED *** Dovecot config and storage versions dovecot_config_version = 2.4.2 dovecot_storage_version = 2.4.2 passdb sql { query = SELECT crypt as password FROM users WHERE username = '%{user}' AND (type = 'local' OR type = 'piped'); } userdb sql { query = SELECT pop as home, uid, gid FROM users WHERE username =dovecot: auth: Fatal: auth-cache: SELECT crypt as password FROM users WHERE username = '%u' AND (type = 'local' OR type = 'piped');: Cache key must contain at least one variable '%{user}'; } sql_driver = mysql mysql /var/run/mysqld/mysqld.sock { user = exim4u password = SECRET dbname = exim4u } protocols { imap = yes pop3 = yes } protocol imap { mail_max_userip_connections = 50 } protocol pop3 { pop3_uidl_format = %{uid}%{uidvalidity} } service auth { user = dovecot } ssl = required ssl_server_cert_file = /etc/pki/tls/exim_tls/exim.cert ssl_server_key_file = /etc/pki/tls/exim_tls/exim.key ssl_server_dh_file = /etc/dovecot/dh.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

2 3

Replication and upgrade
by Francis Augusto Medeiros-Logeay 20 Jan '26

20 Jan '26

Hi, I have used Dovecot for about seven years, and I have a two server configuration with replication between them, mostly for redundancy and backup. I have by chance read that replication is gone with 2.4.0. I use the packages that come with ubuntu, so I feel I have to be careful with upgrading there. I read also that I can keep the functionality by using a replication plugin. My question is: do I need to compile dovecot myself to use the plugin, or can I simply install it ? Is there any guide for people like me who needs to keep replication? Best, Francis

2 2

Help regarding Postfix and Dovecot SASL
by Christophe Lohr 19 Jan '26

19 Jan '26

Hello, Please excuse my naive question. I am trying to understand how "service auth" is supposed to work between Postfix and Dovecot. (https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html) Here is my test setup: - dovecot and postfix talking in lmtpd (via unix_listener /var/spool/postfix/private/dovecot-lmtp) - dovecot and postfix talking in sasl (via unix_listener /var/spool/postfix/private/auth) - "bob" and "alice" are virtual users of the virtual domain "my_domain.org" - passwd-file (plain) is /etc/dovecot/passwd Now, postrfix receive (by smtp) an email From: bob(a)my_domain.org To: alice(a)my_domain.org Postfix validate the domain according to its config (main.cf: virtual_mailbox_domains=my_domain.org) Then, it queries dovecot about these users via sasl: and that's where it fails! Here are logs from postfix: 2026-01-16T14:28:55.829532+01:00 pc-serveur postfix/qmgr[25055]: CA20D880486: from=<bob(a)my_domain.org>, size=9988, nrcpt=1 (queue active) 2026-01-16T14:28:55.831365+01:00 pc-serveur postfix/lmtp[25080]: CA20D880486: to=<alice(a)my_domain.org>, relay=pc-serveur.my_domain.org[private/dovecot-lmtp], delay=0, delays=0/0/0/0, dsn=5.1.1, status=bounced (host pc-serveur.tp-reseaux.enstb.org[private/dovecot-lmtp] said: 550 5.1.1 <alice(a)my_domain.org> User doesn't exist: alice(a)my_domain.org (in reply to RCPT TO command)) Here are logs from dovecot: Jan 16 14:28:55 lmtp(25081): Info: Connect from local Jan 16 14:28:55 auth: Debug: conn unix:/run/dovecot/auth-userdb (pid=25081,uid=118): Server accepted connection (fd=24) Jan 16 14:28:55 auth: Debug: master in: USER 1 bob(a)my_domain.org protocol=lmtp Jan 16 14:28:55 auth(bob7): Debug: passwd-file: Performing userdb lookup Jan 16 14:28:55 auth(bob7): Debug: passwd-file: lookup: user=bob7 file=/etc/dovecot/passwd Jan 16 14:28:55 auth(bob7): Info: passwd-file: unknown user Jan 16 14:28:55 auth(bob7): Debug: passwd-file: Finished userdb lookup Jan 16 14:28:55 auth: Debug: userdb out: NOTFOUND 1 Jan 16 14:28:55 lmtp(25081): Info: Disconnect from local: Logged out (state=READY) Jan 16 14:28:55 lmtp(25081): Info: Connect from local Jan 16 14:28:55 auth: Debug: master in: USER 2 alice(a)my_domain.org protocol=lmtp Jan 16 14:28:55 auth(alice7): Debug: passwd-file: Performing userdb lookup Jan 16 14:28:55 auth(alice7): Debug: passwd-file: lookup: user=alice7 file=/etc/dovecot/passwd Jan 16 14:28:55 auth(alice7): Info: passwd-file: unknown user Jan 16 14:28:55 auth(alice7): Debug: passwd-file: Finished userdb lookup Jan 16 14:28:55 auth: Debug: userdb out: NOTFOUND 2 Jan 16 14:28:55 lmtp(25081): Info: Disconnect from local: Logged out (state=READY) So, what's wrong? It seems to me that Dovecot receives a SASL request for the user "bob(a)my_domain.org", but only does a lookup for "bob", without the domain. Isn't it? So, why? What can I do? Best regards, Christophe

7 20

IMAP with Dovecot: Kerberos/GSSAPI in LAN only
by r.barclay＠habmalnefrage.de 19 Jan '26

19 Jan '26

Hi, I'm setting up a new IMAPS server using Dovecot 2.4 at the moment. I'd like my network internal users to authenticate using GSSAPI. The server is also exposed to the Internet for smart phone email access. I want to offer PLAIN login only for external users as they can't be legitimate internal Kerberos users. (Just as an additional layer of security.) Would this approach work? service imap-login { inet_listener imaps_external { port = 1993 ssl = yes auth_mechanisms = plain login } inet_listener imaps_internal { port = 7993 ssl = yes auth_mechanisms = plain login gssapi } } Then I'd allow only port 1993 externally and keep port 7993 for the LAN. Thank you for your advice! Reg

3 2

2.4.2 breaks big-endian builds
by Noah Meyerhans 19 Jan '26

19 Jan '26

From the Debian s390 build log, no merging parent is NULL ............................................ : ok no merging parent sent to stats ...................................... : ok no merging parent timestamp differs .................................. : ok merge events parent NULL ............................................. : ok merge events parent sent to stats .................................... : ok skip empty parents ................................................... : ok merge events and skip empty parents .................................. : ok parent updated after send ............................................ : ok large event id ....................................................... : ok merge events global .................................................. : ok 0 / 10 tests failed test-master-service-settings.c:472: Assert(#16) failed: strstr(error, tests[i].error) != NULL test-master-service-settings: Error: Failed to parse configuration: Settings block doesn't end with NUL at offset 70 test-master-service-settings.c:472: Assert(#19) failed: strstr(error, tests[i].error) != NULL test-master-service-settings: Error: Failed to parse configuration: Settings block doesn't end with NUL at offset 84 master_service_settings_read() - binary corruption ................... : FAILED 1 / 1 tests failed make[4]: *** [Makefile:958: check-local] Error 1 make[4]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src/lib-master' make[3]: *** [Makefile:806: check-am] Error 2 make[3]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src/lib-master' make[2]: *** [Makefile:604: check-recursive] Error 1 make[2]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1/src' make[1]: *** [Makefile:739: check-recursive] Error 1 make[1]: Leaving directory '/build/reproducible-path/dovecot-2.4.2+dfsg1' The build failure was introduced with commit 41bd7a502 ("lib-settings, config: Use native CPU endianess in binary config file"). The build is successful at the previous commit, but fails at that commit. I haven't yet determined whether the failure is with the code itself or the test. Full build log is available at https://buildd.debian.org/status/fetch.php?pkg=dovecot&arch=s390x&ver=1%3A2… noah

2 2

Re: Issue upgrading from 2.3.x to 2.4.1 when changing the mail driver from mbox to dbox
by Michael Slusarz 18 Jan '26

18 Jan '26

> On 01/16/2026 10:50 AM MST actionmystique via dovecot <dovecot(a)dovecot.org> wrote: > > I followed all the requirements detailed in https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html, but there seems to be an issue on my side configuring correctly the Mailbox locations. > In 10-mail.conf, I changed the mail driver from: > mail_driver = mbox --> mail_driver = dbox > I thought that would be sufficient but apparently, it is not the case. Changing mailbox format requires migration. See https://doc.dovecot.org/latest/core/admin/migration.html michael > All updated configurations are: > dovecot -n > # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf > # Pigeonhole version 2.4.1-4 (0a86619f) > # OS: Linux 6.17.0-8-generic x86_64 Ubuntu 25.10 > # Hostname: <hostname> > dovecot_config_version = 2.4.1 > auth_debug = yes > auth_debug_passwords = yes > auth_mechanisms = plain > auth_verbose = yes > auth_verbose_passwords = sha1 > dovecot_storage_version = 2.4.1 > fts_autoindex = yes > fts_autoindex_max_recent_msgs = 999 > fts_search_add_missing = yes > log_debug = category=ssl > log_timestamp = "%Y-%m-%d %H:%M:%S " > mail_driver = dbox > mail_home = /home/%{user|username} > mail_inbox_path = /var/mail/%{user} > mail_path = %{home}/mail > mail_privileged_group = mail > protocols = imap lmtp > ssl = required > ssl_cipher_list = <some list> > ssl_curve_list = <some list> > ssl_min_protocol = TLSv1.3 > passdb pam { > driver = pam > fields { > allow_nets = <nets> > } > result_failure = return-fail > result_internalfail = return-fail > result_success = return-ok > skip = never > } > 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 virtual/All { > special_use = "\\All" > } > } > service imap-login { > inet_listener imap { > port = 143 > listen = 127.0.0.1 [::1] > } > inet_listener imaps { > port = 993 > ssl = yes > listen = * [::] > } > } > service pop3-login { > inet_listener pop3 { > } > inet_listener pop3s { > } > } > service submission-login { > inet_listener submission { > } > } > service lmtp { > inet_listener lmtp { > port = 8024 > listen = 127.0.0.1 ::1 > } > } > service imap { > } > service pop3 { > } > service submission { > } > service auth { > unix_listener auth-userdb { > } > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > service auth-worker { > } > service dict { > unix_listener dict { > } > } > ssl_server { > ca_file = <path> > cert_file = <path> > key_file = <path> > prefer_ciphers = server > request_client_cert = yes > require_crl = no > } > ssl_client { > ca_dir = /etc/ssl/certs > require_valid_cert = yes > } > protocol lmtp { > auth_username_format = %{user | username} > mail_plugins = quota sieve > postmaster_address = <email> > } > > In mail.err, I get multiple error messages such as: > Error: Mailbox INBOX: open() failed with file /var/mail/<user>/dovecot.index.log: Not a directory > of course, because /var/mail/<user> is not a folder but a file containing all the received mails. > > So, in /var/mail, I have one file per user, plus one user.lock.sav, and also some weird files such as mu8xTBeL, muaBkJQL... belonging to one of the user. > > How should I configure dbox? > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Issue upgrading from 2.3.x to 2.4.1 when changing the mail driver from mbox to dbox
by actionmystique＠gmail.com 16 Jan '26

16 Jan '26

I followed all the requirements detailed in https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html, but there seems to be an issue on my side configuring correctly the Mailbox locations. In 10-mail.conf, I changed the mail driver from: mail_driver = mbox --> mail_driver = dbox I thought that would be sufficient but apparently, it is not the case. All updated configurations are: dovecot -n # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.0-8-generic x86_64 Ubuntu 25.10 # Hostname: <hostname> dovecot_config_version = 2.4.1 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain auth_verbose = yes auth_verbose_passwords = sha1 dovecot_storage_version = 2.4.1 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes log_debug = category=ssl log_timestamp = "%Y-%m-%d %H:%M:%S " mail_driver = dbox mail_home = /home/%{user|username} mail_inbox_path = /var/mail/%{user} mail_path = %{home}/mail mail_privileged_group = mail protocols = imap lmtp ssl = required ssl_cipher_list = <some list> ssl_curve_list = <some list> ssl_min_protocol = TLSv1.3 passdb pam { driver = pam fields { allow_nets = <nets> } result_failure = return-fail result_internalfail = return-fail result_success = return-ok skip = never } 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 virtual/All { special_use = "\\All" } } service imap-login { inet_listener imap { port = 143 listen = 127.0.0.1 [::1] } inet_listener imaps { port = 993 ssl = yes listen = * [::] } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } } service lmtp { inet_listener lmtp { port = 8024 listen = 127.0.0.1 ::1 } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { ca_file = <path> cert_file = <path> key_file = <path> prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_dir = /etc/ssl/certs require_valid_cert = yes } protocol lmtp { auth_username_format = %{user | username} mail_plugins = quota sieve postmaster_address = <email> } In mail.err, I get multiple error messages such as: Error: Mailbox INBOX: open() failed with file /var/mail/<user>/dovecot.index.log: Not a directory of course, because /var/mail/<user> is not a folder but a file containing all the received mails. So, in /var/mail, I have one file per user, plus one user.lock.sav, and also some weird files such as mu8xTBeL, muaBkJQL... belonging to one of the user. How should I configure dbox?

1 0

Is dovecot CE 2.4.x supported with 32bit compile?
by dovecot＠freakout.de 16 Jan '26

16 Jan '26

these compiler messages make me nervous: test-event-filter.c:1006:53: warning: integer overflow in expression of type 'long int' results in '-694967296' [-Woverflow] 1006 | { "field = 1hours", 60L * 60 * 1000 * 1000, TRUE },

2 1

issue with quota warning using separate namespace quotas
by Andreas Oster 15 Jan '26

15 Jan '26

Hello everyone, I am currently trying to implement quota warnings for two separate namespaces (INBOX, MailArchive). The individual quota values for these namespaces are derived from ldap, which is working fine. However since adding the quota_warning configuration error messages appear in the logs: Error: quota-count: Filter quota_warning=warn-95 unexpectedly not found (invalid userdb or -o override settings?) Error: quota-count: Filter quota_warning=ma-warn-95 unexpectedly not found (invalid userdb or -o override settings?) The relevant configuration parameters from my config: quota_storage_size = 1G userdb ldap { fields { quota/ma_quota/storage_size = %{ldap:quota1} quota_storage_size = %{ldap:quota2} } } namespace subscriptions { mailbox_subscriptions_filename = subscriptions hidden = yes list = no prefix = subscriptions = yes } namespace inbox { inbox = yes prefix = INBOX/ subscriptions = no quota user_quota { name = User Quota quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } quota_warning warn-under { quota_storage_percentage = 100 threshold = under execute quota-warning { args = below %{user} } } } mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Sent { auto = subscribe special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } mailbox Spam { auto = subscribe special_use = "\\Junk" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { auto = subscribe special_use = "\\Trash" quota_storage_percentage = 110 } } namespace MailArchive { mail_driver = maildir mail_index_path = /var/mail/indexes/mailarchive/%{user} mail_path = /var/mail/mailarchive/%{user}/Maildir list = children prefix = MailArchiv/ subscriptions = no type = private quota ma_quota { name = MailArchive Quota quota_warning ma-warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning ma-warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } quota_warning ma-warn-under { quota_storage_percentage = 100 threshold = under execute quota-warning { args = below %{user} } } } mailbox "Archived Mails" { auto = subscribe special_use = "\\Archive" } } } service quota-warning { executable = script /var/mail/scripts/quota-warning.sh user = vmail unix_listener quota-warning { } } Does anyone have an idea what could be causing this behavior ? Thank you very much for your kind help. Andreas

1 0

Dovecot 2.4.2: How to fix maildir incoming mails going to cur/ instead of new/
by Andy Baugh 13 Jan '26

13 Jan '26

Add the following to dovecot.conf if you use maildir: # Disable the maildir breaking default behavior of # mail_attachment_detection_options, as setting ANY flag forces you out of new/ # and into cur/ mail_attachment_detection_options = ..and voila, maildir works as it previously did. This is *hinted* to in the migration guide document, as the old default value was shown as blank in the table, but I didn't figure it out till reading through the source code to find what was adding the 'a' flag to all incoming mails (thus forcing them out of new, as any flag does this). Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com

2 2

How should virtual users update their password?
by vwoloszczuk＠tutanota.com 13 Jan '26

13 Jan '26

Hi, I now have my email system working with virtual users, using a passwd-file for passdb. Now I am at the stage where I would like to change my password and possibly add other virtual users for my friends, who should be able to add/change their password without my involvement. I had a look at the IMAP RFCs but didn't see any sort of "change password" instruction. I also looked at the Dovecot docs but didn't see any article which covered this. What is the recommended/suggested way to do this? Is there a way to do with within the MDA/IMAP ecosystem or is it required to have an external solution e.g. entering the new password on a webpage? Thanks, Viktor Hi, I now have my email system working with virtual users, using a passwd-file for passdb. Now I am at the stage where I would like to change my password and possibly add other virtual users for my friends, who should be able to add/change their password without my involvement. I had a look at the IMAP RFCs but didn't see any sort of "change password" instruction. I also looked at the Dovecot docs but didn't see any article which covered this. What is the recommended/suggested way to do this? Is there a way to do with within the MDA/IMAP ecosystem or is it required to have an external solution e.g. entering the new password on a webpage? Thanks, Viktor

4 3

BUG-Report: mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) second attempt!
by Klaus Tachtler 13 Jan '26

13 Jan '26

Hello everyone, Problem info: An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log > 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) > 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: > mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in > (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: > 45 sql_driver = mysql > 46 > 47 mysql db.idmz.tachtler.net { > 48 host = db.idmz.tachtler.net > 49 port = 3306 > 50 user = postfixuser > 51 password = geheim > 52 dbname = postfix > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA > 58 } WITHOUT the following line, a database connections is possible and works as expected: > 53 ssl = yes > 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem > 55 ssl_client_cert_file = > /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem > 56 ssl_client_key_file = > /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem > 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

1 0

Re: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Stephen Callaghan 12 Jan '26

12 Jan '26

Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped) Having a similar issue: 2.4.2 (0962ed2104) via docker. Causing constant core dumping and my client keeps retrying blocking everything up. Any suggestions on how to identify the cause of the problem? S. Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 [unw_get_proc_name() failed: -10] -> #4 i_panic[0x7f13c0e8b7dd] -> #5 [unw_get_proc_name() failed: -10] -> #6 [unw_get_proc_name() failed: -10] -> #7 [unw_get_proc_name() failed: -10] -> #8 mailbox_save_alloc[0x7f13c11baf52] -> #9 [unw_get_proc_name() failed: -10] -> #10 [unw_get_proc_name() failed: -10] -> #11 cmd_move[0x5572105ab0ca] -> #12 command_exec[0x5572105c33f4] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 [unw_get_proc_name() failed: -10] -> #17 client_handle_input[0x5572105c060c] -> #18 client_input[0x5572105c0847] -> #19 io_loop_call_io[0x7f13c0eb9798] -> #20 io_loop_handler_run_internal[0x7f13c0ebd48a] -> #21 io_loop_handler_run[0x7f13c0eb9aea] -> #22 io_loop_run[0x7f13c0eb9963] -> #23 master_service_run[0x7f13c0d7264b] -> #24 main[0x5572105db2a4] -> #25 [unw_get_proc_name() failed: -10] -> #26 __libc_start_main[0x7f13c0ae4ce0] -> #27 _start[0x5572105a62f0] Jan 09 19:22:13 imap(SNIP)<555><rn1EcflH+ILwCwUB>: Fatal: master: service(imap): child 555 killed with signal 6 (core dumped)

2 1

Lazy expunge does not work as previously after upgrade from Dovecot 2.3 to 2.4.1
by Peter Milesson 11 Jan '26

11 Jan '26

Hi folks, I upgraded an IMAP server from Dovecot 2.3 to 2.4.1 (Debian 13). I have used the lazy expunge plugin for many years, and after upgrade, it was impossible to get it working as previously. After many trials I got it working sort of, but not as previously. The mail location and driver is the following: mail_home = /data/vmail/%{user | username} mail_driver = sdbox mail_path = ~/dbox Previously I had the following structure ~/dbox (user's mailboxes) ~/expunged (user's expunged emails) After upgrade I had to resort to store expunged messages in the inbox namespace in the hidden folder .EXPUNGED, instead of in a separate structure under ~/expunged. This is something I sincerely dislike, as I want expunged messages separate. Now, when messages are expunged, Dovecot no longer obeys the structure of the mailboxes, and puts all expunged messages in the .EXPUNGED folder. Previously the structure of the ~/expunged folder was a copy of the inbox namespace, but now it is just a large garbage bag. This is really a breaking change, and very unfortunate. I had a retention period of 90 days for expunged messages, mainly as a forensic tool. It has been of great help in correcting users that do not follow company guidelines, and opened insecure/infected archives, even if it's strictly prohibited. It has also rescued whole folder structures with sub folders on several occasions, when the users have inadvertently deleted a main folder, and then emptied trash. Now all expunged messages are stored in one big mess, which is much harder to analyze, and I assume, almost impossible to recover to the original state, if that would be needed. I would like to ask, if it is at all possible to get the equivalent of the previous behavior, and in that case, what the configuration would look like. Any help would be very appreciated. Best regards, Peter

1 0

mail-crypt transition from Dovecot 2.3 to 2.4
by m＠maltris.org 11 Jan '26

11 Jan '26

In Dovecot 2.3 I had used the following query: password_query = \ SELECT USER.user, USER.host, \ SECRET.password, SECRET.public_key AS mail_crypt_global_public_key, SECRET.private_key AS mail_crypt_global_private_key \ FROM USER \ WHERE USER.user = '%Lu' This worked fine, enabling encryption and decryption properly. For Dovecot 2.4 this does not work anymore. Example from LMTP: Dec 11 15:02:59 lmtp(975838): Info: lmtp-server: conn unix:pid=975905,uid=113 [1]: rcpt user(a)test.de: <Ti6aNxPPOmne4w4APAc66w>: Failed to send message to <user(a)test.de> at server:24: 451 4.2.0 <user(a)test.de> get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled (1/1 at 12 ms) I tried to adapt it to Dovecot 2.4 per the documentation, ending up with this: query = \ SELECT \ USER.user, USER.host, \ SECRET.password, \ concat('inline:', SECRET.public_key) AS crypt_global_public_key_file, \ 'main' AS crypt_global_private_key, \ concat('inline:', SECRET.private_key) AS 'crypt_global_private_key/main/crypt_private_key_file' \ FROM USER \ WHERE USER.user = '%{user | lower}' Still the error message: get_public_key(INBOX) failed: mailbox_attribute_get(INBOX, /shared/vendor/vendor.dovecot/pvt/crypt/active) failed: Mailbox attributes not enabled Additionally I tried without the "inline:" prefix, because without, doveadm mailbox cryptokey list would return a "no such file or directory error" trying to treat the key as a filename. With the "inline:" prefix it returns nothing except a warning: Warning: mailbox cryptokey list: Nothing was matched. Use -U or specify mask? What is the right way to proceed here?

2 2

Created DokuWiki entries for the migration from Dovecot 2.3 to 2.4.
by Klaus Tachtler 10 Jan '26

10 Jan '26

Hello everyone, Over the past few weeks, I have migrated from Dovecot 2.3 to 2.4 and documented this in my DokuWiki. I do not claim that this is complete, nor is it an all-encompassing description. It includes a configuration for Dovecot 2.3 and the respective migration to Dovecot 2.4. I implemented the following configurations: Dovecot ArchLinux Dovecot ArchLinux - SSL/TLS Dovecot ArchLinux - SASL Dovecot ArchLinux - Quotas Dovecot ArchLinux - Mail-Log-Schreibung Dovecot ArchLinux - Zlib-Komprimierung Dovecot ArchLinux - SQL Dovecot ArchLinux - SQL - Quota: SQL Dovecot ArchLinux - Sieve (Pigeonhole) Dovecot ArchLinux - Shares Dovecot ArchLinux - Master-User The DokuWiki entries are in German, but I think the code examples speak for themselves, and if necessary, a translation program can also be used. The Dokuwiki and my implementations can be accessed at the following link: https://dokuwiki.tachtler.net/doku.php?id=index#imap-server_dovecot_imap-se… The documentation was created using the Archlinux operating system, but can certainly be ported to other Linux distributions. I hope someone else might find my notes useful too? Best regards, Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

3 3

Problems building from source under Trixie
by William Silverstein 09 Jan '26

09 Jan '26

I am running Debian Trixie. I try building the, but the configuration fails: I tried building with: ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 \ --with-ldap I get configure: error: cannot build with MySQL support: Neither MySQL (mysqlclient) nor MariaDB library (libmariadb) found. But I did install libldb-dev. I also installed libldap2-dev liblz4-dev But when I do: EXPAT_CFLAGS=/usr/include EXPAT_LIBS=/lib/x86_64-linux-gnu \ LZ4_CFLAGS=/usr/include LZ4_LIBS=/usr/lib/x86_64-linux-gnu \ ZLIB_CFLAGS=/usr/include ZLIB_LIBS=/lib/x86_64-linux-gnu \ MARIADB_LIBS=/usr/lib/x86_64-linux-gnu MARIADB_CFLAGS=/usr/include/mariadb \ ./configure \ --prefix=/usr/local/dovecot \ --with-sql \ --with-mysql \ --without-pam \ --without-pgsql \ --without-sqlite \ --with-solr \ --with-bzlib \ --with-lz4 It configures, them fails in the build. I got some LZ4_DEPRECATED("use LZ4_compress_default() instead") LZ4LIB_API int LZ4_compress (const char* src, char* dest, int srcSize); I get a bunch of linker errors: /usr/bin/ld: ./.libs/libcompression.a(istream-lz4.o): in function `i_stream_lz4_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-lz4.c:192:(.text+0x619): undefined reference to `LZ4_decompress_safe' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_init': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:324:(.text+0x1d): undefined reference to `inflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:46:(.text+0xa8): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_reset': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x168): undefined reference to `inflateEnd' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:358:(.text+0x3a7): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(istream-zlib.o): in function `i_stream_zlib_read': /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:264:(.text+0x97f): undefined reference to `inflate' /usr/bin/ld: /usr/local/src/dovecot-2.4.2/src/lib-compression/istream-zlib.c:220:(.text+0xa7f): undefined reference to `inflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-lz4.o): in function `o_stream_lz4_compress': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-lz4.c:94:(.text+0x12f): undefined reference to `LZ4_compress' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_close': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:91:(.text+0x1ee): undefined reference to `deflateEnd' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_create_zlib': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:412:(.text+0x339): undefined reference to `deflateInit2_' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_flush': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:281:(.text+0x577): undefined reference to `deflate' /usr/bin/ld: ./.libs/libcompression.a(ostream-zlib.o): in function `o_stream_zlib_send_chunk': /usr/local/src/dovecot-2.4.2/src/lib-compression/ostream-zlib.c:213:(.text+0x83b): undefined reference to `deflate' Any suggestions? Thanks. -- William G. Silverstein, Esq. 8383 Wilshire Blvd. Suite 630. Beverly Hills, CA 90211

2 1

Error: userdb: client doesn't have lookup permissions for this user
by vwoloszczuk＠tutanota.com 09 Jan '26

09 Jan '26

Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp(<user> <mailto:viktor@woloszcz.uk>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable.I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user.I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page:https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor Hi, I am trying to configure Dovecot 2.4.2 to work as MDA for Postfix 3.10.5, using LMTP and SASL, with virtual users. This is Debian 13. I had Postfix working fine before trying to incorporate Dovecot, and I was also able to get LMTP working with system users (no SASL), but now things are not working. I've followed the guides in the documentation for using Dovecot and Postfix, in particular the following page: [1]https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html I've set up my 'service auth {}' to look like in that page. When I send mail to <user>, I get the following logs and the message is deferred by Postfix: lmtp(119643): Connect from local auth(<user>): Error: userdb: client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (to bypass this check, set: service auth { unix_listener /run/dovecot/auth-userdb { mode=0777 } }) lmtp([2]<user>)<119643><SRJICIBlYGlb0wEAk6KCeQ>: Error: auth-master: userdb lookup(<user>): Auth USER lookup failed lmtp(119643): Error: lmtp-server: conn unix:pid=119900,uid=101 [3]: rcpt <user>: Failed to lookup user <user>: Internal error occurred. Refer to server log for more information. lmtp(119643): Disconnect from local: Logged out (state=READY) I am using passwd-file passdb '/etc/dovecot/passwd' with entries in the form '<user>:{PLAIN}password'. This file is owned by root and is world-readable. I am not using a userdb but have set 'mail_uid = vmail' and 'mail_gid = vmail' The socket is located at '/var/spool/postfix/dovecot/auth' (i.e. visible to Postfix) and is owned by the postfix user. I've tried changing the permissions of the socket as the error message instructed but this didn't have any effect. I haven't set 'user = doveauth' as in this page: [3]https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html I don't understand what that would do. Please find attached my full dovecot.conf in case it is useful. Thanks in advance, Viktor References Visible links 1. https://doc.dovecot.org/2.4.2/howto/sasl/postfix.html 2. mailto:viktor@woloszcz.uk 3. https://doc.dovecot.org/2.4.2/howto/virtual/postfix.html

2 3

how to use dovecot-lda with dovecot.crt?
by Matthias Bodenbinder 09 Jan '26

09 Jan '26

Hi, I have a self signed certificate for dovecot: > [root@rakete] /etc/dovecot > # ll > insgesamt 12K > -rwxr-xr-x 1 root root 1,7K 2026-01-09@09:56 dovecot.conf > -rw-r----- 1 root root 1,4K 2026-01-09@09:54 dovecot.crt > -rw-r----- 1 root root 1,7K 2026-01-09@09:54 dovecot.key in dovecot.conf I have: ssl_server { cert_file = /etc/dovecot/dovecot.crt key_file = /etc/dovecot/dovecot.key } This works fine for the evolution email client. But when I want to use dovecot-lda as part of my getmail6 config I get a permission denied: # getmail --rcfile dogado-rc -n -v getmail version 6.19.10 Copyright (C) 1998-2025 Charles Cazabon and others. Licensed under GPL-2.0. SimpleIMAPSSLRetriever:bodenbinder_de_9@imap.dogado.net:993: Delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) [INBOX] msg 1/1 (1392 bytes), delivery error (command dovecot-lda 1510042 error (89, doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 51: cert_file: open(/etc/dovecot/dovecot.crt) failed: Permission denied)) 1 messages (1392 bytes) retrieved, 0 skipped dogado-rc has this delivery section: [destination] type = MDA_external path = /usr/lib/dovecot/dovecot-lda arguments = ("-d", "matthias") When I change ownership of the certificate files it works: # chown root:matthias /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key [root@rakete] /etc/dovecot # ll /etc/dovecot/dovecot.crt /etc/dovecot/dovecot.key -rw-r----- 1 root matthias 1,4K 2026-01-09@09:54 /etc/dovecot/dovecot.crt -rw-r----- 1 root matthias 1,7K 2026-01-09@09:54 /etc/dovecot/dovecot.key If I do not change permissions for dovecot.key I get a similar error for that file too. But can this be the solution? That would mean that I need to give read access to the crt/key file to every user who wants to use dovecot-lda. Is that correct? Matthias

2 2

Republish of dovecot 2.4.2 packages
by Aki Tuomi 08 Jan '26

08 Jan '26

Hi! Due to mistake in RHEL 10 packaging, we have republished packages for 2.4.2. Content is still the same, build number has increased by one. The important change is that there is now pigeonhole package for RHEL 10. You can find the packages at https://repo.dovecot.org/ as usual. Kind regards, Aki Tuomi

1 0

File system errors
by Jyrki Partanen 07 Jan '26

07 Jan '26

I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks! I am trying to move from one VPS to another and strange (for me) file system errors arose. On the new VPS the IMAP client can see the Inbox, but not any other mailboxes. I get these errors in the log: Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: open(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/dovecot.list.index.log stat(/home/jyrki/mail/.imap/dovecot.list.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145495><65K/GptHn8tVnMi0>: Error: Couldn't create mailbox list lock /home/jyrki/mail/.imap/mailboxes.lock: file_create_locked(/home/jyrki/mail/.imap/mailboxes.lock) failed: safe_mkstemp(/home/jyrki/mail/.imap/mailboxes.lock) failed: Permission denied Jan 5 04:49:14 partanen dovecot[144921]: imap(jyrki)<145499><nxbBGptHoMtVnMi0>: Error: Mailbox INBOX: open(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=1000(jyrki) egid=1000(jyrki) missing +r perm: /home/jyrki/mail/.imap/INBOX/dovecot.index.log stat(/home/jyrki/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied) ...etc... The thing is that the permissions should be OK, the files are not "missing +r perm". Any idea how to fix this? Thanks!

4 4

Non Existent User Login Attempts
by Bryan Simmons 07 Jan '26

07 Jan '26

Log contains several messages from dovecot that are not clear to me exactly what is occurring, single example below. These appear to be login attempts for the same group of non existent user ids from various rip addresses. Am I interpreting these correctly and, if so, is there any issue with just ignoring them? dovecot: pop3-login: Disconnected: Connection closed (auth failed, 1 attempts in 0 secs): user=<non-existent-user(a)example.net>, rip=0.0.0.0 Thank you, Bryan

6 6

How can I use /etc/passwd auth for linux users and a passwd-file for virtual mailbox users?
by Ethan Merrill 06 Jan '26

06 Jan '26

Hello, I hope this is the right mailing list to send questions to. Please direct me where to go if it is not. Thanks. --- I am setting up a postfix/dovecot email server on a Debian 13 VPS. Dovecot is v2.4.1. I have thus far been able to successfully configure the server for smtp and imap support for my primary domain (we'll say `user(a)example.com` who is a linux user with a home folder). I have been even been able to configure postfix to have virtual mailboxes and aliases, and from ssh I can can even see that the mail gets delivered to the correct place. However, I am struggling to set up dovecot to authenticate a virtual mailbox user (we'll say `user(a)example.net` who only has a virtual mailbox). [This documentation page](https://doc.dovecot.org/2.4.2/core/config/auth/mutltiple.html) describes the process to configure multiple authentication databases. It describes being able to use multiple `passdb` and `userdb` sections in order to authenticate dovecot users. Based upon what it suggested, I tried this configuration: > ## Snippet from /etc/dovecot/dovecot.conf ## > passdb passwd-file { > # So example.net => /etc/dovecot/passwd/example.net > passwd_file_path = /etc/dovecot/passwd/%{user | domain} > } > # Fall thru to PAM for unix users > passdb pam { > } > > userdb passwd-file { > passwd_file_path = /etc/dovecot/passwd/%{user | domain} > } > # Fall thru to /etc/passwd for unix users > userdb passwd { > } > > ## Snippet from /etc/dovecot/passwd/example.net ## > support@example.net:$y$j9...hash...:800:800::/var/postfix/virtual/example.net/support:: This is the configuration I landed on that hypothetically checks multiple databases for authentication that allows at least `user(a)example.com` to still login with Thunderbird and do email stuff. However it does not authenticate `user(a)example.net`. The biggest difference between my config and the example is that they use a `sql` database while I am trying the `passwd-file` database. In principle this seems like it should work, unless I am understanding the dovecot docs or have made my passwd file incorrectly. I even tried reversing the order of `userdb` and `passdb` sections to see if it would help to no avail. [This thread](https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thre… seems to address a similar issue, and more or less has the same configuration setup suggested as the one in the snippet above. It's also from 2006 so the API looks kinda different from the current docs. [This thread](https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thre… is from 2013 addressing a similar issue, but despite again different API it translates to more or less what the snippet above shows. Here is the journalctl output from when I tried to login as `user(a)example.net`: > # journalctl -xeu dovecot | tail > Dec 29 11:38:19 example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown > Dec 29 11:38:19 example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user(a)example.net rhost=10.0.0.1 > Dec 29 11:38:28 example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown > Dec 29 11:38:28 example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=user(a)example.net rhost=10.0.0.1 > Dec 29 11:41:19 example.com dovecot[4700]: imap-login: Login aborted: Inactivity (auth failed, 2 attempts in 180 secs) (auth_failed): user=<user(a)example.net>, method=LOGIN, rip=10.0.0.1, lip=10.0.0.2, TLS, session=<z8Tj3hlHkLxJMmuL> The last message referring to "Inactivity" is because at that point fail2ban blocked my IP, but before that it was consistent with results I have been getting. I'm at an absolute loss. I feel like I've trawled every doc I could find, every config file involved in the setup process, all the Stack Exchange answers that seem to exist. Honestly it baffles me to see that even what looks like the same setup as official documentation, it just doesn't... work? Can anybody point to me what is going wrong? Thanks for reading, ~ Ethan Merrill Hello, I hope this is the right mailing list to send questions to. Please direct me where to go if it is not. Thanks. --- I am setting up a postfix/dovecot email server on a Debian 13 VPS. Dovecot is v2.4.1. I have thus far been able to successfully configure the server for smtp and imap support for my primary domain (we'll say `user(a)example.com` who is a linux user with a home folder). I have been even been able to configure postfix to have virtual mailboxes and aliases, and from ssh I can can even see that the mail gets delivered to the correct place. However, I am struggling to set up dovecot to authenticate a virtual mailbox user (we'll say `user(a)example.net` who only has a virtual mailbox). [1]This documentation page describes the process to configure multiple authentication databases. It describes being able to use multiple `passdb` and `userdb` sections in order to authenticate dovecot users. Based upon what it suggested, I tried this configuration: ## Snippet from /etc/dovecot/dovecot.conf ## passdb passwd-file { # So [2]example.net => /etc/dovecot/passwd/example.net passwd_file_path = /etc/dovecot/passwd/%{user | domain} } # Fall thru to PAM for unix users passdb pam { } userdb passwd-file { passwd_file_path = /etc/dovecot/passwd/%{user | domain} } # Fall thru to /etc/passwd for unix users userdb passwd { } ## Snippet from /etc/dovecot/passwd/example.net ## [3]support@example.net:$y$j9...hash...:800:800::/var/postfix/virtual/example.net/support:: This is the configuration I landed on that hypothetically checks multiple databases for authentication that allows at least `user(a)example.com` to still login with Thunderbird and do email stuff. However it does not authenticate `user(a)example.net`. The biggest difference between my config and the example is that they use a `sql` database while I am trying the `passwd-file` database. In principle this seems like it should work, unless I am understanding the dovecot docs or have made my passwd file incorrectly. I even tried reversing the order of `userdb` and `passdb` sections to see if it would help to no avail. [4]This thread seems to address a similar issue, and more or less has the same configuration setup suggested as the one in the snippet above. It's also from 2006 so the API looks kinda different from the current docs. [5]This thread is from 2013 addressing a similar issue, but despite again different API it translates to more or less what the snippet above shows. Here is the journalctl output from when I tried to login as `user(a)example.net`: # journalctl -xeu dovecot | tail Dec 29 11:38:19 [6]example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown Dec 29 11:38:19 [7]example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot [8]ruser=user(a)example.net rhost=10.0.0.1 Dec 29 11:38:28 [9]example.com auth[4719]: pam_unix(dovecot:auth): check pass; user unknown Dec 29 11:38:28 [10]example.com auth[4719]: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot [11]ruser=user(a)example.net rhost=10.0.0.1 Dec 29 11:41:19 [12]example.com dovecot[4700]: imap-login: Login aborted: Inactivity (auth failed, 2 attempts in 180 secs) (auth_failed): user=<[13]user(a)example.net>, method=LOGIN, rip=10.0.0.1, lip=10.0.0.2, TLS, session=<z8Tj3hlHkLxJMmuL> The last message referring to "Inactivity" is because at that point fail2ban blocked my IP, but before that it was consistent with results I have been getting. I'm at an absolute loss. I feel like I've trawled every doc I could find, every config file involved in the setup process, all the Stack Exchange answers that seem to exist. Honestly it baffles me to see that even what looks like the same setup as official documentation, it just doesn't... work? Can anybody point to me what is going wrong? Thanks for reading, ~ Ethan Merrill References Visible links 1. This documentation page https://doc.dovecot.org/2.4.2/core/config/auth/mutltiple.html 2. http://example.net/ 3. mailto:support@example.net 4. This thread https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/VMXU2… 5. This thread https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/YO3DF… 6. http://example.com/ 7. http://example.com/ 8. mailto:ruser=user@example.net 9. http://example.com/ 10. http://example.com/ 11. mailto:ruser=user@example.net 12. http://example.com/ 13. mailto:user@example.net

6 10

Putting a file in a shared namespace causes Panic in quota.c
by Christopher V. 06 Jan '26

06 Jan '26

Dear all, I guess I found a bug. I'm currently testing a migration of my Debian based dovecot bare metal installation from 2.3.19 --> 2.4.1 I'm using shared mailboxes. My understanding from the documentation is: "Quota plugin considers shared namespaces against owner's quota" and "The quota limits are also taken from the userdb." The following setup leads to a "Panic: file quota.c": * Quota is defined per-user and defined in a MySQL Database (and looked up as part of userdb) * User A shares directory "Inbox/teilemich" with user B. * User B has full access rights (details see below) * User A has a quota of 100MB - currently using 60% * User B has a quota of 4GB - currently using 550MB * User A puts mail xyz in the shared directory --> works * User B puts mail abc in the shared directory --> error message (see below) and mail is not stored. Defining the following not-overwritable global quota > 550 MB eliminates the error message. Defining a global quota < 550 MB still leads to the error message. quota "User quota" { storage_size = 560M storage_grace = 10M } Defining an overwritable global quota that is > 550 MB still leads to the error message. quota_storage_size = 560M quota "User quota" { storage_grace = 10M } Can you please check, if this is a bug? If you need some details I'm happy to provide it. Also - I would be very grateful for a workaround / fix. Thanks for all the effort & Best regards, Christopher ----------------------------------------------------- Detailed error message: ==================== Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Panic: file quota.c: line 512 (quota_root_is_visible): assertion failed: (box->list->ns->type == MAIL_NAMESPACE_TYPE_SHARED) Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Error: Raw backtrace: #1 [unw_get_proc_name() failed: -10] -> #2 [unw_get_proc_name() failed: -10] -> #3 i_panic[0x7fa1b4c655e6] -> #4 [unw_get_proc_name() failed: -10] -> #5 [unw_get_proc_name() failed: -10] -> #6 quota_test_alloc[0x7fa1b45a7850] -> #7 quota_try_alloc[0x7fa1b45aa4e0] -> #8 [unw_get_proc_name() failed: -10] -> #9 mailbox_save_finish[0x7fa1b508c7f0] -> #10 mail_storage_copy[0x7fa1b507e670] -> #11 [unw_get_proc_name() failed: -10] -> #12 [unw_get_proc_name() failed: -10] -> #13 [unw_get_proc_name() failed: -10] -> #14 [unw_get_proc_name() failed: -10] -> #15 [unw_get_proc_name() failed: -10] -> #16 mailbox_move[0x7fa1b508cc10] -> #17 [unw_get_proc_name() failed: -10] -> #18 command_exec[0x55da1ef57080] -> #19 [unw_get_proc_name() failed: -10] -> #20 [unw_get_proc_name() failed: -10] -> #21 [unw_get_proc_name() failed: -10] -> #22 client_handle_input[0x55da1ef5d990] -> #23 client_input[0x55da1ef5ded0] -> #24 io_loop_call_io[0x7fa1b4d51710] -> #25 io_loop_handler_run_internal[0x7fa1b4d534b0] -> #26 io_loop_handler_run[0x7fa1b4d53640] -> #27 io_loop_run[0x7fa1b4d53820] -> #28 master_service_run[0x7fa1b4ca6330] -> #29 main[0x55da1ef48880] -> #30 [unw_get_proc_name() failed: -10] -> #31 __libc_start_main[0x7fa1b4e52ce0] -> #32 _start[0x55da1ef48f30] Jan 04 17:27:25 <Servername> dovecot[135430]: imap(test@<Servername>.de)<135441><JJetaZJH7O1P12UP>: Fatal: master: service(imap): child 135441 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Output of "doveadm acl get -A inbox/teilemich": ======================================= Username ID Global Rights <user A> user=<user B> admin create delete expunge insert lookup post read write write-deleted write-seen Output of "doveconf -a": ==================== # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.57+deb13-cloud-amd64 x86_64 Debian 13.2 ext4 # Hostname: <Servername> # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 # NOTE: Send doveconf -n output instead when asking for help. acl_cache_ttl = 30 secs acl_defaults_from_inbox = no acl_driver = vfile acl_global_path = acl_globals_only = no acl_groups = acl_id = acl_ignore = no acl_rights = acl_user = %{master_user} apparmor_hats = auth_allow_cleartext = no auth_allow_weak_schemes = no auth_anonymous_username = anonymous auth_cache_negative_ttl = 180 seconds auth_cache_size = 1024 auth_cache_ttl = 180 seconds auth_cache_verify_password_with_worker = no auth_debug = no auth_debug_passwords = no auth_default_domain = <servername> auth_failure_delay = 2 secs auth_gssapi_hostname = auth_internal_failure_delay = 2 secs auth_krb5_keytab = auth_master_user_separator = auth_mechanisms = plain login auth_policy_check_after_auth = yes auth_policy_check_before_auth = yes auth_policy_hash_mech = sha256 auth_policy_hash_nonce = auth_policy_log_only = no auth_policy_reject_on_fail = no auth_policy_report_after_auth = yes auth_policy_request_attributes = auth_policy_server_api_header = auth_policy_server_url = auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %{user|lower} auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth charset_aliases = compress_bz2_block_size_100k = 9 compress_deflate_level = 6 compress_gz_level = 6 compress_zstd_level = 3 crypt_acl_require_secure_key_sharing = no crypt_global_public_key_file = crypt_private_key_file = crypt_private_key_name = crypt_private_key_password = crypt_user_key_curve = crypt_user_key_password = crypt_user_key_require_encrypted = no crypt_write_algorithm = aes-256-gcm-sha256 debug_log_path = default_client_limit = 1000 default_idle_kill_interval = 1 mins default_internal_group = dovecot default_internal_user = dovecot default_login_user = dovenull default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%{msgid}: %{message} dict_driver = dict_file_lock_method = dotlock dict_file_path = dict_map_expire_field = dict_map_key_field_name = dict_map_key_field_type = string dict_map_key_field_value = dict_map_ldap_filter = dict_map_pattern = dict_map_sql_table = dict_map_username_field = dict_map_value = dict_map_value_field_name = dict_map_value_field_type = string dict_name = dict_proxy_idle_timeout = 0 dict_proxy_name = dict_proxy_slow_warn = 5 secs dict_proxy_socket_path = dict dotlock_use_excl = yes doveadm_allowed_commands = doveadm_api_key = doveadm_password = doveadm_port = 0 doveadm_socket_path = doveadm-server doveadm_ssl = no doveadm_username = doveadm doveadm_worker_count = 0 dovecot_storage_version = 2.4.0 dsync_alt_char = _ dsync_commit_msgs_interval = 100 dsync_features = dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%{user} -U event_exporter_driver = log event_exporter_file_path = event_exporter_format = event_exporter_http_post_url = event_exporter_name = event_exporter_time_format = rfc3339 event_exporter_unix_connect_timeout = 250 ms event_exporter_unix_path = execute_args = execute_driver = unix execute_fork_path = execute_name = execute_tcp_host = execute_tcp_port = 0 execute_unix_socket_path = fifo_listener_group = fifo_listener_mode = 0600 fifo_listener_path = fifo_listener_type = fifo_listener_user = first_valid_gid = 1 first_valid_uid = 500 fs_compress_read_plain_fallback = no fs_compress_write_method = fs_crypt_read_plain_fallback = no fs_dict_value_encoding = raw fs_driver = fs_name = fs_posix_accurate_mtime = no fs_posix_fsync = yes fs_posix_lock_method = flock fs_posix_mode = 0600 fs_posix_prefix = fs_randomfail_ops = fs_sis_queue_path = fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_decoder_driver = fts_decoder_script_socket_path = fts_decoder_tika_url = fts_driver = fts_flatcurve_commit_limit = 500 fts_flatcurve_min_term_size = 2 fts_flatcurve_optimize_limit = 10 fts_flatcurve_rotate_count = 5000 fts_flatcurve_rotate_time = 5 secs fts_flatcurve_substring_search = no fts_header_excludes = fts_header_includes = fts_message_max_size = unlimited fts_search = yes fts_search_add_missing = yes fts_search_read_fallback = yes fts_search_timeout = 30 secs haproxy_timeout = 3 secs haproxy_trusted_networks = hostname = http_client_connect_timeout = 0 http_client_delete_request_max_attempts = 0 http_client_delete_request_timeout = 0 http_client_max_connect_attempts = 0 http_client_max_idle_time = 0 http_client_max_parallel_connections = 1 http_client_max_pipelined_requests = 1 http_client_proxy_password = http_client_proxy_socket_path = http_client_proxy_ssl_tunnel = yes http_client_proxy_url = http_client_proxy_username = http_client_rawlog_dir = http_client_read_request_max_attempts = 0 http_client_read_request_timeout = 0 http_client_request_absolute_timeout = 0 http_client_request_max_attempts = 1 http_client_request_max_redirects = 0 http_client_request_timeout = 1 mins http_client_write_request_max_attempts = 0 http_client_write_request_timeout = 0 http_server_max_client_idle_time = 0 http_server_max_pipelined_requests = 1 http_server_rawlog_dir = imap_acl_allow_anyone = no imap_capability = imap_client_workarounds = imap_fetch_failure = disconnect-immediately imap_hibernate_timeout = 5s imap_id_retain = no imap_id_send = imap_literal_minus = no imap_logout_format = in=%{input} out=%{output} deleted=%{deleted} expunged=%{expunged} trashed=%{trashed} hdr_count=%{fetch_hdr_count} hdr_bytes=%{fetch_hdr_bytes} body_count=%{fetch_body_count} body_bytes=%{fetch_body_bytes} imap_metadata = no imap_urlauth_host = imap_urlauth_logout_format = in=%{input} out=%{output} imap_urlauth_port = 143 imap_urlauth_stream_user = imap_urlauth_submit_user = imapc_cmd_timeout = 5 mins imapc_connection_retry_count = 1 imapc_connection_retry_interval = 1 secs imapc_connection_timeout_interval = 30 secs imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_max_line_length = unlimited imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_sasl_mechanisms = imapc_ssl = no imapc_user = %{owner_user} imapsieve_expunge_discarded = no imapsieve_from_name = imapsieve_url = import_environment = inet_listener_haproxy = no inet_listener_name = inet_listener_port = 0 inet_listener_reuse_port = no inet_listener_ssl = no inet_listener_type = info_log_path = instance_name = dovecot language_default = no language_filter_normalizer_icu_id = Any-Lower; NFKD; [: Nonspacing Mark :] Remove; NFC; [\x20] Remove language_filter_stopwords_dir = /usr/share/dovecot/stopwords language_filters = normalizer-icu snowball stopwords language_name = language_tokenizer_address_token_maxlen = 250 language_tokenizer_generic_algorithm = simple language_tokenizer_generic_explicit_prefix = no language_tokenizer_generic_token_maxlen = 30 language_tokenizer_generic_wb5a = no language_tokenizers = generic email-address last_login_key = # hidden, use -P to show it last_login_precision = s last_valid_gid = 0 last_valid_uid = 0 lazy_expunge_mailbox = lazy_expunge_only_last_instance = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To ldap_auth_dn = ldap_auth_dn_password = ldap_auth_sasl_authz_id = ldap_auth_sasl_mechanisms = ldap_auth_sasl_realm = ldap_base = ldap_debug_level = 0 ldap_deref = never ldap_max_idle_time = 0 ldap_scope = subtree ldap_starttls = no ldap_timeout = 30 secs ldap_uris = ldap_version = 3 listen = lmtp_add_received_header = yes lmtp_client_workarounds = lmtp_hdr_delivery_address = final lmtp_proxy = no lmtp_proxy_rawlog_dir = lmtp_rawlog_dir = lmtp_rcpt_check_quota = no lmtp_save_to_detail_mailbox = no lmtp_user_concurrency_limit = 0 lock_method = fcntl log_core_filter = log_debug = log_path = syslog log_timestamp = "%b %d %H:%M:%S " login_log_format = %{message}: %{elements} login_log_format_elements = user=<%{user}> method=%{mechanism} rip=%{remote_ip} lip=%{local_ip} mpid=%{mail_pid} %{secured} session=<%{session}> login_plugin_dir = /usr/lib/dovecot/modules/login login_plugins = login_proxy_max_disconnect_delay = 0 login_proxy_max_reconnects = 3 login_proxy_notify_path = proxy-notify login_proxy_rawlog_dir = login_proxy_timeout = 30 secs login_socket_path = login_source_ips = login_trusted_networks = lua_file = lua_settings = mail_access_groups = mail_alt_path = mail_always_cache_fields = mail_attachment_detection_options = mail_cache_fields = mail_chroot = mail_compress_write_method = mail_control_path = mail_debug = no mail_driver = Maildir mail_ext_attachment_min_size = 128 k mail_ext_attachment_path = mail_fsync = optimized mail_full_filesystem_access = no mail_gid = vmail mail_home = /var/spool/dovecot/%{user|domain}/%{user|username}/home mail_inbox_path = mail_index_path = mail_index_private_path = mail_log_cached_only = no mail_log_events = mail_log_fields = mail_log_prefix = "%{service}(%{user})<%{process:pid}><%{session}>: " mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = mail_nfs_index = no mail_nfs_storage = no mail_path = /var/spool/dovecot/%{user|domain}/%{user|username}/mail mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins { acl = yes quota = yes fts = yes fts_flatcurve = yes quota_clone = yes } mail_prefetch_count = 0 mail_privileged_group = mail mail_server_admin = mailto:admin@<servername> mail_server_comment = mail_shared_explicit_inbox = no mail_sort_max_read_count = 0 mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = vmail mail_utf8_extensions = no mail_volatile_path = mail_vsize_bg_after_count = 0 mailbox_auto = no mailbox_autoexpunge = 0 mailbox_autoexpunge_max_mails = 0 mailbox_comment = mailbox_directory_name_legacy = yes mailbox_list_index = yes mailbox_list_index_include_inbox = no mailbox_list_index_prefix = dovecot.list.index mailbox_list_index_very_dirty_syncs = no mailbox_list_layout = fs mailbox_list_storage_escape_char = mailbox_list_visible_escape_char = mailbox_name = mailbox_notify_status = no mailbox_special_use = maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_empty_new = no maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%{input}/%{output} managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k managesieve_notify_capability = managesieve_sieve_capability = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_read_locks = mbox_very_dirty_syncs = no mbox_write_locks = mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 10 M metric_description = metric_exporter = metric_exporter_include = metric_fields = metric_filter = metric_group_by_field = metric_group_by_method_discrete_modifier = metric_group_by_method_exponential_base = 10 metric_group_by_method_exponential_max_magnitude = 0 metric_group_by_method_exponential_min_magnitude = 0 metric_group_by_method_linear_max = 0 metric_group_by_method_linear_min = 0 metric_group_by_method_linear_step = 0 metric_group_by_method_method = discrete metric_name = mmap_disable = no mysql_client_flags = 0 mysql_connect_timeout = 5 secs mysql_connection_limit = 5 mysql_dbname = mysql_host = mysql_option_file = mysql_option_group = client mysql_password = mysql_port = 0 mysql_read_timeout = 30 secs mysql_ssl = no mysql_user = mysql_write_timeout = 30 secs namespace_alias_for = namespace_disabled = no namespace_hidden = no namespace_ignore_on_failure = no namespace_inbox = no namespace_list = yes namespace_name = namespace_order = 0 namespace_prefix = namespace_separator = namespace_subscriptions = yes namespace_type = private notify_status_value = {"messages":%{messages},"unseen":%{unseen}} oauth2_active_attribute = oauth2_active_value = oauth2_client_id = oauth2_client_secret = oauth2_fields = oauth2_force_introspection = no oauth2_grant_url = oauth2_introspection_mode = oauth2_introspection_url = oauth2_issuers = oauth2_openid_configuration_url = oauth2_scope = oauth2_send_auth_headers = no oauth2_tokeninfo_url = oauth2_use_worker_with_mech = no oauth2_username_attribute = email oauth2_username_validation_format = %{user} passdb_default_password_scheme = PLAIN passdb_deny = no passdb_driver = passdb_fields = passdb_fields_import_all = yes passdb_master = no passdb_mechanisms_filter = passdb_name = passdb_pam_failure_show_msg = no passdb_pam_max_requests = 100 passdb_pam_service_name = dovecot passdb_pam_session = no passdb_pam_setcred = no passdb_result_failure = continue passdb_result_internalfail = continue passdb_result_success = return-ok passdb_skip = never passdb_sql_query = passdb_sql_update_query = passdb_static_password = passdb_use_cache = yes passdb_use_worker = no passdb_username_filter = passwd_file_path = pop3_client_workarounds = pop3_delete_type = default pop3_deleted_flag = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%{top_count}/%{top_bytes}, retr=%{retr_count}/%{retr_bytes}, del=%{deleted_count}/%{deleted_bytes}, size=%{message_bytes} pop3_migration_all_mailboxes = no pop3_migration_ignore_extra_uidls = no pop3_migration_ignore_missing_uidls = no pop3_migration_mailbox = pop3_migration_skip_size_check = no pop3_migration_skip_uidl_cache = no pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %{uid | hex(8)}%{uidvalidity | hex(8)} pop3c_features = pop3c_host = pop3c_master_user = pop3c_password = pop3c_port = 110 pop3c_quick_received_date = no pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_verify = yes pop3c_user = %{user} postmaster_address = postmaster@%{user|domain|default(hostname)} process_shutdown_filter = protocols { imap = yes lmtp = yes sieve = yes } push_notification_driver = push_notification_name = push_notification_ox_cache_ttl = 1 mins push_notification_ox_url = push_notification_ox_user_from_metadata = no quota_clone_unset = no quota_driver = count quota_enforce = yes quota_exceeded_message = Quota exceeded (mailbox for user is full) quota_fs_message_limit = no quota_fs_mount_path = quota_fs_type = any quota_full_tempfail = yes quota_hidden = no quota_ignore = no quota_ignore_unlimited = no quota_imapc_mailbox_name = INBOX quota_imapc_root_name = quota_mail_size = unlimited quota_mailbox_count = unlimited quota_mailbox_message_count = unlimited quota_message_count = unlimited quota_message_percentage = 100 quota_name = quota_over_status_current = quota_over_status_lazy_check = no quota_over_status_mask = quota_status_nouser = REJECT Unknown user quota_status_overquota = 554 5.2.2 %{error} quota_status_success = OK quota_status_toolarge = quota_storage_extra = 0 quota_storage_grace = 10 M quota_storage_percentage = 100 quota_storage_size = 50M quota_warning_name = quota_warning_resource = storage quota_warning_threshold = over rawlog_dir = recipient_delimiter = + redis_db_id = 0 redis_expire = 0 redis_host = 127.0.0.1 redis_key_prefix = redis_password = redis_port = 6379 redis_request_timeout = 30 secs redis_socket_path = rejection_reason = Your message to <%{to}> was automatically rejected:%{literal('\r\n')}%{reason} rejection_subject = Rejected: %{subject} sendmail_path = /usr/sbin/sendmail service_chroot = service_client_limit = 0 service_drop_priv_before_exec = no service_executable = service_extra_groups = service_group = service_idle_kill_interval = 0 service_name = service_privileged_group = service_process_limit = 0 service_process_min_avail = 0 service_protocol = service_restart_request_count = unlimited service_type = service_user = service_vsz_limit = 0 shutdown_clients = yes sieve_duplicate_default_period = 12 hours sieve_duplicate_max_period = 2 days sieve_editheader_header_forbid_add = no sieve_editheader_header_forbid_delete = no sieve_editheader_header_name = sieve_editheader_max_header_size = 2 k sieve_enabled = yes sieve_environment = sieve_execute_bin_dir = sieve_execute_exec_timeout = 10 secs sieve_execute_input_eol = crlf sieve_execute_socket_dir = sieve_extensions { fileinto = yes reject = yes envelope = yes encoded-character = yes vacation = yes subaddress = yes comparator-i;ascii-numeric = yes relational = yes regex = yes imap4flags = yes copy = yes include = yes body = yes variables = yes enotify = yes environment = yes mailbox = yes date = yes index = yes ihave = yes duplicate = yes mime = yes foreverypart = yes extracttext = yes editheader = no spamtest = yes mboxmetadata = yes virustest = yes } sieve_filter_bin_dir = sieve_filter_exec_timeout = 10 secs sieve_filter_input_eol = crlf sieve_filter_socket_dir = sieve_global_extensions = sieve_implicit_extensions = sieve_include_max_includes = 255 sieve_include_max_nesting_depth = 10 sieve_max_actions = 32 sieve_max_cpu_time = 0 sieve_max_redirects = 4 sieve_max_script_size = 1 M sieve_notify_mailto_envelope_from = sieve_pipe_bin_dir = sieve_pipe_exec_timeout = 10 secs sieve_pipe_input_eol = crlf sieve_pipe_socket_dir = sieve_plugin_dir = /usr/lib/dovecot/modules/sieve sieve_plugins = sieve_quota_script_count = 0 sieve_quota_storage_size = 0 sieve_redirect_duplicate_period = 43200 sieve_redirect_envelope_from = sieve_report_from = sieve_resource_usage_timeout = 1 hours sieve_script_active_path = sieve_script_bin_path = sieve_script_cause = sieve_script_driver = file sieve_script_ldap_filter = sieve_script_ldap_modified_attribute = sieve_script_ldap_script_attribute = sieve_script_name = sieve_script_path = sieve_script_precedence = unlimited sieve_script_storage = sieve_script_type = personal sieve_spamtest_score_max_header = sieve_spamtest_score_max_value = sieve_spamtest_status_header = sieve_spamtest_status_type = score sieve_spamtest_text_value = sieve_trace_addresses = no sieve_trace_debug = no sieve_trace_dir = sieve_trace_level = none sieve_user_email = sieve_user_log_path = sieve_vacation_check_recipient = yes sieve_vacation_default_period = 1 weeks sieve_vacation_default_subject = sieve_vacation_default_subject_template = sieve_vacation_max_period = 60 days sieve_vacation_min_period = 1 days sieve_vacation_send_from_recipient = no sieve_vacation_to_header_ignore_envelope = no sieve_vacation_use_original_recipient = no sieve_variables_max_scope_count = 255 sieve_variables_max_value_size = 4 k sieve_virustest_score_max_header = sieve_virustest_score_max_value = sieve_virustest_status_header = sieve_virustest_status_type = score sieve_virustest_text_value = sql_driver = mysql ssl = yes ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH:!AECDH:!RC4-SHA:!SHA1 ssl_cipher_suites = ssl_client_ca_dir = ssl_client_ca_file = ssl_client_cert_file = ssl_client_key_file = ssl_client_key_password = ssl_client_require_valid_cert = yes ssl_crypto_device = ssl_curve_list = ssl_min_protocol = TLSv1.2 ssl_options = ssl_server_alt_cert_file = ssl_server_alt_key_file = ssl_server_ca_file = ssl_server_cert_file = ssl_server_cert_username_field = commonName ssl_server_dh_file = ssl_server_key_file = ssl_server_key_password = ssl_server_prefer_ciphers = client ssl_server_request_client_cert = no ssl_server_require_crl = yes stats_writer_socket_path = stats-writer submission_add_received_header = yes submission_backend_capabilities = submission_client_workarounds = submission_host = submission_logout_format = in=%{input} out=%{output} submission_max_mail_size = 0 submission_max_recipients = 0 submission_relay_command_timeout = 5 mins submission_relay_connect_timeout = 30 secs submission_relay_host = submission_relay_master_user = submission_relay_max_idle_time = 29 mins submission_relay_password = submission_relay_port = 25 submission_relay_rawlog_dir = submission_relay_ssl = no submission_relay_ssl_verify = yes submission_relay_trusted = no submission_relay_user = submission_ssl = no submission_timeout = 30 secs syslog_facility = mail textcat_config_path = trash_priority = 0 unix_listener_group = unix_listener_mode = 0600 unix_listener_path = unix_listener_type = unix_listener_user = userdb_driver = userdb_fields = userdb_fields_import_all = yes userdb_name = userdb_result_failure = continue userdb_result_internalfail = continue userdb_result_success = return-ok userdb_skip = never userdb_sql_iterate_query = userdb_sql_query = userdb_static_allow_all_users = no userdb_use_cache = yes userdb_use_worker = no valid_chroot_dirs = verbose_proctitle = no version_ignore = no virtual_max_open_mailboxes = 64 welcome_wait = no mysql localhost { dbname = sys_mail password = # hidden, use -P to show it ssl = no user = sys_dovecot } userdb sql { iterate_query = SELECT username AS user FROM mailbox query = SELECT CONCAT('/var/spool/dovecot/',maildir,'mail') AS mail_path, CONCAT('/var/spool/dovecot/',maildir) AS home, 5000 AS uid, 5000 AS gid, CONCAT(quota,'B') AS quota_storage_size FROM mailbox WHERE username = '%{user|lower}' } passdb pam { default_password_scheme = CRYPT service_name = dovecot skip = authenticated } namespace inbox { inbox = yes separator = / type = private mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { auto = subscribe special_use = "\\Junk" } mailbox Trash { auto = subscribe special_use = "\\Trash" quota_storage_percentage = 110 } mailbox Sent { auto = subscribe special_use = "\\Sent" } mailbox "Sent Messages" { auto = no special_use = "\\Sent" } } namespace shared { mail_driver = maildir mail_index_path = /var/spool/dovecot/%{user|domain}/%{user|username}/sharedmailboxes/%{owner_user|domain}/%{owner_user|username} mail_path = /var/spool/dovecot/%{owner_user|domain}/%{owner_user|username}/mail list = children prefix = shared/$user/ separator = / type = shared } service imap-login { inet_listener imap { listen = 127.0.0.1 } inet_listener imaps { } } service lmtp { unix_listener lmtp { } } service auth { unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } } service auth-worker { user = $SET:default_internal_user } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-hibernate { unix_listener imap-hibernate { group = vmail mode = 0660 user = dovecot } } service imap { unix_listener imap-master { user = dovecot } } ssl_server { cert_file = /etc/letsencrypt/live/<Servername>.de/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/<Servername>.de/privkey.pem prefer_ciphers = server } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 30 mail_plugins { imap_sieve = yes imap_quota = yes imap_acl = yes imap_zlib = no } } protocol lmtp { auth_username_format = %{user | username | lower} mail_plugins { sieve = yes } } service managesieve-login { process_min_avail = 1 restart_request_count = 1 vsz_limit = 64M inet_listener sieve { port = 4190 listen = 127.0.0.1 } } service managesieve { process_limit = 1024 } protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536 } dict_server { dict mysql { driver = sql hostname = localhost sql_driver = mysql ssl = no dict_map priv/quota/storage { sql_table = quota2 username_field = username dict_map_value_field bytes { type = uint } } dict_map priv/quota/messages { sql_table = quota2 username_field = username dict_map_value_field messages { type = uint } } dict_map "shared/shared-boxes/user/$to/$from" { sql_table = user_shares dict_map_value_field dummy { } dict_map_key_field from_user { value = $from } dict_map_key_field to_user { value = $to } } dict_map "shared/shared-boxes/anyone/$from" { sql_table = anyone_shares dict_map_value_field dummy { } dict_map_key_field from_user { value = $from } } } } acl_sharing_map { dict proxy { name = mysql } } language en { filters = lowercase snowball english-possessive stopwords } language de { default = yes filters = snowball stopwords normalizer-icu } fts flatcurve { substring_search = yes } quota "User quota" { driver = count storage_grace = 10M quota_warning warn-100 { quota_storage_percentage = 100 execute quota-full { args = 100 %{user} } } quota_warning warn-95 { quota_storage_percentage = 95 execute quota-warning { args = 95 %{user} } } quota_warning warn-80 { quota_storage_percentage = 80 execute quota-warning { args = 80 %{user} } } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } } service quota-full { executable = script /usr/local/bin/quota-warning-full.sh unix_listener quota-full { user = vmail } } quota_clone { dict proxy { name = mysql } } sieve_script personal { active_path = /var/spool/dovecot/%{user|domain}/%{user|username}/sieve/.dovecot.sieve driver = file path = /var/spool/dovecot/%{user|domain}/%{user|username}/sieve } sieve_script default { driver = file name = default path = /var/spool/dovecot/sieve/default.sieve type = default } service indexer-worker { executable = /usr/bin/nice -n 10 /usr/lib/dovecot/indexer-worker process_limit = 1 user = vmail }

2 2

time diff miscalculation on 32-bit systems
by Andy Spiegl 06 Jan '26

06 Jan '26

Dear dovecot team, I believe I found a bug in dovecot on 32-bit systems. Dovecot version: 1:2.4.1+dfsg1-6 (Architecture: i386) Operating system: Linux lar 6.13.7-64+ #1 SMP PREEMPT Fri Mar 21 08:33:47 MEZ 2025 x86_64 GNU/Linux Distributor ID: Debian Description: Debian GNU/Linux 13 (trixie) Release: 13 Codename: trixie * What led up to the situation? Upgrade from 2.3.21.1 to 1:2.4.1 * What was the outcome of this action? Logs are flooded with messages "Warning: Time moved forward" * Problem Description: The function io_loop_get_wait_time in ioloop.c contains the line: ioloop->next_max_time.tv_sec = (1ULL << (TIME_T_MAX_BITS-1)) - 1; On 32-bit systems TIME_T_MAX_BITS is 31 such that the result of this calculation is 1073741823. Far from the intended "infinity" and even before "now". This leads to problems in the function io_loop_handle_timeouts_real: the calculation of the time difference between now and next_max_time is then something like -693628953 seconds which confuses dovecot and floods the logs with these warnings: Jan 02 17:43:43 lmtp(38364): Warning: Time moved forward 693630400.301863 seconds Jan 02 17:43:43 lmtp(38364): Warning: Time moved forward 693630400.304144 seconds Jan 02 17:45:43 lmtp(38364): Warning: Time moved forward 693630520.416053 seconds * Possible solution/workaround ? ioloop->next_max_time.tv_sec = INT_MAX; Thanks for your consideration, Andy

2 1

Missing dovecot-pigeonhole packages in official CE-2.4 repo for RHEL/Rocky Linux 10
by Mateusz Kiczela 06 Jan '26

06 Jan '26

Hello Dovecot Team, I am attempting to install Dovecot 2.4.2 on Rocky Linux 10 (RHEL 10 compatible) using the official repository found at: http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/ The Issue: Although the core Dovecot packages (dovecot, dovecot-imapd, etc.) are present, the Pigeonhole (Sieve/ManageSieve) packages are completely missing from the repository index. I have verified this by browsing the directory listing directly. Missing Packages: - dovecot-pigeonhole - dovecot-sieve - dovecot-managesieved Could you please check the build pipeline for RHEL/CentOS/Rocky Linux 10? It appears the Pigeonhole artifacts are not being published, and the base dependencies might need a rebuild against current EL10 libraries. Thank you for your support! Best regards. Mateusz Kiczela Hello Dovecot Team, I am attempting to install Dovecot 2.4.2 on Rocky Linux 10 (RHEL 10 compatible) using the official repository found at: [1]http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/ The Issue: Although the core Dovecot packages (dovecot, dovecot-imapd, etc.) are present, the Pigeonhole (Sieve/ManageSieve) packages are completely missing from the repository index. I have verified this by browsing the directory listing directly. Missing Packages: - dovecot-pigeonhole - dovecot-sieve - dovecot-managesieved Could you please check the build pipeline for RHEL/CentOS/Rocky Linux 10? It appears the Pigeonhole artifacts are not being published, and the base dependencies might need a rebuild against current EL10 libraries. Thank you for your support! Best regards. Mateusz Kiczela References Visible links 1. http://repo.dovecot.org/ce-2.4-latest/rhel/10/RPMS/x86_64/

2 3

Getting Dovecot to coredump
by Washington Odhiambo 05 Jan '26

05 Jan '26

Can someone please give simple steps to make dovecot to coredump on Debian 12? After reading this: https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps - I am still not able to get it to work. I have been running dovecot from git (yes, I know I shouldn't!) until I updated today and then it would be killed by signal 11. I have so far installed the release versions and all is fine, but I'd like to ensure that in the future, I have the coredump working. -- 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] Can someone please give simple steps to make dovecot to coredump on Debian 12? After reading this: [1]https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps - I am still not able to get it to work. I have been running dovecot from git (yes, I know I shouldn't!) until I updated today and then it would be killed by signal 11. I have so far installed the release versions and all is fine, but I'd like to ensure that in the future, I have the coredump working. -- 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 '^$|^.*#' -\_(Tu)_/- :-) [How to ask smart questions: [2]http://www.catb.org/~esr/faqs/smart-questions.html] References Visible links 1. https://doc.dovecot.org/2.4.2/developers/debugging.html#coredumps 2. http://www.catb.org/~esr/faqs/smart-questions.html

2 3

dovecot-2.3.21.1 for Fedora 43
by John Fawcett 04 Jan '26

04 Jan '26

Hi I realize this may seem overly nostalgic, but I was wondering if anyone has successfully got dovecot-2.3.21.1 running on Fedora 43? I'm about to do an upgrade to Fedora 43 and I wanted to avoid doing a simultaneous upgrade to Dovecot 2.4 which is now the distro packaged version, since I have not yet converted my configuration. I managed to compile from source (after taking care of adding -licuuc to the linker flags when linking test-fts-filter). However running test-lib then fails on two tests. test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED and test-data-stack.c:191: Assert failed: a == b data-stack buffer interruption ....................................... : FAILED If instead I use a src rpm like the one from here: https://koji.fedoraproject.org/koji/buildinfo?buildID=2651758 that includes fedora specific patches and try to rebuild it, it builds without the libicuuc issue, but then fails on one (different) test: Error: error:078C0102:common libcrypto routines::passed a null parameter test-hmac.c:275: Assert(#3) failed: memcmp(res->data, vec->okm, vec->okm_len) == 0 hkdf sha256 rfc5869 vectors .......................................... : FAILED My assumption as yet unverified is that the fedora specific patches are avoiding the two test errors iwhen using the unpatched source, but contribute to the error produced when using the patched source, though my test did not rule out environment differences between these two tests. John

2 2

Failed tests in core & pigeonhole git HEAD
by Patrick 02 Jan '26

02 Jan '26

Hi, Happy New Year! During make check of core git rev 6d6724bd529493c448d5aa02e70aee9aaff4f2c3 (from github) with mock a test fails with: <mock-chroot> sh-5.3# more test-suite.log ============================================ Dovecot 2.4.3: src/imap/test-suite.log ============================================ # TOTAL: 2 # PASS: 1 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 System information (uname -a): Linux 6.17.12-300.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 13 05:06:24 UTC 2025 x8 6_64 Distribution information (/etc/os-release): NAME="Fedora Linux" VERSION="43 (Forty Three)" RELEASE_TYPE=stable ID=fedora VERSION_ID=43 VERSION_CODENAME="" PRETTY_NAME="Fedora Linux 43 (Forty Three)" ANSI_COLOR="0;38;2;60;110;180" .. contents:: :depth: 2 FAIL: test-imap-client-hibernate ================================ imap client hibernate: non-IDLE ...................................... : ok test-common.c:300: Assert failed: suppress == TRUE test-imap-client-hibernate: Error: Couldn't hibernate imap client: net_connect_unix(/builddir/build/BUILD/dovecot-2 .4.3-build/dovecot/.test/imap-client-hibernate-130478.fdf4a74f3b5b21f2/imap-hibernate) failed: File name too long imap client hibernate: socket not found .............................. : FAILED test-imap-client-hibernate: Fatal: net_listen_unix(/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/.test/imap-cli ent-hibernate-130478.fdf4a74f3b5b21f2/imap-hibernate) failed: File name too long FAIL test-imap-client-hibernate (exit status: 89) Pigeonhole git rev 7229ac65540889fc3e9658c4623eafc5a9952006 make check shows: make check-local make[1]: Entering directory '/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/dovecot-pigeonhole' rm -rf ./.test make[1]: Leaving directory '/builddir/build/BUILD/dovecot-2.4.3-build/dovecot/dovecot-pigeonhole' testsuite: Fatal: execv(/usr/bin/doveconf) failed: No such file or directory make: *** [Makefile:1280: tests/testsuite.svtest] Error 84 Best, Patrick

1 0

Hello, i came here for Your help cant do a proper configuration of dovecot from 2.3.X to 2.4.1
by revolt2＠wp.pl 31 Dec '25

31 Dec '25

I would like to ask if someone could correct the configuration file for Dovecot dovecot.conf for version 2.4.1? Its the old file from 2.3.X but I'm sorry to say it doesn't work ;( https://pastebin.com/BjXuPEvv , and here is an dovecot-sql.conf file : https://pastebin.com/C4dFG2Zi If any further changes are needed, please let me know, I will adapt, I tried to understand the AI documentation but I couldn't, so we have to meet here,, Thank you in advance for your help

3 2

2.4 use a dictionary when receiving authentification requests
by info＠opdepc.nl 31 Dec '25

31 Dec '25

In conf.d/10-auth.conf I do: dict lookuptable { dict_name = lookuptable dict_driver = file dict_file_path = /etc/dovecot/mailtouserid.dict } auth_username_format = %{user | lower | dict:lookuptable/shared/ } But it seems the dictionary doesn't work here... it is skipped. Is this a bug, is it something that will be added lateron or do I do something wrong? My goal is to allow users to logon with their email address as username. Best wishes for 2026 to all! -Huibert.

2 4

quota_mailbox_message_count
by James 31 Dec '25

31 Dec '25

New for 2.4 is quota_mailbox_message_count. I have set limits for: quota_storage_size quota_message_count quota_mailbox_message_count Defaults in dovecot.conf and per user value from userdb sql. These are working proved by the rejection of test messages. 1. To monitor users' quotas one can run: doveadm quota get -A This lists values for Types STORAGE and MESSAGE. Is there a way to list mailbox_message_count values? It is per mailbox so might need a mailbox option on doveadm. doveadm-quota(1) shows -A and -u. 2. How does one send quota warning messages when quota_mailbox_message_count crosses thresholds? The documentation [1] has examples for quota_storage_size and quota_message_count but not quota_mailbox_message_count. I am missing quota_mailbox_message_percentage. Thank you. 1. Quota example: https://doc.dovecot.org/2.4.2/core/plugins/quota.html#example-configuration

2 2

Minor note about what seems like a behavior change with the 'user' field in passdb/userdb overrides
by Andy Baugh 30 Dec '25

30 Dec '25

Just finished fixing a bug with our setup where the "archive" pseudo-user we setup wasn't listing the correct dirs in IMAP yet would show their other mailboxes, folders, etc. just fine via `doveadm mailbox list`. Turns out the issue was that the 'user' field is more important on dovecot 2.4's IMAP implementation than on 2.3, but in ways that the documentation didn't really suggest to me. In both cases it says that it overrides the user, but what that means is different. On 2.3, it's mostly saying "act as if you are this user but with these other params we set in the user/passdb return" On 2.4.x, it is a straight up alias to another userdb/passdb return in IMAP's context, so any other params you override do not in fact get used. You can pretty quickly verify this with `doveadm user`/`doveadm auth lookup` calls; when your "override" user matches another user which has an entry reported back from your userdb/passdb, it just returns their data instead even if your auth source provided other data. What's odd to me is more that `doveadm mailbox list` worked "as expected" here, as everything else was consistent with 'user' being an aliasing trigger. I wound up fixing my bug by just no longer setting the 'user' variable for this archival psuedo-user, and instead relying on the (already set even on 2.3) uid/gid fields to make sure they didn't have permissions errors. Then things worked precisely how they did on 2.3. I only figured this out by accidentally making a new IMAP dir for the original user and then noticing that show up for the pseudo-user (I then scrutinized the userdb/passdb returns more carefully, then noticing the difference). Hopefully my tale helps others avoid the many hours of fruitless debugging I was doing before making that crucial mistake lol. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

1 0

Error I can't fix
by John Hill 27 Dec '25

27 Dec '25

Hello, I’m encountering a reproducible parsing issue in Dovecot 2.4 on Debian 13 (Trixie). Even when /etc/dovecot/conf.d/auth-sql.conf.ext contains a valid passdb block, Dovecot reports that the block is empty. Environment: - Debian 13 (Trixie) - Dovecot 2.4 (from Debian repository) - Clean install, no custom patches Error: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/auth-sql.conf.ext line 1: passdb { } is missing section name Steps to reproduce: 1. Remove the file: rm -f /etc/dovecot/conf.d/auth-sql.conf.ext 2. Recreate it cleanly: cat > /etc/dovecot/conf.d/auth-sql.conf.ext <<'EOF' passdb { driver = sql args = /etc/dovecot/sql.conf.ext } userdb { driver = sql args = /etc/dovecot/sql.conf.ext } EOF 3. Verify the file contents: sed -n '1,20p' /etc/dovecot/conf.d/auth-sql.conf.ext | cat -A Output: passdb {$ driver = sql$ args = /etc/dovecot/sql.conf.ext$ }$ $ userdb {$ driver = sql$ args = /etc/dovecot/sql.conf.ext$ }$ 4. Run: doveconf Actual result: Dovecot still reports that the passdb block is empty, even though the file is valid. Expected result: Dovecot should accept the passdb block and load SQL authentication normally. Additional notes: - No BOM (ef bb bf) present. - No CRLF (^M) present. - No stray characters. - File is not a symlink. - No duplicate auth-sql.conf.ext files exist. - The include line in 10-auth.conf is correct. - The error persists even after full deletion and recreation of the file. This appears to be a parser or include-path issue in Dovecot 2.4. Any guidance or confirmation would be appreciated.

4 7

dovecot-optimize FTS Xapian Failed to open glass revision file for reading
by Torge Riedel 27 Dec '25

27 Dec '25

Dears, from time to time (no regular frequency) I get the following error: /etc/cron.daily/dovecot-optimize: doveadm(account(a)domain.de): Error: FTS Xapian: Optimize (6) /var/vmail/mailboxes/domain.de/account/index/xapian-indexes/db_<longhex>/iamglass: Failed to open glass revision file for reading The reason is the file "iamglass" is owned by "root", when I change this back to "vmail" the error disappears for a while. I do not find the cause why this sometimes changes. And it is only this file, where the ownership changes. The content of /etc/cron.daily/dovecot-optimize is: #!/bin/sh doveadm fts optimize -A I welcome any help / hint, thanks and kind regards Torge

1 0

mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings)
by Klaus Tachtler 26 Dec '25

26 Dec '25

Hello everyone, Problem info: An error occurs, while trying to establish a TLS/SSL secured connection to a database (mariadb), which has the ability to accept TLS/SSL connections. Analysis from Archlinux Gitlab Issue, which could be found under following link by - Toolybird: https://gitlab.archlinux.org/archlinux/packaging/packages/dovecot/-/issues/… > Thanks for reporting. It would appear to be some kind of (upstream?) > bug in the autofoo. The error message can be traced back to > HAVE_MYSQL_SSL being undefined when it should be defined. This is > reflected in log: https://reproducible.archlinux.org/api/v0/builds/946041/log > It took quite some debugging, but adding the following hack before the > autoreconf call appears to make it work: > checking for mysql_ssl_set in -llibmariadb... no > sed -i 's/mysql_driver="libmariadb"/mysql_driver="mariadb"/' m4/ > want_mysql.m4 > After that it now shows: > checking for mysql_ssl_set in -lmariadb... yes Steps to reproduce: 1. Configure dovecot 2.4.2-4 as described below 2. Restart dovecot 2.4.2-4 3. Try send an email (echo "Test-E-Mail" | /usr/sbin/sendmail root) 4. Determine error messages inside dovecot 2.4.2-4-Log 01 Dec 22 04:57:38 server dovecot[842]: auth: Error: mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) 02 Dec 22 04:57:38 server dovecot[842]: auth-worker: Error: mysql(db.idmz.tachtler.net): mysql: SSL support not compiled in (remove ssl_client_ca_file and ssl_client_ca_dir settings) Additional info: OS version: Archlinux package version(s): dovecot 2.4.2-4 necessary config file part: 45 sql_driver = mysql 46 47 mysql db.idmz.tachtler.net { 48 host = db.idmz.tachtler.net 49 port = 3306 50 user = postfixuser 51 password = geheim 52 dbname = postfix 53 ssl = yes 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem 55 ssl_client_cert_file = /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem 56 ssl_client_key_file = /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem 57 ssl_cipher_list = DHE-RSA-AES256-SHA 58 } WITHOUT the following line, a database connections is possible and works as expected: 53 ssl = yes 54 ssl_client_ca_file = /etc/dovecot/ssl/certs/CAcert.pem 55 ssl_client_cert_file = /etc/dovecot/ssl/certs/client.idmz.tachtler.net.pem 56 ssl_client_key_file = /etc/dovecot/ssl/private/client.idmz.tachtler.net.key.pem 57 ssl_cipher_list = DHE-RSA-AES256-SHA Thanky you in advance for your help! Klaus Tachtler. -- --------------------------------------- e-Mail : klaus(a)tachtler.net Homepage: https://www.tachtler.net DokuWiki: https://dokuwiki.tachtler.net ---------------------------------------

1 0

Rootless docker image missing /usr/bin/sleep causing health check to not work
by saturos+dove＠gmail.com 23 Dec '25

23 Dec '25

Hello! I was attempting to set up health checking as in the Health Checking document [1]. But it seems that the rootless image is missing the sleep command, which prints the error: dovecot[16633]: Dec 22 22:05:04 health-check: Error: /dovecot/libexec/dovecot/health-check.sh: 31: sed: not found Reproduction: $ podman run --rm -it index.docker.io/dovecot/dovecot:latest-dev which sleep /usr/bin/sleep $ podman run --rm -it index.docker.io/dovecot/dovecot:latest-root which sleep /usr/bin/sleep $ podman run --rm -it index.docker.io/dovecot/dovecot:latest which sleep $ Set up healthchecking on 5001. With latest: $ echo -e "PING\n" | nc -v localhost 5001 Connection to localhost (::1) 5001 port [tcp/*] succeeded! $ With latest-dev: $ echo -e "PING\n" | nc -v localhost 5001 Connection to localhost (::1) 5001 port [tcp/*] succeeded! PONG and the error log above is generated. Version: $ podman run --rm -it index.docker.io/dovecot/dovecot:latest dovecot --version 2.4.2 (0962ed2104) [1] https://doc.dovecot.org/2.4.2/core/config/health_check.html

2 1

quota_mail_size question
by Marcel Menzel 22 Dec '25

22 Dec '25

Hello List, I've enabled the quota_mail_size parameter to match what I've set in Postfix, but it seems to me that this parameter has no effect. Currently set to quota_mail_size = 104857600B (with or without the suffix does not matter in my case as both won't work), but connecting to the LMTP socket does not seem to advertise SIZE: # socat /run/dovecot/lmtp readline 220 mail-fra01 Hello there LHLO test 250-mail-fra01 250-8BITMIME 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-SMTPUTF8 250 STARTTLS quit 221 2.0.0 Bye Also looking at IMAP logs on clients, APPENDLIMIT also does not seem to get advertised there. Quota itself seems to work fine via userdb, also via the IMAP quota extension as my clients report the usage. Thanks, Marcel doveconf -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-hardened1-1-hardened x86_64 # Hostname: mail-fra01 dovecot_config_version = 2.4.2 auth_verbose = yes dovecot_storage_version = 2.4.2 first_valid_uid = 8 fts_autoindex = yes hostname = mail-fra01 imap4rev2_enable = yes last_valid_uid = 8 lmtp_rcpt_check_quota = yes login_greeting = Hello there mail_driver = maildir mail_gid = mail mail_home = /var/vmail/%{user | domain}/%{user | username} mail_path = ~/ mail_plugins { quota = yes quota_clone = yes notify = yes virtual = yes fts = yes fts_xapian = yes } mail_server_admin = mailto:marcel@menzel.de mail_server_comment = hi mail_uid = mail mail_utf8_extensions = yes mailbox_list_storage_escape_char = \ mailbox_list_utf8 = yes passdb_default_password_scheme = SHA256-CRYPT protocols { imap = yes pop3 = yes sieve = yes lmtp = yes } quota_mail_size = 104857600B quota_status_nouser = DUNNO sieve_global_extensions { vnd.dovecot.pipe = yes vnd.dovecot.environment = yes } sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_plugins { sieve_imapsieve = yes sieve_extprograms = yes } sieve_redirect_envelope_from = recipient sql_driver = pgsql ssl = required 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 ssl_curve_list = X448:X25519:P-256 ssl_options = no_ticket submission_host = 127.0.0.1:25 verbose_proctitle = yes protocol imap { imap_hibernate_timeout = 10 secs imap_idle_notify_interval = 29 mins imap_metadata = yes mail_max_userip_connections = 50 mail_plugins { imap_quota = yes imap_sieve = yes last_login = yes } } protocol pop3 { mail_plugins { last_login = yes } } protocol sieve { mail_plugins { last_login = yes } } protocol lmtp { mail_plugins { sieve = yes push_notification = yes } postmaster_address = postmaster@%{user | domain} } service lmtp { user = mail unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service auth-worker { user = $SET:default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = dovecot mode = 0660 user = mail } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } } service indexer-worker { vsz_limit = 8 G } maildir { very_dirty_syncs = yes } mail_attribute { dict file { path = %{home}/dovecot-attributes } } fts xapian { } language en { default = yes } language de { } namespace inbox { inbox = yes separator = / mailbox Archive { auto = subscribe special_use = "\\Archive" } mailbox Drafts { auto = subscribe special_use = "\\Drafts" } mailbox Junk { fts_autoindex = no auto = subscribe autoexpunge = 30 days special_use = "\\Junk" } mailbox Sent { special_use = "\\Sent" } mailbox Trash { fts_autoindex = no auto = subscribe autoexpunge = 120 days special_use = "\\Trash" quota_storage_extra = 100M } } pgsql mcl { parameters { dbname = mail host = 10.10.3.2 password = <redacted> port = 6432 sslmode = disable user = mail } } userdb sql { iterate_query = SELECT username AS user FROM mailbox; query = SELECT CONCAT(quota, 'B') AS quota_storage_size FROM mailbox WHERE username = '%{user | lower}' LIMIT 1; } passdb sql { query = SELECT username AS user, password, allow_nets FROM mailbox WHERE username = '%{user | lower}' AND active = true LIMIT 1; } ssl_server { cert_file = /etc/ssl/private/dovecot.crt.pem key_file = /etc/ssl/private/dovecot.pk.pem prefer_ciphers = server } ssl_client { ca_dir = /etc/ssl/certs } sieve_script default { name = default path = /var/vmail/global.sieve type = default } sieve_script personal { active_path = /var/vmail/%{user | domain}/%{user | username}/dovecot.sieve path = /var/vmail/%{user | domain}/%{user | username}/sieve type = personal } mailbox Spam { sieve_script spam { cause = copy append path = /usr/lib/dovecot/sieve-pipe/report-spam.sieve type = before } } imapsieve_from Spam { sieve_script ham { cause = copy append path = /usr/lib/dovecot/sieve-pipe/report-ham.sieve type = before } } quota "User quota" { } quota_clone { dict proxy { name = quota_clone_sql } } dict_server { dict quota_clone_sql { driver = sql sql_driver = pgsql dict_map priv/quota/messages { sql_table = quota2 username_field = username dict_map_value_field messages { } } dict_map priv/quota/storage { sql_table = quota2 username_field = username dict_map_value_field bytes { } } } }

2 1

2.4.2 post login core dump when trash plugin is enabled
by Aragon Gouveia 22 Dec '25

22 Dec '25

Hi, docker run --rm --name dovecot -e USER_PASSWORD=test123 -v dovecot_mail:/srv/vmail -v ~aragon/dovetest/local.conf:/etc/dovecot/conf.d/local.conf -p 110:31110 -p 143:31143 --ulimit core=-1 dovecot/dovecot:latest-dev Dec 16 00:49:57 master: Info: Dovecot v2.4.2 (0962ed2104) starting up for imap, pop3, lmtp, sieve Dec 16 00:50:08 pop3-login: Info: Logged in: user=<test>, method=PLAIN, rip=172.17.0.1, lip=172.17.0.2, mpid=16, secured, session=<m5/SGwdGHNKsEQAB> Dec 16 00:50:08 pop3(test)<16><m5/SGwdGHNKsEQAB>: Fatal: master: service(pop3): child 16 killed with signal 11 (core dumped) Contents of ~aragon/dovetest/local.conf: mail_plugins { quota = yes trash = yes } protocols = imap pop3 lmtp sieve login_trusted_networks = 172.16.0.0/15 # telnet localhost 110 Trying ::1... Connected to localhost. Escape character is '^]'. +OK [XCLIENT] Dovecot ready. user test +OK pass test123 +OK Logged in. Connection closed by foreign host. dovecot-sysreport uploaded to https://limewire.com/d/PLgit#mrIN2Wx73J Is this sufficient info? Regrettably no debug symbols in the Docker builds, unless I missed something. Thank you in advance. Regards, Aragon

2 2

Sieve regex behavior
by Luca Weiss 22 Dec '25

22 Dec '25

Hi, I'm having troubles lately with a Sieve script of mine: require "fileinto"; require "mailbox"; require "regex"; if header :regex "Subject" "\\[.*PATCH.*\\]" { fileinto :create "Inbox.Patches"; } This should move all patches with "[PATCH]" or "[RFC PATCH v3]" into this Inbox subfolder, I'm pretty sure this version worked flawlessly in the past but since a couple of weeks ago it's not working with some emails. Debugging this, with manually editing mail files, I came to this discovery. That one mail matches and it's getting moved to the correct folder: Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: qcm6490-shift-otter: A Adding one more character leads to it not getting moved: Subject: Re: [PATCH v2 3/6] arm64: dts: qcom: qcm6490-shift-otter: Ad Does anybody have an explanation for this why this broke, and how to fix either Dovecot/Pigeonhole or my Sieve script? I've already lost hours trying to figure this out and I'm not getting any wiser... Regards Luca

4 3

Error after power failure
by Doug Hardie 22 Dec '25

22 Dec '25

My mail server lost power and now I am having issues with dsync for one user. Here is the command and output: mail# doveadm backup -u doug remote:sermons dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: /var/mail/home_mail/doug/Maildir/dovecot.index: Couldn't set transaction log view (seq 295..297): Missing middle file seq=296 (between 295..297, we have seqs 295,297): Not found from .log.2: File is already open dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: Failed to read transaction log for mailbox INBOX dsync-local(doug)<EauXLsjZRWkgLgAAZU03Dg>: Error: Remote command returned error 75: ssh sermons doveadm dsync-server -udoug -U How do I fix this issue? Thanks, -- Doug

2 1

Pigeonhole managesieve-login panic
by revsuine 19 Dec '25

19 Dec '25

Hi folks, I'm getting a ``` Dec 19 16:18:07 managesieve-login: Panic: file client.c: line 350 (managesieve_client_input_next_cmd): assertion failed: (args != NULL) Dec 19 16:18:07 auth: Debug: conn unix:login (pid=7390,uid=91) [2]: Disconnected: Connection closed (fd=20) Dec 19 16:18:07 managesieve-login: Fatal: master: service(managesieve-login): child 7390 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) ``` When trying to connect to MANAGESIEVE using [sieve-connect][1]. The command I'm using is ``` sieve-connect -s revsuine.xyz -u pid1 --passwordfd=5 5<<<"$(command to get pass here)" ``` This command was working previously (within the past year), though I don't remember which versions of Dovecot/Pigeonhole I tried it on. sieve-connect has not been updated recently, so there aren't any changes in sieve-connect that would've caused this. I'm attaching the files generated by `dovecot-sysreport` which includes my `dovecot -n`. Server OS is Alpine Linux 3.23.2. ~revsuine [1]: https://github.com/philpennock/sieve-connect

1 0

Attachments corrupted by sieve "redirect" action
by Michael Orlitzky 18 Dec '25

18 Dec '25

We got a report today from one of our customers that they are unable to "redirect" mail with attachments off-site. At first I was skeptical, because sieve does not mess with the message body... but sure enough, it's easy to reproduce: 1. Create a new address (mailbox) 2. Create a single sieve "redirect" filter for that address, pointing to my own mailbox 3. Send it a message with an attachment 4. An attachment is visible on the message that arrives, but it is corrupt For example: $ cat hello.original.txt Hello, world! but $ cat hello.attached.txt (it's empty). Sending a JPEG image is a bit more enlightening: $ /bin/ls -l *jpg -rw------- 1 mjo mjo 337119 Dec 18 11:15 image.attached.jpg -rw-r--r-- 1 mjo mjo 337173 Dec 18 11:13 image.original.jpg So something _is_ sent, but the start of the file is corrupt. Looking at it in a hex editor, it's only the first few lines that are messed up. This is with dovecot 2.4.2, but notably, we are using zlib compression: mail_plugins = mail_compress mail_compress_write_method = gz I'm curious if anyone else can reproduce this? Redirecting via sieve is not common, so this isn't an emergency, but obviously it is preferable to have it working.

2 1

Imap-login bind errors after upgrading dovecot from 2.3 to 2.4
by onyeibo 18 Dec '25

18 Dec '25

Greetings I updated the OS in a VPS blindly and broke the mail service. I had set up this service over four years ago and never had issues with upgrades until recently. I realized the gravity of my mistake after dovecot refused to start. Version 2.4.1 had arrived and I am in so much trouble. So far, I have adapted the configuraton files to 2.4 standards. "doveadm auth test user" tells me that the authentication is working fine. I am able to view old mails via doveadm. However, I get nothing new from mail clients. The maillog tells me that mails are getting queued (why?). I see status=sent (250.2.0.0) in some transactions, but that is the extent of success. However, I still get a nagging error message (see the end of this mail). dovecot -n # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.11-300.fc43.x86_64 x86_64 Fedora release 43 (Forty Three) dovecot_config_version = 2.4.1 auth_debug = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 first_valid_uid = xxxx mail_driver = maildir mail_home = /home/mails/%{user | domain}/%{user | username} mail_path = %{home}/Maildir mail_privileged_group = mail passdb_default_password_scheme = BLF-CRYPT protocols { imap = yes lmtp = yes sieve = yes } sql_driver = pgsql ssl = required ssl_cipher_list = PROFILE=SYSTEM pgsql localhost { parameters { dbname = postfix password = xxxxxxx user = postfix } } passdb sql {n query = SELECT username AS user, password FROM mailbox WHERE username = '%{user}' AND active='1' } userdb sql { query = SELECT '/home/mails/' || maildir AS home, xxxx as uid, xxxx as gid FROM mailbox WHERE username = '%{user}' AND active = '1' } namespace inbox { inbox = yes mailbox Drafts { auto = create special_use = "\\Drafts" } mailbox Junk { auto = create special_use = "\\Junk" } mailbox Trash { auto = create special_use = "\\Trash" } mailbox Sent { auto = create special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service lmtp { executable = lmtp -L process_min_avail = 5 user = vmail 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 = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_server { cert_file = /etc/letsencrypt/live/xxxxxxx.com/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/xxxxxxx.com/privkey.pem prefer_ciphers = server } protocol lmtp { info_log_path = /var/log/lmtp/dovecot-lmtp.log mail_plugins { sieve = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve} I did adjust an entry in postfix (master.cf). I switched from dovecot-lda to dovecot-lmtp. LDA was throwing permission errors when accessing the cert file. Most reference materials recommended LMTP because its processes already have the required privileges. So ... master.cf (postfix)dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -a ${original_recipient} -d ${user}@${nexthop}# maillog errors Dec 16 22:16:29 xxxxxxx.com dovecot[139456]: master: Error: bind(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 xxxxxxx.com dovecot[139456]: master: Fatal: Failed to create per-PID unix_listener %{pid}: net_listen_unix(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 xxxxxxx.com dovecot[809]: master: Error: service(imap-login): command startup failed, throttling for 2.000 secsDec 16 22:16:29 xxxxxxx.com dovecot[139216]: imap-login: Fatal: master: service(imap-login): child 139456 returned error 89 (Fatal failure) What am I missing? Regards Onyeibo Greetings I updated the OS in a VPS blindly and broke the mail service. I had set up this service over four years ago and never had issues with upgrades until recently. I realized the gravity of my mistake after dovecot refused to start. Version 2.4.1 had arrived and I am in so much trouble. So far, I have adapted the configuraton files to 2.4 standards. "doveadm auth test user" tells me that the authentication is working fine. I am able to view old mails via doveadm. However, I get nothing new from mail clients. The maillog tells me that mails are getting queued (why?). I see status=sent (250.2.0.0) in some transactions, but that is the extent of success. However, I still get a nagging error message (see the end of this mail). dovecot -n # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.17.11-300.fc43.x86_64 x86_64 Fedora release 43 (Forty Three) dovecot_config_version = 2.4.1 auth_debug = yes auth_mechanisms = plain login dovecot_storage_version = 2.4.1 first_valid_uid = xxxx mail_driver = maildir mail_home = /home/mails/%{user | domain}/%{user | username} mail_path = %{home}/Maildir mail_privileged_group = mail passdb_default_password_scheme = BLF-CRYPT protocols { imap = yes lmtp = yes sieve = yes } sql_driver = pgsql ssl = required ssl_cipher_list = PROFILE=SYSTEM pgsql localhost { parameters { dbname = postfix password = xxxxxxx user = postfix } } passdb sql {n query = SELECT username AS user, password FROM mailbox WHERE username = '%{user}' AND active='1' } userdb sql { query = SELECT '/home/mails/' || maildir AS home, xxxx as uid, xxxx as gid FROM mailbox WHERE username = '%{user}' AND active = '1' } namespace inbox { inbox = yes mailbox Drafts { auto = create special_use = "\\Drafts" } mailbox Junk { auto = create special_use = "\\Junk" } mailbox Trash { auto = create special_use = "\\Trash" } mailbox Sent { auto = create special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service lmtp { executable = lmtp -L process_min_avail = 5 user = vmail 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 = 0600 user = postfix } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_server { cert_file = /etc/letsencrypt/live/xxxxxxx.com/fullchain.pem dh_file = /etc/dovecot/dh.pem key_file = /etc/letsencrypt/live/xxxxxxx.com/privkey.pem prefer_ciphers = server } protocol lmtp { info_log_path = /var/log/lmtp/dovecot-lmtp.log mail_plugins { sieve = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve } I did adjust an entry in postfix (master.cf). I switched from dovecot-lda to dovecot-lmtp. LDA was throwing permission errors when accessing the cert file. Most reference materials recommended LMTP because its processes already have the required privileges. So ... master.cf (postfix) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -a ${original_recipient} -d ${user}@${nexthop}# maillog errors Dec 16 22:16:29 [1]xxxxxxx.com dovecot[139456]: master: Error: bind(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 [2]xxxxxxx.com dovecot[139456]: master: Fatal: Failed to create per-PID unix_listener %{pid}: net_listen_unix(/run/dovecot/srv.imap-login/139456) failed: No such file or directory Dec 16 22:16:29 [3]xxxxxxx.com dovecot[809]: master: Error: service(imap-login): command startup failed, throttling for 2.000 secs Dec 16 22:16:29 [4]xxxxxxx.com dovecot[139216]: imap-login: Fatal: master: service(imap-login): child 139456 returned error 89 (Fatal failure) What am I missing? Regards Onyeibo References Visible links 1. http://xxxxxxx.com/ 2. http://xxxxxxx.com/ 3. http://xxxxxxx.com/ 4. http://xxxxxxx.com/

4 9

Bug Report: authCacheFlush HTTP API crashes with assertion failure
by Yurii Krainiuk 17 Dec '25

17 Dec '25

*## Title* authCacheFlush HTTP API crashes with assertion failure - type mismatch between API schema and implementation *## Dovecot Version* 2.4.2 *## Component* doveadm HTTP API *## Description* The authCacheFlush command via doveadm HTTP API causes a server crash with an assertion failure. The HTTP API schema declares the user parameter as array type, but the internal implementation (doveadm_cmd_param_str) expects string type, causing a type mismatch assertion failure. *## Steps to Reproduce* 1. Send any authCacheFlush request to doveadm HTTP API: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":"username(a)domain.com"},"tag1"]]' \ http://localhost:8080/doveadm/v1 2. Or with user as array (matching the declared schema): bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":["username(a)domain.com"]},"tag1"]]' \ http://localhost:8080/doveadm/v1 3. Or without any parameters: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{},"tag1"]]' \ http://localhost:8080/doveadm/v1 *## Expected Result* Auth cache should be flushed and API returns success response like: json [["doveadmResponse",[{"entries":1}],"tag1"]] *## Actual Result* Server crashes with empty reply (HTTP connection closed). The doveadm process is killed with signal 6 (SIGABRT). *## Error Log* Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) Error: Raw backtrace: #0 test_subprocess_fork[0x7362eb54a570] -> #1 backtrace_append[0x7362eb54a820] -> #2 backtrace_get[0x7362eb54a9c0] -> #3 e_info[0x7362eb556370] -> #4 i_syslog_fatal_handler[0x7362eb5564b0] -> #5 i_panic[0x7362eb474f28] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7362eb4e6a00] -> #8 io_loop_call_io[0x7362eb572510] -> #9 io_loop_handler_run_internal[0x7362eb5743a0] -> #10 io_loop_handler_run[0x7362eb574540] -> #11 io_loop_run[0x7362eb574740] -> #12 master_service_run[0x7362eb4bc640] -> #13 main[0x64c4233d74f0] -> #14 __libc_init_first[0x7362eb02a150] -> #15 __libc_start_main[0x7362eb02a200] -> #16 _start[0x64c4233d76e0] Fatal: master: service(doveadm): child 2302469 killed with signal 6 (core dumped) *## API Schema (from GET /doveadm/v1)* The API endpoint reports the following schema for authCacheFlush: json { "command": "authCacheFlush", "parameters": [ {"name": "socketPath", "type": "string"}, {"name": "user", "type": "array"} ] } *## Analysis* The API schema declares user as array, but line 120 in doveadm-cmd-parse.c calls doveadm_cmd_param_str() which asserts param->type == CMD_PARAM_STR. This type mismatch causes the crash. The relevant assertion in source code: c // doveadm-cmd-parse.c:120 assertion failed: (param->type == CMD_PARAM_STR) *## Note* - The CLI command doveadm auth cache flush <user> works correctly - Only the HTTP API is affected - All authentication methods (X-Dovecot-API header, Basic Auth) produce the same crash - The crash occurs regardless of whether parameters are provided or not *## Workaround* Currently no workaround via HTTP API. Must use CLI directly or via SSH. *## Environment* - OS: Linux (Ubuntu/Debian) - Dovecot: 2.4.2 - doveadm HTTP API enabled on port 8080 ## Title authCacheFlush HTTP API crashes with assertion failure - type mismatch between API schema and implementation ## Dovecot Version 2.4.2 ## Component doveadm HTTP API ## Description The authCacheFlush command via doveadm HTTP API causes a server crash with an assertion failure. The HTTP API schema declares the user parameter as array type, but the internal implementation (doveadm_cmd_param_str) expects string type, causing a type mismatch assertion failure. ## Steps to Reproduce 1. Send any authCacheFlush request to doveadm HTTP API: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":"[1]username(a)domain.com"},"tag1"]]' \ [2]http://localhost:8080/doveadm/v1 2. Or with user as array (matching the declared schema): bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{"user":["[3]username(a)domain.com"]},"tag1"]]' \ [4]http://localhost:8080/doveadm/v1 3. Or without any parameters: bash curl -X POST \ -H "Authorization: X-Dovecot-API <api_key>" \ -H "Content-Type: application/json" \ -d '[["authCacheFlush",{},"tag1"]]' \ [5]http://localhost:8080/doveadm/v1 ## Expected Result Auth cache should be flushed and API returns success response like: json [["doveadmResponse",[{"entries":1}],"tag1"]] ## Actual Result Server crashes with empty reply (HTTP connection closed). The doveadm process is killed with signal 6 (SIGABRT). ## Error Log Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) Error: Raw backtrace: #0 test_subprocess_fork[0x7362eb54a570] -> #1 backtrace_append[0x7362eb54a820] -> #2 backtrace_get[0x7362eb54a9c0] -> #3 e_info[0x7362eb556370] -> #4 i_syslog_fatal_handler[0x7362eb5564b0] -> #5 i_panic[0x7362eb474f28] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7362eb4e6a00] -> #8 io_loop_call_io[0x7362eb572510] -> #9 io_loop_handler_run_internal[0x7362eb5743a0] -> #10 io_loop_handler_run[0x7362eb574540] -> #11 io_loop_run[0x7362eb574740] -> #12 master_service_run[0x7362eb4bc640] -> #13 main[0x64c4233d74f0] -> #14 __libc_init_first[0x7362eb02a150] -> #15 __libc_start_main[0x7362eb02a200] -> #16 _start[0x64c4233d76e0] Fatal: master: service(doveadm): child 2302469 killed with signal 6 (core dumped) ## API Schema (from GET /doveadm/v1) The API endpoint reports the following schema for authCacheFlush: json { "command": "authCacheFlush", "parameters": [ {"name": "socketPath", "type": "string"}, {"name": "user", "type": "array"} ] } ## Analysis The API schema declares user as array, but line 120 in doveadm-cmd-parse.c calls doveadm_cmd_param_str() which asserts param->type == CMD_PARAM_STR. This type mismatch causes the crash. The relevant assertion in source code: c // doveadm-cmd-parse.c:120 assertion failed: (param->type == CMD_PARAM_STR) ## Note - The CLI command doveadm auth cache flush <user> works correctly - Only the HTTP API is affected - All authentication methods (X-Dovecot-API header, Basic Auth) produce the same crash - The crash occurs regardless of whether parameters are provided or not ## Workaround Currently no workaround via HTTP API. Must use CLI directly or via SSH. ## Environment - OS: Linux (Ubuntu/Debian) - Dovecot: 2.4.2 - doveadm HTTP API enabled on port 8080 References Visible links 1. mailto:username@domain.com 2. http://localhost:8080/doveadm/v1 3. mailto:username@domain.com 4. http://localhost:8080/doveadm/v1 5. http://localhost:8080/doveadm/v1

2 1

mTLS ldap auth failure against openldap + TLSVerifyClient: demand
by Patrick Laimbock 16 Dec '25

16 Dec '25

Hi, I'm trying to setup up a Dovecot/Postfix/OpenLDAP combo on a Fedora 43 aarch64 box with the following versions: dovecot-2.4.2 from https://src.fedoraproject.org/rpms/dovecot/tree/rawhide and rebuilt for F43 at https://copr.fedorainfracloud.org/coprs/patrickl/dovecot/ postfix-3.10.3 openldap-2.6.10 openssl-3.5.4 Problem: I can't seem to make Dovecot (lmtp) establish a mTLS connection with the slapd server. Postfix works fine when using /etc/postfix/ldap-aliases.cf etc to get info from the slapd server which demands that the client sends a certificate due to olcTLSVerifyClient: demand. This is with a self-signed CA, intermediate CA and client & server certificates. Dovecot journalctl error: lmtp(92847): Error: lmtp-server: conn unix:pid=92846,uid=89 [1]: rcpt patrick@<domain>: Failed to lookup user patrick@<domain>: Internal error occurred. Refer to server log for more information. # doveadm log errors Dec 15 22:35:41.655525 Error: auth: ldap(ldaps://<FQDN>:636): Connection lost to LDAP server, reconnecting <snipped many more of the same message> Slapd error: TLS trace: SSL_accept:before SSL initialization <snip> TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL3 alert write:fatal:unknown TLS trace: SSL_accept:error in error TLS: can't accept: error:0A0000C7:SSL routines::peer did not return a certificate. TLS accept failure error=-1 id=1178, closing conn=1178 fd=15 closed (TLS negotiation failure) It seems that Dovecot does not send its client certificate to the slapd server when asked? Perhaps due to a config error? Example with postfix where the client cert is sent and mTLS succeeds: # postmap -q info@<domain> ldap:/etc/postfix/ldap-aliases.cf TLS trace: SSL_accept:before SSL initialization TLS trace: SSL_accept:before SSL initialization SSL_accept:SSLv3/TLS read SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS certificate verification: depth: 2, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 1, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 0, err: 0, subject: /CN=postfix-ldap, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA TLS trace: SSL_accept:TLSv1.3 read client compressed certificate TLS trace: SSL_accept:SSLv3/TLS read certificate verify TLS trace: SSL_accept:SSLv3/TLS read finished TLS trace: SSL_accept:SSLv3/TLS write session ticket TLS trace: SSL_accept:SSLv3/TLS write session ticket conn=1000 fd=13 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.3 tls_cipher=TLS_AES_256_GCM_SHA384 Dovecot config # dovecot -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-300.fc43.aarch64 aarch64 Fedora release 43 (Forty Three) # Hostname: <FQDN> # 5 default setting changes since version 2.4.1 dovecot_config_version = 2.4.1 auth_mechanisms = plain dovecot_storage_version = 2.4.1 first_valid_uid = 1000 ldap_auth_dn = cn=dovecot,dc=hosted,dc=ldap ldap_auth_dn_password = # hidden, use -P to show it ldap_uris = ldaps://<FQDN> log_debug = category=ssl mail_driver = sdbox mail_gid = vmail mail_home = /var/mail/virtual/%{user | domain}/%{user | username} mail_path = ~/mail mail_uid = vmail protocols { imap = yes lmtp = yes } ssl = required ssl_cipher_list = PROFILE=SYSTEM ssl_cipher_suites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 ssl_min_protocol = TLSv1.3 namespace inbox { inbox = yes separator = / } ssl_server { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/kronos.laimbock.nl.crt key_file = /etc/pki/dovecot/private/kronos.laimbock.nl_nopass.key.crt prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/dovecot-ldap.crt key_file = /etc/pki/dovecot/private/dovecot-ldap_nopass.key.crt require_valid_cert = yes } protocol !smtp { auth_ssl_require_client_cert = yes } passdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap default_password_scheme = CRYPT fields { user = %{ldap:mail} } bind = yes filter = (&(objectClass=person)(mail=%{user})) } userdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap fields { user = %{ldap:mail} } filter = (&(objectClass=person)(uid=%{user})) } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } The dovecot_ca_bundle.pem is created with # cat subca.crt ca.crt > dovecot_ca_bundle.pem The RootCA is imported into the trust store via: # cp ca.crt /etc/pki/ca-trust/source/anchors/ # update-ca-trust extract The public certificates live in /etc/pki/dovecot/certs: lrwxrwxrwx. 1 root root 16 Dec 15 15:49 1c2dd8a4.0 -> dovecot-ldap.crt lrwxrwxrwx. 1 root root 22 Dec 15 15:49 8dafd16f.0 -> <FQDN>.crt lrwxrwxrwx. 1 root root 9 Dec 15 20:15 d18284cf.0 -> subca.crt -rw-r--r--. 1 root root 773 Dec 12 21:21 dhparam -rw-r--r--. 1 root root 3456 Dec 15 21:34 dovecot_ca_bundle.pem -rw-r--r--. 1 root root 1586 Dec 15 20:15 dovecot-ldap.crt -rw-r--r--. 1 root root 1655 Dec 15 20:15 <FQDN>.crt -rw-r--r--. 1 root root 1850 Dec 15 20:15 subca.crt The private keys live in /etc/pki/dovecot/private: -rw-------. 1 root root 1704 Dec 15 20:15 dovecot-ldap_nopass.key.crt -rw-------. 1 root root 1704 Dec 15 20:15 <FQDN>_nopass.key.crt SELinux: there are no AVCs in /var/log/audit/audit.log but to make sure I ran: # restorecon -v -F -R /etc/dovecot # restorecon -v -F -R /etc/pki/doveecot With setenforce 0 no change in results. The slapd config: dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /run/openldap/slapd.args olcPidFile: /run/openldap/slapd.pid olcPasswordCryptSaltFormat: $6$%s olcLogLevel: 1023 # cat subca.crt ca.crt > slapd_ca_bundle.pem olcTLSCACertificateFile: /etc/openldap/certs/slapd_ca_bundle.pem olcTLSCertificateFile: /etc/openldap/certs/<FQDN>.crt olcTLSCertificateKeyFile: /etc/openldap/certs/<FQDN>_nopass.key.crt olcTLSCipherSuite: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 olcTLSVerifyClient: demand olcTLSCRLCheck: none I would appreciate any hints what I missed, what to read, where to look, etc If you need more info I'll be happy to provide. Thanks! Cheers, Patrick

1 0

mTLS ldap auth failure against openldap + TLSVerifyClient: demand
by Patrick Laimbock 16 Dec '25

16 Dec '25

Hi, I'm trying to setup up a Dovecot/Postfix/OpenLDAP combo on a Fedora 43 aarch64 box with the following versions: dovecot-2.4.2 from https://src.fedoraproject.org/rpms/dovecot/tree/rawhide and rebuilt for F43 at https://copr.fedorainfracloud.org/coprs/patrickl/dovecot/ postfix-3.10.3 openldap-2.6.10 openssl-3.5.4 Problem: I can't seem to make Dovecot (lmtp) establish a mTLS connection with the slapd server. Postfix works fine when using /etc/postfix/ldap-aliases.cf etc to get info from the slapd server which demands that the client sends a certificate due to olcTLSVerifyClient: demand. This is with a self-signed CA, intermediate CA and client & server certificates. Dovecot journalctl error: lmtp(92847): Error: lmtp-server: conn unix:pid=92846,uid=89 [1]: rcpt patrick@<domain>: Failed to lookup user patrick@<domain>: Internal error occurred. Refer to server log for more information. # doveadm log errors Dec 15 22:35:41.655525 Error: auth: ldap(ldaps://<FQDN>:636): Connection lost to LDAP server, reconnecting <snipped many more of the same message> Slapd error: TLS trace: SSL_accept:before SSL initialization <snip> TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS trace: SSL3 alert write:fatal:unknown TLS trace: SSL_accept:error in error TLS: can't accept: error:0A0000C7:SSL routines::peer did not return a certificate. TLS accept failure error=-1 id=1178, closing conn=1178 fd=15 closed (TLS negotiation failure) It seems that Dovecot does not send its client certificate to the slapd server when asked? Config error? Example with postfix where this succeeds: # postmap -q info@<domain> ldap:/etc/postfix/ldap-aliases.cf TLS trace: SSL_accept:before SSL initialization TLS trace: SSL_accept:before SSL initialization SSL_accept:SSLv3/TLS read SSL_accept:TLSv1.3 early data TLS trace: SSL_accept:error in TLSv1.3 early data TLS trace: SSL_accept:TLSv1.3 early data TLS certificate verification: depth: 2, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 1, err: 0, subject: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleCA TLS certificate verification: depth: 0, err: 0, subject: /CN=postfix-ldap, issuer: /C=ZZ/ST=FooBar/O=Example/OU=IT/CN=ExampleSubCA TLS trace: SSL_accept:TLSv1.3 read client compressed certificate TLS trace: SSL_accept:SSLv3/TLS read certificate verify TLS trace: SSL_accept:SSLv3/TLS read finished TLS trace: SSL_accept:SSLv3/TLS write session ticket TLS trace: SSL_accept:SSLv3/TLS write session ticket conn=1000 fd=13 TLS established tls_ssf=256 ssf=256 tls_proto=TLSv1.3 tls_cipher=TLS_AES_256_GCM_SHA384 Dovecot config # dovecot -n: # 2.4.2 (0962ed2104): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.2 (767418c3) # OS: Linux 6.17.11-300.fc43.aarch64 aarch64 Fedora release 43 (Forty Three) # Hostname: <FQDN> # 5 default setting changes since version 2.4.1 dovecot_config_version = 2.4.1 auth_mechanisms = plain dovecot_storage_version = 2.4.1 first_valid_uid = 1000 ldap_auth_dn = cn=dovecot,dc=hosted,dc=ldap ldap_auth_dn_password = # hidden, use -P to show it ldap_uris = ldaps://<FQDN> log_debug = category=ssl mail_driver = sdbox mail_gid = vmail mail_home = /var/mail/virtual/%{user | domain}/%{user | username} mail_path = ~/mail mail_uid = vmail protocols { imap = yes lmtp = yes } ssl = required ssl_cipher_list = PROFILE=SYSTEM ssl_cipher_suites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 ssl_min_protocol = TLSv1.3 namespace inbox { inbox = yes separator = / } ssl_server { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/kronos.laimbock.nl.crt key_file = /etc/pki/dovecot/private/kronos.laimbock.nl_nopass.key.crt prefer_ciphers = server request_client_cert = yes require_crl = no } ssl_client { ca_file = /etc/pki/dovecot/certs/dovecot_ca_bundle.pem cert_file = /etc/pki/dovecot/certs/dovecot-ldap.crt key_file = /etc/pki/dovecot/private/dovecot-ldap_nopass.key.crt require_valid_cert = yes } protocol !smtp { auth_ssl_require_client_cert = yes } passdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap default_password_scheme = CRYPT fields { user = %{ldap:mail} } bind = yes filter = (&(objectClass=person)(mail=%{user})) } userdb ldap { ldap_base = ou=People,ou=%{ user | domain },dc=hosted,dc=ldap fields { user = %{ldap:mail} } filter = (&(objectClass=person)(uid=%{user})) } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } The dovecot_ca_bundle.pem is created with # cat subca.crt ca.crt > dovecot_ca_bundle.pem The RootCA is imported into the trust store via: # cp ca.crt /etc/pki/ca-trust/source/anchors/ # update-ca-trust extract The public certificates live in /etc/pki/dovecot/certs: lrwxrwxrwx. 1 root root 16 Dec 15 15:49 1c2dd8a4.0 -> dovecot-ldap.crt lrwxrwxrwx. 1 root root 22 Dec 15 15:49 8dafd16f.0 -> <FQDN>.crt lrwxrwxrwx. 1 root root 9 Dec 15 20:15 d18284cf.0 -> subca.crt -rw-r--r--. 1 root root 773 Dec 12 21:21 dhparam -rw-r--r--. 1 root root 3456 Dec 15 21:34 dovecot_ca_bundle.pem -rw-r--r--. 1 root root 1586 Dec 15 20:15 dovecot-ldap.crt -rw-r--r--. 1 root root 1655 Dec 15 20:15 <FQDN>.crt -rw-r--r--. 1 root root 1850 Dec 15 20:15 subca.crt The private keys live in /etc/pki/dovecot/private: -rw-------. 1 root root 1704 Dec 15 20:15 dovecot-ldap_nopass.key.crt -rw-------. 1 root root 1704 Dec 15 20:15 <FQDN>_nopass.key.crt SELinux: there are no AVCs in /var/log/audit/audit.log but to make sure I ran: # restorecon -v -F -R /etc/dovecot # restorecon -v -F -R /etc/pki/doveecot With setenforce 0 no change in results. The slapd config: dn: cn=config objectClass: olcGlobal cn: config olcArgsFile: /run/openldap/slapd.args olcPidFile: /run/openldap/slapd.pid olcPasswordCryptSaltFormat: $6$%s olcLogLevel: 1023 # cat subca.crt ca.crt > slapd_ca_bundle.pem olcTLSCACertificateFile: /etc/openldap/certs/slapd_ca_bundle.pem olcTLSCertificateFile: /etc/openldap/certs/<FQDN>.crt olcTLSCertificateKeyFile: /etc/openldap/certs/<FQDN>_nopass.key.crt olcTLSCipherSuite: TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256 olcTLSVerifyClient: demand olcTLSCRLCheck: none I would appreciate any hints what I missed, what to read, where to look, etc If you need more info I'll be happy to provide. Thanks! Cheers, Patrick

1 0

Why doesn't Dovecot documentation specify which files to edit?
by n4ch0 13 Dec '25

13 Dec '25

I've noticed that the official Dovecot documentation frequently omits crucial information about which specific files should be modified when configuring different functionalities. Concrete examples: In the LMTP integration guide with Postfix (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-l…) It indicates to modify the socket configuration, but doesn't specify in which file this modification should be made In the quota plugin documentation (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota) It requests enabling the quota module, but doesn't mention the corresponding configuration file I managed to achieve the configuration I wanted but it took more time than it should have. My question: I understand that Dovecot uses a modular configuration system and that technically I can place directives in any file. However, wouldn't it be clearer and more efficient if the documentation followed an established order and specified recommended locations? For example: "Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf" Is there a technical reason why the documentation deliberately avoids recommending specific files, or does it simply assume that users already know these conventions? Is there a general guide about Dovecot's configuration file structure and best practices for organizing them? Thanks!

5 6

Dovecot crash after waking up from sleep
by Peter Psenak 13 Dec '25

13 Dec '25

Hi, I'm experiencing a dovecot crash every time my PC wakes up from sleep. Is this a know issues? # 2.4.0 (daeb6bc59c): /opt/homebrew/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) # OS: Darwin 25.1.0 arm64 File system: APFS Dec 11 22:24:20 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Dec 11 22:24:20 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102dc35f4 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102dc3738 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102dd0b64 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102dcf614 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102dcf5e0 fatal_handler_real + 0 -> 5 dovecot 0x0000000102b1a8fc master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102dcf794 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102e24ce0 event_callback.cold.1 + 0 -> 8 libdovecot.0.dylib 0x0000000102de61c4 io_loops_timeouts_update + 308 -> 9 \libdovecot.0.dylib 0x0000000102e24668 io_loop_handle_timeouts.cold.1 + 20 -> 10 libdovecot.0.dylib 0x0000000102de49b8 io_loop_handle_timeouts + 560 -> 11 libdovecot.0.dylib 0x0000000102de6e64 io_loop_handler_run_internal + 388 -> 12 libdovecot.0.dylib 0x0000000102de4f00 io_loop_handler_run + 220 -> 13 libdovecot.0.dylib 0x0000000102de4e04 io_loop_run + 88 -> 14 libdovecot.0.dylib 0x0000000102d4ec3c master_service_run + 28 -> 15 dovecot 0x0000000102b1a224 main + 2944 -> 16 dyld 0x000000019ff4dd54 start + 7184 thanks, Peter

2 1

Re: Why doesn't Dovecot documentation specify which files to edit?
by Michael Slusarz 12 Dec '25

12 Dec '25

See, e.g., https://doc.dovecot.org/2.4.2/core/config/quick.html#tldr-i-just-want-dovec… michael > On 12/11/2025 3:29 PM MST Chad Wallace via dovecot <dovecot(a)dovecot.org> wrote: > > > I think the configuration layout you're seeing may be provided by your > distribution (Debian, RedHat, etc.). In the original release provided > by Dovecot, I only see a single config file: dovecont.conf.in > > Also, it is quite easy to find which file has certain types of > configuration: > > $ grep -ri lmtp /etc/dovecot > > > On Thu, 11 Dec 2025 20:47:44 +0000 > n4ch0 via dovecot <dovecot(a)dovecot.org> wrote: > > > I've noticed that the official Dovecot documentation frequently omits > > crucial information about which specific files should be modified > > when configuring different functionalities. Concrete examples: > > > > In the LMTP integration guide with Postfix > > (https://doc.dovecot.org/2.4.2/howto/lmtp/postfix.html#postfix-and-dovecot-l…) > > > > It indicates to modify the socket configuration, but doesn't specify > > in which file this modification should be made > > > > > > In the quota plugin documentation > > (https://doc.dovecot.org/2.4.2/core/plugins/quota.html#quota-plugin-quota) > > > > It requests enabling the quota module, but doesn't mention the > > corresponding configuration file > > > > > > > > I managed to achieve the configuration I wanted but it took more time > > than it should have. My question: I understand that Dovecot uses a > > modular configuration system and that technically I can place > > directives in any file. However, wouldn't it be clearer and more > > efficient if the documentation followed an established order and > > specified recommended locations? For example: > > > > "Edit /etc/dovecot/conf.d/10-master.conf to configure the LMTP socket" > > "Enable the quota plugin in /etc/dovecot/conf.d/10-mail.conf" > > > > Is there a technical reason why the documentation deliberately avoids > > recommending specific files, or does it simply assume that users > > already know these conventions? Is there a general guide about > > Dovecot's configuration file structure and best practices for > > organizing them? > > > > Thanks! > > _______________________________________________ > > dovecot mailing list -- dovecot(a)dovecot.org > > To unsubscribe send an email to dovecot-leave(a)dovecot.org > > > > -- > Chad Wallace > Software Developer | The Lodging Company® > P: +1 250 869 4931 ext. 251 > TF: +1 888 676 9977 > E: cwallace(a)lodgingcompany.com > W: www.lodgingcompany.com > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Migration of the Maildir standard from Dovecot 2.3 to Dovecot 2.4
by byteme＠linuxmaker.net 10 Dec '25

10 Dec '25

Hello everyone, I have a Dovecot 2.3 installation on a Debian 12 Linux system that is being upgraded to Dovecot 2.4. The server hosts many domains with numerous email accounts. Users had created folder structures containing many received and sent emails, following the Maildir standard as "dot-prefixed folders." When switching to Dovecot 2.4, all these emails and folders are no longer visible. This is what it looks like on the old system: root@mx1 /var/vmail/example.com/systemmails # ll -a insgesamt 256 drwx------ 14 vmail vmail 4096 3. Nov 09:15 . drwx------ 15 vmail vmail 4096 6. Apr 2021 .. drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Archive drwx------ 2 vmail vmail 86016 27. Okt 12:19 cur -rw------- 1 vmail vmail 0 15. Sep 2018 dovecot-acl-list -rw------- 1 vmail vmail 1080 29. Okt 06:50 dovecot.index -rw------- 1 vmail vmail 23400 30. Okt 01:36 dovecot.index.cache -rw------- 1 vmail vmail 10600 30. Okt 01:41 dovecot.index.log -rw------- 1 vmail vmail 6627 26. Aug 09:56 dovecot.index.thread -rw------- 1 vmail vmail 24 20. Apr 2024 dovecot-keywords -rw------- 1 vmail vmail 1256 3. Nov 09:05 dovecot.list.index -rw------- 1 vmail vmail 5156 3. Nov 09:15 dovecot.list.index.log -rw------- 1 vmail vmail 672 15. Jul 16:45 dovecot.mailbox.log -rw------- 1 vmail vmail 1781 30. Okt 01:36 dovecot-uidlist -rw------- 1 vmail vmail 8 15. Jul 16:45 dovecot-uidvalidity -r--r--r-- 1 vmail 1002 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a3 -r--r--r-- 1 vmail vmail 0 15. Sep 2018 dovecot-uidvalidity.5b9d20a5 drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Drafts drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.Fail2ban drwx------ 5 vmail vmail 4096 3. Nov 09:15 .INBOX.vzdump drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Junk drwx------ 2 vmail vmail 36864 30. Okt 01:36 new drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Quarantine drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Sent drwx------ 3 vmail vmail 4096 3. Dez 06:25 sieve -rw------- 1 vmail vmail 70 15. Jul 16:45 subscriptions drwx------ 2 vmail vmail 4096 2. Nov 16:41 tmp drwx------ 5 vmail vmail 4096 3. Nov 09:15 .Trash This should be preserved so that users don't notice the system upgrade. Dovecot 2.4 works quite differently in this regard. What solution is there for migrating both the namespace and the existing emails to Dovecot 2.4? Thank you for your suggestions ByteMe

5 21

compilation build fail
by Franck Bourdonnec 10 Dec '25

10 Dec '25

Hello, I'm used to build Dovecot since a long time without any problem. Last one 2.3.21 With 2.4.2 I get a compiler error !!! CC unix-socket-create.lo CC unlink-directory.lo CC unlink-old-files.lo CC unichar.lo CC unicode-data-types.lo CC unicode-data-tables.lo CC unicode-data.lo CC unicode-transform.lo unicode-transform.c:211:1: error: initializer element is not constant static const size_t uni_hangul_n_count = uni_hangul_v_count * uni_hangul_t_count; ^ unicode-transform.c:212:1: error: initializer element is not constant static const uint16_t uni_hangul_l_end = uni_hangul_l_base + uni_hangul_l_count; ^ unicode-transform.c:213:1: error: initializer element is not constant static const uint16_t uni_hangul_v_end = uni_hangul_v_base + uni_hangul_v_count; ^ unicode-transform.c:214:1: error: initializer element is not constant static const uint16_t uni_hangul_t_end = uni_hangul_t_base + uni_hangul_t_count; ^ Makefile:1684: recipe for target 'unicode-transform.lo' failed make[4]: *** [unicode-transform.lo] Error 1 make[4]: Leaving directory '/data/users/root/dovecot-2.4.2/src/lib' Makefile:1333: recipe for target 'all' failed I know my system is old, Opensuse Leap 42.3. Perhaps something missing , not tested ? /* * Hangul syllable (de)composition */ static const uint16_t uni_hangul_s_base = 0xac00; static const uint16_t uni_hangul_l_base = 0x1100; static const uint16_t uni_hangul_v_base = 0x1161; static const uint16_t uni_hangul_t_base = 0x11a7; static const size_t uni_hangul_l_count = 19; static const size_t uni_hangul_v_count = 21; static const size_t uni_hangul_t_count = 28; static const size_t uni_hangul_n_count = uni_hangul_v_count * uni_hangul_t_count; static const uint16_t uni_hangul_l_end = uni_hangul_l_base + uni_hangul_l_count; static const uint16_t uni_hangul_v_end = uni_hangul_v_base + uni_hangul_v_count; static const uint16_t uni_hangul_t_end = uni_hangul_t_base + uni_hangul_t_count; static const uint16_t uni_hangul_s_end = 0xD7A4; Franck !DSPAM:69384f6f6071731448408!

3 2

Permission denied errors loading configuration in 2.4.1 (running utilities as unprivileged user)
by Jason J.G. White 09 Dec '25

09 Dec '25

I noticed the following after upgrading from 2.3 to 2.4.1: if I run various Dovecot utilities as an unprivileged user, they attempt to load the entire Dovecot configuration. The configuration loading then fails with a "fatal" permission denied error while trying to access the x.509 private key, which is accessible only to root for security reasons. Example: try running sievec as a normal user to compile a Sieve script. This should work, but it doesn't for the aforementioned reason. I'm not asking for help here, as I can work around it, but I would like to make sure it's on the bug list, if not fixed already.

1 0

auth: Fatal: master: service(auth): child N killed with signal 11
by alexey＠*.com 08 Dec '25

08 Dec '25

Hello there, Got a server powered by "AlmaLinux 9.7 (Moss Jungle Cat)" with Dovecot 2.4.2 compiled from sources by directadmin with the following options: ./configure \ --with-ldap=yes \ --with-pam=yes \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --without-icu Dovecot crashes and no IMAP auth is possible on the server Got this only from dumped core: Reading symbols from /usr/libexec/dovecot/auth... (No debugging symbols found in /usr/libexec/dovecot/auth) [New LWP 3855978] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/dovecot/auth'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 (gdb) bt #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 #1 0x000055da11c889bb in auth_sasl_instance_init () #2 0x000055da11c6eb9e in ?? () #3 0x000055da11c6f4ed in auths_preinit () #4 0x000055da11c6d245 in ?? () #5 0x000055da11c6d8a0 in main () (gdb) info threads Id Target Id Frame * 1 Thread 0x7f6636273ac0 (LWP 3855978) 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 (gdb) thread apply all bt Thread 1 (Thread 0x7f6636273ac0 (LWP 3855978)): #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 #1 0x000055da11c889bb in auth_sasl_instance_init () #2 0x000055da11c6eb9e in ?? () #3 0x000055da11c6f4ed in auths_preinit () #4 0x000055da11c6d245 in ?? () #5 0x000055da11c6d8a0 in main () (gdb) thread apply all bt full Thread 1 (Thread 0x7f6636273ac0 (LWP 3855978)): #0 0x00007f6635f5fe41 in sasl_server_instance_create () from /usr/lib64/dovecot/libdovecot.so.0 No symbol table info available. #1 0x000055da11c889bb in auth_sasl_instance_init () No symbol table info available. #2 0x000055da11c6eb9e in ?? () No symbol table info available. #3 0x000055da11c6f4ed in auths_preinit () No symbol table info available. #4 0x000055da11c6d245 in ?? () No symbol table info available. #5 0x000055da11c6d8a0 in main () No symbol table info available. (gdb) Have no issue with Dovecot 2.4.1 Kindly advice. Regards, Alex.

2 2

Can't get Dovecot working with Exim
by Christopher Curzio 07 Dec '25

07 Dec '25

Hello everyone. I'm in the process of migrating my mail server to Debian running exim4 and dovecot. I was previously using exim4 and dovecot on Slackware and I moved the configs over, however I can't get dovecot working with exim on the new system. These configs worked fine previously. I did have to make some minor changes, but overall everything is mostly the same as it was. dovecot config: https://pastebin.com/Hrhj6xeb exim config: https://pastebin.com/bAQ9mTJb No matter what I do, I'm getting this when mail is received: dovecot_delivery transport output: Can't open log file /var/log/dovecot/deliver-error.log: Permi ssion denied I've tried everything, even going as far as setting permissions on /var/log/dovecot to a+rwx recursive (solely as a test) but I still get the same message. Help getting this working would be greatly appreciated since I've exhausted my own knowledge trying to wrench it into submission. Thanks. Hello everyone. I'm in the process of migrating my mail server to Debian running exim4 and dovecot. I was previously using exim4 and dovecot on Slackware and I moved the configs over, however I can't get dovecot working with exim on the new system. These configs worked fine previously. I did have to make some minor changes, but overall everything is mostly the same as it was. dovecot config: [1]https://pastebin.com/Hrhj6xeb exim config: [2]https://pastebin.com/bAQ9mTJb No matter what I do, I'm getting this when mail is received: dovecot_delivery transport output: Can't open log file /var/log/dovecot/deliver-error.log: Permi ssion denied I've tried everything, even going as far as setting permissions on /var/log/dovecot to a+rwx recursive (solely as a test) but I still get the same message. Help getting this working would be greatly appreciated since I've exhausted my own knowledge trying to wrench it into submission. Thanks. References Visible links 1. https://pastebin.com/Hrhj6xeb 2. https://pastebin.com/bAQ9mTJb

6 12

Issues with mail_crypt plugin: per-user encryption with keys from LDAP
by luis.neapolis＠gmail.com 06 Dec '25

06 Dec '25

Hi everyone, I am trying to configure Dovecot's mail_crypt plugin to support per-user encryption, with public and private keys stored in LDAP and retrieved via userdb. My Goal: 1) Each user has their own key pair (public/private) stored in LDAP. 2) Incoming emails should be encrypted via LMTP using the user’s public key. 3) Users should be able to read emails via IMAP/Webmail using their private key, which is password-protected (the user’s login password). Current situation: 1) Using global keys (same key for all users) works fine: LMTP encrypts emails and users can read them correctly. 2) When trying to use per-user keys, I get encryption errors in IMAP, because Dovecot seems to require the private key even during LMTP, even though only the public key should be needed for encryption. Typical error: lmtp(…): Failed to initialize user: mail_crypt_plugin: main: crypt_private_key_password unset, no password to decrypt the key file Example configuration (LDAP userdb): crypt_user_key_require_encrypted = yes userdb ldap { driver = ldap ldap_filter = (&(objectClass=MailClass) (mail=%{user})) result_internalfail = continue-ok fields { quota_storage_size = %{ldap:quota|default('5')}G mail_home = %{ldap:homeDirectory} crypt_global_public_key_file=inline:%{ldap:CryptoGlobalPubKey|default("")} crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:CryptoGlobalPrivKey|default('')} crypt_private_key_password=%{password} } } Questions / help requested: 1) Is it possible to configure mail_crypt so that LMTP can encrypt emails using only the user’s public key, without needing the private key? 2) What is the correct way to use per-user keys with password-protected private keys? 3) Are there any working examples of mail_crypt configurations using LDAP as the source for per-user keys? I am fully aware that LMTP needs the private key of the user even if LMTP doesn't use, but during LMTP session the user password is not available. Version: 2.4.2-1 (0962ed2104) Thanks in advance for any guidance!

1 0

Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)
by Thomas 03 Dec '25

03 Dec '25

Hello, I'm new to dovecot and greet everyone! I come from courier-imap and updated my imap server now to dovecot-2.4.2. All user directories and files were copied 1:1. In some cases, I now receive the following message in logfiles: 2025-11-28 15:20:52.184760182 Nov 28 15:20:52 imap(Email_address_hidden)<2297539><zNQfVqhEx98l90IK>: Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f8eb793ab09] -> libdovecot.so.0(backtrace_get+0x22) [0x7f8eb793ac42] -> libdovecot.so.0(+0x1493fc) [0x7f8eb79493fc] -> libdovecot.so.0(+0x149491) [0x7f8eb7949491] -> libdovecot.so.0(+0x6bde2) [0x7f8eb786bde2] -> lib95_imap_sieve_plugin.so(+0x49b7) [0x7f8eb74bb9b7] -> lib95_imap_sieve_plugin.so(+0x7c8b) [0x7f8eb74bec8b] -> libdovecot-storage.so.0(index_mail_free+0xe) [0x7f8eb7cb4c9e] -> lib95_imap_sieve_plugin.so(+0x6ef5) [0x7f8eb74bdef5] -> libdovecot-storage.so.0(mail_free+0x1a) [0x7f8eb7c29bca] -> libdovecot-storage.so.0(+0xf5c52) [0x7f8eb7cc7c52] -> libdovecot-storage.so.0(mail_index_transaction_commit_full+0x8c) [0x7f8eb7ce11ec] -> libdovecot-storage.so.0(index_transaction_commit+0xf2) [0x7f8eb7cc81f2] -> libdovecot-storage.so.0(+0xcff1e) [0x7f8eb7ca1f1e] -> lib95_imap_sieve_plugin.so(+0x8576) [0x7f8eb74bf576] -> lib15_notify_plugin.so(+0x368f) [0x7f8eb7bc668f] -> lib10_quota_plugin.so(+0xd99d) [0x7f8eb74d999d] -> libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x79) [0x7f8eb7c3bac9] -> imap(+0x1762b) [0x562bf69c462b] -> imap(command_exec+0xa4) [0x562bf69d3334] -> imap(+0x24180) [0x562bf69d1180] -> imap(+0x24214) [0x562bf69d1214] -> imap(+0x2449b) [0x562bf69d149b] -> imap(client_handle_input+0x1c5) [0x562bf69d1675] -> imap(client_input+0x73) [0x562bf69d1c33] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f8eb7960187] -> libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f8eb79618ba] -> libdovecot.so.0(io_loop_handler_run+0x51) [0x7f8eb7960231] -> libdovecot.so.0(io_loop_run+0x48) [0x7f8eb7960408] -> libdovecot.so.0(master_service_run+0x19e) [0x7f8eb78b011e] 2025-11-28 15:20:52.940692672 Nov 28 15:20:52 imap(Email_address_hiddene)<2297539><zNQfVqhEx98l90IK>: Fatal: master: service(imap): child 2297539 killed with signal 6 (core dumped) If I filter for "Panic" now I see: 2025-11-28 15:20:52.183676628 Nov 28 15:20:52 imap(Email_address_hidden)<2297539><zNQfVqhEx98l90IK>: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box) Panic repeats up to several times. In moment of crash I can find lots [# of repeats] of copies of ONE mail file in users .Trash/tmp dir. Original mail file also in e.g. INBOX/cur Please tell me wht's going on here. I checked all permission, dirs and so on. CentOS 10 s/qmail dovecot-2.4.2 dovecot-pigeonhole-2.4.2 Regards, Thomas

2 3

Defining "INBOX" in mdbox context from ldap
by Florian Lohoff 03 Dec '25

03 Dec '25

Hi, i am in the middle of converting a handful of 2.3 installations to 2.4 and while at it i fail to see a point on how to define what the INBOX is in the mdbox/ldap context. So right now i am transferring the attributes from LDAP like this (iredmail schema) fields { user=%{ldap:mail} home=%{ldap:storageBaseDirectory} mail_driver=%{ldap:MailMessageStore | index(':', 0)} mail_path=%{ldap:mailMessageStore | index(':', 1)} quota_storage_size=%{ldap:mailQuota} } I fail to find the syntax for "mail_inbox_path" - In maildir its obvious. I tried various things but it mainly failed on me. I now removed it completely from the config which it seems makes the dbox/mdbox driver assume a sane default of "INBOX". But i am still wondering how do i configure the INBOX. I'd like to fetch that information from LDAP as i think i still have a handful of Maildir/mdbox mix installations. Flo -- Florian Lohoff f(a)zz.de Any sufficiently advanced technology is indistinguishable from magic.

1 0

Re: Dovecot 2.4.1 with mbox format
by "Tóth Attila" 02 Dec '25

02 Dec '25

Hi Bill, 2025.December 1.(H) 23:56 időpontban Bill Steinberg via dovecot ezt írta: > Hello again, > I didn't fully read the section in the documentation about using the > mbox > format. There is a setting, mail_inbox_path = /var/mail/%{user} to > specify > the iNBOX location for mails that are stored in /var/mail. > After setting mail_inbox_path I did initially have an issue about > dovecot > being able to write dotlock files, which was noted in the > documentation. I > was able to fix by adding users to the group "mail". > I am using these settings in the new server now: > > mail_driver = mbox > > mail_path = ~/mail > > mail_inbox_path = /var/mail/%{user} > > mail_index_path = ~/mail/index > > mail_control_path = ~/mail/control I'm struggling with the same setup as yourself. Sendmail delivers mails under /var/spool/mail/username and mail user agents were fetching the incoming mail from there and put them under /home/username/mail. This has been fine for ages - I have to say decades now. While 2.3 created files/directories in the name of the current user under ~/mail, 2.4 tries to write as mail:mail and therefore gets denied, since the user directories are owned by username:users and obviously have no permissions for other users. This change of behaviour is unacceptable in my opinion and 2.4 should also act in the name of the actual user. If some of the files would be owned by mail:mail and others by username:users: that would be a mess and the user would not be able to read contents using other user agents (for e.g. alpine) or make a backup of their own emails using an arbitrary tool or script of their own. For this reason I downgraded back to 2.3, because I have no time to dig deeper into this and reintroduce the mechanism granting current user access rights - running certain processes under proper conditions. Bill: how do you achieve that dovecot creates and writes files in users home directories in the name of the current user? Back in the good old 2.3 days I had this in the config and everything just worked as expected: mail_location = mbox:~/mail/:INBOX=/var/spool/mail/%u In case of the new 2.4 version I was unsuccessful with the following: mail_driver = mbox mail_path = /home/%{user}/mail mail_inbox_path = /var/spool/mail/%{user} server dovecot: imap(user)<48978><1LgipBQ3LO1/AAAB>: Error: mkdir(/home/user/mail/.imap) failed: Permission denied (euid=8(mail) egid=12(mail) missing +x perm: /home/user/mail, dir owned by 1000:100 mode=0700) Although I haven't specified mail_index_path and mail_control_path as you, I wouldn't expect this to make any difference regarding user rights. I'm aware, that mbox is deprecated, but still: this is a regression from my point of view. So how about user rights in your case Bill? Thanks: Dwokfur > > On Dec 1, 2025, at 10:18AM, Bill Steinberg via dovecot > <dovecot(a)dovecot.org> wrote: > Hello, > I'm attempting to upgrade a mbox format based dovecot server to the > latest > 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot > server > I'm attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in > the > user's ~/mail location For example Sent, Trash, Drafts, ... In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u",so when a client connects to the > dovecot > server their sendmail based mbox /var/mail isn't visible. Additionally mbox folders directly under a user's ~/mail iike Sent, > Trash, > Drafts are not visible either. > The new 2.4.1 dovecot server creates a folder named "inbox" under > ~/mail > as well as an .imap directory which contains directories that > appear > to > correspond to the folders at the top level along with other dovecot > based > files. > Can you describe how I would make the seamail delivered mail in > /var/spool > as well as a users top level mbox folders accessible in the new > dovecot > mbox structures? > Thanks in advance for any help, > -Bill > ====================================== > Dovecot config > ====================================== > > dovecot_config_version = 2.4.1 > > dovecot_storage_version = 2.4.1 > > protocols { > > imap = yes > > lmtp = yes > > } > > mail_driver = mbox > > mail_home = /home/%{user} > > mail_path = ~/mail > > mbox_write_locks = fcntl > > namespace inbox { > > inbox = yes > > separator = / > > } > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org >

3 4

Dovecot 2.4.1 with mbox format
by Bill Steinberg 02 Dec '25

02 Dec '25

Hello, I’m attempting to upgrade a mbox format based dovecot server to the latest 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot server I’m attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in the user’s ~/mail location For example Sent, Trash, Drafts, … In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u”,so when a client connects to the dovecot server their sendmail based mbox /var/mail isn’t visible. Additionally mbox folders directly under a user’s ~/mail iike Sent, Trash, Drafts are not visible either. The new 2.4.1 dovecot server creates a folder named “inbox” under ~/mail as well as an .imap directory which contains directories that appear to correspond to the folders at the top level along with other dovecot based files. Can you describe how I would make the seamail delivered mail in /var/spool as well as a users top level mbox folders accessible in the new dovecot mbox structures? Thanks in advance for any help, -Bill ====================================== Dovecot config ====================================== dovecot_config_version = 2.4.1 dovecot_storage_version = 2.4.1 protocols { imap = yes lmtp = yes } mail_driver = mbox mail_home = /home/%{user} mail_path = ~/mail mbox_write_locks = fcntl namespace inbox { inbox = yes separator = / } Hello, I'm attempting to upgrade a mbox format based dovecot server to the latest 2.4.1 on Fedora release 43. I am using sendmail at the MTA. I have provided a synopsis of my 2.4.1 dovecot config below. The dovecot server I'm attempting to upgrade is running dovecot 2.3.21 on Fedora 37. In the 2.3.21 setup all mbox based folders are at the top level in the user's ~/mail location For example Sent, Trash, Drafts, ... In dovecot 2.4.1 this setting no longer works: "mail_location = mbox:~/mail:INBOX=/var/mail/%u",so when a client connects to the dovecot server their sendmail based mbox /var/mail isn't visible. Additionally mbox folders directly under a user's ~/mail iike Sent, Trash, Drafts are not visible either. The new 2.4.1 dovecot server creates a folder named "inbox" under ~/mail as well as an .imap directory which contains directories that appear to correspond to the folders at the top level along with other dovecot based files. Can you describe how I would make the seamail delivered mail in /var/spool as well as a users top level mbox folders accessible in the new dovecot mbox structures? Thanks in advance for any help, -Bill ====================================== Dovecot config ====================================== dovecot_config_version = 2.4.1 dovecot_storage_version = 2.4.1 protocols { imap = yes lmtp = yes } mail_driver = mbox mail_home = /home/%{user} mail_path = ~/mail mbox_write_locks = fcntl namespace inbox { inbox = yes separator = / }

1 1