The problem was that an FTS crash corrupted the mdbox index, which
resulted in thousands of e-mails to be placed back into INBOX again.
This happened in two separate accounts in the course of a few months.
It seems that dbox format is quick but very fragile, so I upgraded it to
Maildir. Even if its index is corrupted, only speed is lost but the
information is retained. This I value a lot more in a PIM application
than speed.
Ákos
2025. 11. 01. 14:01 keltezéssel, Ákos Szőts via dovecot írta:
Hi everyone,
Suddenly, the following messages appeared in my Dovecot error log:
master: Warning: Killed with signal 15 (by pid=0 uid=0 code=kill)
Error: Mailbox Trash: Synchronization corrupted index header
[...]/Trash/dbox-Mails/dovecot.index: uidvalidity=0, but next_uid=73
Warning: Mailbox Trash: fscking index file [...]/Trash/dbox-Mails/dovecot.index
Warning: mdbox([...]/mail/storage): rebuilding indexes: Mailbox Trash index was
fsck'd
Warning: mdbox([...]/mail/storage): fscking index file
[...]/index/inbox/storage/dovecot.map.index
Error: Mailbox INBOX: [...]/INBOX/dbox-Mails/dovecot.index reset, view is now
inconsistent
The first message is because I restarted the container.
Since then, Thunderbird shows thousands of previously deleted e-mails again in
INBOX where all my messages are marked as unread.
- Do you know what can cause it and how can I avoid to happen again?
- Is the used mdbox storage engine that fragile? Is the fault tolerance of
other engines better?
I have a backup from some days ago. Is it possible to somehow revert back to it
and sync the new e-mails on top of those?
Version: 2.4.2.
Thank you,
Ákos
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]
