February 2025 - dovecot

Dovecot 2.4 quota_storage_size override from userdb not working
by Andreas Oster 06 Feb '25

06 Feb '25

Hello, I am currently trying to migrate my Dovecot 2.3 server to version 2.4. Unfortunately I do not seem to get the basic per user quota to work. I am using LDAP for userdb and have used the "Override: LDAP" example from https://doc.dovecot.org/2.4.0/core/plugins/quota.html as a starting point. ( By the way, there is an error in the example: % is missing in front of "{ldap:quotaBytes}B" ) I have set the LDAP field according to my setup and validated with "doveadm auth test username" that the correct value is returned. In my case I get "quota_storage_size=3G" but this does not override the default value of 1G from the global quota config file: quota "User quota" { storage_size = 1G } Can someone please help with this issue ? Thank you very much. -- Best regards Andreas Oster

1 0

question from a newbie
by Zane B Stein 06 Feb '25

06 Feb '25

My mail was hosted by a site that no longer handles email. I asked them if they could send me a file with all my emails in it and they said sure. I was thinking maybe I would get something I could import into Outlook such as a .pst or .ost file, or perhaps a .csv file. What I received was a zipped file and when I opened it there were a bunch of folders with emails in them in some strange format (each one with a . in front of it, such as .NEWMAIL ), plus a bunch of files along with the folders such as dovecat.index, dovecatindex.cache, dovecot.index.log2, dovecot.list.inex, divecot.mailbox and others with a dovecot prefix, plus one called maildirsize and one called subscriptions. I have no idea how to read the emails in this format. Can someone tell me how I can access the emails in this set of files? Feel free to ask if you need more information before you can answer. If I need a special program to read the files, is there an easy one available that is user friendly for someone with no experience with dovecot files? Thank you. Zane B Stein

5 7

solved my problem
by Zane B Stein 06 Feb '25

06 Feb '25

In my initial post I questioned, as a newbie, how to access the email files I was given that were in dovecot format, and a few people were kind enough to explain things to me a bit. But some of the solutions were a bit over my head. And then I found a solution. I downloaded an app called "SysTools Maildir Converter" and was able to convert the whole email file into a .pst file, and input it in Outlook. Now all my emails are accessible, and I can reply to them like any other emails in Outlook. The only thing I don't exactly understand is that each folder I had with emails in it has a subfolder called "cur" and that is where all the emails reside. It is not an issue, just not sure exactly why that is so. (If someone has an idea why the emails are in "cur" subfolders rather than directly in the folders, and can explain it to me without getting super technical, that would be great. But it isn't a big deal, I'm just curious.) Zane

2 1

Replicator Crash
by Kent Borg 05 Feb '25

05 Feb '25

I have replicator working well enough…to crash: > Jan 28 11:26:12 la dovecot[1187]: replicator: Panic: data stack: Out > of memory when allocating 268435496 bytes > Jan 28 11:26:12 la dovecot[1187]: replicator: Error: Raw backtrace: #0 > t_askpass[0x7fa59db0c0] -> #1 backtrace_append[0x7fa59db374] -> #2 > backtra\ > ce_get[0x7fa59db510] -> #3 execvp_const[0x7fa59e7ba4] -> #4 > i_syslog_fatal_handler[0x7fa59e8510] -> #5 i_panic[0x7fa5936808] -> #6 > t_pop_pass_str\ > [0x7fa59e0eb4] -> #7 connection_deinit[0x7fa59e6430] -> #8 > pool_datastack_create[0x7fa5a0e7b0] -> #9 > array_bsearch_insert_pos_i[0x7fa59d46d0] -> \ > #10 t_base64_scheme_decode[0x7fa59dcb24] -> #11 > buffer_append[0x7fa59dd3d0] -> #12 replicator_queue_push[0x556e8f4f40] > -> #13 replicator_brain_in\ > it[0x556e8f53e4] -> #14 _start[0x556e8f3d70] -> #15 > _start[0x556e8f3f04] -> #16 io_loop_call_io[0x7fa5a02f20] -> #17 > io_loop_handler_run_internal\ > [0x7fa5a05450] -> #18 io_loop_handler_run[0x7fa5a05680] -> #19 > io_loop_run[0x7fa5a05944] -> #20 master_service_run[0x7fa59684b0] -> > #21 main[0x55\ > 6e8f3930] -> #22 __libc_init_first[0x7fa57676d0] -> #23 > __libc_start_main[0x7fa5767780] -> #24 _start[0x556e8f3b80] > Jan 28 11:26:12 la dovecot[1187]: replicator: Fatal: master: > service(replicator): child 1185 killed with signal 6 (core dumps > disabled - https://\ > dovecot.org/bugreport.html#coredumps) This is on Debian 12. > # dovecot --version > 2.3.19.1 (9b53102964) There are gigabytes of free RAM, though it says it is trying to allocate 268,435,496 bytes--on the stack--and that does seem wrong in any case. The Maildir being synced is over 430MB, is that too much for dsync?? Suggestions? Thanks, -kb

