- dovecot - dovecot.org

(2.3->2.4) How to expunge with hierarhy saving?
by Kamil Jońca 03 May '25

03 May '25

I have used lazy_expunge plugin with namespace (configuration convert): namespace expunged { mail_driver = maildir mail_path = ~/Mail/expunged/ hidden = yes inbox = no list = no prefix = .EXPUNGED/ separator = / } with lazy_expunge_mailbox = .EXPUNGED this allowed me to keep hierarchy (i.e.mails from "admin" mailbox were expunged to "~/Mail/expunged/admin" ) this is no longer true - the best I can achieve is to have single mailbox with all mails :( Is it possible to get older behavior? (lazy_expunge_mailbox = .EXPUNGED/ - ends with error) KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Zuzanka najwyraźniej pełni obowiązki Albina Siwaka w tej ekipie... (C) Slawek Kotynski w dyskusj nt. pl.whatewer.SETI@home...

1 0

GSSAPI authentication regression with 2.4.x
by Noah Meyerhans 02 May '25

02 May '25

While preparing the Debian packages of Dovecot 2.4.1, I encountered what appears to be a regression that impacts the ability of some clients to successfully negotiate gssapi/krb5 authentication. The regression has so far been observed in gsasl, which was able to successfully authenticate to 2.3.19 but cannot authenticate to 2.4.1. Mutt is able to successfully authenticate with 2.3.19 and 2.4.1. Doveconf output is attached. The debug logs for both failed (gsasl) and successful (mutt) authentications follow. Note that all logs are from an ephemeral debug environment, and sensitive data is not redacted. I can provide additional information as needed, and can test different code and/or configuration changes. Failed authentication dovecot debug log: Apr 30 13:40:09 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:40:09 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:40:09 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libmech_gssapi.so Apr 30 13:40:09 auth: Debug: Read auth token secret from /home/noahm/dovecot-root/b/auth-token-secret.dat Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: Server accepted connection (fd=18) Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: auth client connected (pid=6791) Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: AUTH 1 GSSAPI protocol=imap final-resp-ok session=FhRIDv8zdMzAqAHa lip=172.18.0.205 rip=192.168.1.218 lport=17436 rport=52340 Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: gssapi: Using all keytab entries Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: CONT 1 # Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: CONT 1 # (previous base64 data may contain sensitive data) Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: gssapi: Processed incoming packet correctly, waiting for another. Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: CONT 1 YEcGBisGAQUFAqA9MDugDTALBgkqhkiG9xIBAgKjKjAooCYbJG5vdF9kZWZpbmVkX2luX1JGQzQxNzhAcGxlYXNlX2lnbm9yZQ== Apr 30 13:40:09 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client in: CONT 1 YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwMCJkwg3LL7QqlEOunOjvQzpXmA/LMbdtEDyW9b0EQNFL9KFkNuRKDC3V8SFkmG1KlEEHFp2GQNij6AN89xvmEGvhj3tqC280awJs8ve3Bbr7GHRJoFO/sikSRsol1HD/K3sC9OMDufEEItsWf94uu8SmEBpB2OBOzedtfw+PRpoWyYUJYEfAL9T4w0KmBD26KVcehzIv8e3vOl52aT3x9Ovjnw8RfFkZa+t/iGhMpYpf8ApWExZDWBZ6uzVJxcAPg== (previous base64 data may contain sensitive data) Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: Auth request finished Apr 30 13:40:09 auth(?,192.168.1.218,sasl:gssapi)<FhRIDv8zdMzAqAHa>: Debug: delaying auth failure Apr 30 13:40:11 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: client passdb out: FAIL 1 Apr 30 13:40:11 auth: Debug: conn unix:login (pid=6791,uid=1000) [1]: Disconnected: Connection closed (fd=18) And the corresponding client log: noahm@42b23a0b5002:~$ gsasl -m GSSAPI -d --no-starttls --imap dovecot-test 17436 Trying 'dovecot-test'... * OK [CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI . OK Pre-login capabilities listed, post-login capabilities have more. . AUTHENTICATE GSSAPI + YEcGBisGAQUFAqA9MDugDTALBgkqhkiG9xIBAgKjKjAooCYbJG5vdF9kZWZpbmVkX2luX1JGQzQxNzhAcGxlYXNlX2lnbm9yZQ== YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwMCJkwg3LL7QqlEOunOjvQzpXmA/LMbdtEDyW9b0EQNFL9KFkNuRKDC3V8SFkmG1KlEEHFp2GQNij6AN89xvmEGvhj3tqC280awJs8ve3Bbr7GHRJoFO/sikSRsol1HD/K3sC9OMDufEEItsWf94uu8SmEBpB2OBOzedtfw+PRpoWyYUJYEfAL9T4w0KmBD26KVcehzIv8e3vOl52aT3x9Ovjnw8RfFkZa+t/iGhMpYpf8ApWExZDWBZ6uzVJxcAPg== . NO [AUTHENTICATIONFAILED] Authentication failed. gsasl: server error Successful authentication (mutt) dovecot debug log: Apr 30 13:32:30 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:32:30 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth Apr 30 13:32:30 auth: Debug: Module loaded: /usr/lib/dovecot/modules/auth/libmech_gssapi.so Apr 30 13:32:30 auth: Debug: Read auth token secret from /home/noahm/dovecot-root/b/auth-token-secret.dat Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: Server accepted connection (fd=18) Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: auth client connected (pid=6788) Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: AUTH 1 GSSAPI protocol=imap final-resp-ok session=4aLx8v4z8JPAqAHa lip=172.18.0.205 rip=192.168.1.218 lport=17436 rport=37872 resp=YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwHCqBBzSB3g1k9BBC5M8XG5NpM35pvpLMHWjw0HIXloN2XjibgczTBt6l+q4DuWo6OWCuf5U+g+BrQ17y52AnCwUk/l722toAEhxwEKA/f3K+7i/lXBzjfCxGTmD2TTO6NUVZUM6TTa6CvwKgGwzGZLh/kQ90VnyzaOyTErL5oiNtl8ZKfguMt38yV8THESf8ZGjxUCKUUa1n3UNClhVk/0Kl88qGD1h11it0yFoNNK5/tbqI5e+sdi+pK4VHsvjPw== (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(?,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: Using all keytab entries Apr 30 13:32:30 auth(noahm@example.com,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: security context state completed. Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: CONT 1 YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsiRFdcazky9GL2l//v2J+U606pbiLSCahGZ2wUxpp05eo9kGAl7j/UQfkzmlOWW7aMfMzPrJTveYBZiDpcfyeTt/wJfAHiEk5A24KYKTIt2ialxe6YOvrmz1e4B+mULZAghrfq5ftdUkQfh0CP/W Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: CONT 1 (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(noahm@example.com,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: gssapi: Negotiated security layer Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: CONT 1 BQQF/wAMAAAAAAAAFUr00gH/////HIlwJEVFPtqhtCU= Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client in: CONT 1 BQQE/wAMAAAAAAAAIfpD4AH///9ub2FobalxyQ7OjgY973Gakw== (previous base64 data may contain sensitive data) Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Performing passdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Finished passdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: Credentials: 70656e63696c Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: Auth request finished Apr 30 13:32:30 auth: Debug: conn unix:login (pid=6788,uid=1000) [1]: client passdb out: OK 1 user=noahm original_user=noahm(a)EXAMPLE.COM Apr 30 13:32:30 auth: Debug: conn unix:/home/noahm/dovecot-root/b/auth-master (pid=6790,uid=0): Server accepted connection (fd=19) Apr 30 13:32:30 auth: Debug: master in: REQUEST 4221435905 6788 1 6b8a10b34adc8ace171603fc8d378730 session_pid=6790 request_auth_token Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Performing userdb lookup Apr 30 13:32:30 auth(noahm,192.168.1.218,sasl:gssapi)<4aLx8v4z8JPAqAHa>: Debug: static: Finished userdb lookup Apr 30 13:32:30 auth: Debug: master userdb out: USER 4221435905 noahm uid=4711 gid=4711 home=/home/noahm/dovecot-root auth_mech=GSSAPI auth_token=705494201f3425a0145e2f7af1edca82fee2ee17 auth_user=noahm(a)EXAMPLE.COM The corresponding client-side logs generated by mutt are: [2025-04-30 13:32:30] Connecting to dovecot-test... [2025-04-30 13:32:30] Connected to dovecot-test:17436 on fd=4 [2025-04-30 13:32:30] 4< * OK [CAPABILITY IMAP4rev1 LOGIN-REFERRALS ID ENABLE IDLE SASL-IR LITERAL+ STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. [2025-04-30 13:32:30] imap_authenticate: Trying method gssapi [2025-04-30 13:32:30] imap_auth_gsasl: using mech GSSAPI [2025-04-30 13:32:30] Authenticating (GSSAPI)... [2025-04-30 13:32:30] 4> a0000 AUTHENTICATE GSSAPI YIIDAAYJKoZIhvcSAQICAQBuggLvMIIC66ADAgEFoQMCAQ6iBwMFACAAAACjggIDYYIB/zCCAfugAwIBBaENGwtFWEFNUExFLkNPTaIfMB2gAwIBA6EWMBQbBGltYXAbDGRvdmVjb3QtdGVzdKOCAcIwggG+oAMCARKhAwIBAqKCAbAEggGsj4jD3VOwvfNdLxjc2hqxFsBYyCvjdOCX0R1So6ANZEYnEWddqZwMCuz7BxXv4z+cXaL6g6iGlVkU4RxQyJQHDFUQC8JroTlyMQ+XsIM4zuwn5N4/xRsgKa+SisK92UNMYyl9hVIPKvu/A54cU0zYTdDjYfDGnkurG2RgXDrKIzMpU2LtpoBEtwl3F1H+rzKFJAqe96e39C85GjK1D4s8/TOm3IcHJ5eofeHxI2GeUodysi+DlurRQTSnsUkGa1LXSgkY+4QdlMf+4goNRG5xNdZ8OA2CLY97TPAFqIeej1Amvb9uQBIKvWfbTjDdItBWOhuvAetlNfqnxlcCbnjbCmFTOIbVsHhNW8W1JIElL28mGydbMPimi9brc250E+ImO0Bxp3gMn5oXGV0tUJl5Y8W1lHlEUU7vKK0V7khUob0b3P3lCGQVJyWZEGNodgpr5zkTbR2M8orP4eI9SYoYp2UB0Ag+JkeYSNoQrKZNxSoKBYLVPGzwwGNPBKl7T0CdXlDAOhfZS/FSxdoy8LGRhuTdv7ghQAvstOllibSbjN3wos8ZC8wH2I5LFkekgc4wgcugAwIBEqKBwwSBwHCqBBzSB3g1k9BBC5M8XG5NpM35pvpLMHWjw0HIXloN2XjibgczTBt6l+q4DuWo6OWCuf5U+g+BrQ17y52AnCwUk/l722toAEhxwEKA/f3K+7i/lXBzjfCxGTmD2TTO6NUVZUM6TTa6CvwKgGwzGZLh/kQ90VnyzaOyTErL5oiNtl8ZKfguMt38yV8THESf8ZGjxUCKUUa1n3UNClhVk/0Kl88qGD1h11it0yFoNNK5/tbqI5e+sdi+pK4VHsvjPw== [2025-04-30 13:32:30] 4< + YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsiRFdcazky9GL2l//v2J+U606pbiLSCahGZ2wUxpp05eo9kGAl7j/UQfkzmlOWW7aMfMzPrJTveYBZiDpcfyeTt/wJfAHiEk5A24KYKTIt2ialxe6YOvrmz1e4B+mULZAghrfq5ftdUkQfh0CP/W [2025-04-30 13:32:30] 4> [2025-04-30 13:32:30] 4< + BQQF/wAMAAAAAAAAFUr00gH/////HIlwJEVFPtqhtCU= [2025-04-30 13:32:30] 4> BQQE/wAMAAAAAAAAIfpD4AH///9ub2FobalxyQ7OjgY973Gakw== [2025-04-30 13:32:30] 4< a0000 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE REPLACE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW SPECIAL-USE STATUS=SIZE SAVEDATE COMPRESS=DEFLATE INPROGRESS NOTIFY LITERAL+] Logged in

5 5

Dovecot 3.21.1 -> 2.4.0 SegFault
by Cata S 02 May '25

02 May '25

Hi guys, There seems to be some issue with Dovecot deployed on alpine. More specifically, the dovecot.config file is not properly read. I have run some debugging and the SegFault is returned in the function below: #0 0x000055555556779b in config_parsed_get_setting () No symbol table info available. #1 0x0000555555563708 in config_dump_full () No symbol table info available. #2 0x000055555555c814 in main () No symbol table info available. This was also addressed by alpine here: https://gitlab.alpinelinux.org/alpine/aports/-/issues/17050 Any idea what could be causing this? Thanks for looking into it, Cata

2 3

2.3 -> 2.4 sieve scripts
by Kamil Jońca 01 May '25

01 May '25

I have configured some sieve scripts to run when I append messages to one of mailbox: --8<---------------cut here---------------start------------->8--- imapsieve_mailbox1_name = Archives imapsieve_mailbox1_causes = APPEND imapsieve_mailbox1_before = file:/.../sieve/dovecot.sieve --8<---------------cut here---------------end--------------->8--- I tried to use this with 2.4 with no luck: # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4 (0a86619f) # OS: Linux 6.12.21-amd64 x86_64 Debian trixie/sid # Hostname: qqrq # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain digest-md5 cram-md5 login compress_zstd_level = 22 default_vsz_limit = 2048M dovecot_storage_version = 2.4.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes mail_compress_write_method = zstd mail_driver = mdbox mail_home = /home/%{user} mail_inbox_path = ~/Mail/0/INBOX mail_path = ~/Mail/0/ mail_plugins { mail_compress = yes acl = yes } mail_privileged_group = mail protocols { imap = yes } 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 notify = yes imapflags = yes editheader = yes } sieve_plugins { sieve_imapsieve = yes sieve_extprograms = yes } sieve_redirect_envelope_from = recipient ssl = no passdb passwd-file { default_password_scheme = PLAIN passwd_file_path = /etc/dovecot/users } userdb passwd-file { passwd_file_path = /etc/dovecot/users } namespace inbox { inbox = yes separator = / mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { } } service auth-worker { } service dict { unix_listener dict { } } protocol imap { mail_plugins { mail_log = yes notify = yes acl = yes imap_acl = yes sieve = yes imap_sieve = yes lazy_expunge = yes } } sieve_script mailbox1 { imapsieve_from_name = Archives cause = append path = file:/.../sieve/dovecot.sieve type = before } When I add message to Archive, I can see in logs: imap(kjonca): 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 -- http://wolnelektury.pl/wesprzyj/teraz/ Never go to bed mad. Stay up and fight. -- Phyllis Diller, "Phyllis Diller's Housekeeping Hints"

1 1

How to backup mdbox
by lutz.niederer＠gmx.net 30 Apr '25

30 Apr '25

Hi, dovecot with mdbox on zfs running fine and robust since one year now. Zfs and mdbox seem to make sense. What we do for backup currently is stop dovecot, take a snapshot and restart dovecot. That only takes a few seconds to complete. After that we have time to do the backup. Is that the correct way, or is there a better, preferred way to get the backup done? Is there a way to freeze dovecot while still keeping the clients happy? Some are thrown off and don't recover (namely outlook, even if it takes a few seconds only). We can live with that, but better would be better. Thanks and cheers, -lutzn

1 0

sieve filter does not work
by Kamil Jońca 29 Apr '25

29 Apr '25

sieve-filter -e -W -D -C -v ~/.dovecot.sieve mailbox sieve-filter: Fatal: 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 -- http://wolnelektury.pl/wesprzyj/teraz/ Even if you do learn to speak correct English, whom are you going to speak it to? -- Clarence Darrow

1 0

2025-04-28
by 村上寛 28 Apr '25

28 Apr '25

test222 test222

1 0

Sieve fails to find existing folder?
by Alexander Skwar 25 Apr '25

25 Apr '25

Hello I've got issues using filters. Although a filter matches a message, the message remains in the INBOX. In the log file a(a)skwar.xyz.sieve.log, I find this: sieve: info: started log at 2025-04-14 18:15:31 +0200. error: msgid=<1051036477.1870592.1744647326637(a)mail.yahoo.com>: fileinto action: failed to store into mailbox '🎗 Social Networks/🏔🚴 Draussen': Mailbox doesn't exist: 🎗 Social Networks/🏔🚴 Draussen. Yes, the folders are **really** named "🎗 Social Networks" and "🏔🚴 Draussen" 😜 I like emojis, makes it easier for me to find things again 🙂 The filter rule for this is: require ["regex","imap4flags","fileinto"]; if anyof (address :regex :comparator "i;octet" "from" ".*@(yahoo\\.com|bergportal\\.ch|freezetag\\.com|garmin\\.com|geocaching\\.com|komoot\\.de|munzee\\.com|quaeldich\\.de|spontacts\\.com|squadrats\\.com|strava\\.com|update\\.strava\\.com|velocity\\.ch|wandrer\\.earth)$", address :regex :comparator "i;octet" ["to", "cc"] "hiking-buddies@acc\\.alexs77\\.rodeo|carving\\.fleshed313@alexs77\\.foobar\\.vip|com\\+wandrer\\.earth@skwar\\.me|squadrats\\.com@acc\\.alexs77\\.rodeo", address :regex :comparator "i;octet" "from" "hikingbuddiesteam(a)gmail.com|email.meetup.com") { fileinto "🎗 Social Networks/🏔🚴 Draussen"; stop; } In this case, it matches on "<whatever>@yahoo.com". Why did it not find the folder? I created the folder and rule in SOGo 5.12.0 from mailcow 2025-03b. bd36093fccaa:/var/vmail/sieve# dovecot --version 2.3.21.1 (d492236fa0) Should the Emojis somehow be encoded, so that the filter would work? Cheers, Alexander

5 9

cgroupv2 privileged execution
by Matt Saladna 23 Apr '25

23 Apr '25

In similar vein to "[cgroup support]" from Jan 30, 2011 I'd like to add cgroupv2 support to Dovecot. With v2, moving processes is more restrictive in that groups can only have a single-writer and the process of the common ancestor cgroup between the losing and gaining group must have write privileges. So far as I understand: - Every hook (mail_user_created, mail_storage_created, etc) occurs after chroot + setuid - Wrapping imap or pop3 executables doesn't expose the userdb data in environment, this is done in the actual imap and pop3 processes respectively - Adding a script-login does export the correct userdb details but the pid isn't known. Since everything spawns under dovecot master, the only practical solution is to enumerate every imap or pop3 process owned by the gid to reassign to the new cgroup. This limits implementation to a plugin that solicits the pid to a separate daemon listening on a socket launched by Dovecot in mail_user_created hook. Ideally I would like for cgroup binding to occur before imap/pop3 binaries launch for cgroupv2 pid rejection to occur, although this seems impossible to achieve? - Matt In similar vein to "[cgroup support]" from Jan 30, 2011 I'd like to add cgroupv2 support to Dovecot. With v2, moving processes is more restrictive in that groups can only have a single-writer and the process of the common ancestor cgroup between the losing and gaining group must have write privileges. So far as I understand: - Every hook (mail_user_created, mail_storage_created, etc) occurs after chroot + setuid - Wrapping imap or pop3 executables doesn't expose the userdb data in environment, this is done in the actual imap and pop3 processes respectively - Adding a script-login does export the correct userdb details but the pid isn't known. Since everything spawns under dovecot master, the only practical solution is to enumerate every imap or pop3 process owned by the gid to reassign to the new cgroup. This limits implementation to a plugin that solicits the pid to a separate daemon listening on a socket launched by Dovecot in mail_user_created hook. Ideally I would like for cgroup binding to occur before imap/pop3 binaries launch for cgroupv2 pid rejection to occur, although this seems impossible to achieve? - Matt

1 0

Android mail client capable of utilizing FTS?
by Alexander Skwar 22 Apr '25

22 Apr '25

Hello I enabled FTS Full Text Search using Tika in dovecot and have all the emails now reindexed. Using either "IMAP by hand" (ie via telnet or openssl s_client), SOGo webmail, or Thunderbird on macOS, I can search for and also find emails based on text which is only in a PDF attachment. Using Thunderbird or the now dead k-9, I'm not finding anything. Can someone maybe suggest an email client for Android which is able to find emails based on text in FTS? Technically, I guess it should do a "search TEXT "foo bar"" query. Here's a complete session done in "IMAP by hand": $ openssl s_client -crlf -connect my-sys:993 … --- read R BLOCK * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a LOGIN myuser@sysd pass a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW STATUS=SIZE SAVEDATE LITERAL+ NOTIFY METADATA SPECIAL-USE COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in b SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped \*)] Flags permitted. * 10 EXISTS * 0 RECENT * OK [UNSEEN 8] First unseen. * OK [UIDVALIDITY 1671377672] UIDs valid * OK [UIDNEXT 1709] Predicted next UID * OK [HIGHESTMODSEQ 2613] Highest b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). c SEARCH TEXT "Veloplatzreservierung" * SEARCH 3 c OK Search completed (0.042 + 0.000 + 0.041 secs). d FETCH 3 (BODY.PEEK[HEADER.FIELDS (Message-ID Date)]) * 3 FETCH (BODY[HEADER.FIELDS (MESSAGE-ID DATE)] {124} Message-Id: <202504100258.53A2waba008043-53A2wabb008043(a)mailqueue01.leuchter-cloud.ch> Date: 10 Apr 2025 04:58:36 +0200 ) d OK Fetch completed (0.001 + 0.000 secs). z LOGOUT * BYE Logging out z OK Logout completed (0.001 + 0.000 secs). closed Alexander Hello I enabled FTS Full Text Search using Tika in dovecot and have all the emails now reindexed. Using either "IMAP by hand" (ie via telnet or openssl s_client), SOGo webmail, or Thunderbird on macOS, I can search for and also find emails based on text which is only in a PDF attachment. Using Thunderbird or the now dead k-9, I'm not finding anything. Can someone maybe suggest an email client for Android which is able to find emails based on text in FTS? Technically, I guess it should do a "search TEXT "foo bar"" query. Here's a complete session done in "IMAP by hand": $ openssl s_client -crlf -connect my-sys:993 … =============================================================================== read R BLOCK * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a LOGIN myuser@sysd pass a OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY PREVIEW STATUS=SIZE SAVEDATE LITERAL+ NOTIFY METADATA SPECIAL-USE COMPRESS=DEFLATE QUOTA ACL RIGHTS=texk] Logged in b SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 Drausssen $Forwarded $activity $label3 $stopped \*)] Flags permitted. * 10 EXISTS * 0 RECENT * OK [UNSEEN 8] First unseen. * OK [UIDVALIDITY 1671377672] UIDs valid * OK [UIDNEXT 1709] Predicted next UID * OK [HIGHESTMODSEQ 2613] Highest b OK [READ-WRITE] Select completed (0.001 + 0.000 secs). c SEARCH TEXT "Veloplatzreservierung" * SEARCH 3 c OK Search completed (0.042 + 0.000 + 0.041 secs). d FETCH 3 (BODY.PEEK[HEADER.FIELDS (Message-ID Date)]) * 3 FETCH (BODY[HEADER.FIELDS (MESSAGE-ID DATE)] {124} Message-Id: <202504100258.53A2waba008043-53A2wabb008043(a)mailqueue01.leuchter- cloud.ch> Date: 10 Apr 2025 04:58:36 +0200 ) d OK Fetch completed (0.001 + 0.000 secs). z LOGOUT * BYE Logging out z OK Logout completed (0.001 + 0.000 secs). closed Alexander

