- dovecot - dovecot.org

Panic with FTS_BACKEND_FLAG_TOKENIZED_INPUT and virtual mailboxes: file index-search-result.c: line 132
by markus-dovecot＠doits.de 30 May '25

30 May '25

Originally posted and debugged here: https://github.com/slusarz/dovecot-fts-flatcurve/issues/66 I have to following panic with fts flatcurve enabled: ``` Panic: file index-search-result.c: line 132 (index_search_result_update_flags): assertion failed: (result->search_args->args == &search_arg) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x46) [0x74e9890a2846] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x74e9890a2962] -> /usr/lib/dovecot/libdovecot.so.0(+0x10d81b) [0x74e9890af81b] -> /usr/lib/dovecot/libdovecot.so.0(+0x10d8b7) [0x74e9890af8b7] -> /usr/lib/dovecot/libdovecot.so.0(+0x5e2e2) [0x74e9890002e2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x518a4) [0x74e9891d38a4] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x274e) [0x74e988bf8a9e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x5c) [0x74e9891eff9c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x39) [0x74e9891f0039] -> dovecot/imap(cmd_select_full+0x1df) [0x62354bd8326f] -> dovecot/imap(command_exec+0xa4) [0x62354bd8b444] -> dovecot/imap(+0x22392) [0x62354bd89392] -> dovecot/imap(+0x22444) [0x62354bd89444] -> dovecot/imap(client_handle_input+0x1bd) [0x62354bd8989d] -> dovecot/imap(client_input+0x74) [0x62354bd89e64] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x74e9890c603d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13a) [0x74e9890c77aa] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x74e9890c60e4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x74e9890c62a0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x74e989036ad7] -> dovecot/imap(main+0x570) [0x62354bd7ad20] -> /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x74e988c29d90] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x74e988c29e40] -> dovecot/imap(_start+0x25) [0x62354bd7ade5] ``` It happens when accessing virtual folder with filters like this: ``` something-*/excep-dev* header x-abc-exception "1" ``` The error happens on subsequent access of the folder: - Removing dovecot.index{,.log} files allows to access the virtual folder again - dovecot.index gets recreated on access and the folder can be accessed multiple times - Marking an e-mail read triggers the error, though! Now each next access raises the error - Removing dovecot.index{,.log} restores access again and the e-mails are still marked as read (so this information is not lost), until the next e-mail is marked as read: then the folder cannot be accessed again Slusarz debugged the backtrace and wrote a detailed description at https://github.com/slusarz/dovecot-fts-flatcurve/issues/66#issuecomment-229… which I'll quote here: > This is not a flatcurve bug - it is a bug within Dovecot's indexing/fts handling. > > (Detailed debug below, so that core team can understand the problem.) > > As discussed above, this bug is triggered with virtual mailboxes on subsequent accesses. The initial access will work fine; the assert crash only happens when the Dovecot lib-storage index code reads the indexes created for the virtual mailboxes. > > `index_search_result_update_appends()` in lib-storage/index/index-search-result.c > > * Inside this function, a "temporary search parameter to limit the search only to the new messages" is added to the mail search args. Later, it is checked that the mail_search args points to this same search parameter after the search is executed. It is this assert check that is failing, because the mail args is changing during the course of the search. > > * `i_assert(result->search_args->args == &search_arg);` > > > The search args are being altered in plugins/fts/fts-search.args.c, `fts_search_args_expand()`. Specifically, in that function, either `fts_search_args_expand_language_top_level()` or `fts_search_args_expand_tree()` is being called, which can replace the current args parameter with a new pointer. > > `fts_search_args_expand()` is being called in plugins//fts/fts-search.c by `fts_search_try_lookup()` when the FTS backend has the FTS_BACKEND_FLAG_TOKENIZED_INPUT flag set. Flatcurve has this flag set. > > This flag is defined in plugins/fts/fts-api-private.h. Comments say: > > ``` > /* Tokenize all the input. update_build_more() will be called a single > directly indexable token at a time. Searching will modify the search > args so that lookup() sees only tokens that can be directly > searched. */ > ``` > > Thus, the comments explicitly say the search args will be modified if this flag is set. This modification is incompatible with the assert check in `index_search_result_update_appends()`, which requires that the search args not be modified. > > The core team will have to determine whether this behavior is correct, or if the assert check is invalid. You can find some more discussion at https://github.com/slusarz/dovecot-fts-flatcurve/issues/66, but I think the most important part (the very detailed analysis from Slusarz, thanks again!) might be enough to understand and maybe fix the problem. Relevant information about the mail system: ``` # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.5.0-45-generic x86_64 Ubuntu 22.04.4 LTS [...] namespace { location = virtual:~/virtual:LAYOUT=maildir++ prefix = _/ separator = / } [...] plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared fts = flatcurve fts_autoindex = yes fts_filters = normalizer-icu snowball stopwords fts_filters_en = lowercase snowball stopwords fts_languages = de en fts_tokenizer_email_address = maxlen=100 fts_tokenizer_generic = algorithm=simple maxlen=30 fts_tokenizers = generic email-address sieve = file:~/sieve;active=~/.dovecot.sieve } [...] ``` I can provide more information if you need. Thanks for looking into it!

