- dovecot - dovecot.org

Late E-Mails
by Kent Borg 03 Apr '25

03 Apr '25

This morning I noticed e-mail out of sequence. I looked in `/var/log/mail.log` and postfix seems to have handled them correctly, recording the same things for them as any other e-mail, and in sensible sequence with the surrounding timestamps. But in my e-mail client (Thunderbird) some were delayed when viewed as I always do by "Order Received". These are the examples I noticed, when compared to surrounding messages: * 1 delayed ~3-hours, then 4-hours after that… * 7 delayed ~16-hours, followed immediately by… * 2 delayed over 5-hours. Other notes: * Thunderbird was not running at the time that these came in (that computer was asleep). * I am running dsync between two servers and both servers show the same details in Thunderbird (so syncing seems working). * I don't notice any dovecot errors in the log in the vicinity of when the delayed e-mails were processed by postfix, nor when the surrounding e-mails were processed by postfix. * There were no reboots during this period. * I do see some other little timestamp "errors", but these seem to be mailing list messages getting an internal timestamp a couple minutes before the message got delivered to my server (I also will see spam with completely false timestamps, but that it not what is going on here). Does Dovecot sometimes not notice new mail? Thanks, -kb/ / This morning I noticed e-mail out of sequence. I looked in `/var/log/mail.log` and postfix seems to have handled them correctly, recording the same things for them as any other e-mail, and in sensible sequence with the surrounding timestamps. But in my e-mail client (Thunderbird) some were delayed when viewed as I always do by "Order Received". These are the examples I noticed, when compared to surrounding messages: * 1 delayed ~3-hours, then 4-hours after that… * 7 delayed ~16-hours, followed immediately by… * 2 delayed over 5-hours. Other notes: * Thunderbird was not running at the time that these came in (that computer was asleep). * I am running dsync between two servers and both servers show the same details in Thunderbird (so syncing seems working). * I don't notice any dovecot errors in the log in the vicinity of when the delayed e-mails were processed by postfix, nor when the surrounding e- mails were processed by postfix. * There were no reboots during this period. * I do see some other little timestamp "errors", but these seem to be mailing list messages getting an internal timestamp a couple minutes before the message got delivered to my server (I also will see spam with completely false timestamps, but that it not what is going on here). Does Dovecot sometimes not notice new mail? Thanks, -kb

1 0

Issue: Attachment from Later Email Appears on Earlier Email
by postfix_dovecot＠gmx.de 03 Apr '25

03 Apr '25

Hello, Today, I encountered a very strange phenomenon, and I'm not sure if Dovecot is involved: A user sent an email at 11:55 AM with a PDF attachment. When checking their inbox in Outlook, they noticed that this exact PDF had somehow been attached to an email that was originally received at 10:50 AM. I verified the timestamps in the logs, and they are correct. So essentially, the attachment from a later-sent email was appended to an earlier-received email sitting in the inbox-even though the two messages are completely unrelated. I have never seen anything like this before-how is this even possible? Does anyone have any advice? Thanks in advance! Jens Hello, Today, I encountered a very strange phenomenon, and I’m not sure if Dovecot is involved: A user sent an email at 11:55 AM with a PDF attachment. When checking their inbox in Outlook, they noticed that this exact PDF had somehow been attached to an email that was originally received at 10:50 AM. I verified the timestamps in the logs, and they are correct. So essentially, the attachment from a later-sent email was appended to an earlier-received email sitting in the inbox—even though the two messages are completely unrelated. I have never seen anything like this before—how is this even possible? Does anyone have any advice? Thanks in advance! Jens

2 1

[Dovecot] auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied
by mailing＠securitylabs.it 03 Apr '25

03 Apr '25

