April 2024 - dovecot - dovecot.org

Dovecot Server issue, cache corruption
by David Mehler 28 Apr '24

28 Apr '24

Hello, I'm using Thunderbird 102 to atempt to retrieve my messages via imap (have tried both 143 and 993) first I wasn't getting any error messages now I am. This is with Dovecot 2.3 on Debian 12.5. Here's the error messages. I do not believe the first set related to public mailboxes is related but I'm not sure what it's problem is either, the problem seems to be corrupted cache. 2024-04-26T02:01:47.832997-04:00 hostname dovecot: imap(username(a)example.com)<586617><WEyTo/kWUwpoDWll>: Error: Mailbox public/example-1: mkdir(/var/vmail/public/.example-1/cur) failed: Permission denied (euid=999(vmail) egid=992(vmail) missing +w perm: /var/vmail/public/.example-1, dir owned by 0:0 mode=0755) 2024-04-26T02:01:48.742111-04:00 hostname dovecot: imap(username(a)example.com)<586617><WEyTo/kWUwpoDWll>: Error: Mailbox INBOX: Deleting corrupted cache record uid=34640: UID 34640: Broken physical size in mailbox INBOX: read(/var/vmail/mailboxes/example.com/username/mail/mailboxes/INBOX/dbox-Ma… failed: Cached message size smaller than expected (1376 < 1647, box=INBOX, UID=34640) 2024-04-26T02:01:48.742239-04:00 hostname dovecot: imap(username(a)example.com)<586617><WEyTo/kWUwpoDWll>: Error: Mailbox INBOX: UID=34640: read(/var/vmail/mailboxes/example.com/username/mail/mailboxes/INBOX/dbox-Ma… failed: Cached message size smaller than expected (1376 < 1647, box=INBOX, UID=34640) (read reason=) 2024-04-26T02:01:48.742308-04:00 hostname dovecot: imap(username(a)example.com)<586617><WEyTo/kWUwpoDWll>: Disconnected: FETCH failed: Mailbox INBOX: UID=34640: read(/var/vmail/mailboxes/example.com/username/mail/mailboxes/INBOX/dbox-Ma… failed: Cached message size smaller than expected (1376 < 1647, box=INBOX, UID=34640) (read reason=) in=889 out=6253 deleted=0 expunged=0 trashed=0 hdr_count=5 hdr_bytes=10 body_count=0 body_bytes=0 Here is a doveconf -n output: # doveconf -n # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 4.19.0 x86_64 Debian 12.5 # Hostname: hostname.example.com auth_mechanisms = plain login dict { lastlogin = mysql:/etc/dovecot/dovecot-last-login.conf } imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags listen = * lmtp_rcpt_check_quota = yes mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_gid = vmail mail_home = /var/vmail/mailboxes/%d/%n mail_location = dbox:~/mail:LAYOUT=fs mail_plugins = acl quota welcome mail_privileged_group = vmail mail_uid = vmail 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 { list = children location = maildir:/var/vmail/public:INDEXPVT=~/public prefix = public/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile:/etc/dovecot/dovecot-acl imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = * last_login_dict = proxy::lastlogin last_login_key = # hidden, use -P to show it quota = count:User quota quota2 = maildir:Shared quota:ns=public/ quota_exceeded_message = User %u has exhausted allowed storage space. quota_grace = 10%% quota_max_mail_size = 100M quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_rule3 = SPAM:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_vsizes = yes quota_warning = storage=100%% quota-warning +100 %u quota_warning2 = storage=95%% quota-warning +95 %u quota_warning3 = storage=80%% quota-warning +80 %u quota_warning4 = -storage=100%% quota-warning -100 %u sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-script.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms stats_refresh = 30 secs stats_track_cmds = yes welcome_script = welcome %u welcome_wait = no } protocols = imap lmtp sieve service auth-worker { vsz_limit = 0 } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { client_limit = 1 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/dovecot-quota { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vmail } service stats { fifo_listener stats-mail { mode = 0644 user = vmail } inet_listener { address = 127.0.0.1 port = 24242 } } service welcome { executable = script /usr/local/bin/welcome.sh unix_listener welcome { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/ssl/example.com/example.com.fullchain.crt 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 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { imap_idle_notify_interval = 29 mins imap_metadata = yes mail_max_userip_connections = 20 mail_plugins = acl quota welcome imap_acl imap_quota imap_sieve last_login welcome quota } protocol lmtp { mail_fsync = optimized mail_plugins = acl quota welcome last_login quota sieve postmaster_address = postmaster(a)example.com } Suggestions welcome. Thanks. Dave. -- Sent from Mozilla Thunderbird 91.13.1