2 2

RE: dragging files into mail folders
by Marc 30 May '25

30 May '25

If I drag files in imap folders in outlook they will show up in eg roundcube/thunderbird as winmail.dat. So I guess this is just a microsoft thing. Would be nice if there were plugins that would add functionality that unwrapped these winmail.dat files. > > > If i Understood correctly you are looking for a software like > > roundcube or something right ?. > > Not necessarily, but would be a good start. Question is if the imap > allows to store these files directly. > > > > that offers ajax based GUI that allows > > you to drap and drop mails into folders. > > Files not mails. .jpg, .odt, .txt etc > > > > > > > > With exchange and outlook I was always used to sometimes drag files > > into mail folders. Is something like this available for imap? Or maybe > a > > dovecot extension? > > > > > > (obviously I am not looking for a solution to store them as > > attachments to mails) > > > _______________________________________________ > > > dovecot mailing list -- dovecot(a)dovecot.org > > > To unsubscribe send an email to dovecot-leave(a)dovecot.org

2 2

dragging files into mail folders
by Marc 28 May '25

28 May '25

With exchange and outlook I was always used to sometimes drag files into mail folders. Is something like this available for imap? Or maybe a dovecot extension? (obviously I am not looking for a solution to store them as attachments to mails)

1 0

Re: NAMESPACE empty when logging via haproxy but populated properly when logging directly
by dk+lists.dovecot.org＠7ns.eu 27 May '25

27 May '25

On 2025-05-22 17:41, dk+lists.dovecot.org(a)7ns.eu wrote: > > On 2025-05-22 16:55, Aki Tuomi via dovecot wrote: >>> >>> I see you a local 10.20.20.20 statement there, which changes how the >>> inbox prefix behaves, and I'm guessing (?) you are testing from >>> 10.20.20.20 as it's local, not remote. >>> >>> Which would explain why. >> >> Also to add a bit that the "local_ip" (not real_local_ip) gets updated >> with haproxy proxy protocol (when enabled), so it will remote >> haproxy's local IP. >> >> Aki >> > Wow. Thank you. It works. I mangled a IPs little bit before I send them > to mailist. All machines are in the same network. Client, Proxy, Server. > All in the same subnet. This is first time I see such problem with > server software and reverse proxy. Never seen similar problem. What > exactly this "local" statement do? Mail client is in the same network as > server, so after PROXY header is stripped, my mail client IP should be > seen by dovecot exactly the same, so shouldn't dovecot treat those > connections equally? oO > > Thank you again for tip Aki. > DK Hmm, now I am struggling with "local_name" filtering in haproxy environment. According to dovecot docs [1] it could potentially work with "send-proxy-v2-ssl" configured on proxy backend. However my dovecot filter does not work. Have the same problem I had with "local" filter. Dovecot does not recognize this connection and does not filter config for it properly. I tried "send-proxy-v2-ssl-cn". Still the same. I even enabled ssl on dovecot globally with "ssl=required" to be sure dovecot does not disable some ssl logic when "ssl=no". Still no go. Seems like dovecot does not get or use TLS/SNI info from haproxy. Does it even work in such environment? Is it supported? Or is this a bug or maybe my error? Any clues please? DK [1] https://doc.dovecot.org/2.4.1/core/config/haproxy.html#tls-forwarding