Hello, just upgraded one of my testing machine from dovecot 1.2.15 to 2.0.7. After some trouble with permissions now all seems working, but when I stop dovecot I have these errors in log: Nov 9 17:08:07 in dovecot: master: Warning: Killed with signal 15 (by pid=20362 uid=0 code=kill) Nov 9 17:08:07 in dovecot: pop3-login: Error: read(anvil) failed: EOF Nov 9 17:08:07 in dovecot: imap-login: Error: read(anvil) failed: EOF Nov 9 17:08:07 in dovecot: imap(mailing(a)securitylabs.it): Server shutting down. bytes=410/59361 Nov 9 17:08:07 in dovecot: imap(mailing(a)securitylabs.it): Server shutting down. bytes=79/26605 Nov 9 17:08:07 in dovecot: imap(mailing(a)securitylabs.it): Server shutting down. bytes=802/55708 Nov 9 17:08:07 in dovecot: imap(mailing(a)securitylabs.it): Server shutting down. bytes=258/1242 Nov 9 17:08:07 in dovecot: auth: Error: read(anvil-auth-penalty) failed: EOF Nov 9 17:08:07 in dovecot: auth: Error: net_connect_unix(anvil-auth-penalty) failed: Permission denied dovecot -n: # 2.0.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-686 i686 Debian squeeze/sid auth_cache_negative_ttl = 2 mins auth_cache_size = 1000 M auth_cache_ttl = 2 mins auth_master_user_separator = * auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@& disable_plaintext_auth = no dotlock_use_excl = yes first_valid_uid = 100 last_valid_uid = 105 lock_method = dotlock log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Server ready. mail_fsync = never mail_gid = Debian-exim mail_location = maildir:~/Maildir:INDEX=/var/indexes/%d/%n mail_privileged_group = Debian-exim mail_uid = Debian-exim managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = separator = / type = private } namespace { location = maildir:~/Maildir/expunged prefix = EXPUNGED/ separator = / type = private } namespace { location = maildir:~/Maildir/deleted prefix = DELETED/ separator = / type = private } namespace { location = maildir:~/Maildir/deleted/expunged prefix = DELETED/EXPUNGED/ separator = / type = private } passdb { args = /usr/local/etc/dovecot-sql.conf driver = sql } passdb { args = /usr/local/etc/passwd.masterusers driver = passwd-file master = yes pass = yes } plugin { lazy_expunge = EXPUNGED/ DELETED/ DELETED/EXPUNGED/ mail_log_events = delete expunge mail_log_group_events = quota = maildir quota_warning = storage=80%% /usr/local/bin/dovecot-quota-warning.sh 80 quota_warning2 = storage=90%% /usr/local/bin/dovecot-quota-warning.sh 90 sieve = ~/.dovecot.sieve } pop3_no_flag_updates = yes protocols = imap pop3 service auth { unix_listener auth-userdb { group = Debian-exim mode = 0600 user = Debian-exim } } service imap-login { client_limit = 256 process_limit = 128 process_min_avail = 3 service_count = 1 } service imap { drop_priv_before_exec = yes process_limit = 256 vsz_limit = 256 B } service pop3-login { client_limit = 256 process_limit = 128 process_min_avail = 3 service_count = 1 } service pop3 { drop_priv_before_exec = yes process_limit = 256 vsz_limit = 256 B } ssl_cert = </usr/local/etc/dovecot.crt ssl_key = </usr/local/etc/dovecot.key userdb { args = /usr/local/etc/dovecot-sql.conf driver = sql } protocol imap { mail_max_userip_connections = 10 mail_plugins = " notify quota imap_quota mail_log lazy_expunge" } protocol pop3 { mail_max_userip_connections = 3 mail_plugins = " notify quota mail_log" pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = quota sieve postmaster_address = postmaster(a)securitylabs.it } My /usr/local/var/run/dovecot directory: 4 drwxr-sr-x 4 root staff 4096 Nov 9 17:08 . 4 drwxrwsrwx 3 root staff 4096 Nov 9 17:05 .. 0 srw------- 1 root staff 0 Nov 9 17:05 anvil 0 srw------- 1 root staff 0 Nov 9 17:05 anvil-auth-penalty 0 srw------- 1 root staff 0 Nov 9 17:05 auth-client 0 srw------- 1 dovecot staff 0 Nov 9 17:05 auth-login 0 srw------- 1 root staff 0 Nov 9 17:05 auth-master 0 srw------- 1 Debian-exim Debian-exim 0 Nov 9 17:05 auth-userdb 0 srw------- 1 dovecot staff 0 Nov 9 17:05 auth-worker 0 srw------- 1 root staff 0 Nov 9 17:05 config 0 srw------- 1 root staff 0 Nov 9 17:05 dict 0 srw------- 1 root staff 0 Nov 9 17:05 director-admin 0 srw-rw-rw- 1 root staff 0 Nov 9 17:05 dns-client 0 srw------- 1 root staff 0 Nov 9 17:05 doveadm-server 0 lrwxrwxrwx 1 root staff 35 Nov 9 17:05 dovecot.conf -> /usr/local/etc/dovecot/dovecot.conf 4 drwxr-xr-x 2 root root 4096 Nov 9 17:05 empty 4 drwxr-x--- 2 root dovenull 4096 Nov 9 17:05 login My emails are delivered as user Debian-exim and users are virtual in a MySQL DB. This system is behind a proxy (so the master user)