3 2

Dovecot migration to new server with namespace issues
by Gabriel Kaufmann | TYPOworx 22 Apr '25

22 Apr '25

Hello, I'm trying to migrate old ispconfig server with dovecot + postfix to a new modernized server. I'm having some trouble with dovecot doing what I want/need to reuse use my old configuration. I've been using maildir++. The new dovecot makes me some headcache as I cannot simply reuse the old configuration or INBOX folder. Any ideas how to get this fixed? My Maildir's & IMAP looked like this for the old system: Maildir/ <-- obviously not shown in IMAP :) INBOX/ Drafts/ Templates/ Sent/ Archives/ Trash On my old ispconfig server with older linux/dovecot version I simply had this configuration: > namespace inbox { > inbox = yes > > mailbox ".Drafts" { > auto = no > special_use = \Drafts > } > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > > mailbox ".Junk" { > auto = no > special_use = \Junk > } > mailbox Spam { > auto = no > special_use = \Junk > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > > mailbox ".Trash" { > auto = no > special_use = \Trash > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > > mailbox Archives { > auto = subscribe > special_use = \Archive > } > } My approach to make this work using dovecot 2.3.21 got me in some trouble. Obviously new dovecot wants to store INBOX-Date in Maildir/{cur,tmp,new} instead of Maildir/INBOX? I've tried with this configuration - which at least correctly shows INBOX-Data now in my IMAP, but I also have some troubles: Maildir/ <-- obviously not shown in IMAP :) INBOX/ My Custom Folder/ Drafts/ <------------- repeating from imap-root subscribing it there duplicates it here :-/ Templates/ Sent/ Archives/ Trash .Trash Drafts/ Templates/ Sent/ Archives/ Trash .Trash (somehow same than Trash, only want Trash non-dotted) New configuration approach: > mail_location = > maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/:maildir_copy_with_hardlinks=yes > maildir_copy_with_hardlinks = yes > > plugin { > mailbox_alias_junk1 = Junk > mailbox_alias_junk2 = Spam > > mailbox_alias_sent_de = Gesendet > } > > namespace { > type = private > separator = / > > location = > maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/:LISTINDEX= > > inbox = no > list = yes > subscriptions = yes > > > mailbox .Junk { > auto = no > special_use = \Junk > } > > mailbox .Drafts { > auto = no > special_use = \Drafts > } > > mailbox .Trash { > auto = no > special_use = \Trash > } > > mailbox .Sent { > auto = no > special_use = \Sent > } > > mailbox .Archives { > auto = no > special_use = \Archive > } > > mailbox .Templates { > auto = no > } > } > > namespace inbox { > type = private > separator = / > prefix = INBOX/ > > location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/ > > inbox = yes > list = yes > hidden = yes > subscriptions = yes > > mailbox .Junk { > auto = no > } > > mailbox .Drafts { > auto = no > } > > mailbox .Trash { > auto = no > } > > mailbox .Sent { > auto = no > } > > mailbox .Archives { > auto = no > } > > mailbox .Templates { > auto = no > } > } -- Best regards Gabriel Kaufmann Hello, I'm trying to migrate old ispconfig server with dovecot + postfix to a new modernized server. I'm having some trouble with dovecot doing what I want/need to reuse use my old configuration. I've been using maildir++. The new dovecot makes me some headcache as I cannot simply reuse the old configuration or INBOX folder. Any ideas how to get this fixed? My Maildir's & IMAP looked like this for the old system: Maildir/ <-- obviously not shown in IMAP :) INBOX/ Drafts/ Templates/ Sent/ Archives/ Trash On my old ispconfig server with older linux/dovecot version I simply had this configuration: namespace inbox { inbox = yes mailbox ".Drafts" { auto = no special_use = \Drafts } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox ".Junk" { auto = no special_use = \Junk } mailbox Spam { auto = no special_use = \Junk } mailbox Junk { auto = subscribe special_use = \Junk } mailbox ".Trash" { auto = no special_use = \Trash } mailbox Trash { auto = subscribe special_use = \Trash } mailbox Archives { auto = subscribe special_use = \Archive } } My approach to make this work using dovecot 2.3.21 got me in some trouble. Obviously new dovecot wants to store INBOX-Date in Maildir/{cur,tmp,new} instead of Maildir/INBOX? I've tried with this configuration - which at least correctly shows INBOX-Data now in my IMAP, but I also have some troubles: Maildir/ <-- obviously not shown in IMAP :) INBOX/ My Custom Folder/ Drafts/ <------------- repeating from imap-root subscribing it there duplicates it here :-/ Templates/ Sent/ Archives/ Trash .Trash Drafts/ Templates/ Sent/ Archives/ Trash .Trash (somehow same than Trash, only want Trash non-dotted) New configuration approach: mail_location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs: DIRNAME=/:maildir_copy_with_hardlinks=yes maildir_copy_with_hardlinks = yes plugin { mailbox_alias_junk1 = Junk mailbox_alias_junk2 = Spam mailbox_alias_sent_de = Gesendet } namespace { type = private separator = / location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/: LISTINDEX= inbox = no list = yes subscriptions = yes mailbox .Junk { auto = no special_use = \Junk } mailbox .Drafts { auto = no special_use = \Drafts } mailbox .Trash { auto = no special_use = \Trash } mailbox .Sent { auto = no special_use = \Sent } mailbox .Archives { auto = no special_use = \Archive } mailbox .Templates { auto = no } } namespace inbox { type = private separator = / prefix = INBOX/ location = maildir:/var/vmail/%d/%n/Maildir/:LAYOUT=fs:DIRNAME=/ inbox = yes list = yes hidden = yes subscriptions = yes mailbox .Junk { auto = no } mailbox .Drafts { auto = no } mailbox .Trash { auto = no } mailbox .Sent { auto = no } mailbox .Archives { auto = no } mailbox .Templates { auto = no } } -- Best regards Gabriel Kaufmann

1 0

Bash automation for Dovecot
by Travis Bean 21 Apr '25

21 Apr '25

Hello, I developed a Bash script to automate the installation and configuration of open-source software (i.e., launchpad.net/linuxha) I want to make sure the syntax of this script is perfect so I can use it as a teaching tool to educate people about Linux. I need to know if there is anything misconfigured with my Dovecot syntax. If you find a bug in LinuxHA, please submit a bug report to bugs.launchpad.net/linuxha/+filebug. Kind regards, Travis Bean Hello, I developed a Bash script to automate the installation and configuration of open-source software (i.e., launchpad.net/linuxha) I want to make sure the syntax of this script is perfect so I can use it as a teaching tool to educate people about Linux. I need to know if there is anything misconfigured with my Dovecot syntax. If you find a bug in LinuxHA, please submit a bug report to bugs.launchpad.net/ linuxha/+filebug. Kind regards, Travis Bean

1 0

mail crypto in Ubuntu 22.04.5 - Provider routines::invalid salt length
by Max Kostikov 18 Apr '25

18 Apr '25

Hi, I am facing mail crypt extension error. When I try to create keys I get this error. doveadm -o plugin/mail_crypt_private_password=e32f1f464d7576716d5df899e7d5cb6b64cdb55584c71882e9f7e7c79f2e69e6 mailbox cryptokey generate -u "foo(a)example.com" doveadm(foo(a)example.com): Error: mail_crypt_user_generate_keypair(foo(a)example.com) failed: error:1C800070:Provider routines::invalid salt length doveadm(foo(a)example.com): Warning: mailbox cryptokey generate: Nothing was matched. Use -U or specify mask? Folder Public ID x ERROR: error:1C800070:Provider routines::invalid salt length Segmentation fault (core dumped) Any insights why? OS: Ubuntu 22.04.5 LTS (FIPS) Dovecot packages installed: dovecot-core/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-imapd/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-lmtpd/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-managesieved/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-mysql/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-pop3d/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] dovecot-sieve/jammy-updates,jammy-security,now 1:2.3.16+dfsg1-3ubuntu2.4 amd64 [installed] Mail crypt configuration: ... mail_attribute_dict = file:/var/vmail/%d/%n/dovecot-attributes mail_plugins = mail_crypt quota plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 mail_crypt_require_encrypted_user_key = yes } ... -- Sincerely, Max Kostikov

1 1

Auth-worker malloc failure
by Scott Q. 17 Apr '25

17 Apr '25