4 10

Sieve vnd.dovecot.config extension does not work when mail is delivered to lmtp inet_listener but works when delivered to lmtp unix_listener
by DK 27 May '25

27 May '25

Hello. I have a strange problem with sieve scripts vnd.dovecot.config extension processing on newest dovecot 2.3 and 2.4. When I deliver mail via lmtp unix_listener sieve script can get sieve_env_* variable with no problem. However when I deliver mail via lmtp inet_listener sieve script can not get the same sieve_env_* variable. I deliver mails from postfix to lmtp inet_listener directly (not via haproxy). The same postfix is used when testing lmtp unix_listener mail delivery which works. Any clues what could be the cause of such problem? DK

1 2

Thunderbird and Dovecot 2.4.0 Incompatibility
by Amit Chaudhari 27 May '25

27 May '25

I'm trying to setup a dovecot 2.4.0 imap server and have it work with Thunderbird. I'm able to connect/auth fine, however trying to save a message to a mailbox causes the connection to close. ``` Info: Disconnected: Too many invalid IMAP commands. in=744 out=2559 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 ``` It appears thunderbird's imap APPEND command is using syntax which dovecot doesn't like? I enabled raw logs and pasted them below: Downgrading to 2.3 resolves the issue, so it’s either a regression, or some config issue I’m not able to pinpoint. ``` 1738942430.025029 5 ID ("name" "Thunderbird" "version" "128.7.0") 1738942430.029320 6 ENABLE UTF8=ACCEPT 1738942430.033907 7 select "Drafts" 1738942430.039796 8 append "Drafts" (\Draft) UTF8 (~{726+} 1738942430.039796 Message-ID: <ea714f62-7186-4bcb-b709-007e39c6a9d6(a)example.com <mailto:ea714f62-7186-4bcb-b709-007e39c6a9d6@example.com>> 1738942430.039796 Date: Fri, 7 Feb 2025 10:33:49 -0500 1738942430.039796 MIME-Version: 1.0 1738942430.039796 User-Agent: Mozilla Thunderbird 1738942430.039796 Content-Language: en-US 1738942430.039796 To: sender(a)example.com <mailto:sender@example.com> 1738942430.039796 From: User Name <user(a)example.com <mailto:user@example.com>> 1738942430.039796 Subject: test 1738942430.039796 X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0; 1738942430.039796 attachmentreminder=0; deliveryformat=0 1738942430.039796 X-Identity-Key: id2 1738942430.039796 Fcc: imap://user%40example.com@192.168.115.203/Sent 1738942430.039796 Content-Type: text/html; charset=UTF-8 1738942430.039796 Content-Transfer-Encoding: 7bit 1738942430.039796 1738942430.039796 <!DOCTYPE html> 1738942430.039796 <html> 1738942430.039796 <head> 1738942430.039796 1738942430.039796 <meta http-equiv="content-type" content="text/html; charset=UTF-8"> 1738942430.039796 </head> 1738942430.039796 <body> 1738942430.039796 <p><br> 1738942430.039796 </p> 1738942430.039796 </body> 1738942430.039796 </html> 1738942430.039796 ) ``` ``` 1738942430.025188 * ID ("name" "Dovecot") 1738942430.025234 5 OK ID completed (0.001 + 0.000 secs). 1738942430.029390 * ENABLED UTF8=ACCEPT 1738942430.029418 6 OK Enabled (0.001 + 0.000 secs). 1738942430.035478 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) 1738942430.035531 * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. 1738942430.035559 * 0 EXISTS 1738942430.035585 * 0 RECENT 1738942430.035611 * OK [UIDVALIDITY 1738898190] UIDs valid 1738942430.035638 * OK [UIDNEXT 1] Predicted next UID 1738942430.035693 7 OK [READ-WRITE] Select completed (0.002 + 0.000 + 0.001 secs). 1738942430.040007 8 BAD Error in IMAP command APPEND: Missing ')' (0.001 + 0.000 secs). 1738942430.040140 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040172 Date: BAD Error in IMAP command FRI,: Unknown command (0.001 + 0.000 secs). 1738942430.040233 MIME-Version: BAD Error in IMAP command 1.0: Unknown command (0.001 + 0.000 secs). 1738942430.040291 User-Agent: BAD Error in IMAP command MOZILLA: Unknown command (0.001 + 0.000 secs). 1738942430.040356 Content-Language: BAD Error in IMAP command EN-US: Unknown command (0.001 + 0.000 secs). 1738942430.040409 To: BAD Error in IMAP command sender(a)example.com <mailto:sender@example.com>: Unknown command (0.001 + 0.000 secs). 1738942430.040467 From: BAD Error in IMAP command USER: Unknown command (0.001 + 0.000 secs). 1738942430.040521 Subject: BAD Error in IMAP command TEST: Unknown command (0.001 + 0.000 secs). 1738942430.040574 X-Mozilla-Draft-Info: BAD Error in IMAP command INTERNAL/DRAFT;: Unknown command (0.001 + 0.000 secs). 1738942430.040638 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040666 X-Identity-Key: BAD Error in IMAP command ID2: Unknown command (0.001 + 0.000 secs). 1738942430.040720 Fcc: BAD Error in IMAP command: Invalid command name (0.001 + 0.000 secs). 1738942430.040746 Content-Type: BAD Error in IMAP command TEXT/HTML;: Unknown command (0.001 + 0.000 secs). 1738942430.040802 Content-Transfer-Encoding: BAD Error in IMAP command 7BIT: Unknown command (0.001 + 0.000 secs). 1738942430.040862 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.040889 <!DOCTYPE BAD Error in IMAP command HTML>: Unknown command (0.001 + 0.000 secs). 1738942430.040966 <html> BAD Error in IMAP command: Invalid command name (0.001 + 0.000 secs). 1738942430.040991 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.041015 * BAD Error in IMAP tag: Invalid tag (0.001 + 0.000 secs). 1738942430.041032 * BYE Too many invalid IMAP commands. ```