1 0

Is it possible to setup ntlm authentication then proxy it to the mail server ?
by karl.l＠as7600.net 26 Apr '24

26 Apr '24

Hi, This is my dovecot version: ``` root@freebsdsvr:~ # dovecot --version 2.3.21 (47349e2482) ``` I'm having trouble in making dovecot as proxy to the mail server when using ntlm authentication. My setup looks like this: email client ------> dovecot (will act as proxy) -------> mail server so basically the email client will connect to dovecot but dovecot will forward it to the mail server. Proxying using auth_mechanism as PLAIN is working but if I use ntlm authentication it just connects into the dovecot server and dovecot server does not proxy to to the mail server. I tried using passdb driver = sql, passdb driver = static, passdb driver = lua and all of them are working when the email client connects using plain auth, once dovecot authenticates the user it will proxy it to the mail server but when I use ntlm authentication it just connects to dovecot and does not do a proxy to the mail server. I switched on all the debugs and I found out in the log that when I connect using PLAIN auth it calls the passdb and gets my default_fields or my proxy fields ```proxy=y``` and ```host=mailserver_domain``` which causes dovecot to proxy into the host(my mail server). but when I connect using NTLM auth it calls the passdb but it does not return my default fields for proxying (when it uses the sql passdb driver it just connects to the database and does not run the password_query) and I think it uses the output from the ```ntlm_auth``` of samba that dovecot uses because it retunrs the field user=username and original_user=username@domain This is the example logs that I recieved once I connect using ntlm and it does not proxy it to my mail server ``` Apr 18 03:37:29 freebsdsvr dovecot[12084]: auth: Debug: mysql(192.168.254.131): Connecting Apr 18 03:37:29 freebsdsvr dovecot[12084]: auth: Debug: auth client connected (pid=12268) Apr 18 03:37:29 freebsdsvr dovecot[12084]: auth: Debug: auth client connected (pid=12270) Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client in: AUTH 1 NTLM service=imap session=Js8TT04WcMnAqP5/ lip=192.168.254.131 rip=192.168.254.127 lport=143 rport=51568 Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client passdb out: CONT 1 Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client in: CONT 1 TlRMTVNTUAABAAAAB4IIAAAAAAAAAAAAAAAAAAAAAAA= (previous base64 data may contain sensitive data) Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client passdb out: CONT 1 TlRMTVNTUAACAAAAFAAUADgAAAAFgooC57WwKq2q4U8sdAAAAAAAAAAFwAXABMAAAABgEAAAasdasdasdAAAA9FAFMAQwAuAE4ARQBUAC4AQQBVAAIAFABFAFMAQwAuAE4ARQBUACad4AQdsQBVAAEasAFABFAFMAQwAuAE4AdaRQBUAC4AQQBVAAQAAAADABQAZQBzAGMALgBuAGUAdAAuAGEAdQAHAAgA/h8T7O2Q2gEAAAAA Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client in: CONT 1 TlRMTVNTUAADAAAAGAAYAFwAAACIAIgAdAAAAAAAAeABAAAAABgAGAEAAAAAWABYARgAAAAAAAAAAAAAABYIIAHMAcwAzAFcATwBSAEsAUwBUAEEAVABJAE8ATgBXKrBA2vF7fMicRiasLK/IyI3fbM46rQ7JHcti/0TU02AqasdasdasdhceI+BaeqMjrAQEAAAAAAACAL88ampDaARzhirKymxxcAAAAAAIAFABFAFMAQwAuAE4ARQBUAC4AQQBVAAEAFABFAFMAQwAuAE4ARQBUAC4AQQBVAAQAAAADABQAZQBzAGMALgBuAGUAdAAuAGEAdQAHAAgA/h8T7O2Q2gEAAAAA (previous base64 data may contain sensitive data) Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: auth(userName,192.168.254.127,<Js8TT04WcMnAqP5/>): Auth request finished Apr 18 03:37:30 freebsdsvr dovecot[12084]: auth: Debug: client passdb out: OK 1 user=userName original_user=userName@FREEBSD-TEST ``` Here's the logs that I get when I connect via Plain Auth and it does the proxy to my mail server ``` Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: mysql(192.168.254.131): Connecting Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): Server accepted connection (fd=15) Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): Sending version handshake Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): auth-worker<1>: Handling PASSV request Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): auth-worker<1>: sql(ss3,192.168.254.127,<zwTdK04W9MbAqP5/>): Performing passdb lookup Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): auth-worker<1>: sql(ss3,192.168.254.127,<zwTdK04W9MbAqP5/>): query: SELECT destuser, password, host, 'Y' as proxy FROM proxy WHERE user = 'userName'; Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: mysql(192.168.254.131): Finished query 'SELECT destuser, password, host, 'Y' as proxy FROM proxy WHERE user = 'userName';' in 0 msecs Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): auth-worker<1>: sql(userName,192.168.254.127,<zwTdK04W9MbAqP5/>): Finished passdb lookup Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth-worker(12138): Debug: conn unix:auth-worker (uid=0): auth-worker<1>: Finished Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: sql(userName,192.168.254.127,<zwTdK04W9MbAqP5/>): Finished passdb lookup Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: auth(userName,192.168.254.127,<zwTdK04W9MbAqP5/>): Auth request finished Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: conn unix:dns-client: dns(mailserver.domain): Lookup started Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: conn unix:dns-client: Connecting Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: conn unix:dns-client (uid=0): Client connected (fd=27) Apr 18 03:27:39 freebsdsvr dovecot[12084]: auth: Debug: conn unix:dns-client (uid=0): Sending version handshake Apr 18 03:27:40 freebsdsvr dovecot[12084]: auth: Debug: conn unix:dns-client (uid=0): dns(mailserver.domain): Lookup successful after 658 msecs Apr 18 03:27:40 freebsdsvr dovecot[12084]: auth: Debug: client passdb out: OK 1 user=userName destuser=userName host=mailserver.domain proxy hostip=mailserverip pass=password ``` Is there a right way to configure ntlm to do proxy? because it does not seem to use the passdb in sql,lua, and static drivers. This is my dovecot -n ``` root@freebsdsvr:~ # dovecot -n # 2.3.21 (47349e2482): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 13.2-RELEASE amd64 zfs # Hostname: freebsdsvr auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login ntlm auth_use_winbind = yes auth_username_format = %n auth_verbose = yes auth_verbose_passwords = plain auth_winbind_helper_path = /usr/local/bin/ntlm_auth disable_plaintext_auth = no mail_debug = yes mail_gid = 1001 mail_location = maildir:/var/mail/vhosts/%n mail_uid = 1001 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 = } protocols = imap pop3 service auth { user = root } ssl_cert = </root/dovecot.crt ssl_cipher_list = ALL:!DH:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH ssl_key = # hidden, use -P to show it passdb { driver = sql # Path for SQL configuration file, see example-config/dovecot-sql.conf.ext args = /usr/local/etc/dovecot/dovecot-sql.conf.ext } userdb { driver = prefetch } ``` dovecot-sql.conf.ext ``` driver = mysql connect = host=192.168.254.134 port=3306 dbname=mails user=karl password=adminpassword password_query = SELECT destuser, password, host, 'Y' as proxy FROM proxy WHERE user = '%u'; ``` Thanks :)