3 2

lmtp problems with dovecot while seeking to build dovecot, postfix, mailman3, opendkim on Debian 12
by pjbondi＠systemdatabase.com 02 Apr '25

02 Apr '25

Hello to all: I have been trying to integrate and to stand up dovecot, postfix, mailman3 and opendkim. I have been studying the following: - https://www.frontline.ro/en/blog/how-to-configure-opendkim-with-postfix-on-… - https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… - https://www.linuxbabe.com/mail-server/build-email-server-from-scratch-debia… - https://www.linuxbabe.com/mail-server/install-dovecot-imap-server-debian This appears to be the best available coaching, but it would take me weeks to find the time to follow this post: - https://pieterhollander.nl/post/mailserver/ I was trying to place the Maildir outside my Debian 12 virtual machine for easier backup. The directory /Debian-12-dovecot-Maildir is setup as NFS share on my NAS. I can orchestrate a daily backup or an rclone of that to OneDrive or some other cloud target via my NAS. I have these errors: Apr 02 11:17:01 shackleton12 postfix/local[795238]: CA26A2D23: passing <mailman(a)systemdatabase.ca> to transport=lmtp Apr 02 11:17:01 shackleton12 postfix/local[795238]: warning: connect #1 to subsystem private/lmtp: Connection refused Apr 02 11:07:00 shackleton12 systemd[1]: Starting dovecot.service - Dovecot IMAP/POP3 email server... Apr 02 11:07:00 shackleton12 dovecot[789615]: Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp Apr 02 11:07:00 shackleton12 dovecot[789615]: master: Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp Apr 02 11:07:00 shackleton12 dovecot[789615]: Fatal: Failed to start listeners Apr 02 11:07:00 shackleton12 dovecot[789615]: master: Fatal: Failed to start listeners Apr 02 11:07:00 shackleton12 systemd[1]: dovecot.service: Main process exited, code=exited, status=89/n/a Apr 02 11:07:00 shackleton12 systemd[1]: dovecot.service: Failed with result 'exit-code'. Apr 02 11:07:00 shackleton12 systemd[1]: Failed to start dovecot.service - Dovecot IMAP/POP3 email server. postconf -n doveconf -n postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no compatibility_level = 3.6 inet_protocols = ipv4 local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp mailbox_size_limit = 0 mailbox_transport = lmtp:unix:private/dovecot-lmtp masquerade_domains = systemdatabase.ca milter_default_action = accept milter_protocol = 2 mydestination = $myhostname, systemdatabase.ca, localhost.systemdatabase.ca, localhost, systemdatabase.homelinux.com mydomain = systemdatabase.ca myhostname = systemdatabase.ca mynetworks = 127.0.0.0/8 myorigin = systemdatabase.ca non_smtpd_milters = $smtpd_milters owner_request_special = no proxy_interfaces = 192.168.1.8 readme_directory = no recipient_delimiter = + relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains relayhost = [smtp.bellnet.ca]:25 smtp_tls_loglevel = 1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_security_level = may smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_milters = inet:localhost:8891 smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination permit_inet_interfaces smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination permit_inet_interfaces smtpd_tls_cert_file = /etc/letsencrypt/live/systemdatabase.ca-0001/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/systemdatabase.ca-0001/privkey.pem smtpd_tls_loglevel = 1 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_security_level = may smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtputf8_enable = no transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 doveconf -n # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-32-amd64 x86_64 Debian 12.10 nfs4 # Hostname: shackleton12.systemdatabase.ca auth_mechanisms = plain login auth_username_format = %n mail_location = maildir:/Debian-12-dovecot-Maildir/%d-%u-Maildir mail_privileged_group = mail namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/systemdatabase.ca-0001/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = passwd }