I recently changed the userdb to sql, using a stored procedure and since then, every so often, maybe 2-3 times per day I see errors like these in the maillog: Apr 17 13:33:04 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: error:140BA041:SSL routines:SSL_new:malloc failure - waiting for 1 seconds before retry Apr 17 13:33:05 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 5 seconds before retry Apr 17 13:33:10 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 25 seconds before retry Apr 17 13:33:35 imap1 dovecot[41212]: auth-worker(41325): Error: mysql(192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 125 seconds before retry Apr 17 13:34:04 imap1 dovecot[41212]: auth-worker(41325): Error: sql(user(a)domain.com,1.2.3.4,): User query failed: Not connected to database Is this the auth-worker running out of memory ? I have these settings: auth_cache_size = 8 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_verbose = yes auth_worker_max_count = 130 service auth { unix_listener auth-master { mode = 0600 user = vuser } user = root client_limit=1500 } I recently changed the userdb to sql, using a stored procedure and since then, every so often, maybe 2-3 times per day I see errors like these in the maillog: Apr 17 13:33:04 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: error:140BA041:SSL routines:SSL_new:malloc failure - waiting for 1 seconds before retry Apr 17 13:33:05 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 5 seconds before retry Apr 17 13:33:10 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 25 seconds before retry Apr 17 13:33:35 imap1 dovecot[41212]: auth-worker(41325): Error: mysql (192.168.1.95): Connect failed to database (virtualusers): SSL connection error: SSL_CTX_new failed - waiting for 125 seconds before retry Apr 17 13:34:04 imap1 dovecot[41212]: auth-worker(41325): Error: sql (user(a)domain.com,1.2.3.4,<5ohIy/wyHvox5b/p>): User query failed: Not connected to database Is this the auth-worker running out of memory ? I have these settings: auth_cache_size = 8 k auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-master auth_verbose = yes auth_worker_max_count = 130 service auth { unix_listener auth-master { mode = 0600 user = vuser } user = root client_limit=1500 }

1 0

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 17 Apr '25

17 Apr '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any /dove/ command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I'm using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I'm using the wrong mailing list, please point me to the right channel

3 7

Problem email client iPhone ios18.2
by andrzej.milewski＠gmail.com 17 Apr '25

17 Apr '25

Hello, I have a fairly new installation of the Dovecot server version 2.3.19.1 on Debian 12.8. In general, the server works correctly. It sends and receives emails without issues. The clients primarily use Thunderbird on desktops and Gmail on Android. However, some clients are using iPhones with various hardware versions. Those with iOS below version 18 work correctly without any issues. Those who have updated their phones to version 18 and now even 18.2 are experiencing problems with mailbox synchronization. On version 18.2, the issue appears as follows: When you open the app, you can read several messages. They load correctly, but, for instance, attachments do not. If I wait for some time, the attachment eventually loads. During this time, I observe the server logs, and it shows that a certain session on the Dovecot server has ended. Dec 17 13:13:01 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<44785><1QGZCHcp/+3AqM2O>: Disconnected: Connection closed (UID SEARCH finished 92.295 secs ago) in=2972 out=6076956 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=36 body_bytes=6059064 Dec 18 08:40:41 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<177412>: Disconnected: Connection closed (UID FETCH finished 90.079 secs ago) in=5126 out=1304237 deleted=0 expunged=0 trashed=0 hdr_count=94 hdr_bytes=289688 body_count=89 body_bytes=969615 Dec 18 08:42:19 iredmail0 dovecot[408]: imap(xxx(a)xxx.com)<177410><D5mqU4cpZ+nAqM2O>: Disconnected: Connection closed (UID FETCH finished 95.051 secs ago) in=4475 out=1162785 deleted=0 expunged=0 trashed=0 hdr_count=95 hdr_bytes=281674 body_count=61 body_bytes=839545 Dec 18 08:44:17 iredmail0 dovecot[408]: imap(edyta.kowalewska(a)laktopol.com.pl)<177918>: Disconnected: Connection closed (UID FETCH finished 92.132 secs ago) in=29399 out=30266644 deleted=0 expunged=0 trashed=0 hdr_count=565 hdr_bytes=1726228 body_count=628 body_bytes=28109455 After the session is closed, the attachment loads immediately. From the logs and router analysis, it appears that the download happens in another previously opened session. After this incident, I go to another message with an attachment, and the situation repeats. There are also situations where the email body does not load, and the app waits for the server until the session closes and the content is fetched in another session. It does not matter whether I connect to the server via the internet or through a local network. On an iPhone 7 with iOS 15.8.3, everything works smoothly. Attachments open without issues. On iOS 18.1.1, attachments do not load, and the session does not close on its own. It takes forever unless the app is closed. In the Gmail app, everything works correctly without any issues. This is clearly a problem with the mail client on iPhone. However, is there anything I can adjust in my server settings to mitigate this issue for users? My dovecot configuration https://pastebin.com/UPNQ5dZz

26 58

config help with sieve_script
by Genes Lists 17 Apr '25

17 Apr '25

Any advice what I am doing wrong: I am in process of converting our 2.3 configs to 2.4.1 and sieve / sieve_script has me stumped. When I use: plugin { sieve_script xxx { ... } sieve_script yyy { ... } } each xxx/yyy is personal or before or after etc. dovecot -n give: ./conf.d/90-sieve.conf line 6: Unknown section name: plugin If I remove the plugin { } part then I get: Unknown section name: sieve_script Obviously I am doing something wrong - appreciate any help? thank you -- Gene Any advice what I am doing wrong: I am in process of converting our 2.3 configs to 2.4.1 and sieve / sieve_script has me stumped. When I use: plugin { sieve_script xxx { ... } sieve_script yyy { ... } } each xxx/yyy is personal or before or after etc. dovecot -n give: ./conf.d/90-sieve.conf line 6: Unknown section name: plugin If I remove the plugin { } part then I get: Unknown section name: sieve_script Obviously I am doing something wrong - appreciate any help? thank you -- Gene

2 2

Decouple the username hash from the login given
by José Celestino 16 Apr '25

16 Apr '25

Hi all, Is there a way to do the hash on the director without setting the user (or destuser) for the Dovecot backend authentication? The scenario is: Our accounts have multiple aliases where each alias can have a different password (long story): Alias1 accountX password1 Alias2 accountX password2 Alias3 accountX password3 accountX accountX passwordX Our goal is to map the same account, regardless of the alias used to authenticate, to the same backend server. We use checkpassword for userdb on the director, and when we set either the user or username to the main account id (accountX on the example) it sends the authentication as accountX, passwordN, and fails. Is there a var that can be set and used for hashing, leaving the authentication untouched? Our installed version is 2.3.21. Thank you. Best regards, José Celestino

1 1

Question about dovecot quota calculation
by Zakaria 16 Apr '25

16 Apr '25

Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug, if not it would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB through quota command? I think both should present identical results, anyone thinks otherwise, I would appreciate if you share with us the reasoning? Also, which one I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak. Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug, if not it would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB through quota command? I think both should present identical results, anyone thinks otherwise, I would appreciate if you share with us the reasoning? Also, which one I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak.

1 0

Question about quota calculation
by Zakaria 16 Apr '25

16 Apr '25

Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug but this would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB in my case through quota command and why is this? Which one would I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak. Hi everyone, I wondered if anyone know the reason why dovecot quota command:- doveadm quota get -u email_address returns slightly smaller size than status command vsize:- doveadm mailbox status -t all "*" -u email_address I wondered if its a bug but this would be noticeable imparity between the two results? given in my case dovecot leaves out around 67 MB in my case through quota command and why is this? Which one would I should use to determine if user exceeded quota limit for certainty? Any recommendation? With thanks. Zak.

1 0

Dovecot24 - passdb configuration syntax
by Juergen Edner 16 Apr '25

16 Apr '25

Hello, as Dovecot 2.4.1 has been published, I started investigation how I need to modify my existing Dovecot 2.3.x configuration, which worked flawlessly the last 5 years. With the help of the doveconf tool I've identified the parameters which need to be modified and I got rid of the error message at the end. Nevertheless, not getting any errors displayed, does not automatically mean, that it has correctly been configured. Here is the initial auth configuration and hopefully the right 2.4 version: Dovecot23: disable_plaintext_auth = yes auth_username_format = %Lu auth_mechanisms = plain login cram-md5 passdb { driver = passwd-file args = username_format=%Lu /path/to/aliases-file } passdb { driver = passwd-file args = scheme=cram-md5 /path/to/cram-md5-file } userdb { driver = passwd } Dovecot24: auth_allow_cleartext = no auth_username_format = %{user | lower} auth_mechanisms = plain login cram-md5 passdb aliases-file { passwd_file_path = /path/to/aliases-file } passdb md5-file { passwd_file_path = /path/to/cram-md5-file } userdb passwd-file { passwd_file_path = /etc/passwd } Here are my questions: - The first passdb configuration (aliases file) initially contained the "args = username_format=%Lu ..." option. Do I still need to convert this to a dedicated "auth_username_format = %{user | lower}" line or is this already covered by the global "auth_username_format" setting? - The second passdb configuration (cram-md5 file) initially contained the "args = scheme=cram-md5 ..." option. I couldn't find any replacement for it. Does this mean the only alternative would be to prefix all passwords in the password file with "{CRAM-MD5}"? - For the third userdb configuration (passwd file) I made use of the "passwd_file_path" parameter. Is this a valid replacement for the original "driver = passwd" entry or have I forgotten anything? BTW, I was curious if ChatGPT could do the job faster than me, but I can say "not yet". It made several errors and had to be corrected one by one but that might change in the future if more and more people are asking for support on this topic. Thanks Juergen -- Mail: juergen(a)eisfair.org

2 2

Stats-writer permission denied
by Ken Wright 15 Apr '25

15 Apr '25

I've got a new Dovecot error (well, new to me, at least)! I ran tail /var/log/mail.err and got the following: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied I checked the file, and it's owned by www-data and the www-data group, with read and write permissions for owner and group... just like I have specified in /etc/dovecot/conf.d/10-master.conf. I can't understand why permission is denied when the file permissions appear to be correct. Can anyone shed any light on this for me? Ubuntu 20.04 Dovecot 2.3.7.2 Ken

3 2

shared folders in dovecot
by Anton Shevtsov 15 Apr '25

15 Apr '25

I used dovecot without shared folders some time ago. All work fine. old dovecot config: |mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox |mail_plugins = acl |protocol imap { mail_plugins = $mail_plugins } | All work fine. Now I want to add shared folder functionality. I am defining namespaces and doing it wrong (maybe) new dovecot config: |mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox |mail_plugins = acl |mail_debug=yes namespace inbox { type = private separator = / prefix = inbox = yes } namespace { type = shared separator = / prefix = shared/%%u/ # wrong #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/shared/%%u |# wrong again location = maildir:%%h/:INDEX=~/%%u |subscriptions = no list = children } protocol imap { mail_plugins = $mail_plugins imap_acl acl } plugin { acl = vfile acl_shared_dict = file:/var/mail/%d/shared-mailboxes.db } | I can set access right for shared folder (screenshot - https://ibb.co/ccxQ63wN) but i can not see shared folder in subscriptions (screenshot - https://ibb.co/PRfpD7X) -- *Anton* I used dovecot without shared folders some time ago. All work fine. old dovecot config: mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox mail_plugins = acl protocol imap { mail_plugins = $mail_plugins } All work fine. Now I want to add shared folder functionality. I am defining namespaces and doing it wrong (maybe) new dovecot config: mail_home=/var/mail/%d/%n mail_location = maildir:/var/mail/%d/%n:UTF-8:INBOX=/var/mail/%d/%n/Inbox mail_plugins = acl mail_debug=yes namespace inbox { type = private separator = / prefix = inbox = yes } namespace { type = shared separator = / prefix = shared/%%u/ # wrong #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/ Maildir/shared/%%u # wrong again location = maildir:%%h/:INDEX=~/%%u subscriptions = no list = children } protocol imap { mail_plugins = $mail_plugins imap_acl acl } plugin { acl = vfile acl_shared_dict = file:/var/mail/%d/shared-mailboxes.db } I can set access right for shared folder (screenshot - https://ibb.co/ccxQ63wN) but i can not see shared folder in subscriptions (screenshot - https://ibb.co/ PRfpD7X) -- Anton

3 8

Reindex all e-mails for FTS?
by Alexander Skwar 14 Apr '25

14 Apr '25

Hello How do I reindex all e-mails (for a user or for all users) for FTS? Seems I can find new emails, but not old ones. I tried this: askwar@mail /o/mailcow-dockerized> time sudo docker compose exec dovecot-mailcow doveadm index -A '*' ________________________________________________________ Executed in 1.73 secs fish external usr time 0.00 millis 0.00 millis 0.00 millis sys time 12.90 millis 1.08 millis 11.83 millis As you can see, this was very fast — should it be…? I'd like to be able to search for a text which is in attachments and then I'd need to be able to find the email. This works fine for new emails, but not for old ones. To verify that the attachment would be readable by tika, I took an old e-mail, saved the PDF attachment, and then mailed it to me. Searching for the e-mail will find the new e-mail, but not the old one. The mailbox is not exactly small: askwar@mail /o/mailcow-dockerized> sudo docker compose exec dovecot-mailcow doveadm quota get -u a(a)skwar.xyz Quota name Type Value Limit % Userquota STORAGE 34908222 61685760 56 Userquota MESSAGE 458837 - 0 bd36093fccaa:/# du -sh /var/vmail_index/a\(a)skwar.xyz/ /var/vmail/skwar.xyz/a 2.4G /var/vmail_index/a(a)skwar.xyz/ 27G /var/vmail/skwar.xyz/a I've enabled full text search fts in dovecot with these settings: plugin { fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts = flatcurve fts_tika = http://tika:9998/tika fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=30 fts_languages = en es de fts_tokenizers = generic email-address fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball english-possessive stopwords fts_index_timeout = 300s } askwar@mail /o/mailcow-dockerized> docker --version Docker version 27.3.1, build ce12230 askwar@mail /o/mailcow-dockerized> sudo docker compose exec dovecot-mailcow dovecot --version 2.3.21.1 (d492236fa0) Thanks, Alexander

3 4

Compile failure on git head : lib-settings/settings-history-core.h
by Genes Lists 14 Apr '25

14 Apr '25

Summary: -------- Our daily test builds of git head started failing on Archlinux using gcc 14.2.1+r753+g1cd744a6828f-1 Compile error occurs on git HEAD branch main: commit : beca41cc94dbc81cb2586aab311762bde39bdb11 Possible relevant commit: ------------------------ commit 9dca2f961f83a071d2ff516cd332cd4aa88484dd Build Error: ------------ ... CCLD test-dns-util make[3]: Leaving directory '.. /src/core/src/lib-dns' Making all in lib-settings make[3]: Entering directory '.. /src/lib-settings' GEN settings-history-core.h Line 3: Invalid version sort order make[3]: *** [Makefile:897: settings-history-core.h] Error 1 Thanks for any help. gene (more detail below) config / build details: ---------------------- git fetch --all; git pull git clean -fdx ./autogen.sh ./configure \ --enable-maintainer-mode \ --prefix=/usr \ --sbindir=/usr/bin \ --sysconfdir=/etc \ --localstatedir=/var \ --libexecdir=/usr/lib \ --with-rundir=/run/dovecot \ --with-moduledir=/usr/lib/dovecot/modules \ --disable-static \ --with-pam \ --with-sqlite \ --with-pgsql \ --with-mysql \ --with-ssldir=/etc/ssl \ --with-gssapi \ --with-ldap=yes \ --with-lua=plugin \ --with-bzlib \ --with-lz4 \ --with-zstd \ --with-solr \ --with-sodium \ --with-libcap \ --enable-experimental-mail-utf8 \ --enable-experimental-imap4rev2 Install prefix . : /usr File offsets ... : 64bit I/O polling .... : epoll I/O notifys .... : inotify SSL ............ : openssl GSSAPI ......... : yes passdbs ........ : static lua (plugin) passwd passwd-file pam ldap sql : -bsdauth userdbs ........ : static lua (plugin) prefetch passwd passwd-file ldap sql CFLAGS ......... : -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 SYSTEMD ........ : notify - /usr/lib/systemd/system/dovecot.service SQL drivers .... : pgsql mysql sqlite : -cassandra Full text search : solr make clean make -- Gene

2 2

email-address Tokenizer Splits Hyphenated Local-Parts, Causing Inaccurate FTS Search Results
by Daniel 11 Apr '25

11 Apr '25

I’m using Dovecot FTS with the flatcurve backend in a mailcow: dockerized setup. When searching for an email address with a hyphenated local-part (e.g., ma-g(a)example.com) the email-address tokenizer splits the local-part on hyphens, producing tokens like ma, g, and ma-g(a)example.com. This prevents searching for ma-g as a single term. With fts_flatcurve_substring_search = yes, searching for ma-g matches unrelated addresses containing ma (e.g., manager(a)example.com) leading to irrelevant results. Dovecot version: 2.3.21.1 (d492236fa0) Including only relevant part of dovecot config: plugin { fts = flatcurve fts_autoindex = yes fts_autoindex_exclude = \Junk fts_autoindex_exclude2 = \Trash fts_autoindex_max_recent_msgs = 999999 fts_tokenizers = generic email-address fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=100 fts_flatcurve_substring_search = yes fts_languages = en es de ru fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball english-possessive stopwords fts_filters_ru = lowercase snowball stopwords fts_index_timeout = 300s } service indexer-worker { process_limit = 12 vsz_limit = 512 MB } Steps to Reproduce: Index an email with ma-g(a)example.com in the From field also index email contains "ma" and "g" in the From field. Check tokenization: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma g example com ma-g(a)example.com Search: doveadm search -u user(a)example.com FROM ma-g Results include manager(a)example.com due to ma matching. Expected Behavior: FROM ma-g should match only emails with ma-g(a)example.com, treating ma-g as a single term or exact local-part. Expected tokens: doveadm fts tokenize -u user(a)example.com "ma-g(a)example.com" Output: ma-g ma g example com ma-g(a)example.com Actual Behavior: The tokenizer splits ma-g into ma and g. Substring search matches "ma" or "g" in unrelated addresses (e.g., manager(a)example.com, greg(a)example.com) Without substring search, ma-g matches nothing unless searching the full address. Impact: Searching hyphenated local-parts for short email address local-parts is unreliable, especially for common fragments like ma, flooding results with irrelevant matches. Request: Add a configuration option, such as "fts_tokenizer_email_address_keep_hyphenated = yes|no" (default: no, for compatibility), to include the hyphenated local-part of an email address as an additional token. For example, with "yes", tokenizing "ma-g(a)example.com" would produce "ma-g", "ma", "g", "example", "com", and "ma-g(a)example.com". This allows searches for "FROM ma-g" to match emails with "ma-g(a)example.com" exactly, while preserving "ma" and "g" for substring searches. Consider "yes" as a future default, as including hyphenated local-parts aligns with RFC 5322 and user expectations for precise email searches, especially for common hyphenated addresses like "first-last(a)domain.com". If changing defaults, provide upgrade notes for users relying on the current token set. Is there any workaround to search hyphenated local-parts accurately? Best regards, Daniel Levin

1 0

Enable Full-Text search for attachments?
by Alexander Skwar 10 Apr '25

10 Apr '25

Hello Is it possible to enable a full-text search (FTS) for attachments (PDF, Text, Docx, …) using the open source dovecot server? If so, how would I do that? I've read https://doc.dovecot.org/2.3/configuration_manual/fts/ but that wasn't clear to me. Thanks, Alexander

2 2

2.4.1: oauth2 - Error: lua: db-lua: 'auth_passdb_lookup' is not a function
by Luigi Trovato 10 Apr '25

10 Apr '25

Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi Hello, I just upgraded 2.4.0 to 2.4.1 and when trying to authenticate with oauth2 I have this error: auth-worker(lonestar(a)lonestar.it,127.0.0.1)<28029><vtg3yW0yBNh/AAAB>: request [11]: Error: lua: db-lua: 'auth_passdb_lookup' is not a function imap-login: Info: Logged in: user=<lonestar(a)lonestar.it>, method=XOAUTH2, rip=127.0.0.1, lip=127.0.0.1, mpid=28281, secured, session=<vtg3yW0yBNh/AAAB> I actually don't have any auth_passdb_lookup defined in the lua script, only auth_password_verify and auth_userdb_lookup, but it was previously working without errors -- Ciao, Luigi

1 1

2.4 Error: login_trusted_networks: Invalid network '::1'
by James 10 Apr '25

10 Apr '25

Good afternoon, With this line added to the default dovecot.conf: login_trusted_networks = ::1 I get this error: Apr 10 12:41:22 mailhost dovecot: [ID 702911 mail.info] master: Dovecot v2.4.1-4 (7d8c0e5759) starting up for imap, lmtp Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: getaddrinfo() failed: non-recoverable name resolution failure Apr 10 12:41:37 mailhost dovecot: [ID 702911 mail.error] imap-login: Error: login_trusted_networks: Invalid network '::1': user=<>, rip=2a02:1234:abcd:1::3, lip=2a02:1234:abcd:a::2, session=<sA2GEWsyNfIqAoAQ0BwAAQAAAAAAAACH> Version 2.4.1 Works with 2.3.21.1 and many versions before. It complains with any IPv6 address in login_trusted_networks.

1 0

Multiple namespaces with individual quota values from LDAP
by Andreas Oster 10 Apr '25

10 Apr '25

Hi all, I have successfully managed to get individual user qota for inboxes with values from LDAP working on Dovecot 2.4. I achieved this with the help of a posting from Aki Tuomi: <-- I'd recommend moving the storage_size out of quota "User Quota", since it's then easier to override: quota "User quota" { driver = count ... } quota_storage_size = 10G Aki --> However, in my setup I am using a separate namespace for mail "archiving" on a slower storage. I would like to also restrict the available storage space for users individually in this namespace. To achieve this I ideally would like to fetch the value from a different LDAP attribute. Can this be achieved with dovecot 2.4 ? In version 2.3 this was not a problem. Thank you very much for your kind help. Best regards Andraes

2 2

SQL userdb homedir
by Scott Q. 08 Apr '25

08 Apr '25

I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you I am trying to use a stored procedure in sql for returning the various fields for the user. I'm concerned about what happens if the stored procedure fails to retrieve the homedir and other fields, for whatever reason. What should it return to notify dovecot of failure ? a single null field, all fields as null, empty result set ? Thank you

1 0

Per-User quota with LDAP
by Damien Brémont 07 Apr '25

07 Apr '25

Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/home/users_LDAP/user uidNumber=10017 *quotaBytes=32000000* dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B* dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/user#011uid=10017#011gid=8#011*quota_storage_size=32000000B*#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 *10485760 60* User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https://doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B *Dovecot version:* 2.4.1-4+ubuntu24.04 *dovecot -n:* # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G 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 user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve } Hi all, I'm trying to setup Per-User quota with LDAP on dovecot 2.4.1 When I try to recalc quota for user, data is retrieved from LDAP server # doveadm quota recalc -u user dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): Server accepted connection (fd=20) dovecot: auth: Debug: master in: USER#0111#011user#011protocol=doveadm dovecot: auth(user): Debug: : Performing userdb lookup dovecot: auth(user): Debug: ldap: Performing passdb lookup dovecot: auth(user): Debug: ldap: pass search: base=ou=user,dc=madrid-ias,dc=eu scope=subtree filter=(&(objectClass=posixAccount)(uid=user)) fields=uid,homeDirectory,uidNumber,gidNumber,quotaBytes dovecot: auth(user): Debug: ldap: result: uid=user gidNumber=8 homeDirectory=/ home/users_LDAP/user uidNumber=10017 quotaBytes=32000000 dovecot: auth(user): Debug: ldap: Finished passdb lookup dovecot: auth(user): Debug: : Finished userdb lookup dovecot: auth: Debug: userdb out: USER#0111#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B dovecot: auth: Debug: conn unix:/run/auth-userdb (pid=34516,uid=0): auth-master client: Disconnected: Connection closed (fd=20) (created 159 msecs ago, handshake 159 msecs ago) Same when an email is delivered: Debug: master userdb out: USER#0113606183937#011user#011home=/home/users_LDAP/ user#011uid=10017#011gid=8#011quota_storage_size=32000000B#011auth_mech=PLAIN#011auth_token=8a4a9216541654643f33119dd9a280c672c#011local_name=127.0.0.1 But finally the quota limit is still the default value # doveadm quota get -u user Quota name Type Value Limit % User quota STORAGE 6294796 10485760 60 User quota MESSAGE 29190 - 0 All my dovecot configuration is available below. About Postfix, dovecot-lda is called with -d option: mailbox_command = /usr/lib/dovecot/dovecot-lda -f "$SENDER" -d "$USER" If you have any idea. Thanks in advance for you help. Best Damien BTW, some "%" seem to be missing in the 2.4 documentation https:// doc.dovecot.org/main/core/plugins/quota.html before {ldap:quotaBytes}B Dovecot version: 2.4.1-4+ubuntu24.04 dovecot -n: # OS: Linux 6.8.0-57-generic x86_64 Ubuntu 24.04.2 LTS ext4 # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_mechanisms = plain login default_client_limit = 12015 default_process_limit = 3003 default_vsz_limit = 256M dovecot_storage_version = 2.3.0 fts_autoindex = yes fts_autoindex_max_recent_msgs = 999 fts_search_add_missing = yes ldap_base = ou=MyOU,dc=domain,dc=com ldap_uris = ldap://localhost log_debug = category=auth mail_driver = maildir mail_home = /home/users_LDAP/%{user}/Maildir mail_path = /home/users_LDAP/%{user}/Maildir mail_plugins { quota = yes } protocols = imap pop3 sieve ssl_min_protocol = TLSv1.3 passdb ldap { fields { user = %{ldap:uid} userdb_gid = %{ldap:gidNumber} userdb_home = %{ldap:homeDirectory} userdb_quota_storage_size = %{ldap:quotaBytes}B userdb_uid = %{ldap:uidNumber} } bind = yes filter = (&(objectClass=posixAccount)(uid=%{user})) } namespace inbox { mail_driver = maildir mail_path = /home/users_LDAP/%{user}/Maildir hidden = no inbox = yes list = yes prefix = separator = / subscriptions = yes type = private mailbox Drafts { special_use = "\\Drafts" } mailbox Junk { special_use = "\\Junk" } mailbox Trash { special_use = "\\Trash" } mailbox Sent { special_use = "\\Sent" } mailbox "Sent Messages" { special_use = "\\Sent" } } service imap-login { inet_listener imap { } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { } inet_listener pop3s { } } service submission-login { inet_listener submission { } inet_listener submissions { } } service lmtp { unix_listener lmtp { } } service imap { } service pop3 { } service submission { } service auth { unix_listener auth-userdb { mode = 0777 user = mail } unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service auth-worker { } service dict { unix_listener dict { } } ssl_server { cert_file = /etc/letsencrypt/live/cert/fullchain.pem key_file = /etc/letsencrypt/live/cert/privkey.pem } protocol lda { mail_plugins { sieve = yes } } protocol imap { mail_max_userip_connections = 50 mail_plugins { imap_sieve = yes imap_quota = yes } } service managesieve-login { vsz_limit = 64M inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service managesieve { } quota "User quota" { driver = count storage_size = 10G 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 user = dovecot unix_listener quota-warning { user = mail } } sieve_script personal { active_path = ~/.dovecot.sieve driver = file path = ~/sieve }

2 2

Pigeonhole: (Sub-)Folders containing emojis not found
by Alexander Skwar 07 Apr '25

07 Apr '25

Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined:require ["regex","imap4flags","fileinto"];if anyof (address :regex :comparator "i;octet" "from" ".*@(bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop;} There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/ Hello $ dovecot --version 2.3.21.1 (d492236fa0) I've got the following rule defined: require ["regex","imap4flags","fileinto"]; if anyof (address :regex :comparator "i;octet" "from" ".*@ (bls\\.ch|redditmail\\.com|mail\\.tagesanzeiger\\.ch|link\\.ch|app\\.intervista\\.ch|news\\.outdooractive\\.com|spschweiz\\.ch|mail\\.landbote\\.ch|sofalesungen\\.ch)$") { fileinto "🗣 MLs Foren/🗞 Newsletter"; addflag "$label6"; stop; } There are also others, of course. In the Sieve log file “a(a)skwar.xyz.sieve.xn--log-9o0a, I find that the filter did not work: error: msgid=<a48c8bad-1d8f-4c29-a41d-e58f2dc2eed6(a)ind1s01mta1013.xt.local>: fileinto action: failed to store into mailbox '🗣 MLs Foren/🗞 Newsletter': Mailbox doesn't exist: 🗣 MLs Foren/🗞 Newsletter. I'm attaching the message as well. The folders DO exist — both parent “🗣 MLs Foren” and subfolder “🗞 Newsletter”. Why's that? I'm using Mailcow v2025-03a; Dovecot: 2.3.21.1 (d492236fa0). I created the folders and filters in SOGo webmail, which is shipped with Mailcow. Thanks, Alexander -- Alexander -- Complete contact details at https://a.skwar.xyz/

1 1

dovecot-pigeonhole 2.4.1 example config files are deprecated
by Peter Varkoly 05 Apr '25

05 Apr '25

dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90-sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve-extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer dovecot-pigeonhole version 2.4.1 The delivered example configuration files 20-managesieve.conf 90-sieve.conf 90- sieve-extprograms.conf have the syntax of 2.3 and dovecot 2.4.1 can not parse these. Following error messages occurs: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve- extprograms.conf line 9: Unknown section name: plugin doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/90-sieve.conf line 24: Unknown section name: plugin 20-managesieve.conf does not cause error messages but does not correspond to what is described under https://doc.dovecot.org/2.4.1/core/plugins/ imap_sieve.html -- Peter Varkoly SW Engineering(Systems) SUSE Software Solutions Germany GmbH Frankenstraße 146 D-90461 Nürnberg T +49-(0)911-740 53 0 E <varkoly(a)suse.com> https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 0

sieve-filter editheader
by Claudinei Luís Bianchini 03 Apr '25

03 Apr '25

Hi, I'm trying to use the editheader extension of sieve, without success. If you can help, I would appreciate it. My setup looks like this: cat 90-sieve.conf plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_plugins = sieve_extprograms sieve_extensions = +body +editheader # with this line it doesn't work either: # sieve_global_extensions = +editheader } dovecot restarted ### # dovecot.sieve # ### # require [ "fileinto", "editheader", "body", "envelope", "imap4flags", "regex", "variables", "relational" ]; # ... sievec dovecot.sieve : dovecot: line 8: error: require command: unknown Sieve capability 'editheader'. dovecot: error: validation failed. sievec(root): Fatal: failed to compile sieve script 'dovecot.sieve' dovecot -n : root@email:/etc/dovecot/conf.d# doveconf -n # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-23-amd64 x86_64 Debian 11.7 # Hostname: email.netcon.com.br auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$ dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } disable_plaintext_auth = no first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_attribute_dict = file:%Lh/dovecot-attributes mail_gid = 2000 mail_location = maildir:%Lh/Maildir/:INDEX=%Lh/Maildir/ mail_plugins = quota mailbox_alias acl mail_log notify mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded- character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapsieve vnd.dovecot.imapsieve namespace { inbox = yes location = mailbox Archive { auto = no special_use = \Archive } mailbox Archives { auto = no special_use = \Archive } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox "Junk E-mail" { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:%%Lh/Maildir/:INDEX=%%Lh/Maildir/Shared/%%Ld/%%Ln prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl imapsieve_mailbox1_before = file:/var/vmail/sieve/report_spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/var/vmail/sieve/report_ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * imapsieve_url = sieve://127.0.0.1:4190 last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it mail_log_events = delete undelete expunge copy mailbox_create mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject flags mailbox_alias_new = Sent Messages mailbox_alias_new2 = Sent Items mailbox_alias_old = Sent mailbox_alias_old2 = Sent quota = dict:user::proxy::quotadict quota_grace = 10%% quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=90%% quota-warning 90 %u quota_warning4 = storage=85%% quota-warning 85 %u sieve = ~/sieve/dovecot.sieve sieve_before = /var/vmail/sieve/dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/vmail/sieve sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment sieve_max_redirects = 30 sieve_pipe_bin_dir = /etc/dovecot/sieve/pipe sieve_plugins = sieve_imapsieve sieve_extprograms sieve_vacation_send_from_recipient = yes } protocols = pop3 imap sieve lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { address = 127.0.0.1 port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { address = 127.0.0.1 port = 4190 } } service pop3-login { service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 12340 } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } service stats { fifo_listener stats-mail { mode = 0644 user = vmail } inet_listener { address = 127.0.0.1 port = 24242 } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/live/imap.netcon.com.br/fullchain.pem ssl_cipher_list = EECDH+CHACHA20:EECDH+AESGCM:EDH+AESGCM:AES256+EECDH ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes syslog_facility = local5 userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve } protocol lmtp { lmtp_save_to_detail_mailbox = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve recipient_delimiter = + } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 30 mail_plugins = quota mailbox_alias acl mail_log notify imap_quota imap_acl last_login imap_sieve } protocol pop3 { mail_max_userip_connections = 30 mail_plugins = quota mailbox_alias acl mail_log notify last_login pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } root@email:/etc/dovecot/conf.d# -- Claudinei Luís Bianchini nei(a)netcon.com.br

2 1

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

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

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

Indexer-worker panic and killed with signal 6 in 2.4 and Solr 9
by Zakaria 26 Mar '25

26 Mar '25

Hi there, I'm reporting what I think is a bug. I just configured dovecot 2.4 with fts_solr plugin running on solr 9.8 release and it throws this panic and sigfaults one after another. Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Panic: settings_get() - event has no SETTINGS_EVENT_ROOT Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f2fe692e549] -> libdovecot.so.0(backtrace_get+0x22) [0x7f2fe692e682] -> libdovecot.so.0(+0x13ccbc) [0x7f2fe693ccbc] -> libdovecot.so.0(+0x13cd51) [0x7f2fe693cd51] -> libdovecot.so.0(+0x6bfff) [0x7f2fe686bfff] -> libdovecot.so.0(+0x5ed08) [0x7f2fe685ed08] -> libdovecot.so.0(+0xba555) [0x7f2fe68ba555] -> libdovecot.so.0(settings_get+0x46) [0x7f2fe68bb576] -> libdovecot.so.0(ssl_client_settings_get+0x66) [0x7f2fe69196e6] -> libdovecot.so.0(http_client_init_ssl_ctx+0xa9) [0x7f2fe68d40a9] -> libdovecot.so.0(http_client_host_submit_request+0x9d) [0x7f2fe68d37dd] -> libdovecot.so.0(http_client_request_submit+0x34) [0x7f2fe68c70c4] -> libdovecot.so.0(+0xc7cf0) [0x7f2fe68c7cf0] -> libdovecot.so.0(http_client_request_send_payload+0x2e) [0x7f2fe68c7d3e] -> lib21_fts_solr_plugin.so(solr_connection_post_more+0x39) [0x7f2fe6e3af89] -> lib21_fts_solr_plugin.so(+0x4469) [0x7f2fe6e38469] -> lib20_fts_plugin.so(fts_backend_update_build_more+0x4a) [0x7f2fe6e5930a] -> lib20_fts_plugin.so(+0xa419) [0x7f2fe6e5a419] -> lib20_fts_plugin.so(+0xae8a) [0x7f2fe6e5ae8a] -> lib20_fts_plugin.so(fts_build_mail+0x57) [0x7f2fe6e5b827] -> lib20_fts_plugin.so(+0x119e1) [0x7f2fe6e619e1] -> libdovecot-storage.so.0(mail_precache+0x2c) [0x7f2fe6cd6b1c] -> indexer-worker(+0x3b8a) [0x559c6212fb8a] -> indexer-worker(+0x44b5) [0x559c621304b5] -> indexer-worker(+0x466b) [0x559c6213066b] -> libdovecot.so.0(connection_input_default+0x199) [0x7f2fe6933439] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f2fe69534d7] -> libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f2fe6954c0a] -> libdovecot.so.0(io_loop_handler_run+0x50) [0x7f2fe6953580] -> libdovecot.so.0(io_loop_run+0x48) [0x7f2fe6953758] Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Fatal: master: service(indexer-worker): child 28216 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Mar 24 11:59:13 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 11:59:13 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 29469 Done find . -name "$name" -print0 Mar 24 11:59:13 server dovecot: decode2text: Error: 29470 Done(123) | xargs -0 cat Mar 24 11:59:13 server dovecot: decode2text: Error: 29471 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32540 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32541 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32542 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32555 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32556 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32557 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:49 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:49 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32832 Done find . -name "$name" -print0 Mar 24 12:00:49 server dovecot: decode2text: Error: 32833 Done(123) | xargs -0 cat Mar 24 12:00:49 server dovecot: decode2text: Error: 32834 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:52 server dovecot: imap-login: Login aborted: Connection closed (disconnected during TLS handshake) (tls_handshake_not_finished): user=, rip=20.65.195.124, lip=77.68.117.221, TLS handshaking: Connection closed, session= Mar 24 12:00:53 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:53 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32955 Done find . -name "$name" -print0 Mar 24 12:00:53 server dovecot: decode2text: Error: 32956 Done(123) | xargs -0 cat Mar 24 12:00:53 server dovecot: decode2text: Error: 32957 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:57 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:57 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 33039 Done find . -name "$name" -print0 Mar 24 12:00:57 server dovecot: decode2text: Error: 33040 Done(123) | xargs -0 cat Mar 24 12:00:57 server dovecot: decode2text: Error: 33041 Segmentation fault | $libexec_dir/xml2text These are my relevant fts configuration:- mail_plugins = mail_compress fts fts_solr fts_autoindex = yes fts solr { url = SOLR_URL batch_size = 1000 } fts_decoder_driver = script fts_decoder_script_socket_path = decode2text service indexer-worker { vsz_limit = 4G } service decode2text { executable = script /usr/libexec/dovecot/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } } language "en" { default = yes } I think anyone can reproduce the panic using following commands while targeting a mailbox which contains as many emails as possible maybe 20K. Commit and optimise dovecot core. /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?commit=true" /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?optimize=true" Rescan and index the mailbox. doveadm fts rescan -u hi(a)zakaria.website doveadm index -u hi(a)zakaria.website -q "*" I tested this on dovecot released solrconfig.xml for solr 9. Note, current solr 9 has breaking changes to the config, I rectified using the following, please refer to https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-so…. Appending n solr deployment configuration following two lines:- SOLR_OPTS="$SOLR_OPTS -Dsolr.config.lib.enabled=true" SOLR_MODULES=extraction,ltr,analysis-extras Also, additional note there are some other minor log warning, but weren't problematic. With thanks. Zak. [https://api.zakaria.website/users/hi@zakaria.website/ f6ebf9ed031e93b5ed35f78ceb338278(a)zakaria.website/30db6adddb640dbc14bfad.png] Hi there, I'm reporting what I think is a bug. I just configured dovecot 2.4 with fts_solr plugin running on solr 9.8 release and it throws this panic and sigfaults one after another. Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Panic: settings_get() - event has no SETTINGS_EVENT_ROOT Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f2fe692e549] - > libdovecot.so.0(backtrace_get+0x22) [0x7f2fe692e682] -> libdovecot.so.0 (+0x13ccbc) [0x7f2fe693ccbc] -> libdovecot.so.0(+0x13cd51) [0x7f2fe693cd51] - > libdovecot.so.0(+0x6bfff) [0x7f2fe686bfff] -> libdovecot.so.0(+0x5ed08) [0x7f2fe685ed08] -> libdovecot.so.0(+0xba555) [0x7f2fe68ba555] - > libdovecot.so.0(settings_get+0x46) [0x7f2fe68bb576] -> libdovecot.so.0 (ssl_client_settings_get+0x66) [0x7f2fe69196e6] -> libdovecot.so.0 (http_client_init_ssl_ctx+0xa9) [0x7f2fe68d40a9] -> libdovecot.so.0 (http_client_host_submit_request+0x9d) [0x7f2fe68d37dd] -> libdovecot.so.0 (http_client_request_submit+0x34) [0x7f2fe68c70c4] -> libdovecot.so.0(+0xc7cf0) [0x7f2fe68c7cf0] -> libdovecot.so.0(http_client_request_send_payload+0x2e) [0x7f2fe68c7d3e] -> lib21_fts_solr_plugin.so(solr_connection_post_more+0x39) [0x7f2fe6e3af89] -> lib21_fts_solr_plugin.so(+0x4469) [0x7f2fe6e38469] - > lib20_fts_plugin.so(fts_backend_update_build_more+0x4a) [0x7f2fe6e5930a] - > lib20_fts_plugin.so(+0xa419) [0x7f2fe6e5a419] -> lib20_fts_plugin.so(+0xae8a) [0x7f2fe6e5ae8a] -> lib20_fts_plugin.so(fts_build_mail+0x57) [0x7f2fe6e5b827] - > lib20_fts_plugin.so(+0x119e1) [0x7f2fe6e619e1] -> libdovecot-storage.so.0 (mail_precache+0x2c) [0x7f2fe6cd6b1c] -> indexer-worker(+0x3b8a) [0x559c6212fb8a] -> indexer-worker(+0x44b5) [0x559c621304b5] -> indexer-worker (+0x466b) [0x559c6213066b] -> libdovecot.so.0(connection_input_default+0x199) [0x7f2fe6933439] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f2fe69534d7] - > libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f2fe6954c0a] - > libdovecot.so.0(io_loop_handler_run+0x50) [0x7f2fe6953580] -> libdovecot.so.0 (io_loop_run+0x48) [0x7f2fe6953758] Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Fatal: master: service(indexer-worker): child 28216 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Mar 24 11:59:13 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 11:59:13 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 29469 Done find . -name "$name" -print0 Mar 24 11:59:13 server dovecot: decode2text: Error: 29470 Done(123) | xargs - 0 cat Mar 24 11:59:13 server dovecot: decode2text: Error: 29471 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32540 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32541 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32542 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32555 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32556 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32557 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:49 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:49 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32832 Done find . -name "$name" -print0 Mar 24 12:00:49 server dovecot: decode2text: Error: 32833 Done(123) | xargs - 0 cat Mar 24 12:00:49 server dovecot: decode2text: Error: 32834 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:52 server dovecot: imap-login: Login aborted: Connection closed (disconnected during TLS handshake) (tls_handshake_not_finished): user=<>, rip=20.65.195.124, lip=77.68.117.221, TLS handshaking: Connection closed, session= Mar 24 12:00:53 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:53 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32955 Done find . -name "$name" -print0 Mar 24 12:00:53 server dovecot: decode2text: Error: 32956 Done(123) | xargs - 0 cat Mar 24 12:00:53 server dovecot: decode2text: Error: 32957 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:57 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:57 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 33039 Done find . -name "$name" -print0 Mar 24 12:00:57 server dovecot: decode2text: Error: 33040 Done(123) | xargs - 0 cat Mar 24 12:00:57 server dovecot: decode2text: Error: 33041 Segmentation fault | $libexec_dir/xml2text These are my relevant fts configuration:- mail_plugins = mail_compress fts fts_solr fts_autoindex = yes fts solr { url = SOLR_URL batch_size = 1000 } fts_decoder_driver = script fts_decoder_script_socket_path = decode2text service indexer-worker { vsz_limit = 4G } service decode2text { executable = script /usr/libexec/dovecot/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } } language "en" { default = yes } I think anyone can reproduce the panic using following commands while targeting a mailbox which contains as many emails as possible maybe 20K. Commit and optimise dovecot core. /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?commit=true" /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/ update?optimize=true" Rescan and index the mailbox. doveadm fts rescan -u hi(a)zakaria.website doveadm index -u hi(a)zakaria.website -q "*" I tested this on dovecot released solrconfig.xml for solr 9. Note, current solr 9 has breaking changes to the config, I rectified using the following, please refer to https://solr.apache.org/guide/solr/latest/upgrade- notes/major-changes-in-solr-9.html. Appending n solr deployment configuration following two lines:- SOLR_OPTS="$SOLR_OPTS -Dsolr.config.lib.enabled=true" SOLR_MODULES=extraction,ltr,analysis-extras Also, additional note there are some other minor log warning, but weren't problematic. With thanks. Zak.

2 2

Dovecot 2.4: Segfault for "doveadm proxy kick foo bar"
by Michael Goth 25 Mar '25

25 Mar '25

Hi! The following command segfaults on Dovecot 2.4: #> doveadm proxy kick foo bar Segmentation fault (core dumped) Giving only one user (doveadm proxy kick foo) works: #> doveadm proxy kick foo 0 connections kicked It does not matter if the users actually exist on the server (so the above command can be used verbatim). This used to work in Dovecot 2.3. I'm running Dovecot 2.4 on Ubuntu 24.04, installed from repo.dovecot.org. Regards, Michael

2 1

Re: lost emails - Opened mail because: snippet ?
by Michael Slusarz 24 Mar '25

24 Mar '25

> On 03/24/2025 9:41 AM MDT Arkadiusz Miśkiewicz via dovecot <dovecot(a)dovecot.org> wrote: > > Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail > not cached, highest cached seq=20 uid=31: reset_id=1742577355) > > "Opened mail because: snippet " - what does this mean? It is reading the mail to create the preview text, which is then stored in the indexes. michael

2 1

lost emails - Opened mail because: snippet ?
by Arkadiusz Miśkiewicz 24 Mar '25

24 Mar '25

Hello. I'm tracking a weird case where dovecot (it's 2.3.21.1) looses incoming emails. Email is delivered over LMTP with full success (in theory). From lmtp raw log: 1742822341.735762 250 2.0.0 <examplelogin@mbox> +LpAG8Vb4Wc9OAAA9fPEKQ Saved 1742822341.735918 221 2.0.0 Bye Log says it got saved: Mar 24 14:19:01 mbox dovecot[22785]: lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, msgid=<XYZ...1611.EURP189.PROD.OUTLOOK.COM>, storage_id=1742822341.M462393P14397.mbox,S=139039,W=141006, delivery_status=saved mail to INBOX There is a file name but # find /var/mail/examplelogin/ -name '1742822341.M462393P14397.mbox*' # nothing. Well, someone could delete or move this email, right? But no, that's not the case, only pop3 sessions around: > Mar 24 14:18:43 mbox dovecot[22785]: pop3(examplelogin): pid=<24041> session=<rX98cRYxIvlTDCet>, Disconnected: Logged out top=0/0, retr=0/0, del=0/20, size=5204114, in=24, out=1002 > Mar 24 14:19:01 mbox dovecot[22785]: lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, msgid=<XYZ...1611.EURP189.PROD.OUTLOOK.COM>, storage_id=1742822341.M462393P14397.mbox,S=139039,W=141006, delivery_status=saved mail to INBOX > Mar 24 14:19:43 mbox dovecot[22785]: pop3-login: Login: user=<examplelogin>, method=PLAIN, rip=1.1.1.1, rport=63799, lip=2.2.2.2, lport=110, mpid=27238, session=<GPgZdRYxN/lTDCet> > Mar 24 14:19:44 mbox dovecot[22785]: pop3(examplelogin): pid=<27238> session=<GPgZdRYxN/lTDCet>, Disconnected: Logged out top=0/0, retr=0/0, del=0/20, size=5204114, in=24, out=1002 Note the same number of total mails in del log before and after problematic mail delivery - "del=0/20", so dovecot doesn't see that new mail (there are few pop3 logins after that - all with del=0/20) So the conclusion is that the file, with email, was not created on the filesystem. LMTP raw session log, debug session log, nothing weird - below. BUT there is one thing: Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=20 uid=31: reset_id=1742577355) "Opened mail because: snippet " - what does this mean? Out of 50k mails delivered only 160 have that "Opened mail because: snippet" and by that I mean that logged for lmtp like: Mar 24 07:25:18 lmtp(xyz): pid=<28535> session=<SPx6Ds764Gd3bwAA9fPEKQ>, Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=291 uid=4094: reset_id=1579231568) The rest have "UID 0: Opened mail because: mail stream". Started looking at these snipped entries. It seems that almost every mail with this logged is missing on the filesystem(!). Huh, what could be happening here? debug log (is there a way to enable even more detailed/low level log?): > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): Started userdb lookup > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): auth USER input: examplelogin home=/var/mail/examplelogin/ mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin uid=1234 gid=7890 sieve_enabled=no > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): Finished userdb lookup (username=examplelogin home=/var/mail/examplelogin/ mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin uid=1234 gid=7890 sieve_enabled=no) > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: changed username to examplelogin > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: lmtp-server: conn unix:pid=25252,uid=8 [89]: rcpt examplelogin@mbox: Added userdb setting: mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: lmtp-server: conn unix:pid=25252,uid=8 [89]: rcpt examplelogin@mbox: Added userdb setting: plugin/sieve_enabled=no > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Effective uid=1234, gid=7890, home=/var/mail/examplelogin/ > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Calkowita przestrzen dla serwera backend=fs args=group > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Calkowita przestrzen dla serwera bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Twoja przestrzen e-mail backend=fs args=user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Twoja przestrzen e-mail bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: maildir++: root=/var/mail/examplelogin, index=/var/lib/dovecot/control/examplelogin, indexpvt=, control=/var/lib/dovecot/control/examplelogin, inbox=/var/mail/examplelogin, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota add mailbox dir = /var/mail/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota block device = /dev/mapper/vg_sys-lv_home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount point = /home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount type = xfs > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: fts: Indexes disabled for namespace '' > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota2_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: User session is finished > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Effective uid=1234, gid=7890, home=/var/mail/examplelogin/ > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Calkowita przestrzen dla serwera backend=fs args=group > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Calkowita przestrzen dla serwera bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Twoja przestrzen e-mail backend=fs args=user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Twoja przestrzen e-mail bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: maildir++: root=/var/mail/examplelogin, index=/var/lib/dovecot/control/examplelogin, indexpvt=, control=/var/lib/dovecot/control/examplelogin, inbox=/var/mail/examplelogin, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota add mailbox dir = /var/mail/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota block device = /dev/mapper/vg_sys-lv_home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount point = /home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount type = xfs > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: fts: Indexes disabled for namespace '' > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota2_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: duplicate db: Initialize > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: Pigeonhole version 0.5.21.1 (49005e73) initializing > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: Sieve is disabled for this user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: duplicate db: Cleanup > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Mailbox opened > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=20 uid=31: reset_id=1742577355) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Adding field hdr.Subject to cache for the first time (uid=0) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Mailbox opened > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: User session is finished ps. logins, uid, gid changed to example values -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Cannot retrieve private key from LDAP
by luis.neapolis＠gmail.com 22 Mar '25

22 Mar '25

Hello, I have a problem setting the mail-crypt plugin using global keys. First of all I prepare keys: penssl ecparam -genkey -name secp521r1 | openssl pkey -aes-256-cbc -passout pass:foobar | base64 -w0 >ecprivkey.pem cat ecprivkey_b64.pem | openssl ec -pubout > ecpubkey.pem Now I would like to pass these values using the LDAP passdb. My conf is: userdb ldap { driver = ldap ldap_filter = ... ldap filter ... fields { ... other fields ... crypt_global_public_key_file = inline:%{ldap:pubkey_in_pem_base64} crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:key_in_pem_base64} crypt_global_private_key/main/private_key_password=foobar } } mail_plugins { mail_crypt = yes } crypt_global_private_key main { # create the filter, but leave its settings empty } when I receive an email I have: lmtp(127004): Fatal: Raw user initialization failed: mail_crypt_plugin: main: Couldn't parse private key : Unknown key format I want to let you know that if I give same keys, without base64 encoding, to configuration: crypt_global_private_key main { crypt_private_key_file= /path/to/key } and: userdb ldap { ..... fields { ... other fields ... # crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:key_in_pem_base64} ... other fields ... } } all works. If I try to retrieve values from LDAP all is ok with: doveadm user user@domain Any suggestion? Thank you.

1 0

dovecot 2.4 : quota config help
by ollie＠ik.me 20 Mar '25

20 Mar '25

Hello ! My dovecot config seems to work ok for managing email, using sieve filters or encrypting emails, but I can't figure out how to use the new quota config. I'm scratching my head over that one since last week and I don't see where I have done a mistake. The quota is properly reported in sql, but when I cross the percentage limit that is supposed to trigger the quota-warning, nothing happens. And I can see that too in the logs compared to my previous 2.3 install where lmtp-server was doing its job to check the quota and trigger the warning. I'm sure that I've forgotten something quite stupid, but at that point I'm not sure if I ever will be able to spot it (and I'm also wondering if that could be a bug... in that case I could scratch my head forever without any hope of finding what's wrong). I'd post my dovecot config if some of you feel like helping, but there are so many posts with configs that do not have answer that I'm wondering if it's useful. So, should I post it or not ?

1 2

Dovecot 2.4.0 local_name wildcard matching regression
by Julius Kriukas 19 Mar '25

19 Mar '25

Hi, Using a wildcard host name in the `local_name` filter no longer works in Dovecot 2.4.0. This is useful for wildcard certificates. Example `dovecot.conf`: ``` ssl_server_cert_file = /etc/dovecot/global.cert ssl_server_key_file = /etc/dovecot/global.key ssl_server_dh_file = /etc/dovecot/dh.pem ... local_name "*.example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } local_name "example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } ``` The configuration is tested with: ``` openssl s_client -connect mail.example.com:993 openssl s_client -connect example.com:993 ``` The first connection to mail.example.com fails because Dovecot uses the default `global.cert` file. The second test with the exact host name match works as expected. Dovecot uses the `example.com.cert` file. Similar to the previously reported multiple hosts on the same line discrepancy, it seems that the `doveconf` tool still has the wildcard matching support: ``` # doveconf -f local_name=mail.example.com ssl_server ssl_server { cert_file = /etc/dovecot/example.com.cert dh_file = /etc/dovecot/dh.pem key_file = /etc/dovecot/example.com.key } ``` Is there a new way to achieve the wildcard matching behaviour of the local_name filter in Dovecot 2.4.0? Thanks. -- Julius Kriukas

3 3

LDAP quota is ignored
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded from dovecot 2.3.x to 2.4.0. I converted the configuration files and all is ok, but there is this strange thing about quota. I have quota limit from LDAP: quota_storage_size = %{ldap:quota}G Value is correctly retrieved from LDAP, with "doveadm user user@domain": quota_storage_size 10G In configuration files of dovecot I have nothing about quota definitions. If I check in webmail I have undefined value. If I set manually in configuration files: quota "User quota" { storage_size = 1G } quota is correctly shown in webmail, but only with this default value. It appears it ignores values from ldap userdb. How can I debug this? Thanks.

2 2

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

2 3

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 18 Mar '25

18 Mar '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel

1 0

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

1 0

Help: Configuration example conversion from 2.3 to 2.4 ?
by ollie＠ik.me 17 Mar '25

17 Mar '25

Hello ! Like many people who are posting here, I'm a bit in "trouble" to convert my actual v2.3 config that is perfectly functional to the new v2.4 I've read the doc, searched on this list and everywhere I could find something among search engine results, and I still can't figure out how to solve my problem. The lack of examples right now is probably what is blocking me, so.. can anyone here with sharp knowledge of v2.4 configuration "translate" this official v2.3 example into a working v2.4 example ? ( ref: https://doc.dovecot.org/2.3/configuration_manual/quota/quota_dict/ ) Server-based Dictionaries -------------------------------------- plugin { # SQL backend: quota = dict:User quota::proxy::sqlquota # Redis backend (v2.1.9+): quota = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota_rule = *:storage=10M:messages=1000 } dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } ============================ Example dovecot-dict-sql.conf.ext: -------------------------------------------------- connect = host=localhost dbname=mails user=sqluser password=sqlpass map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } Thanks a million times to whoever can do that ! :) Lon.

2 2

RFC header to plain address(es)
by Jochen Bern 14 Mar '25

14 Mar '25

This has got to be one of the most stupid questions I've ever asked online ... I have a need of a "helper function" that takes a string someone would "want to send an e-mail to", i.e., something like an RFC 5322 "address" token, as used in a "To:" header, and extract just the actual e-mail address(es) from it. (The capability to deal with lists of *several* recipients is likely optional.) I found a certain number of *libraries* for various programming languages that offer such a functionality¹, but I would prefer an executable from some run-of-the-mill Linux/UNIX package to be called by shell command. Considering that pretty much every MTA and MUA must contain such functionality (to construct an SMTP envelope for a mail to be sent), and then some (I looked into, e.g., procmail), I'm surprised that apparently none of them *expose* it. (I seem to remember that the original "sendmail -bt" came somewhat close at least ...) Does anyone have an idea what tool I could (ab)use for that purpose? ¹ Namely: -- parseaddr() for python https://documentation.help/Python-PEP/module-email.Utils.html -- maildrop for C https://www.courier-mta.org/maildrop/rfc822.html -- mail_parser for Rust https://docs.rs/mail-parser/latest/mail_parser/ -- address-rfc2822 for JavaScript https://www.npmjs.com/package/address-rfc2822 -- mailparse-rfc822-parse-addresses for PHP https://www.php.net/manual/en/function.mailparse-rfc822-parse-addresses.php -- mail-header-parse-address for LISP https://www.gnu.org/software/emacs/manual/html_node/emacs-mime/Interface-Fu… -- and I suppose you could try to stuff the syntax definition into some parser code generator, too https://www.rfc-editor.org/rfc/rfc5322#section-3.4 Thanks in advance, -- Jochen Bern Systemingenieur Binect GmbH

2 1

Build error without ldap support
by Lafiel 14 Mar '25

14 Mar '25

Hi. Cannot build Dovecot without LDAP support. Configure flags: --with-ldap=no Error: In file included from db-ldap-settings.c:9: ../../src/lib-ldap/ldap-settings-parse.h:4:10: fatal error: ldap.h: No such file or directory 4 | #include <ldap.h> | ^~~~~~~~ compilation terminated. make[3]: *** [Makefile:2138: auth-db-ldap-settings.o] Error 1 Dovecot version: 2.4.0 -- Best regards, Lafiel mailto:lafiel@elven.pw

3 4

Instructions for upgrading to a newer version returns 404
by Jose Celestino 14 Mar '25

14 Mar '25

Hi, https://doc.dovecot.org/2.4.0/installation/upgrading.html returns a 404. Best regards, José Celestino

3 2

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 13 Mar '25

13 Mar '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use the doveadm command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf if anyone can help 🙏 dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use the doveadm command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf if anyone can help 🙏 dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel

1 0

Bug: Logout counters reset after recreating hibernated process
by Eirik Rye 12 Mar '25

12 Mar '25

Hello, # dovecot --version 2.3.20 (80a5ac675d) When using hibernation (`imap_hibernate_timeout = 10s`), counters such as deleted/expunged messages, appear to be reset after the user process is recreated. Steps to reproduce: 1. Configure IMAP hibernation 2. Login with IMAP client 3. Delete+expunge a message 4. IDLE, and wait 10s for process to be hibernated 5. Unhibernate process (`DONE`), and log out 6. Observe the logged line: 2023-09-05T17:36:26+0200 imap(<redacted>)<776933><jA2nYJ4EPdcqAVtAAADwAAutur4AAAAB>: Info: Disconnected: Logged out in=9 out=88 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 The expected output is "deleted=1 expunged=1", not "deleted=0 expunged=0". If you follow the steps above, but skip the IDLE/hibernate step, the output is as expected. Interestingly, if the client is disconnected during hibernation (without recreating the process), the output from `imap-hibernate` is still as expected: 2023-09-05T17:45:15+0200 imap-hibernate(<redacted>)<770540><0qE0gJ4Emt8qAVtAAADwAAutur4AAAAB>: Info: Disconnected: Connection closed in=97 out=1020 deleted=1 expunged=1 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 This leads me to believe the counters are lost during process recreation, not during hibernation. This is an issue as customers will often come to us asking why messages have disappeared in their inbox, or asking for help to identify which client is expunging messages. Right now, this information is lost if hibernation is used and the client is hibernated after expunging. Best regards, Eirik Rye

2 2

SELinux blocking dovecot from writing to passwd.db
by jcalvert＠crystal3.com 11 Mar '25

11 Mar '25

Greetings, I'm running dovecot 2.3.21.1 (Plesk says up-to-date) on AlmaLinux 8.10, Plesk Obsidian 18.0.67 #3. I'm getting this repeated error in /var/log/messages... "SELinux is preventing /usr/libexec/dovecot/auth from write access on the file passwd.db." (I think passwd.db is the one in /var/lib/plesk/mail/auth/) This causes... "Activating via systemd: service name='org.fedoraproject.Setroubleshootd'" which is taking a lot of CPU. This error is happening continuously, about 1-3 times per minute. Am I correct in thinking that an email client or webmail client is trying to change an email account password via IMAP? If so, I would like to know how to disable this ability in dovecot. (I would like to change email account passwords only via Plesk.) If not, why is dovecot trying to write to the passwd.db file? The fact that SELinux is blocking this is concerning. thanks, JC

4 8

How to configure director
by akshay＠deeproot.in 11 Mar '25

11 Mar '25

Hi, I am testing instance with 1 director and 2 nodes. followed instructions in https://doc.dovecot.org/2.3/configuration_manual/director_settings/ but the authentication happens within the director server. Director does not forward connections to configured mail servers. LDAP is my user backend. How do i configure director ? Following is my director configuration # Director.conf director_servers = 10.22.13.164 director_mail_servers = 10.22.13.11 10.22.13.244 director_user_expire = 15 min service director { user = dovecot group = dovecot unix_listener login/director { mode = 0666 user = dovecot group = dovecot } fifo_listener login/proxy-notify { mode = 0666 } unix_listener director-userdb { mode = 0600 } inet_listener { port = 9090 } unix_listener director-admin { mode = 0666 } } service imap-login { executable = imap-login director #executable = director imap-login user = dovecot group = dovecot } service pop3-login { #executable = pop3-director } service submission-login { #executable = submission-login director } protocol lmtp { auth_socket_path = director-userdb } #### Thanks, Akshay

2 2

Some folders are not displayed correctly via IMAP protocol
by Lafiel 10 Mar '25

10 Mar '25

Hi. The Bat! email client does not display folder, it will appear as ' Example'. The email client technical support said quotation marks. Log IMAP: ``` C: { ------ TImapUpdateSubscription sta C: 9 LSUB "" "*" S: * LSUB (\Drafts) "." Drafts S: * LSUB (\Sent) "." Sent S: * LSUB (\Junk) "." Junk S: * LSUB (\Trash) "." Trash S: * LSUB () "." [Example] S: * LSUB () "." Example S: 9 OK Lsub completed (0.001 + 0.000 s C: } ------ TImapUpdateSubscription fin ``` I'm using the Dovecot version 2.3.21.1. -- Best regards, Lafiel mailto:lafiel@elven.pw

2 2

Questions about fts_flatcurve in Dovecot 2.4
by Andrea Gabellini 10 Mar '25

10 Mar '25

Hi, I'm testing the fts_flatcurve plugin on Dovecot 2.4. This is my first time using an FTS plugin, and I have a few questions. Below is the configuration I am referring to. - Does the language_filters setting apply by default when a language xx {} section is defined? - If so, within a language section where a filter is declared, should I set filter_name = no to remove it? - The documentation includes this warning: "Using stopwords with multiple languages configured WILL cause some searches to fail. The recommended solution is to NOT use the stopword filter when multiple languages are present in the configuration." Does this mean it's best to avoid the stopwords filter entirely, or can it still be used for at least one language? - Does the attached configuration make sense? :-) language_filters { lowercase = yes normalizer-icu = yes snowball = yes } language it { default = yes filters { lowercase = yes normalizer-icu = yes snowball = yes stopwords = yes } } language en { } language de { } language es { } language fr { filters { lowercase = yes normalizer-icu = yes snowball = yes contractions = yes } } Thanks in advance for your support! Andrea -- TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

1 0

Dovecot Crash
by Kent Borg 08 Mar '25

08 Mar '25

In this morning's logwatch e-mail I see a dovecot crash: > Mar 7 20:45:49 la postfix/local[1059550]: 5F068405A88E8: > to=<kentborg(a)mail2.borg.org>, orig_to=<kentborg-lkml(a)borg.org>, > relay=local, delay=0.35, delays=0.35/0/0/0, dsn=2.0.0, status=sent > (delivered to maildir) > Mar 7 20:45:49 la postfix/qmgr[1620]: 5F068405A88E8: removed > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Panic: file > dsync-ibc.c: line 168 (dsync_ibc_send_mail_request): assertion failed: > (request->guid != NULL || request->uid != 0) > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x5c) > [0x7f920106dc] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x24) > [0x7f92010848] -> /usr/lib/dovecot/libdovecot.so.0(+0xfd750) > [0x7f9201d750] -> > /usr/lib/dovecot/libdovecot.so.0(i_syslog_error_handler+0) > [0x7f9201e064] -> /usr/lib/dovecot/libdovecot.so.0(i_unreached+0) > [0x7f91f6698c] -> > dovecot/doveadm-server(dsync_ibc_send_mail_request+0xd8) > [0x558263fb38] -> > dovecot/doveadm-server(dsync_brain_sync_mails+0x\2f0) [0x5582639440] > -> dovecot/doveadm-server(+0x4eea0) [0x558262eea0] -> > dovecot/doveadm-server(+0x4f338) [0x558262f338] -> > dovecot/doveadm-server(+0x5b2b4) [0x558263b2b4] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x74) [0x7f92039d44] > -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x138) > [0x7f9203c488] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) > [0x7f9203c5d4] -> /usr/lib/dovecot/libdo\vecot.so.0(io_loop_run+0x44) > [0x7f9203c898] -> dovecot/doveadm-server(+0x32374) [0x5582612374] -> > dovecot/doveadm-server(+0x32ed4) [0x5582612ed4] -> > dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x610) > [0x5582614514] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x448) > [0x558261ef18] -> dovecot/doveadm-server(+0x4aeac) [0x558262aeac] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x74) [0x7f92039d44] > -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x138) > [0x7f9203c488] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) > [0x7f9203c5d4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x44) > [0x7f9203c898] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x20) > [0x7f91f99ef0] -> dovecot/doveadm-server(main+0x108) [0x55825fe708] -> > /lib/aarch64-linux-gnu/libc.so.6(+0x27740) [0x7f91cf7740] -> > /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98) > [0x7f91cf7818] -> dovecot/doveadm-server(_start+0x30) [0x55825fe7b0] > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Fatal: master: > service(doveadm): child 1059554 killed with signal 6 (core dumps > disabled - https://dovecot.org/bugreport.html#coredumps) I am assuming that message 5F068405A88E8 was the one being processed, and it seems to have vanished. It is one thing for me to have dsync glitches that fix themselves, but this is a serious bug if I am losing e-mail. I am running Dovecot 2.3.19.1 (b907e01) with two small changes I've talked about before* (https://github.com/kentborg/dovecot-core on branch kb-replicator_queue_handle_sync_lookups) on Debian 12. -kb * These changes are not up the call chain from this crash. I tried to make a pull request for my changes but got stalled on figuring out how to reference my repository in the github GUI. Do I need to download their custom CLI tools to do it?

1 0

Re: Some folders are not displayed correctly via IMAP protocol
by Lafiel 07 Mar '25

07 Mar '25

Hi, Michael Slusarz. The client developers claim that in practice this approach leads to various problems for users. In one case, the square lines may be treated as a syntax element, and in others as part of the folder name. Predicting what is what is extremely difficult. How can i modify source code in my mail server to force the use of quotes? Michael Slusarz писал(а) 2025-03-07 08:33: > Given the mailbox 'Trash', it's fine for a server to send it back either with or without double quotes (see the RFC 3501 > ABNF). > > Thus, either of these are allowable under the > standard: > > S: * LSUB () "/" > "Trash" > S: * LSUB () "/" > Trash > > Apparently your client is not handling the non-quoted alternative correctly (the 2nd example). So this is a client bug, at least if the client is claiming to be IMAP4rev1 > compliant. > > michael -- Best regards, Lafiel mailto:lafiel@elven.pw

1 0

Re: Some folders are not displayed correctly via IMAP protocol
by Michael Slusarz 07 Mar '25

07 Mar '25

> On 03/06/2025 8:47 PM MST Stephan Bosch via dovecot <dovecot(a)dovecot.org> wrote: > > Can you explain what exactly is wrong in that output? I think it's this: S: * LSUB () "." [Example] Groking ABNF (from RFC 3501): mailbox-data = ... "LSUB" SP mailbox-list ... mailbox-list = "(" [mbx-list-flags] ")" SP (DQUOTE QUOTED-CHAR DQUOTE / nil) SP mailbox // Looking at "mailbox" part... mailbox = "INBOX" / astring astring = 1*ASTRING-CHAR / string ASTRING-CHAR = ATOM-CHAR / resp-specials ATOM-CHAR = <any CHAR except atom-specials> atom-specials = "(" / ")" / "{" / SP / CTL / list-wildcards / quoted-specials / resp-specials list-wildcards = "%" / "*" quoted-specials = DQUOTE / "\" resp-specials = "]" So... for the mailbox "[Example]", the "]" is the character that is troubling, since it is an "atom-special". *However*, "mailbox" is an astring, which can be composed of ASTRING-CHARs, and that element specifically adds the "]" back into the list of allowable characters. Put another way, a "mailbox" only requires quoting (an IMAP "string") if it contains one of the following characters: (){<SP><CTL>%*"\ The mailbox [Example] does not contain any of these forbidden characters, so it can be output without quotes. The Dovecot output you have provided is standards compliant. michael > Op 6-3-2025 om 14:59 schreef Lafiel via dovecot: > > Hi. > > > > The Bat! email client does not display > > folder, it will appear as ' Example'. > > > > The email client technical support said > > quotation marks. > > > > Log IMAP: > > ``` > > C: { ------ TImapUpdateSubscription sta > > C: 9 LSUB "" "*" > > S: * LSUB (\Drafts) "." Drafts > > S: * LSUB (\Sent) "." Sent > > S: * LSUB (\Junk) "." Junk > > S: * LSUB (\Trash) "." Trash > > S: * LSUB () "." [Example] > > S: * LSUB () "." Example > > S: 9 OK Lsub completed (0.001 + 0.000 s > > C: } ------ TImapUpdateSubscription fin > > ``` > > > > I'm using the Dovecot version 2.3.21.1. > > > > > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Issue with mail-crypt plugin on Debian Bookworm and Dovecot 2.4
by Andrea Gabellini 05 Mar '25

05 Mar '25

Hi everyone, I'm trying to use the mail-crypt plugin on Debian Bookworm with Dovecot 2.4. This is my first time using it, so please forgive any basic questions... I've added the following configuration: mail_plugins { mail_crypt = yes } crypt_global_public_key_file = /etc/dovecot/xxx_pub.pem crypt_global_private_key main { crypt_private_key_file = /etc/dovecot/xxx_priv.pem } log_debug = category=debug However, as soon as I try to use it, I see the following log entry: Fatal: dcrypt_initialize(): Plugin 'dcrypt_openssl' not found from directory /usr/lib/x86_64-linux-gnu/dovecot I've searched my file system and checked the available dovecot-* packages, but I couldn't find any trace of the missing library. Am I missing something, or is this library indeed absent from the official packages? Thanks in advance for your help! Best regards, Andrea -- TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 8

Re: 2.4 crashing on macOS with time moving forward?
by John Muccigrosso 04 Mar '25

04 Mar '25

OK, still crashed overnight while the laptop was closed. Here's the log. I had shut the laptop a bit before this first entry: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) .There were a number of "Time moved forward" entries earlier as well. The one here was isolated, but often they occur in pairs with nearly identical amounts of time, differing only by the fractions of a second between them, I suppose. For example (pairs highlighted with the same color): Mar 04 13:12:38 master: Warning: Time moved forward by 9.347642 seconds - adjusting timeouts. Mar 04 13:14:31 imap(12422): Warning: Time moved forward 83.410157 seconds Mar 04 13:14:31 imap(12420): Warning: Time moved forward 83.410166 seconds Mar 04 13:19:44 imap(12422): Warning: Time moved forward 282.970564 seconds Mar 04 13:19:44 imap(12420): Warning: Time moved forward 282.970608 seconds Mar 04 13:19:44 master: Warning: Time moved forward by 366.378919 seconds - adjusting timeouts. Mar 04 13:25:27 imap(12422): Warning: Time moved forward 282.941775 seconds Mar 04 13:25:27 imap(12420): Warning: Time moved forward 282.943614 seconds Mar 04 13:25:27 master: Warning: Time moved forward by 282.937627 seconds - adjusting timeouts. Mar 04 13:30:20 imap(12422): Warning: Time moved forward 263.355743 seconds Mar 04 13:30:20 imap(12420): Warning: Time moved forward 263.350968 seconds Now that I look, I realize that most, but not all, of the imap warnings (vs master) come in pairs. J > On Mar 2, 2025, at 18:18, J wrote: > > OK, done. Will restart. Here's the new pmset info: > > System-wide power settings: > SleepDisabled 0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by useractivityd, powerd, sharingd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 0 > womp 0 > > J > >> On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >> >> Hi! >> >> Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? >> >> Aki >> >>> On 02/03/2025 17:30 EET J wrote: >>> >>> >>> Below are the results of "pmset -g". >>> >>> Keep in mind that this >>> >>> >>> J >>> >>> >>>> On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >>>> >>>> >>>> I wonder if this is some power saving feature that pauses dovecot processes? Do >>>> you have power saving enabled? >>> >>> >>> >>> System-wide power settings: >>> SleepDisabled0 >>> Currently in use: >>> standby 1 >>> Sleep On Power Button 1 >>> hibernatefile /var/vm/sleepimage >>> powernap 1 >>> networkoversleep 0 >>> disksleep 10 >>> sleep 1 (sleep prevented by powerd) >>> hibernatemode 3 >>> ttyskeepawake 1 >>> displaysleep 20 >>> tcpkeepalive 1 >>> lowpowermode 1 >>> womp 0 >> >> _______________________________________________ >> dovecot mailing list -- dovecot(a)dovecot.org >> To unsubscribe send an email to dovecot-leave(a)dovecot.org >

1 0

Re: 2.4 crashing on macOS with time moving forward?
by John Muccigrosso 03 Mar '25

03 Mar '25

OK, first here's a series of warnings while the laptop was closed, 18:43-19:04: Mar 02 18:44:02 imap(1392): Warning: Time moved forward 24.925040 seconds Mar 02 18:44:02 imap(1397): Warning: Time moved forward 24.925062 seconds Mar 02 19:01:24 imap(1397): Warning: Time moved forward 993.009103 seconds Mar 02 19:01:24 imap(1392): Warning: Time moved forward 993.023098 seconds Mar 02 19:04:57 imap(1397): Warning: Time moved forward 182.863245 seconds Mar 02 19:04:57 imap(1392): Warning: Time moved forward 182.871467 seconds But it took until overnight, when the laptop was again closed, for the crash: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) A couple of observations: 1. There are often two warnings within a second, for time periods that are nearly, but not quite identical. 2. The time periods in question are long, minutes or tens of minutes. J > On Mar 2, 2025, at 18:18, J wrote: > > OK, done. Will restart. Here's the new pmset info: > > System-wide power settings: > SleepDisabled 0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by useractivityd, powerd, sharingd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 0 > womp 0 > > J > >> On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >> >> Hi! >> >> Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? >> >> Aki >> >>> On 02/03/2025 17:30 EET J wrote: >>> >>> >>> Below are the results of "pmset -g". >>> >>> Keep in mind that this >>> >>> >>> J >>> >>> >>>> On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >>>> >>>> >>>> I wonder if this is some power saving feature that pauses dovecot processes? Do >>>> you have power saving enabled? >>> >>> >>> >>> System-wide power settings: >>> SleepDisabled0 >>> Currently in use: >>> standby 1 >>> Sleep On Power Button 1 >>> hibernatefile /var/vm/sleepimage >>> powernap 1 >>> networkoversleep 0 >>> disksleep 10 >>> sleep 1 (sleep prevented by powerd) >>> hibernatemode 3 >>> ttyskeepawake 1 >>> displaysleep 20 >>> tcpkeepalive 1 >>> lowpowermode 1 >>> womp 0 >> >> _______________________________________________ >> dovecot mailing list -- dovecot(a)dovecot.org >> To unsubscribe send an email to dovecot-leave(a)dovecot.org > OK, first here's a series of warnings while the laptop was closed, 18:43-19:04: Mar 02 18:44:02 imap(1392): Warning: Time moved forward 24.925040 seconds Mar 02 18:44:02 imap(1397): Warning: Time moved forward 24.925062 seconds Mar 02 19:01:24 imap(1397): Warning: Time moved forward 993.009103 seconds Mar 02 19:01:24 imap(1392): Warning: Time moved forward 993.023098 seconds Mar 02 19:04:57 imap(1397): Warning: Time moved forward 182.863245 seconds Mar 02 19:04:57 imap(1392): Warning: Time moved forward 182.871467 seconds But it took until overnight, when the laptop was again closed, for the crash: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) A couple of observations: 1. There are often two warnings within a second, for time periods that are nearly, but not quite identical. 2. The time periods in question are long, minutes or tens of minutes. J On Mar 2, 2025, at 18:18, J wrote: OK, done. Will restart. Here's the new pmset info: System-wide power settings: SleepDisabled 0 Currently in use: standby 1 Sleep On Power Button 1 hibernatefile /var/vm/sleepimage powernap 1 networkoversleep 0 disksleep 10 sleep 1 (sleep prevented by useractivityd, powerd, sharingd) hibernatemode 3 ttyskeepawake 1 displaysleep 20 tcpkeepalive 1 lowpowermode 0 womp 0 J On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: Hi! Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? Aki On 02/03/2025 17:30 EET J wrote: Below are the results of "pmset -g". Keep in mind that this J On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: I wonder if this is some power saving feature that pauses dovecot processes? Do you have power saving enabled? System-wide power settings: SleepDisabled0 Currently in use: standby 1 Sleep On Power Button 1 hibernatefile /var/vm/sleepimage powernap 1 networkoversleep 0 disksleep 10 sleep 1 (sleep prevented by powerd) hibernatemode 3 ttyskeepawake 1 displaysleep 20 tcpkeepalive 1 lowpowermode 1 womp 0 _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Re: 2.4 crashing on macOS with time moving forward?
by Aki Tuomi 02 Mar '25

02 Mar '25

Hi! Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? Aki > On 02/03/2025 17:30 EET John Muccigrosso <muccigrosso(a)icloud.com> wrote: > > > Below are the results of "pmset -g". > > Keep in mind that this > > > J > > > > On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: > > > > > > I wonder if this is some power saving feature that pauses dovecot processes? Do > > you have power saving enabled? > > > > System-wide power settings: > SleepDisabled0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by powerd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 1 > womp 0

1 0

2.4 crashing on macOS with time moving forward?
by John Muccigrosso 02 Mar '25

02 Mar '25

After last week's struggle with the new version and my conf file, I got everything working. Now however dovecot crashes on me every few hours. The logs show a bunch of this kind of warning, which I find mention of on the internets: > Feb 07 15:13:47 imap(58317): Warning: Time moved forward 48.803640 seconds > Feb 07 16:30:27 master: Warning: Time moved forward by 694.039203 seconds - adjusting timeouts. > Feb 07 16:52:47 imap(61246): Warning: Time moved forward 293.443011 seconds > Feb 07 16:52:47 master: Warning: Time moved forward by 1279.423507 seconds - adjusting timeouts. > Feb 07 17:25:39 imap(61286): Warning: Time moved forward 1942.575589 seconds > Feb 07 17:25:39 imap(61288): Warning: Time moved forward 172.563346 seconds > Feb 07 17:25:39 master: Warning: Time moved forward by 1912.666999 seconds - adjusting timeouts. > Feb 07 17:49:32 imap(61286): Warning: Time moved forward 1402.761862 seconds > Feb 07 17:51:13 master: Warning: Time moved forward by 1473.582569 seconds - adjusting timeouts. > Feb 07 17:51:13 imap(61286): Warning: Time moved forward 70.823888 seconds > Feb 07 17:53:07 master: Warning: Time moved forward by 53.843767 seconds - adjusting timeouts. > Feb 07 18:44:22 imap(61286): Warning: Time moved forward 1386.259444 seconds > Feb 07 19:11:41 master: Warning: Time moved forward by 615.609964 seconds - adjusting timeouts. Note the very large jump dovecot claims is happening in all of these, up to half an hour, with a minimum of 48 seconds in this bunch. You can see that it even does a pair of these in rapid succession, like at 17:25:39 above, and will do >10 within the space of an hour. These seem eventually to be followed by a crash ("eventually" because I'm running this on my laptop which isn't always open and running). The crash log entries all start with something like this: > Feb 07 16:17:53 imap(58315): Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) The reports will end with one of these: > Feb 06 17:45:07 log(48089): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) > Feb 07 16:17:53 imap(58317): Fatal: master: service(imap): child 58317 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) One more detail, I usually do `sudo brew services start dovecot` to run dovecot and this results in the crashes. When I was testing this on Saturday, I started it with `sudo dovecot -F` instead, so that I would see problems in the terminal. It went all day without crashing and I finally stopped and restarted it with the brew method. That's not a rigorous test, but it is suggestive. Happy to provide more info, but I'm hoping this is sufficient to suggest a course of action. dovecot 2.4.0 installed via homebrew macOS 13.6.9 J

3 8

Pigeonhole: sieve_redirect_envelope_from orig_recipient results in mail bombs
by doobry 28 Feb '25

28 Feb '25

Dear Dovecot community, we changed `sieve_redirect_envelope_from` to `orig_recipient` recently to fix sieve redirects in case the forwarded mail comes from a DMARC-enabled domain. While this works well, it creates a new problem: if the receiving mail server (the one in charge of the redirect destination) reacts with a bounce mail, the bounce now will go to `orig_recipient` - the mail address that has the redirect in place, which means no less than creating a mail bomb (endless mail loop). See the following example: 1. alice(a)sender.org sends mail to jane(a)our-domain.org 2. jane(a)our-domain.org has a sieve redirect to jane(a)redirect-target.org 3. jane(a)redirect-target.org replies with a bounce because their mailbox is full. 4. The bounce mail gets sent to jane(a)our-domain.org. 5. The loop starts again at step 2. Is it possible to configure dovecot/pigeonhole to *not* forward the bounce mails from step 4 again? Probably it would work to add manual extra checks to the sieve redirect rules, but that would need to be followed by any user who configures a redirect. So I'm more looking for a server-wide configuration change that fixes this problem. Looking forward to hear about your thoughts on the problem. Kind regards doobry

3 3

Dovecot 2.4.0 multiple hosts SNI configuration regression
by Julius Kriukas 27 Feb '25

27 Feb '25

Hello everyone. We are testing out Dovecot 2.4.0 and noticed a regression in how the `local_name` filter with multiple space-separated host names works. For example, having the following dovecot.conf: ``` ... ssl_server_cert_file = /etc/dovecot/global.cert ssl_server_key_file = /etc/dovecot/global.key ssl_server_dh_file = /etc/dovecot/dh.pem ... local_name "server.example.com mail.example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } local_name "good.example.org" { ssl_server_cert_file = /etc/dovecot/example.org.cert ssl_server_key_file = /etc/dovecot/example.org.key } ... ``` Connection to server.example.com:993 (with SNI support) does not work as expected. The global certificate from the `global.cert` file is used, and validation fails. However, connection to good.example.org:993 (with SNI support) works fine. The `example.org.cert` file is used. The `doveconf` tool thinks the example configuration should work, hinting that this is likely to be a bug. Example: ``` # doveconf -f local_name=mail.example.com ssl_server ssl_server { cert_file = /etc/dovecot/example.com.cert dh_file = /etc/dovecot/dh.pem key_file = /etc/dovecot/example.com.key } ``` The results show correct file paths, but the `dovecot` server is not using them. Any confirmation if this is really a bug, or maybe an intended configuration syntax change (to force repeating the local_name blocks for each hostname) would be really appreciated. Thanks. -- Julius

3 3

Issue with ACLs in Dovecot 2.4
by Andrea Gabellini 27 Feb '25

27 Feb '25

Hi, I'm trying to migrate my setup to Dovecot 2.4, but I'm experiencing an unusual issue with ACLs. After multiple tests, I’ve stripped the configuration down to the bare minimum to pinpoint the root cause of the problem. Basically, if I set "owner lr" as the permissions for a folder, I am unable to move any messages, yet I can still create subfolders. Here’s the relevant configuration: ini Copia Modifica protocol imap { mail_plugins { acl = yes } } acl_driver = vfile acl_globals_only = yes namespace inbox { inbox = yes separator = / mailbox Test { acl owner { rights = lr } } } Am I missing any configuration, or have I encountered a bug? Thanks, Andrea -- TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 2

Strange problem with iPhone Mail
by Simon Hoffmann 27 Feb '25

27 Feb '25

Hey list, I am experiencing a strange problem where I don't even know where to begin to debug. I am running my own email server in my office. The server itself works fine. In my office firewall, I have set up DNAT/port forwarding to be able to access the server from outside. With my Android phone and my iPad I have no problems accessing the mails from anywhere, including my home WiFi. However with my iPhone, I have problems accessing my inbox when I am on my home WiFi. The problems only started a few weeks ago, it worked fine for years before. I have not changed any network related settings. Now, when I am on my home WiFi, I cannot use the "pull down to refresh" gesture. It just is not fetching any emails. The automatic sync/fetching is also not fetching the newest emails. Eventually, some emails will come through, but they are from ~6-7 hours ago. Same WiFi as my other devices that work fine. As soon as I disable WiFi on my iPhone and switch to mobile data and do the "pull down to refresh" gesture, all mails from the last 6-7 hours immediately come in. Has anyone ever experienced something like this and can help me analyse the problem? root@mx01:~# uname -a Linux mx01 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux root@mx01:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@mx01:~# dpkg -l dovecot* ||/ Name Version Architektur Beschreibung +++-======================-========================-============-=============================================== un dovecot-abi-2.3.abiv13 <keine> <keine> (keine Beschreibung vorhanden) un dovecot-common <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-core 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - core files un dovecot-gssapi <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-imapd 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - IMAP daemon un dovecot-ldap <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-lmtpd 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - LMTP server un dovecot-lucene <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-managesieved 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - ManageSieve server un dovecot-mysql <keine> <keine> (keine Beschreibung vorhanden) un dovecot-pgsql <keine> <keine> (keine Beschreibung vorhanden) un dovecot-pop3d <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-sieve 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - Sieve filters support un dovecot-solr <keine> <keine> (keine Beschreibung vorhanden) un dovecot-sqlite <keine> <keine> (keine Beschreibung vorhanden) un dovecot-submissiond <keine> <keine> (keine Beschreibung vorhanden) Thanks! Cheers, Simon

2 1

Fwd: Re: Thunderbird IMAP Problem
by Felix Zielcke 26 Feb '25

26 Feb '25

Forgot to CC list. -------- Weitergeleitete Nachricht -------- Von: Felix Zielcke <fzielcke(a)z-51.de> An: wertstoffe(a)nurfuerspam.de Betreff: Re: Thunderbird IMAP Problem Datum: 26.02.2025 14:43:36 > Am Mittwoch, dem 26.02.2025 um 13:47 +0100 schrieb Jakob: > > Ok... > > > > And does imap-login with thunderbird also work with this patch? > > > > Will this patch be merged in a further release from dovecot? > > I don't like selfcompiling... > > > > Jakob > > > > It's a patch for exim4 not dovecot. So it only fixes SMTP > authentication with it. > Timo said that there will probable be some sort of workaround in > dovecot 2.4.1. included. > > So no it won't fix imap-login. > I don't use Thunderbird so I have no clue why it fails for you. > Maybe it would have been useful to have your dovecot config?

2 1

Thunderbird IMAP Problem
by wertstoffe＠nurfuerspam.de 26 Feb '25

26 Feb '25

Hi there! I upgraded to dovecot 2.4 from dovecot repo on my debian bookworm. I modified the config for the needs for 2.4. My Fairemail could connect to dovecot and receive emails via imap. But thunderbird did not work. I activated the debug-logging for thunderbird in shell and got this |2025-02-26 07:46:15.775740 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770954ef3f00] 2025-02-26 07:46:15.776145 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770957d74600] 2025-02-26 07:46:15.776820 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776853 UTC - [Parent 677248: Main Thread]: I/IMAP queuing url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776869 UTC - [Parent 677248: Main Thread]: I/IMAP considering playing queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776881 UTC - [Parent 677248: Main Thread]: I/IMAP creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776897 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776909 UTC - [Parent 677248: Main Thread]: I/IMAP failed creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.777125 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777217 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777302 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777317 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777348 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/discoverallboxes: = currentUrl 2025-02-26 07:46:15.777362 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777404 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777420 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/select%3E/INBOX: = currentUrl 2025-02-26 07:46:15.822761 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823122 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823329 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823509 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/discoverallboxes) 2025-02-26 07:46:15.823573 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823816 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/select%3E/INBOX) 2025-02-26 07:46:15.824515 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824529 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824723 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824748 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770954ef3f00] 2025-02-26 07:46:15.824760 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824785 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770957d74600] Dovecot-log shows only this two lines on a login-try with thunderbird. ||Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<ryQk2gYvMp+sHgAB> Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<zR8k2gYvIp+sHgAB> Other logins had a user and auth attempts... only from thunderbird it does not work. I also use dovecot-login for my exim4. And smtp-login was also not able. Not even directly via openssl s_client. I could connect, send ehlo, and when i sent AUTH LOGIN <base64-username-passwor-string> and then it hangs. I went back to dovecot 2.3, and thunderbird could login again, also smtp-login works. There seems something wrong in dovecot 2.4. Have ldap-authentication. My bad, i deinstalled dovecot 2.4 and now i can not create a conf with doveconf to add it here. Hope you can help me. Jakob | Hi there! I upgraded to dovecot 2.4 from dovecot repo on my debian bookworm. I modified the config for the needs for 2.4. My Fairemail could connect to dovecot and receive emails via imap. But thunderbird did not work. I activated the debug-logging for thunderbird in shell and got this 2025-02-26 07:46:15.775740 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770954ef3f00] 2025-02-26 07:46:15.776145 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770957d74600] 2025-02-26 07:46:15.776820 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/ Synoptic/Rechnungen 2025-02-26 07:46:15.776853 UTC - [Parent 677248: Main Thread]: I/IMAP queuing url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776869 UTC - [Parent 677248: Main Thread]: I/IMAP considering playing queued url:imap://my.user@imap.domain.tld:143/ folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776881 UTC - [Parent 677248: Main Thread]: I/IMAP creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/ folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776897 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/ Synoptic/Rechnungen 2025-02-26 07:46:15.776909 UTC - [Parent 677248: Main Thread]: I/IMAP failed creating protocol instance to play queued url:imap://my.user@imap.domain.tld: 143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.777125 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777217 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777302 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777317 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777348 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/ discoverallboxes: = currentUrl 2025-02-26 07:46:15.777362 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777404 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777420 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/ select%3E/INBOX: = currentUrl 2025-02-26 07:46:15.822761 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823122 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823329 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823509 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/discoverallboxes) 2025-02-26 07:46:15.823573 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823816 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/select%3E/INBOX) 2025-02-26 07:46:15.824515 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824529 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824723 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824748 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770954ef3f00] 2025-02-26 07:46:15.824760 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824785 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770957d74600] Dovecot-log shows only this two lines on a login-try with thunderbird. Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<ryQk2gYvMp+sHgAB> Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<zR8k2gYvIp+sHgAB> Other logins had a user and auth attempts... only from thunderbird it does not work. I also use dovecot-login for my exim4. And smtp-login was also not able. Not even directly via openssl s_client. I could connect, send ehlo, and when i sent AUTH LOGIN <base64-username- passwor-string> and then it hangs. I went back to dovecot 2.3, and thunderbird could login again, also smtp-login works. There seems something wrong in dovecot 2.4. Have ldap-authentication. My bad, i deinstalled dovecot 2.4 and now i can not create a conf with doveconf to add it here. Hope you can help me. Jakob