5 7

Dovecot and pigeonhole/sieve without ldap
by ppn＠parhuet.fr 26 May '25

26 May '25

Hi, First of all, thanks for your work on this software overall. Since 2.4 dovecot/pigeonhole (2.4.1 gentoo here), it fails to build without ldap support. I've seen nothing that justifies this requirement so it seems like a bug/issue? Configure for dovecot : ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-dependency-tracking --disable-silent-rules --disable-static --docdir=/usr/share/doc/dovecot-2.4.1-r1 --htmldir=/usr/share/doc/dovecot-2.4.1-r1/html --with-sysroot=/ --libdir=/usr/lib64 --with-rundir=/run/dovecot --with-statedir=/var/lib/dovecot --with-moduledir=/usr/lib64/dovecot --disable-hardening --disable-rpath --with-bzlib --without-libbsd --with-libcap --with-icu --enable-experimental-mail-utf8 --without-sodium --without-cdb --without-gssapi --without-lua --without-ldap --without-flatcurve --without-lz4 --without-mysql --with-pam --without-pgsql --without-sqlite --without-solr --without-stemmer --without-systemd --without-textcat --without-libunwind --without-zstd --disable-static userdbs ........ : static prefetch passwd passwd-file : -ldap -sql Configure for pigeonhole : ./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --datarootdir=/usr/share --disable-dependency-tracking --disable-silent-rules --disable-static --docdir=/usr/share/doc/dovecot-2.4.1-r1 --htmldir=/usr/share/doc/dovecot-2.4.1-r1/html --with-sysroot=/ --libdir=/usr/lib64 --disable-static --localstatedir=/var --enable-shared --disable-hardening --with-dovecot=/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4 --without-ldap --without-managesieve script drivers . : file dict : -ldap Error : age/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-sasl -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/li b-dcrypt -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-program-client -I/var/tmp/portage/net-mail/dovecot-2. 4.1-r1/work/dovecot-2.4.1-4/src/lib-oauth2 -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-var-expand -I/var/t mp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-index -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1- 4/src/lib-storage -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-storage/list -I/var/tmp/portage/net-mail/dov ecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-storage/index -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-stora ge/index/raw -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-imap-storage -I/var/tmp/portage/net-mail/dovecot- 2.4.1-r1/work/dovecot-2.4.1-4/src/plugins/quota -I/var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-ldap -I../../. ./.. -I../../../../src/lib-sieve -O2 -pipe -frecord-gcc-switches -flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -fa synchronous-unwind-tables -c sieve-ldap-storage.c -fPIC -DPIC -o .libs/sieve-ldap-storage.o In file included from sieve-ldap-storage.c:6: /var/tmp/portage/net-mail/dovecot-2.4.1-r1/work/dovecot-2.4.1-4/src/lib-ldap/ldap-utils.h:4:10: fatal error: ldap.h: No such file or dir ectory 4 | #include <ldap.h> | ^~~~~~~~ compilation terminated. make[5]: *** [Makefile:607: sieve-ldap-storage.lo] Error 1 Regards, NicoP