2 1

Bug: dovecot 2.3.21.1 fails to build with recent ICU
by Marcel Telka 01 Apr '25

01 Apr '25

Hi, dovecot 2.3.21.1 fails to build with ICU 77. There are also reports it does not build with ICU 76 for the same reason: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284832 There is no issue when built with ICU 75. The failure is this: /bin/bash ../../libtool --tag=CC --mode=link /usr/gcc/14/bin/gcc -std=gnu99 -m64 -O3 -Wno-incompatible-pointer-types -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 -I/usr/openssl/3/include -no-undefined -m64 -o test-fts-icu test-fts-icu.o fts-icu.lo -licui18n ../lib-test/libtest.la ../lib/liblib.la -lsocket -lnsl -lsendfile libtool: link: /usr/gcc/14/bin/gcc -std=gnu99 -m64 -O3 -Wno-incompatible-pointer-types -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 -I/usr/openssl/3/include -m64 -o test-fts-icu test-fts-icu.o .libs/fts-icu.o -licui18n ../lib-test/.libs/libtest.a ../lib/.libs/liblib.a -lsocket -lnsl -lsendfile Undefined first referenced symbol in file ucasemap_utf8ToLower_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_strFromUTF8Lenient_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_errorName_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_cleanup_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ucasemap_close_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) u_strToUTF8WithSub_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ucasemap_open_77 .libs/fts-icu.o (symbol belongs to implicit dependency /usr/lib/amd64/libicuuc.so.77) ld: fatal: symbol referencing errors. No output written to test-fts-icu collect2: error: ld returned 1 exit status The workaround is easy: to add -licuuc to LDFLAGS, however it would be great if dovecot builds without any workarounds needed. Thank you. -- +-------------------------------------------+ | Marcel Telka e-mail: marcel(a)telka.sk | | homepage: http://telka.sk/ | +-------------------------------------------+

3 2

Dovecot v2.4.1 released
by Aki Tuomi 31 Mar '25

31 Mar '25