3 4

iOS email content loading issue
by Zieseniss Peter 05 Feb '25

05 Feb '25

Hello All, i hope everyone is well! i have a rather irksome and pressing issue that i can't seem to resolve.. This happens only on iOS devices.. Specifically, the problem is that the content of messages seems to timeout when it loads either when you open a message, or when you hit reply or forward, or whatever.. The email appears to load, but the content simply never shows up, leaving only a wheel that says 'Loading' Please see a screenshot of what it looks like: https://zconsulting.net/_stuff/dovecot-ios-loading.jpg This happens on all iOS devices (at least 18), many different versions from the most current down to iOS 16.. This has been happening for at least 2 years, and it happens about 50-80% of the time when interacting with an older message (more than 6 months old) Mail on macOS, Thunderbird on Windows, and RoundCube on the server all work perfectly.. Note that most of these accounts have at between 12GB and 80GB (that's the extreme case) of email.. The server is: Dedicated 4-Core Xeon, 16GB RAM, 512GB NVMe SSD AlmaLinux release 8.10 (Cerulean Leopard) Dovecot 2.3.21.1 Exim 4.98 Here's what i've tried: On the server, i installed FTS-Xapian On the server, i set mail_max_userip_connections=512 On the clients, i disabled all email privacy settings and disabled iCloud mail The problem is that i really can't figure out what the issue is, but this seems to be a very common issue between Dovecot and iOS, judging by the amount of similar questions i see on g00gle, but no useful answers (example here <https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/6YCEV…>).. It certainly seems like the iOS mail client is timing out when receiving the body of these older messages, but i don't see anything useful in the logs.. Please help! Any suggestions are welcome! My client is about to crucify me over this.. Thank You All in advance! Sincerely, Peter -- Peter Zieseniss Principal https://www.zconsulting.net peter(a)zconsulting.net

3 2

Fatal: block_alloc(134217728): Out of memory
by Michael 05 Feb '25

05 Feb '25

