December 2024 - dovecot

Problem email client iPhone ios18.2
by andrzej.milewski＠gmail.com 10 Feb '25

10 Feb '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

21 47

find mailbox (path) of message
by Marc 13 Jan '25

13 Jan '25

How should I use 'doveadm search -u' to get the mailbox path where the message is stored?

4 4

Hard-coded upper limit for sieve_max_redirects ?
by Maciej Polewczynski 02 Jan '25

02 Jan '25

Hello, After upgrading Dovecot from version 2.3.4 to 2.3.19 i noticed errors for some users having sieve redirects. Before upgrade all worked fine. In sieve plugin i have two limits: sieve_max_actions = 500 sieve_max_redirects = 150 If user have up to 100 redirects all works fine but if there are 101 or more none of them works and there is error: dovecot: lmtp(test2.mbox) Error: sieve: msgid=<***l>: redirect action: failed to check for duplicate forward to <101th.email.address> It seams that there is another limit but cant find where. When checked "dovecot -n|grep 100" there was only "default_process_limit". Increasing this changed nothing. Still the same error. File ".dovecot.sieve.log" in user home dir don't have any additional information. There is only: redirect action: failed to check for duplicate forward: internal error occurred: refer to server log for more information. Do you have any ideas how to fix it? -- Best regards, Maciej Polewczyński Do or do not. There is no try.

3 4

Moving all mail from one user to another
by Peter Reinhold 29 Dec '24

29 Dec '24

Hi all I have a user that has changed domain, and I am looking to move all her mail from her old account into her new one, but I am really unsure about how to go about it I would think that I am should use https://doc.dovecot.org/main/core/man/doveadm-move.1.html to do it, but the example supplied and all discussion about that tool I can find online is only about moving a users mail across folders on their account, and not the entire accounts content to another account. Has anyone tried to do something like this? -- Peter Reinhold

3 2

993 SSL 143 No encryption
by Dino Edwards 26 Dec '24

26 Dec '24

Hello, I have a dovecot server that listens on both 143 and 993 using SSL. I'm trying to get the 143 port to be unencrypted while 993 to remain encrypted. Is there any way to accomplish this? Thanks

2 3

vacation auto reply mail line endings CR LF
by tobias.niethammer＠projektb.net 21 Dec '24

21 Dec '24

Hi all, I tried to setup dovecot 2.3.21.1 (d492236fa0) (dovecot-pigeonhole-0.5.21.1) with the sieve vacation function. I'm getting here a bit into trouble. if I sent an e-mail to an receipient dovecot does via dma and the local mailserver an mail reply but the mail does only have the header inside. After a bit research my conclusion is that the reply mail which gets generated has line endings CR LF. I have to remove this manualy and set it to \LF to get the mail correcly transfered. I Setup the sieve rule with roundcube. I tried to manualy change the .dovecot.sieve file endings and comipled with sievec .dovecot.sieve .dovecot.svbin the binary again, with no change in the behavior. I guess i missed somewhere an variable to fix this issue? here the sieve file: #################################################### require ["vacation"];^M # rule:[Urlaub]^M if true^M {^M vacation :addresses "test02(a)projektb-mail.net" :subject "test Urlaub" text:^M test 1 test 2 test 3^M .^M ;^M }^M #################################################### thank you for your Support Tobias

4 5

Sekt
by Michael Grimm 20 Dec '24

20 Dec '24

.

1 1

COPY vs MOVE
by Scott Q. 19 Dec '24

19 Dec '24

Anyone that knows a bit about the dovecot internals. is move in any way faster than copy / set deleted flag / expunge ? Thanks! Scott

1 0

failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown: SSL alert number 46, session=
by Marc 19 Dec '24

19 Dec '24

What is the best way to get rid of this message? I think clients start generating after ssl crt update.

3 8

ACL propagation with acl_defaults_from_inbox
by Francois Lesueur 19 Dec '24

19 Dec '24

Hello, When dovecot is configured with "acl_defaults_from_inbox = yes", ACL propagation when creating folders seems a bit strange to us. The current behavior is : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside ("acl_defaults_from_inbox = yes") - When creating a folder, a dovecot-acl file is created inside this folder with a copy of the contents of the dovecot-acl from the INBOX The behavior we expected was : - INBOX has some ACLs defined in its dovecot-acl file - This ACL is the default for subfolders without a dovecot-acl file inside - When creating a folder directly under INBOX, a dovecot-acl file should not be created, as the default from INBOX is already enforced. For subfolders, defaults from INBOX should not be propagated either in the dovecot-acl files. Although dovecot-acl files in subfolders allow to have exceptions, most usage of "acl_defaults_from_inbox = yes" is probably to have mailbox-wide ACLs. In the current behavior, when someone removes an ACL from the INBOX, it will still be present in subfolders, which is error-prone in a setup where users expect that their INBOX ACL is enforced throughout their mailbox. I think that avoiding propagating INBOX ACL when creating a new folder in the case where "acl_defaults_from_inbox" is activated would be more intuitive. Am I missing something ? Cheers, Francois

1 0