Hi! We arey happy to release Dovecot v2.4.1! Some IMPORTANT things to notice (still): - We have changed the signing key for 2.4 going forward, releases are signed with EF0882079FD4ED32BF8B23B2A1B09EF84EDC5219, which can be found at https://repo.dovecot.org/DOVECOT-REPO-GPG-2.4 and is signed with the previous key. The old key has been renamed to https://repo.dovecot.org/DOVECOT-REPO-GPG-2.3. - New 2.4 packages **are not** compatible with old 2.3 configuration, please carefully review https://doc.dovecot.org/2.4.1/installation/upgrade/2.3-to-2.4.html before installing the new packages. - We are happy to provide experimental arm64 support in the form of a Docker image. There are now three kinds of images, latest, latest-dev and latest-root. - The latest docker image is now ran rootless, with UID 1000 as vmail. Please take this into consideration when upgrading. The latest-root image still runs as root. Latest 2.3 image can be used with tag 2.3-latest still We won't be sending separate mail about Pigeonhole anymore as we will release one anyways when we release Dovecot, and Pigeonhole versioning has been changed to match Dovecot versioning. Source codes available at - https://www.dovecot.org/releases/2.4/dovecot-2.4.1.tar.gz - https://www.dovecot.org/releases/2.4/dovecot-2.4.1.tar.gz.sig - https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.1.tar.gz - https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.1.tar.gz… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Kind regards, Aki Tuomi Open-Xchange oy --- Dovecot Core NEWS ----------------- * auth: Change unix_listener/auth-userdb/group = $SET:default_internal_group This change needs dovecot_config_version=2.4.1. * auth: lua - Remove support for single string result. * imap: Unconditionally advertise SPECIAL-USE capability. * lib-dcrypt: Install dcrypt_openssl.so into dovecot modules directory. * lib-master: For glibc, default MALLOC_MMAP_THRESHOLD_=131072. * lib-storage: Change default mail_cache_fields to: hdr.date hdr.subject hdr.from hdr.sender hdr.reply-to hdr.to hdr.cc hdr.bcc hdr.in-reply-to hdr.message-id date.received size.virtual imap.bodystructure mime.parts hdr.references hdr.importance hdr.x-priority hdr.x-open-xchange-share-url pop3.uidl pop3.order. This change needs dovecot_config_version=2.4.1. * lib-var-expand: Use moduledir instead of pkglibdir for crypt. * lmtp: Change the default lmtp_user_concurrency_limit to 10. This change needs dovecot_config_version=2.4.1. * lmtp: Change the default service_restart_request_count to 1. This change needs dovecot_config_version=2.4.1. + auth: Allow configuring passdb/userdb sql to use auth-workers. + config: Add default group @mailbox_defaults = english. + config: Improve "Unknown setting" error with more details and suggestions. + doveconf: Add -U parameter to ignore unknown settings in config file. + fts-flatcurve: Support lock files in VOLATILEDIR. + imap-acl: Add support for the IMAP LIST-MYRIGHTS capability (RFC 8440). + imap-client: Support ANONYMOUS authentication. + imap: Implement support for the REPLACE capability. - auth: ldap - Passdb fields were ignored with passdb_ldap_bind_userdn=yes. - auth: lua - Fix error result handling in lua passdb/userdb. - auth: oauth2 - When building oauth2 failure reply, memory would leak. - config: local_name handling would work wrong with multiple names and wildcards. - fts-flatcurve: A potential crash could occur when searching virtual mailboxes. Fixes: Panic: file fts-search.c: line 87 (level_scores_add_vuids): assertion failed: (array_count(&vuids_arr) == array_count(&br->scores)) - fts-flatcurve: Maybe queries were done wrong. - fts-flatcurve: Non-selectable mailboxes were not ignored when doing optimize/rescan. - fts-flatcurve: Signal 11 crash could happen with fts rescan. - fts: Fix crash caused by event object lifecycle mishandling. - imap-hibernate: Client counters would get reset on unhibernation, affecting imap_logout_format variables. - imap: Crash would occur with Maildir when trying to send INPROGRESS during mailbox syncing. - ldap: Dovecot could not be compiled without LDAP. - lib-dcrypt: Output stream encryption can cause assert crash if attempting to encrypt over 64 GiB of data with GCM. This is still not supported with GCM, but it fails better. - lib-http: HTTP client context memory usage was increasing. - lib-http: Pipeline corruption could happen after 100 Continue response. - lib-settings: Variable expansion initialization could crash with Panic: file settings.c: line 1560 (settings_var_expand_init_add): assertion failed: (I_MAX(num_tables, num_provs) == num_ctx) - lib-smtp: Pipelining initial SASL response after AUTH was broken. - lib-var-expand: If filter failed, memory leak would occur. - lib-var-expand: Older bison versions did not have error symbol for handling causing unexpected behaviour on the parser on error conditions. - quota: Quota calculations had minor bugs causing small errors. Pigeonhole NEWS --------------- - global: Fix settings handling bugs. Especially %variables weren't working in various settings. - ldap: Pigeonhole could not be built without LDAP.

5 8

For additional modules, the mail_plugin_dir parameter is ignored
by Lafiel 31 Mar '25

