April 2025 - dovecot - dovecot.org

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

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

22 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

3 3

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

Unable to save message in shared mailbox
by Markus Bach 17 Apr '25

17 Apr '25

Hello, I have a curious problem. We are running a Debian bookworm server with dovecot 2.3.19.1. We have a lot of shared mailboxes and most of them are behaving just fine. But we have a problem with one shared mailbox: Users aren't able to save messages in it even though they have the right to. This issue popped up, when a user This mailbox is set up like every other shared-mailbox, so I don't think it's a permission problem. We tried it with several users giving them the same access rights and always got an error when trying to save a mail in the shared mailbox. I didn't find anything that could help in the log files. Even after turning on `mail_debug` I can't even see the try to save a message in the logs. Some of the things I've tried so far without any success: * doveadm force-resync * increasing the quota for the shared-mailbox * disabling the quote for the shared-mailbox * recreating the Sent folder in the shared-maiblox. Does anybody have any idea how I can debug this further or where the issue could be? Mit freundlichen Grüßen Markus Bach IT-Administration -- Telefon: +49 (30) 31 98 31 200 E-Mail: support(a)pegasusgmbh.de PEGASUS GmbH Gesellschaft für soziale/gesundheitliche Innovation IT-Systemleistungen Brunowstr. 52 13507 Berlin Datenschutzhinweise: https://www.pegasusgmbh.de/datenschutz Internet: http://www.pegasusgmbh.de Sitz der Gesellschaft: PEGASUS GmbH Gesellschaft für soziale/gesundheitliche Innovation Potsdamer Str. 98 10785 Berlin Geschäftsführer: Friedrich Kiesinger Registergericht: Amtsgericht Berlin Charlottenburg Registernummer: HRB 69935 B

1 2