hey, :) i have a postfix instance trying to deliver a message to dovecot via lmtp, but fails due to an out-of-memory error in dovecot: the message is generated by a cron job like a thousand times before, and hundreds of times afterwards. the only thing maybe worth mentioning is its size of ~80MB. but since i don't have any size limits configured, i don't see why it shouldn't be delivered. any hints are appreciated! greetings... # dovecot --version 2.3.21.1 (d492236fa0) # cat /etc/apt/sources.list.d/dovecot.list #deb http://repo.dovecot.org/ce-2.3-latest/debian/bullseye bullseye main deb https://repo.dovecot.org/ce-2.3-latest/debian/bullseye bullseye main postfix log: Feb 5 12:21:42 mail01 postfix/qmgr[1175]: B95E360E5C: from=<root(a)mail01.example.com>, size=85100558, nrcpt=1 (queue active) Feb 5 12:21:43 mail01 postfix/lmtp[3990]: B95E360E5C: to=<root(a)example.com>, orig_to=<root>, relay=mail01.example.com[private/dovecot-lmtp], delay=3265236, delays=3265235/0.01/0.01/1.1, dsn=4.4.2, status=deferred (lost connection with mail01.example.com[private/dovecot-lmtp] while sending end of data -- message may be sent more than once) dovecot log: /var/log/dovecot/dovecot-lmtp.log:Feb 05 12:21:43 lmtp(root(a)example.com)<3991><SEldMcZJo2eXDwAAPczdCw>: Fatal: block_alloc(134217728): Out of memory /var/log/dovecot/dovecot-lmtp.log:Feb 05 12:21:43 lmtp(root(a)example.com)<3991><SEldMcZJo2eXDwAAPczdCw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f439cc1e662] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f439cc1e77e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1043db) [0x7f439cc2b3db] -> /usr/lib/dovecot/libdovecot.so.0(+0x104411) [0x7f439cc2b411] -> /usr/lib/dovecot/libdovecot.so.0(+0x5688f) [0x7f439cb7d88f] -> /usr/lib/dovecot/libdovecot.so.0(+0x5ae87) [0x7f439cb81e87] -> /usr/lib/dovecot/libdovecot.so.0(+0x1245ac) [0x7f439cc4b5ac] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x2f524) [0x7f439c30b524] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x307e9) [0x7f439c30c7e9] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_message_body_get_text+0x4a) [0x7f439c30d40a] -> /usr/lib/dovecot/libdovecot-sieve.so.0(ext_body_get_part_list+0x51) [0x7f439c34a3e1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x6ebc2) [0x7f439c34abc2] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x9a) [0x7f439c320cda] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0x92) [0x7f439c338202] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x39ba) [0x7f439c3a99ba] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x179) [0x7f439ce6f8d9] -> dovecot/lmtp(lmtp_local_default_deliver+0x1d4) [0x55c39e8ec724] -> dovecot/lmtp(lmtp_local_data+0x5ac) [0x55c39e8ece7c] -> dovecot/lmtp(client_default_cmd_data+0x18d) [0x55c39e8eb83d] -> dovecot/lmtp(cmd_data_continue+0x180) [0x55c39e8eb5d0] -> /usr/lib/dovecot/libdovecot.so.0(+0x7628b) [0x7f439cb9d28b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f439cc41609] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7f439cc42cf2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f439cc416b0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f439cc41870] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f439cbb38e3] -> dovecot/lmtp(main+0x22a) [0x55c39e8ea27a] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f439c972d7a] -> dovecot/lmtp(_start+0x2a) [0x55c39e8ea38a]

4 4

Help with migration of LDAP Quota config to 2.4.0
by Eduardo Costa 05 Feb '25

05 Feb '25

Hi, I converted most of my configuration to 2.4.0, but I couldn't figure out in the documentation how to convert my LDAP-based quota configuration: ... dict { quota = ldap:/usr/local/etc/dovecot/dovecot-ldap.conf.ext } .... mail_plugins = $mail_plugins quota ... protocol imap { mail_plugins = $mail_plugins imap_quota } ... user_attrs = mailMessageStore=home,mailQuotaSize=quota_rule=*:storage=%$B,mail_plugins ... plugin { quota = maildir quota_rule2 = Trash:storage=+10%% } How can I convert to the new version, or even to the new driver count? Regards, Eduardo Costa

1 0

RFC 2971: Cannot find Client ID in LOG
by Patrick Ben Koetter 05 Feb '25

05 Feb '25