31 Mar '25

Hi. The NixOS distribution for Dovecot uses a patch that hardcodes the path to the plugins in `/etc/dovecot/modules`. The modules themselves are located at `/nix/store/z9kf4ri8sq9f3r510qsm59g1n6kfc7q6-dovecot-2.3.21.1/lib/dovecot`, the script creates symlinks in the `/etc/dovecot/modules` directory. The additional modules are loaded normally. Now I want to remove the patch. I added the parameter `“--with-moduledir=$(out)/etc/dovecot/modules”`, and the modules are located at path `/nix/store/wb885d6w5dfchg9v481f55zj4a2p3r89-dovecot-2.3.21.1/etc/dovecot/modules`. In the configuration I added the parameter `mail_plugin_dir = /etc/dovecot/modules`. The main modules load fine, but the optional modules don't want to load: ``` Error: Plugin 'imap_sieve' not found from directory /nix/store/wb885d6w5dfchg9v481f55zj4a2p3r89-dovecot-2.3.21.1/etc/dovecot/modules ``` For additional modules, the mail_plugin_dir parameter is ignored. Temporary solution - in src/config/config-parser.h file I replaced the line ``` #define CONFIG_MODULE_DIR MODULEDIR"/settings” ``` by ``` #define CONFIG_MODULE_DIR “/etc/dovecot/modules/settings” ``` -- Best regards, Lafiel mailto:lafiel@elven.pw

2 5

Bug: Inconsistency in configuration between various clients.
by Louis Schmitz 27 Mar '25

27 Mar '25