3 12

lmtp user verification
by Christian H. Kuhn 26 May '25

26 May '25

Hi, after a new install and avoiding a lot of simple faults, i try to run my system postfix as smtpd, smtpds, and submission, and dovecot as imap and lmtp server. I can login to imap, and i can send via 587 with sasl authentification. So i think that most things are ok :-) What does NOT work is the local transport to my maildir. christian.kuhn(a)qno.de is not resolved to qno(a)qno.de but to qno(a)bywater.qno.de, and lmtp rejects that unverified user: 2025-05-25T18:13:25.431342+02:00 bywater postfix/smtpd[987726]: NOQUEUE: reject: RCPT from mail-lj1-f176.google.com[209.85.208.176]: 450 4.1.1 <qno(a)bywater.qno.de>: Recipient address rejected: unverified address: host bywater.qno.de[private/dovecot-lmtp] said: 550 5.1.1 <qno(a)bywater.qno.de> User doesn't exist: qno(a)bywater.qno.de (in reply to RCPT TO command) also mails to qno-anyextension(a)qno.de are rejected. I set recipient_delimiter to -, but it seems to be ignored by lmtp: 2025-05-25T15:24:10.147369+02:00 bywater postfix/smtpd[985952]: NOQUEUE: reject: RCPT from higher.littydate.com[104.244.79.41]: 450 4.1.1 <qno-planets(a)qno.de>: Recipient address rejected: unverified address: host bywater.qno.de[private/dovecot-lmtp] said: 550 5.1.1 <qno-planets(a)qno.de> User doesn't exist: qno-planets(a)qno.de (in reply to RCPT TO command); from=<webmaster(a)littydate.com> to=<qno-planets(a)qno.de> proto=ESMTP helo=<higher.littydate.com> postconf -n: (postfix 3.8.6) broken_sasl_auth_clients = yes compatibility_level = 3.6 content_filter = amavis:[127.0.0.1]:10024 default_database_type = cdb indexed = ${default_database_type}:${tabledir} inet_interfaces = 127.0.0.1, 65.21.136.15, [::1], [2a01:4f9:3b:25b0:9:6:1:e01] local_recipient_maps = mailbox_transport = lmtp:unix:private/dovecot-lmtp mydestination = $myhostname mydomain = qno.de myhostname = bywater.qno.de mynetworks = 127.0.0.0/8 65.21.136.15/32 [::1]/128 [2a01:4f9:3b:25b0:9:6:1:e01]/128 [2a01:4f8:171:b85:9:6:1:e01]/128 136.243.102.134/32 myorigin = $mydomain policyd-spf_time_limit = 3600 postscreen_access_list = permit_mynetworks postscreen_bare_newline_action = enforce postscreen_bare_newline_enable = no postscreen_dnsbl_action = enforce postscreen_dnsbl_reply_map = ${indexed}dnsbl_reply postscreen_dnsbl_sites = zusbyxqsairu6mu6ayyhstc3ua.zen.dq.spamhaus.net postscreen_dnsbl_threshold = 1 postscreen_non_smtp_command_action = enforce postscreen_non_smtp_command_enable = no postscreen_pipelining_action = enforce postscreen_pipelining_enable = no receive_override_options = no_address_mappings recipient_delimiter = - smtp_bind_address = 65.21.136.15 smtp_bind_address6 = 2a01:4f9:3b:25b0:9:6:1:e01 smtp_generic_maps = ${indexed}generic smtp_tls_exclude_ciphers = aNULL smtp_tls_loglevel = 1 smtp_tls_mandatory_ciphers = medium smtp_tls_mandatory_exclude_ciphers = RC4, MD5, SHA1 smtp_tls_security_level = may smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_required = yes smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unverified_recipient, check_policy_service unix:private/policyd-spf, reject_rbl_client zusbyxqsairu6mu6ayyhstc3ua.zen.dq.spamhaus.net, reject_rhsbl_reverse_client zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net, reject_rhsbl_helo zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net, reject_rhsbl_sender zusbyxqsairu6mu6ayyhstc3ua.dbl.dq.spamhaus.net smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_tls_security_options = $smtpd_sasl_security_options smtpd_sasl_type = dovecot smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_tls_auth_only = yes smtpd_tls_eccert_file = /etc/letsencrypt/live/mail.qno.de/fullchain.pem smtpd_tls_eckey_file = /etc/letsencrypt/live/mail.qno.de/privkey.pem smtpd_tls_mandatory_ciphers = high smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5, SHA1 smtpd_tls_mandatory_protocols = >=TLSv1.2 smtpd_tls_received_header = yes smtpd_tls_security_level = may tabledir = ${config_directory}/tables.d/ virtual_alias_domains = $mydomain virtual_alias_maps = ${indexed}virtual virtual_gid_maps = static:5000 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = sk-koenig-tegel.de virtual_mailbox_maps = mysql:${tabledir}virtual_mailbox_maps.cf virtual_minimum_uid = 10000 virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_uid_maps = static:5000 doveconf -n: # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 6.8.0-60-generic x86_64 Ubuntu 24.04.2 LTS # Hostname: bywater.qno.de auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = yes listen = 65.21.136.15, 2a01:4f9:3b:25b0:9:6:1:c01 mail_debug = yes mail_location = maildir:~/Maildir mail_privileged_group = mail 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 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 } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/letsencrypt/live/imap2.qno.de/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-CHACHA20-POLY1305 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes verbose_ssl = yes TIA QNo