Greetings, I'm trying to get dovecot (2.3.21.1 (d492236fa0)) to note a client's ID (see: RFC 2971) in the LOG, but no matter if I increase LOG verbosity using (mail|auth)_debug = yes or not I can't find it allthough dovecot supports the RFC, shows it in a session and responds to it like this: # telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN] Dovecot ready. a0001 LOGIN user password a0001 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 SPECIAL-USE] Logged in a0002 ID ("name" "sodr" "version" "19.34" "vendor" "Pink Floyd Music Limited") * ID ("name" "Dovecot") a0002 OK ID completed (0.001 + 0.000 secs). a0003 LOGOUT * BYE Logging out a0003 OK Logout completed (0.001 + 0.000 secs). In the LOG I see this: Feb 05 11:17:13 v22016013320531498 dovecot[319998]: imap-login: Login: user=<user>, method=PLAIN, rip=::1, lip=::1, mpid=320008, secured I would expect it to note something like that: Feb 05 11:17:13 v22016013320531498 dovecot[319998]: imap-login: Login: user=<user>, method=PLAIN, rip=::1, lip=::1, mpid=320008, id=... secured Am I doing it wrong? TIA, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 2

Exim / Dovecot v2.4.0 authentication patch
by Timo Sirainen 04 Feb '25

04 Feb '25

Hi, Dovecot v2.4.0 changed authentication protocol slightly to allow new functionality (SCRAM TLS channel binding). It attempted to preserve backwards compatibility by checking client-provided VERSION first before sending data that the client wouldn't handle correctly. However, Exim's Dovecot authenticator doesn't send VERSION until Dovecot has sent the whole authentication handshake. This causes Exim to get stuck when trying to authenticate. I guess we'll provide some kind of a workaround for v2.4.1, but this should get fixed on Exim side as well. Attached a patch that I tested works (against 4.97-4ubuntu4).

2 1

OpenLDAP Pass-through Authentication
by Dino Edwards 04 Feb '25

04 Feb '25

Hi, Trying to get pass-through authentication working however, I'm running to the following error in OpenLDAP: openldap | 679ceede.3aa31e0a 0x7f2ff617e6c0 conn=1004 op=1 SRCH attr=uid mail displayName openldap | 679ceede.3aa4b816 0x7f2ff617e6c0 conn=1004 op=1 SEARCH RESULT tag=101 err=0 qtime=0.000019 etime=0.000172 nentries=1 text= openldap | 679ceede.3aaafd88 0x7f2ff597d6c0 conn=1005 fd=14 ACCEPT from IP=172.16.32.1:47082 (IP=0.0.0.0:1389) openldap | 679ceede.3aab8f34 0x7f2ff597d6c0 conn=1005 op=0 BIND dn="cn=username(a)domain.tld,ou=users,dc=domain,dc=local" method=128 openldap | 679ceede.3aac9267 0x7f2ff597d6c0 SASL [conn=1005] Failure: cannot connect to saslauthd server: No such file or directory openldap | 679ceede.3aad25b9 0x7f2ff597d6c0 conn=1005 op=0 RESULT tag=97 err=49 qtime=0.000005 etime=0.000120 text= openldap | 679ceede.3ab0191f 0x7f2ff617e6c0 conn=1005 fd=14 closed (connection lost) openldap | 679ceede.3ab3d76a 0x7f2ff597d6c0 conn=1004 fd=13 closed (connection lost) I followed the admin docs at: https://www.openldap.org/doc/admin26/guide.html#Pass-Through%20authenticatio n Here's what I did: Created /usr/lib/sasl2/slapd.conf with the following content: mech_list: plain pwcheck_method: saslauthd saslauthd_path: /var/run/sasl2/mux Created /etc/saslauthd.conf with the following content: ldap_servers: ldap://192.168.xxx.xxx.xxx ldap_search_base: OU=Users,DC=domain,DC=tld ldap_filter: (uid=%u) ldap_bind_dn: CN=saslauthd,CN=Users,DC=domain,DC=tld ldap_password: somepassword Added a user that already exists in domain.tld in openldap with the following password: {SASL}username(a)domain.tld I would appreciate some help on this. Thanks

1 1