5 6

using keycloak
by A. Schulze 25 Apr '24

25 Apr '24

Hello, I'm relative new to oauth2. I like to understand a setup for dovecot but https://doc.dovecot.org/configuration_manual/authentication/oauth2/ is not enough for me. Could anybody describe a simple setup where dovecot uses keycloak. For simplification I would start with keycloak's builtin user management only. - how to configure dovecot - how to configure keycloak - how to test with 'curl --verbose --some-magic-options imap://dovecot-server' Thanks, Andreas

1 0

Which DKIM application for postfix 3.9.0
by dovecot＠outputservices.com 25 Apr '24

25 Apr '24

I am upgrading to postfix 3.9.0. I have not used DKIM in previous postfix installs, but I would like to start now with the new google rules. I have done some research and opendkim is the most recommended, however, other research states the opendkim has been abandoned by it's maintainers. So I am looking for a good alternative dkim software that will work with postfix that I can compile myself. I do not run on any linux version, so therefore I can not just apt-get a new dkim application. I run Solaris and therefore need to compile my applications, postfix and dkim. Any good suggestions will be appreciated.

7 8

HELP with email attachments ONLY clean up
by INFO ＠ TRIMLINE 25 Apr '24

25 Apr '24

Hello Dovecot Dev team, In my cpanel, we use your email management. This is what my hosting provider has allowed. Our problem: Since the introduction of "hi def cameras on mobile phones", we are getting emails with "huge attachments". The email which comes with the attachments is also important. However, once we download the email (imap), using any of the email clients (outlook, bluemail etc.) the mailbox still has these huge attachments. Because of this, our mailbox storage gets filled up quickly. In our email client software, we can delete (attachments only), and leave the email in our mailbox. So this work around helps us keep our mailbox size manageable. Unfortunately, not everyone does this "email attachment cleanup" regularly and end up being locked out of email storage space and probably lost a few hours of productive time. Our dev Request: Would it be possible to create a setting for end users in our Cpanel, in which we can delete the attachments without deleting the actual message? So query should have: <per email mailbox account> (drop down selection, like you have it now) * Filter 01: Select Messages older than nnn days (where nnn would be 100 to 999 days) (so for the first 99 days, every imap client would have the opportunity to download the email and the attachments) * From Filter 01 = Filter 02: Select messages which are >xxx Mb (where xxx could be 001 to 999 Mb) * From Filter 02 = Filter 03: Select only messages which contain attachments (Yes) * From Filter 03: Permanently Delete the attachments ONLY, So not deleting the actual email msg (OK). So on day 100 (or after the clean up is done), the imap email client will now only get the email but not the attachments (in the event they need to refresh their email setup). If such a query can be created and installed on our Cpanel, we can run this "clean up attachments" query regularly and as such reduce our mailbox size. Q: Would it be possible to create such a clean up tool (pre-defined) so that the cpanel web service admin user only has to enter (nnn and xxx and Yes) to finally click on "OK" to delete the attachments? If this would be possible, what will it cost us to have it installed on our Cpanel? There is so much information/documentation already on your website (doc.dovecot.org) and I spent about 60 min looking for such a "clean up tool" documentation, but started getting dizzy reading all that script language etc. Not my cup of tea. Please help. Thank you for considering and reading this request. Kind regards M. Akil Walji