2 3

Two instances on one machine — can they share indexes?
by dove＠redir.desz.cz 24 May '25

24 May '25

Hello, I (think I) need to run two instances of Dovecot on one machine (rationale below, if someone's interested). They access the same mail share (NFS, maildir), but the indexes are kept on local storage. One of them would also provide lmtp service to local MTA. For now I set the instances to keep indexes separate, in different directories, but I wonder, if they can share the indexes, to avoid unnecessary duplication? Of course, mmap_disable = yes, but would locking suffice? The platform is Linux (Devuan chimaera ATM, equivalet of Debian 11), filesystem - ext4, Dovecot version 2.3.13 (from distribution packages). Why? I have to provide different authentication methods to external IMAP clients and locally-running webmail; at first I hoped to make it via remote filter, but docs state that “auth settings currently only support the protocol filter”, so I had to come with some other idea. It _is_ possible that users would be logged in both via external mail client and webmail at the same time – and even if not, there's also lmtp, that can run at any moment. Sincerely, Bartosz Stępień

1 0

Guidance re doveadm sync full (-f) and stateful (-s)
by Georgios Kontaxis 24 May '25

24 May '25

Hi, I’m looking for guidance on how to use doveadm sync with flags -f (full synchronization) and -s. (stateful synchronization) After reading the doveadm-sync man page it seems one should do the following: (omitting -u -l -N flags for clarity) 1. First sync: doveadm sync -f 2. Second sync: doveadm sync -s “" > state 3. Subsequent infrequent syncs: doveadm sync -f 4. Subsequent frequent syncs: doveadm sync -s “$(<state)” > state (I’m assuming that before the first sync replica A has all the mailboxes and replica B has no mailboxes. I’m also assuming that the above commands are executed from replica A. The goal is to do master/master sync continuously.) Can you help me answer the following questions? a. Each time we execute (4) stateful sync after (3) full sync, is it correct to include previous state? b. What happens if we do: doveadm sync -f -s “” or doveadm sync -f -s “$(<state)” I think the replicator code does (b) in https://github.com/dovecot/core/blob/47349e24828be3ec7f591570e02c0b15ae26c6… and I’m not sure why. Overall, it would be good to have more examples in the man page demonstrating the various synchronization modes. Thanks, Georgios

1 0