April 2025 - 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

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