3 2

Debian, Postfix, Dovecot, MySQL, and argon2 password hashing scheme?
by David Mehler 25 Apr '24

25 Apr '24

Hello, I have a quick question. Can Debian, and/or it's Postfix/Dovecot/MySQL/MariaDB packages support the argon2 password hashing scheme? I had a previously-working e-mail setup on a *BSD system, utilizing the argon2ID scheme with Dovecot, Postfix, and MySQL. Since changing systems to Debian 12.5 I can't send, though checking the password with a manual login to Dovecot works fine. I'm wondering if I have to migrate the passwords from argon2ID to SHA512-CRYPT? Thanks. Dave. -- Sent from Mozilla Thunderbird 91.13.1

2 1

RE: Which DKIM application for postfix 3.9.0
by Joseph Tam 24 Apr '24

24 Apr '24

On Tue, Apr 23, 2024 at 7:33 AM <dovecot-request(a)dovecot.org> wrote: > > I am upgrading to postfix 3.9.0. I have not used DKIM in previous postfix installs, but I >> would like to start now with the new google rules. I have done some research and opendkim >> is the most recommended, however, other research states the opendkim has been >> abandoned by it's maintainers. So I am looking for a good alternative dkim software >> that will work with postfix that I can compile myself. I do not run on any linux >> version, so therefore I can not just apt-get a new dkim application. >> I run Solaris and therefore need to compile my applications, postfix and dkim. >> Any good suggestions will be appreciated. I just rolled out a locally compiled opendkim on my mail server. It works, but there are a few gotchas. Although it seems like a moribund project, there is a late beta version that includes some important patches, most notably the "Header:\n LongHeaderValue" bug that needs fixing. You can look at https://sourceforge.net/p/opendkim/patches/ to find that patch, as well as others you deem important. As DKIM standards are not going to change soon, having end-of-line software is not as bad as it seems unless you need particular enhancements to make it work better in your circumstances. Once you get your setup dialed, you can probably set it and forget it. Most of the headaches have actually been internal: local mail injection via sendmail would skip miltering, From header canonicalization by the MTA would not be seen by the opendkim milter thereby creating messages with missing or invalid signatures, and mailing list/auto reply/forwarder software mangling messages. I think Postfix does a better job in this regard, so these issues may not present itself. (I did a Postfix/opendkim milter on an Ubuntu system and it was much less hassle.) You should look at *lots* of DMARC RUA reports. People are doing crazy batsh*t stuff with your mail domain. Joseph Tam <jtam.home(a)gmail.com>