2 1

dovecot Panic
by Jakob 24 Feb '25

24 Feb '25

Hi! I face in short intervals (every few minutes) such error-messages in dovecot Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Panic: file mail-index-view.c: line 165 (view_lookup_full): assertion failed: (seq > 0 && seq <= mail_in dex_view_get_messages_count(view)) Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb1e519f662] -> /usr/l ib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb1e519f77e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1043db) [0x7fb1e51ac3db] -> /usr/lib/dovecot/libdovecot.so.0(+0x104471) [0x7fb1e51ac471 ] -> /usr/lib/dovecot/libdovecot.so.0(+0x566a0) [0x7fb1e50fe6a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4fe26) [0x7fb1e52cae26] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x102116) [0x7fb1e537d116] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x10514c) [0x7fb1e538014c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x105ff5) [0x7fb1e5380ff5] -> /usr/lib/dovecot/libdovec ot-storage.so.0(+0x101d14) [0x7fb1e537cd14] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_keyword_indexes+0x6b) [0x7fb1e535027b] -> /usr/lib/dovecot/libdovecot-storage.so.0(inde x_mail_get_keywords+0x6d) [0x7fb1e53502fd] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x2ef9) [0x7fb1e4ba4ef9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(notify_contexts_m ail_copy+0x5f) [0x7fb1e4cbd50f] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x24f8) [0x7fb1e4cbe4f8] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xf863) [0x7fb1e4eab863] -> /usr /lib/dovecot/libdovecot-storage.so.0(+0x6508f) [0x7fb1e52e008f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x5e) [0x7fb1e52e024e] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x13ef8) [0x55766c74aef8] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](command_exec+0xa4) [0x55766c7595b4] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x20 52f) [0x55766c75752f] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x205da) [0x55766c7575da] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x208ed) [0x55766c7578ed] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](client_handle_input+0x1b5) [0x55766c757ab5] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](client_input+0x70) [0x55766c758020] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fb1e51c2609] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fb1e51c3cf2] -> /usr/lib/dovecot/libdov ecot.so.0(io_loop_handler_run+0x50) [0x7fb1e51c26b0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fb1e51c2870] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f b1e51348e3] Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Fatal: master: service(imap): child 711331 killed with signal 6 (core dumped) I run this # dpkg -l|grep dovecot ii dovecot-core 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - LMTP server ii dovecot-lucene 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Lucene support ii dovecot-managesieved 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-pop3d 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Sieve filters support ii dovecot-solr 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Solr support on debian bookworm. The client, the user uses is maybe apples mail-app on ios... but I'm not sure. And i don't know, what he is doing. Can not interpret this message. Best regards Jakob

