- dovecot - dovecot.org

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