We found out about this through a misconfiguration in our web panel. In the main config file the following line includes a subdirectory; !include conf.d/*.conf The web panel created the following two relevant configuration snippets in /etc/dovecot/conf.d/ 11-plesk-security-ssl.conf > ssl_dh=</opt/psa/etc/dhparams2048.pem > ssl_min_protocol=TLSv1.2 > ssl_cipher_list=EECDH+AESGCM+AES128:EECDH+AESGCM+AES256:EECDH+CHACHA20:EECDH+SHA256+AES128:EECDH+SHA384+AES256:EECDH+SHA1+AES128:EECDH+SHA1+AES256:EECDH+HIGH:AESGCM+AES128:AESGCM+AES256:CHACHA20:SHA256+AES128:SHA256+AES256:SHA1+AES128:SHA1+AES256:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!KRB5:!aECDH:!kDH:!EDH > ssl_prefer_server_ciphers=yes > ssl=yes > ssl_cert=</etc/dovecot/private/dovecot.pem > ssl_key=</etc/dovecot/private/dovecot.pem This sets a server wide certificate as being the cert in /etc/dovecot/private/dovecot.pem. Let's say our main server domain is 'acme.com' for example, its 'hostname' (linux hostname) is for example 's02.acme.com'. Then it would also create 14-plesk-sni-mail.acme.com.conf, containing something akin to: > local_name mail.acme.com { > ssl_cert = </opt/psa/var/certificates/scf7b9lcY > ssl_key = </opt/psa/var/certificates/scf7b9lcY > } These point to the ssl cert and key configured for that specific vhost (not the entire server), which can be different from that configured for the server. When some clients connected to the server (connecting to mail.acme.com) it would serve the /etc/dovecot/private/dovecot.pem certificate. This was renewed and the clients would work without issue. Other clients, however, used the certificate at /opt/psa/var/certificates/scf7b9lcY. This certificate is supposed to be the same, but expired and wasn't renewed along with the other one. This was tricky to figure out since the problems did not appear on our side, only when looking at a client. Once I went around the panel GUI and into the actual dovecot configuration files I found the culprit(s). I think, but do not know, that it could be related to which IP protocol (V4 or V6) is used to connect to dovecot. All clients who failed happened to connect over V6. The cases that did not used V4. This seems entirely unrelated and strange behaviour that must be a bug of some kind. Either both should use the one certificate, or the other, or there should be an error or warning if local_name includes a variant subdomain of the server name, the latter in addition to making a consistent choice. It appears that sometimes the first relevant ssl_key and ssl_cert are used, and other times the second when the option is included twice in the configuration, pointing to different matching certificates/keys. It's not apparently a race condition: The behaviour is very consistent for the same client connecting.

1 0

Input Buffer Full with OAuth login
by Brad Koehn 26 Mar '25

26 Mar '25

I’m running Dovecot 2.3.21.1 using Authentik for OAuth authentication. I’m using SOGo 5.12.0 as a UI, also with OAuth authentication. When SOGo connects to Dovecot and authenticates with OAuth, it fails and the following is logged: imap-login: Info: Disconnected: Input buffer full (no auth attempts in 0 secs): user=<>, rip=10.42.1.1, lip=10.42.1.196, TLS, session=<NZnp7zMxQuMKKgEB> My dovecot-oauth2.conf.ext looks like this: openid_configuration_url = https://auth.koehn.com/application/o/dovecot-oauth2/.well-known/openid-conf… introspection_url = https://auth.koehn.com/application/o/introspect/ introspection_mode = post client_id = [redacted] client_secret = [redacted] username_attribute = email debug = yes rawlog_dir = /tmp/oauth2 And my auth-oauth2.conf.ext looks like this: passdb { driver = oauth2 mechanisms = xoauth2 oauthbearer args = /etc/dovecot/conf.d/dovecot-oauth2.conf.ext } I’m using the Dovecot Debian packages from repo.dovecot.org. I’ve tried auth for introspection_mode, to no avail. There’s nothing extra in the logs when I turn on debug, and there’s nothing logged in the /tmp/oauth2 directory either, FWIW. Any ideas? — Brad I’m running Dovecot 2.3.21.1 using Authentik for OAuth authentication. I’m using SOGo 5.12.0 as a UI, also with OAuth authentication. When SOGo connects to Dovecot and authenticates with OAuth, it fails and the following is logged: imap-login: Info: Disconnected: Input buffer full (no auth attempts in 0 secs): user=<>, rip=10.42.1.1, lip=10.42.1.196, TLS, session=<NZnp7zMxQuMKKgEB> My dovecot-oauth2.conf.ext looks like this: openid_configuration_url = https://auth.koehn.com/application/o/dovecot- oauth2/.well-known/openid-configuration introspection_url = https://auth.koehn.com/application/o/introspect/ introspection_mode = post client_id = [redacted] client_secret = [redacted] username_attribute = email debug = yes rawlog_dir = /tmp/oauth2 And my auth-oauth2.conf.ext looks like this: passdb { driver = oauth2 mechanisms = xoauth2 oauthbearer args = /etc/dovecot/conf.d/dovecot-oauth2.conf.ext } I’m using the Dovecot Debian packages from repo.dovecot.org. I’ve tried auth for introspection_mode, to no avail. There’s nothing extra in the logs when I turn on debug, and there’s nothing logged in the /tmp/ oauth2 directory either, FWIW. Any ideas? — Brad

3 3

Dovecot and IP check at the user connection (auth-worker problems: no IP...)
by ik7xja＠gmail.com 26 Mar '25

26 Mar '25

Hi to all, I'm using Postfix and Dovecot for my little server. I'm experimenting many false user caming fron the entire world to access to my account. I'm only in a country and I would like to restrict accesso to user coming from IPs located in my country. Since the access is granteg by mysql and SQL in passdb and userdb, I've created a table with only the IPs of my country and check the user remote IP. The trick is working well when I try to access to my account beacuse the variable "%r" is not empy... But... But when there is a delivery of a new message, the auth-worker have no IP and the check fail: auth-worker<5>: sql(user(a)my.domain): unknown user and the new message, coming in my box from other servers come back to the sender as "unknown user" There is a way to user a different query in this auth-worker process (I guess is using the same SQL with the IP-check)? Or "force" an IP (like 127.0.0.1) in the auth-worker invocation? Thanks in advance for any advice.

1 1