1 0

User authentication for shared mailbox
by sveyret＠gmail.com 23 Feb '25

23 Feb '25

Hi, I’m using Dovecot 2.3.21.1. I have mailboxes for the family members and some shared mailboxes, all of them available with IMAP protocol. Users are authenticating using PAM, and shared mailboxes appear as sub-folders of user accounts. Because it is easier to use with some clients, I’m looking for a way to use the shared mailboxes as independent accounts. This would mean that, on a client, I would like to create an account to access to `family@mydomain`, but using my own username and password. I thought of a way to do this by tricking the password, setting it, for example, to `myname+mysecretpassword`, then split it in dovecot configuration in order to override the username and password. But not only didn’t I found a way to split the string, but also, if I understand correctly, setting another user to PAM module will override the name of the mailbox I want to open. What would you suggest me to do in order to get this desired behavior? Thank you.

2 2

Mail locations must use the same hierarchy separator
by Mike 21 Feb '25

21 Feb '25

Hello, First post, and yes Ive searched the archives and didn't find an answer. Sorry if this is old hat but... I am trying build a new mailserver (iredmail) and import messages from the old server (old old iredmail), and convert from dbox to maildir in the process. I have previously used doveadm sync successfully several years/versions ago with a master user and imapc:. Now however, Im getting errors that don't make sense to me. doveadm -D -c /etc/dovecot/dovecot.conf sync -1 -R -u example(a)example.com imapc: results in: dsync(example(a)example.com): Info: imapc(mail.example.com:993): Connected to 192.0.2.1:993 (local 192.0.2.1:51732) dsync(example(a)example.com): Error: Mail locations must use the same hierarchy separator (specify namespace prefix="" { separator } explicitly) I have tried all sorts of chicanery including testing every combination of "" and / and . for each of prefix and separator in dovecot.conf, no dice. I am refraining from providing full debug dump/config files since this seems excessive if this is a config file issue, but will do so upon your advice if requested. Thank you. Hello, First post, and yes Ive searched the archives and didn't find an answer. Sorry if this is old hat but... I am trying build a new mailserver (iredmail) and import messages from the old server (old old iredmail), and convert from dbox to maildir in the process. I have previously used doveadm sync successfully several years/versions ago with a master user and imapc:. Now however, Im getting errors that don't make sense to me. doveadm -D -c /etc/dovecot/dovecot.conf sync -1 -R -u example(a)example.com imapc: results in: dsync(example(a)example.com): Info: imapc(mail.example.com:993): Connected to 192.0.2.1:993 (local 192.0.2.1:51732) dsync(example(a)example.com): Error: Mail locations must use the same hierarchy separator (specify namespace prefix="" { separator } explicitly) I have tried all sorts of chicanery including testing every combination of "" and / and . for each of prefix and separator in dovecot.conf, no dice. I am refraining from providing full debug dump/config files since this seems excessive if this is a config file issue, but will do so upon your advice if requested. Thank you.