4 3

Setting compression to specific namespace
by Filip Bartmann 23 Apr '24

23 Apr '24

Hello, is it possible to set compression for specific namespace or spefic mailbox folder? Thanks, Filip Bartmann

1 0

Question about line length limit in lmtp.
by Kamil Jońca 22 Apr '24

22 Apr '24

I have postfix + dovecot server. Mail for local users are saved by dovecot lmtp. Recently I got some messages from postfix: --8<---------------cut here---------------start------------->8--- 4NQ07L4h4LztXXr: breaking line > 998 bytes with <CR><LF>SPAC --8<---------------cut here---------------end--------------->8--- This is because postfix has configured with default value lmtp_line_length_limit (990). I can turn off this limit (set to 0) but I am curious if dovecot lmtp will accept so lengthty lines? Does dovecot lmtp has any line limits? KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

4 6

doveadm index to terminate non-zero in case of failure
by Jaco Kroon 22 Apr '24

22 Apr '24

Hi, It would be great if doveadm index could terminate non-zero in the case of index corruption, that way the tool can be used as a way to determine and remove corrupted indexes. Example: othala [13:56:24] ~ # doveadm index -u lumi_james INBOX doveadm(lumi_james): Error: Corrupted transaction log file /path/to/lumi_james/dovecot.list.index.log seq 2: Unexpected garbage at EOF (sync_offset=7168) doveadm(lumi_james): Error: Failed to map transaction log /path/to/lumi_james/dovecot.list.index.log at sync_offset=7168 after locking: Unexpected garbage at EOF othala [13:56:34] ~ # echo $? 0 othala [13:56:37] ~ # If doveadm index exited non-zero in above case we'd be able to: if ! doveadm index -u lumi_james INBOX; then rm /path/to/lumi_james/dovecot.index{,log,.cache} fi Which may be over-zealous in removing indexes, but we'd rather have that. We believe we already fixed the locking issue that caused the corrupt indexes and are busy cleaning them up based on log files, but it would still be great if the above could be integrated into our check battery if/when users report problems, of "run the script and it fixes 99% of things that are known to break". In the same breath, we're seeing that folders with & in the name are causing problems for doveadm index -u someuser '*' usage. Kind regards, Jaco

1 0