2 1

Unable to debug sieve
by Roberto Puzzanghera 20 Feb '25

20 Feb '25

I'm trying to enable sieve debug with no success on dovecot 4.0. I would like to know what it is doing when taking decisions if running a script or not and what it does when a script is executed These settings do not enable the trace sieve_trace_debug = yes sieve_trace_dir = /tmp (I also tried any other world writable dir and also ~/.sieve while testing trace for personal scripts) nor this one is enabling the debug log_debug = category=sieve sieve is working perfectly for personal but not for global scripts. Any hint appreciated. Thanks in advance, Roberto

1 0

autoexpunge
by Doug Hardie 20 Feb '25

20 Feb '25

I have the following in 15-mailboxes.config: mailbox Trash { special_use = \Trash autoexpunge = 30 days } I thought that would empty the deleted emails after 30 days. However, I find that in .Deleted Messages/cur there are over 18K messages dating back to the 90's. What do I need to set to make the autoexpunge work? -- Doug

6 9

iOS Mail.app Network error POSIX 54: is there a workaround?
by Gerben Wierda 19 Feb '25

19 Feb '25

I understand that this error that appears on iOS 18 devices is an iOS bug. Is this indeed the case and is there anything I can do about it on th server side as a workaround? Thanks, Gerben

1 0

Preventing message deletion
by dovecot＠iotti.biz 19 Feb '25

19 Feb '25

Hi all How may I disable message deletions via IMAP for some or all of my users? I read on the net that a possible solution would be to use the ACL IMAP plugin. But the examples I found were not so clear to me. We do not use shared mailboxes or namespaces. Only simple virtual users, each with it's own private mailbox. I would like to use the global acl file both for administration simplicity and because as I understood, global acl enrties take preference over any user setting. In the ACL page example there is a line: * user=foo lrw But in the comment it tells that doing so, every user' mailbox would be shared with the foo user, with the lrw permissions. Which is not what I would want. I don't need to share anything, just to restrict what the user, foo here, can do on his mailbox. Thank you, Luigi

2 4

IMAP dovecot\postgres low authentication performance
by Anatoliy Zhestov 19 Feb '25

19 Feb '25

Hi. We have a performance problem with imap authentication through postgresql. Our servers(modoboa based) have a big amount of permanent imap connections(5000-50000). Current performance is about 3000 successful authentications per hour. No visible reasons for such low speed. Accordingly, after a network failure or server restart, all clients try to reconnect, but restoring the connection pool takes hours and even tens of hours. Judging by the logs after the restart, a huge number of auth requests closed by timeout after 70-90 seconds. The postgresql database is not overloaded at the restore connections process and the postgresql connection pool (100) does not overflow. Manually started sql auth queries work fast, tables have indexes. So I guess there is a bottleneck somewhere in dovecot auth service or postgresql driver. I couldn't find any settings in the documentation that are directly responsible for regulating the number of connections to PostgreSQL from the auth service or performance of the driver. Is there any way to manage this? Does it make sense to use pgbouncer in front of the base? What else can be a bottleneck in our configuration and how to regulate the number of possible simultaneous authentications via PostgreSQL? I would be happy for any advice on how to increase the performance to at least 100 authentications per second. Thanks in advance for your help. Anatoliy Zhestov. ---------------- configs of server with 48 core, 184 gb mem --------------- dovecot 2.3.16 # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.15.0-126-generic x86_64 Ubuntu 22.04.5 LTS # Hostname: imap.ourcompany.net auth_cache_negative_ttl = 0 auth_cache_size = 20 M auth_cache_ttl = 3 hours auth_master_user_separator = * auth_mechanisms = plain login default_client_limit = 131072 default_process_limit = 131072 dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } mail_location = maildir:~/Maildir mail_plugins = quota 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 mai lbox date index ihave duplicate mime foreverypart extracttext editheader imapflags notify vnd.dovecot.pipe vnd.dovecot.execute namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { quota = dict:User quota::proxy::quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = . sieve_extensions = +notify +imapflags +editheader +body +vnd.dovecot.execute +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-execute sieve_pipe_socket_dir = . sieve_plugins = sieve_extprograms } protocols = " imap lmtp sieve" service anvil { client_limit = 393219 } service auth { client_limit = 524288 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-radicale { group = radicale mode = 0666 user = radicale } unix_listener auth-userdb { user = vmail } } service config { vsz_limit = 1 G } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap { executable = imap postlogin process_limit = 131072 vsz_limit = 1 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 512 M } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login /usr/local/bin/postlogin.sh service_count = 1000 process_min_avail = 5 user = modoboa } service send-to-click-frontapp1 { executable = script /usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh unix_listener send-to-click-frontapp1 { group = vmail mode = 0666 user = vmail } user = dovenull vsz_limit = 2 G } service send-to-click { executable = script /usr/lib/dovecot/sieve-execute/clickhouse_log.sh unix_listener send-to-click { group = vmail mode = 0666 user = vmail } user = dovenull vsz_limit = 2 G } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } vsz_limit = 2 G } ssl_cert = </etc/letsencrypt/live/imap.ourcompany.net/fullchain.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1 stats_writer_socket_path = userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)imap.ourcompany.net } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota imap_quota } /etc/dovecot/dovecot-sql-master.conf.ex driver = pgsql connect = host=127.0.0.1 port=5432 dbname=modoboa user=modoboa password=XXXXXXXXXXXXXXXXX password_query = SELECT email AS user, password FROM core_user WHERE email='%u' and is_active and master_user /etc/dovecot/dovecot-sql.conf.ext driver = pgsql connect = host=127.0.0.1 port=5432 dbname=modoboa user=modoboa password=XXXXXXXXXXXXXXXXX user_query = SELECT '/srv/vmail/%d/%n' AS home, 1003 as uid, 1003 as gid, '*:bytes=' || mb.quota || 'M' AS quota_rule FROM admin_mailbox mb INNER JOIN admin_domain dom ON mb.domain_id=dom.id INNER JOIN core_user u ON u.id=mb.user_id WHERE (mb.is_send_only IS NOT TRUE OR '%s' NOT IN ('imap', 'pop3', 'lmtp')) AND mb.address='%n' AND dom.name='%d' password_query = SELECT email AS user, password, '/srv/vmail/%d/%n' AS userdb_home, 1003 AS userdb_uid, 1003 AS userdb_gid, CONCAT('*:bytes=', mb.quota, 'M') AS userdb_quota_rule FROM core_user u INNER JOIN admin_mailbox mb ON u.id=mb.user_id INNER JOIN admin_domain dom ON mb.domain_id=dom.id WHERE (mb.is_send_only IS NOT TRUE OR '%s' NOT IN ('imap', 'pop3')) AND email='%u' AND is_active AND dom.enabled iterate_query = SELECT email AS user FROM core_user /usr/local/bin/postlogin.sh #!/bin/sh PATH="/usr/bin:/usr/local/bin:/bin" psql -c "UPDATE core_user SET last_login=now() WHERE username='$USER'" > /dev/null exec "$@" /usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh #!/bin/bash cd /tmp logger -i -t SIEVE_TEST "$1,$2,$3,$4" clickhouse-client -h XXXXXXXXXXXXXXXXX -d default -u some_user --password XXXXXXXXXXXXXXXXX \ --param_origin_from="$1" \ --param_origin_to="$2" \ --param_message_id="$3" \ --param_forward="$4" \ -q "INSERT INTO frontapp1_redirects (origin_from_email,origin_to_email,message_id,forward_email) VALUES ({origin_from:String},{origin_to:String},{message_id:String},{forward:String})" /usr/lib/dovecot/sieve-execute/clickhouse_log.sh #!/bin/bash cd /tmp logger -i -t SIEVE_TEST "$1,$2,$3,$4" clickhouse-client -h XXXXXXXXXXXXXXXXX -d default -u some_user --password XXXXXXXXXXXXXXXXX \ --param_origin_from="$1" \ --param_origin_to="$2" \ --param_message_id="$3" \ --param_forward="$4" \ -q "INSERT INTO frontapp_redirects (origin_from_email,origin_to_email,message_id,forward_email) VALUES ({origin_from:String},{origin_to:String},{message_id:String},{forward:String})"

6 30

auth_userdb_iterate
by Luigi Trovato 19 Feb '25

19 Feb '25

Hello, I have a doubt: is the lua function "auth_userdb_iterate" expected to always return the whole list of users no matter what, or it should evaluate if a specific virtual domain is provided as req argument and only list the users in that specific domain? And should the returned user list be in the format "username(a)domain.tld" or "username" ? -- Ciao, Luigi

1 1

lua API and returning reason and CONTACTADMIN
by Arkadiusz Miśkiewicz 19 Feb '25

19 Feb '25

Hello. Trying to pass reason response via lua by passing it at dovecot.auth.PASSDB_RESULT_USER_DISABLED like: function auth_password_verify(request, password) return dovecot.auth.PASSDB_RESULT_USER_DISABLED, "reason=custom_message" end function auth_userdb_lookup(request) return dovecot.auth.PASSDB_RESULT_OK, "uid=428671 gid=9726 home=/var/mail/existusertest" end function script_init() return 0 end function script_deinit() end Unfortunately returned result contains no custom message and also returns AUTHENTICATIONFAILED instead of CONTACTADMIN: NO [AUTHENTICATIONFAILED] Authentication failed. while I would expect something like: NO [CONTACTADMIN] custom_message: Any reason for such behaviour and how to get reason passed and proper CONTACTADMIN? Tests done on 2.3.21.1. passdb { driver = lua mechanisms = login plain args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } userdb { driver = lua args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 6

Can someone explain this to me, please?
by Ken Wright 19 Feb '25

19 Feb '25

The last time I checked my mail.log I found the following line: 2025-02-18T22:41:31.175798-05:00 grace dovecot: imap-login: Login aborted: Connection closed (auth failed, 1 attempts in 8 secs) (auth_failed): user=<wizard(a)koalatyworks.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<wTMBiHYu5pXAqAEB> Is this a password error or something more? Ken

2 1

Doveadm Backup
by Doug Hardie 18 Feb '25

18 Feb '25

I tried the backup again tonight. I am now getting a new error: mail# doveadm backup -f -u doug remote:checkout dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Warning: Deleting mailbox 'INBOX': UID=92440 GUID=1465118975.V4eI7cfa32M232845.mail is missing locally dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Error: Couldn't delete mailbox INBOX: INBOX can't be deleted. dsync-local(doug)<N0q9NI0xtGf4vgAAZU03Dg>: Error: Remote command returned error 65: ssh checkout doveadm dsync-server -udoug -U Anytime I run it now generates the same error messages. However on the backup machine the .cur directory is empty. I presume that is the INBOX referred to in the messages. All the other directories appear to be intact. -- Doug

2 3

2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'
by Bjoern Franke 18 Feb '25

18 Feb '25

Hi, I have the following (manage)sieve-related parts in my 2.4.0 config: within the namespace inbox: mailbox Junk { auto = subscribe autoexpunge = 14d sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.sieve } special_use { "\Junk" = yes } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } sieve_script personal { active_path = /data/mail/%{user}/dovecot.sieve driver = file path = /data/mail/%{user}/sieve } Accessing via managesieve fails: Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' But the sieve rules in general work. Regards Bjoern

2 2

Re: Userdb lookup problems
by Ken Wright 18 Feb '25

18 Feb '25

On Mon, 2025-02-17 at 15:49 +0200, Timo Sirainen wrote: > On 16. Feb 2025, at 17.03, Ken Wright via dovecot > <dovecot(a)dovecot.org> wrote: > > mysql localhost { > > user = something > > password = MYPASSWORD > > dbname = something > > } > .. > > According to the logs, Dovecot isn't trying to connect using the > > user > > something, it's using the user dovecot. That's not the user for > > the > > database. > > The default mysql user is empty, not "dovecot". So it must be getting > "dovecot" user from somewhere in your config. Look at your "doveconf" > output - maybe the mysql_user gets overridden in some other config > file. Things to look at: > > doveconf mysql > doveconf | grep mysql > doveconf I went through every file in conf.d trying to find a mention of dovecot with no positive results. Then I tried the three things to look at you suggested, and got this: doveconf mysql: mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } doveconf | grep mysql: sql_driver = mysql mysql localhost { doveconf: # 2.4.0-2+ubuntu24.04 (daeb6bc59c): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0-2+ubuntu24.04 (1b2d5bb9) # OS: Linux 6.8.0-53-generic x86_64 Ubuntu 24.04.2 LTS ext4 # Hostname: localhost dovecot_config_version = 2.4.0 auth_mechanisms = auth_mechanisms { plain = yes login = yes } dovecot_storage_version = 2.4.0 mail_driver = maildir mail_gid = vmail mail_inbox_path = /var/vmail/%{user | domain}/%{user | username } mail_path = /var/vmail/%{user | domain }/%{user | username }/Maildir mail_uid = vmail mailbox_list_utf8 = yes passdb_default_password_scheme = ARGON2I protocols = protocols { imap = yes lmtp = yes sieve = yes } sql_driver = mysql ssl = required ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem prefer_ciphers = server } namespace inbox { mailbox Drafts { auto = create special_use = special_use { "\\Drafts" = yes } } mailbox Junk { auto = create special_use = special_use { "\\Junk" = yes } } mailbox Trash { auto = create special_use = special_use { "\\Trash" = yes } } mailbox Sent { auto = create special_use = special_use { "\\Sent" = yes } } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } passdb sql { query = SELECT username AS username, domain, password FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } userdb sql { iterate_query = SELECT username AS username, domain FROM mailbox query = SELECT mail_path, uid, gid FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } local 127.0.0.1 { local_name mailserver.example1.com { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem } } } local_name mail.example2.net { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mail.example2.net/fullchain.pem key_file = /etc/letsencrypt/live/mail.example2.net/privkey.pem } } } } I can't find anything indicating a database user 'dovecot.' Would you like to see the results of tail /var/log/mail.log? Ken On Mon, 2025-02-17 at 15:49 +0200, Timo Sirainen wrote: On 16. Feb 2025, at 17.03, Ken Wright via dovecot <dovecot(a)dovecot.org> wrote: mysql localhost { user = something password = MYPASSWORD dbname = something } .. According to the logs, Dovecot isn't trying to connect using the user something, it's using the user dovecot. That's not the user for the database. The default mysql user is empty, not "dovecot". So it must be getting "dovecot" user from somewhere in your config. Look at your "doveconf" output - maybe the mysql_user gets overridden in some other config file. Things to look at: doveconf mysql doveconf | grep mysql doveconf I went through every file in conf.d trying to find a mention of dovecot with no positive results. Then I tried the three things to look at you suggested, and got this: doveconf mysql: mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } doveconf | grep mysql: sql_driver = mysql mysql localhost { doveconf: # 2.4.0-2+ubuntu24.04 (daeb6bc59c): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0-2+ubuntu24.04 (1b2d5bb9) # OS: Linux 6.8.0-53-generic x86_64 Ubuntu 24.04.2 LTS ext4 # Hostname: localhost dovecot_config_version = 2.4.0 auth_mechanisms = auth_mechanisms { plain = yes login = yes } dovecot_storage_version = 2.4.0 mail_driver = maildir mail_gid = vmail mail_inbox_path = /var/vmail/%{user | domain}/%{user | username } mail_path = /var/vmail/%{user | domain }/%{user | username }/Maildir mail_uid = vmail mailbox_list_utf8 = yes passdb_default_password_scheme = ARGON2I protocols = protocols { imap = yes lmtp = yes sieve = yes } sql_driver = mysql ssl = required ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem prefer_ciphers = server } namespace inbox { mailbox Drafts { auto = create special_use = special_use { "\\Drafts" = yes } } mailbox Junk { auto = create special_use = special_use { "\\Junk" = yes } } mailbox Trash { auto = create special_use = special_use { "\\Trash" = yes } } mailbox Sent { auto = create special_use = special_use { "\\Sent" = yes } } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } } mysql localhost { dbname = database password = # hidden, use -P to show it user = DBuser } passdb sql { query = SELECT username AS username, domain, password FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } userdb sql { iterate_query = SELECT username AS username, domain FROM mailbox query = SELECT mail_path, uid, gid FROM mailbox WHERE username = '%{user | username}' AND domain = '%{user | domain}' AND active= '1' } local 127.0.0.1 { local_name mailserver.example1.com { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mailserver.example1.com/fullchain.pem key_file = /etc/letsencrypt/live/mailserver.example1.com/privkey.pem } } } local_name mail.example2.net { protocol imap { ssl_server { cert_file = /etc/letsencrypt/live/mail.example2.net/fullchain.pem key_file = /etc/letsencrypt/live/mail.example2.net/privkey.pem } } } } I can't find anything indicating a database user 'dovecot.' Would you like to see the results of tail /var/log/mail.log? Ken

1 0

Doveadm Backup
by Doug Hardie 18 Feb '25

18 Feb '25

I am using doveadm backup to backup the mail server's files for a specific user. This is a test environment for the backup machine. All it does is sit there until I run backup on the mail server. However, I am encountering an issue occasionally where backup throws the following message: Warning: Deleting mailbox 'Deleted Messages': UID=533920 already exists locally for a different mail: GUIDs don't match (1739791386.M526904P56414.checkout,S=2206,W=2264 vs 1739674845.M569094P6598.mail,S=6530202,W=6615064) At this point it stops and the indicated mailbox has been deleted. It is not always the same mailbox. I then have to run the backup again and wait for it to download the entire directory which takes a long time. I was hoping to use this approach for a frequently run backup, but it appears it is not feasible. Some mailboxes are large enough that a second backup would be initiated before the complete reload had completed. Can this be corrected? -- Doug

1 0

Question about push notification plugin
by Zakaria 17 Feb '25

17 Feb '25

Hi Dovecot Mailing List members, I just struggled to understand the plugin events and wondered if anyone can help on this. I wanted to capture the event when I mark message as not spam move event as well as when I move message to new folder event, I found MessageNew and MessageAppend, and couldnt figure out which one is responsible of the relevant event? Also, feedback to the dovecot dev team, it would great if we have push notification redis driver. Thanks in advance. Zakaria.

2 2

Re: Doveadm Backup Error
by Asai 17 Feb '25

17 Feb '25

Thank you, Timo, that fixed the problem. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: > On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: >> >> sieve_script personal { >> active_path = /vmail/%{user | domain }/%{user | username >> }/home/.dovecot.sieve >> driver = file >> path = /vmail/%{user | domain }/%{user | username }/home/sieve >> } > > Looks like %variables aren't really working right with Sieve / doveadm > combination. It gives an error: > > Error: sieve: sieve_file_storage settings: Failed to parse > configuration: Failed to expand sieve_script_path setting variables: > Unknown variable 'user' > > So for now the only way is to avoid %variables there - that simplifies > the config anyway: > > sieve_script personal { > active_path = ~/.dovecot.sieve > path = ~/sieve > } > Thank you, Timo, that fixed the problem. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: sieve_script personal { active_path = /vmail/%{user | domain }/%{user | username }/ home/.dovecot.sieve driver = file path = /vmail/%{user | domain }/%{user | username }/home/sieve } Looks like %variables aren't really working right with Sieve / doveadm combination. It gives an error: Error: sieve: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' So for now the only way is to avoid %variables there - that simplifies the config anyway: sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve }

1 0

Re: Doveadm Backup Error
by Asai 17 Feb '25

17 Feb '25

Thanks Timo, OK, I'll give that a try, I should point out that the Sieve filters are working as they should be for general delivery, outside of doveadm backup. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: > On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: >> >> sieve_script personal { >> active_path = /vmail/%{user | domain }/%{user | username >> }/home/.dovecot.sieve >> driver = file >> path = /vmail/%{user | domain }/%{user | username }/home/sieve >> } > > Looks like %variables aren't really working right with Sieve / doveadm > combination. It gives an error: > > Error: sieve: sieve_file_storage settings: Failed to parse > configuration: Failed to expand sieve_script_path setting variables: > Unknown variable 'user' > > So for now the only way is to avoid %variables there - that simplifies > the config anyway: > > sieve_script personal { > active_path = ~/.dovecot.sieve > path = ~/sieve > } > Thanks Timo, OK, I'll give that a try, I should point out that the Sieve filters are working as they should be for general delivery, outside of doveadm backup. Asai On 2/17/2025 9:03 AM, Timo Sirainen wrote: On 17. Feb 2025, at 16.26, Asai via dovecot <dovecot(a)dovecot.org> wrote: sieve_script personal { active_path = /vmail/%{user | domain }/%{user | username }/ home/.dovecot.sieve driver = file path = /vmail/%{user | domain }/%{user | username }/home/sieve } Looks like %variables aren't really working right with Sieve / doveadm combination. It gives an error: Error: sieve: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' So for now the only way is to avoid %variables there - that simplifies the config anyway: sieve_script personal { active_path = ~/.dovecot.sieve path = ~/sieve }

1 0

FTS Xapian 1.9.1 released - Compatibility with git and 2.4
by Joan Moreau 17 Feb '25

17 Feb '25

Hi Finally released 1.9.1 to catch-up with 2.4.x and git recent changes Same "simplistic" approach - You get what you search for, no approximation/elastic/stemming, any language - No config required by default - Drastically reduced storage required / Drastically improved indexing/searching speed - Works on small servers or big servers https://github.com/grosjo/fts-xapian/ Thank you Aki Tuomi to help me pass this over the line Enjoy JM Hi Finally released 1.9.1 to catch-up with 2.4.x and git recent changes Same "simplistic" approach - You get what you search for, no approximation/elastic/stemming, any language - No config required by default - Drastically reduced storage required / Drastically improved indexing/ searching speed - Works on small servers or big servers https://github.com/grosjo/fts-xapian/ Thank you Aki Tuomi to help me pass this over the line Enjoy JM

2 1

Doveadm Backup Error
by Asai 17 Feb '25

17 Feb '25

Greetings, On 2.3 I was able to run the following command, but now on 2.4 I'm getting the following error: doveadm backup -u user(a)domain.tld maildir:/mnt/backups/daily/domain.tld/user dsync(user(a)domain.tld): Error: brain M: Exporting mailbox INBOX failed: Mailbox attribute iteration failed: Mailbox attributes not enabled So, I tried to set the configs to include: protocol imap { imap_metadata = yes ... } mail_attribute { dict file { path = %{home}/dovecot-attributes } } But then I get: Error: brain M: Exporting mailbox INBOX failed: Mailbox attribute iteration failed: BUG: Unknown internal error Can anyone clarify the proper configs for this? Thank you, Asai

3 5

Dovecot 2.4 - Example config
by Joan Moreau 17 Feb '25

17 Feb '25

Hi For those struggling with the new config, here an example I am using (Xapian, Sieve, mdbox, LMTP, ...) --- dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 base_dir = /run/dovecot state_dir = /var/lib/dovecot default_login_user = dovecot listen = * :: verbose_proctitle = yes mail_gid = mail mail_uid = mailusers mail_driver = mdbox mail_path = /data/mails/%{user | domain }/%{user | username } mail_home = /data/mails/%{user | domain }/%{user | username } mail_plugins = fts fts_xapian # mail_debug = yes # mail_cache_max_size = 128M ssl_server_cert_file = /etc/letsencrypt/live/gjnet/fullchain.pem ssl_server_key_file = /etc/letsencrypt/live/gjnet/privkey.pem ssl_server_dh_file = /etc/mail/dovecot/dh.pem mdbox_rotate_size = 64M default_vsz_limit = unlimited sendmail_path = /usr/sbin/sendmail sql_driver = mysql mysql localhost { user = services password = MYPASSWORD dbname = services } fts xapian { } fts_autoindex = yes fts_decoder_driver = script fts_decoder_script_socket_path = decode2text sieve_script default { type = default driver = file path = /data/mails/sieve/default.sieve } sieve_script before { type = before driver = file path = /data/mails/sieve/after.sieve } sieve_script after { type = after driver = file path = /data/mails/sieve/after.sieve } sieve_script personal { type = personal driver = file path = /data/mails/%{user | domain }/%{user | username }/sieve/ active_path = /data/mails/%{user | domain }/%{user | username }/sieve/default.sieve } sieve_script global { type = global driver = file path = /data/mails/sieve/ } namespace inbox { inbox = yes mailbox Trash { auto = subscribe special_use = \Trash fts_autoindex = no } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } } userdb sql { query = SELECT 1 from users where user like '%{user | username}' and domain like '%{user | domain}' and active=1 iterate_query = SELECT user AS username, domain FROM users where active=1 } passdb sql { query = SELECT concat(user, '@', domain) AS user, password from users where user like '%{user | username}' and domain like '%{user | domain}' and active=1 } service auth { unix_listener auth-userdb { mode = 0600 user = mailusers } } protocols = imap pop3 sieve lmtp service imap-login { chroot = login process_min_avail = 8 restart_request_count = unlimited } service indexer-worker { vsz_limit = 4G } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep imap_max_line_length = 655360 mail_max_userip_connections = 256 } service pop3-login { chroot = login } protocol pop3 { mail_max_userip_connections = 256 pop3_enable_last = yes pop3_lock_session = no pop3_reuse_xuidl = yes } service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 24 } unix_listener lmtp { mode = 0666 } process_min_avail = 8 } service managesieve-login { chroot = login inet_listener sieve { port = 4190 } inet_listener sieveold { port = 2000 } } protocol sieve { managesieve_implementation_string = dovecot mail_max_userip_connections = 256 managesieve_max_line_length = 65536 } protocol lmtp { mail_plugins { fts = yes fts_xapian = yes sieve = yes } } protocol lda { auth_socket_path = /run/dovecot/auth-userdb hostname = mx.grosjo.net mail_plugins = $mail_plugins sieve postmaster_address = admin(a)grosjo.net lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins { fts = yes fts_xapian = yes sieve = yes } } service stats { unix_listener stats-writer { mode = 0660 user = mailusers } } service decode2text { executable = script /usr/libexec/dovecot/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } }

1 0

Registering module in 2.4
by Joan Moreau 16 Feb '25

16 Feb '25

Hi I am trying to adjust the Xapian plugin to the very recent massive changes. https://github.com/grosjo/fts-xapian I implemented the changes about the settings However, I get to : Feb 16 13:39:44 gjserver dovecot[2211311]: imap(xxx)<2211361><W21YikIuomA2rj7G>: Error: fts: Failed to initialize backend 'xapian': Unknown backend Has the module registration changed as well ? Thank you so much

1 4