25 Feb
2016
25 Feb
'16
12:34 p.m.
Hello
We experienced corrupted dovecot indexes, probably caused by a server crash. This does not cause a lot of harm, just annoyance. For instance, LMTP raises an assertion during delivery, which causes mail to multiple recipients e-mail to remain in the queue if a single of them hits a corrupted index.
The workaround for now is to detect the situation in the logs and to remove corrupted indexes when the problem arise.
A better fix would be to sanity check all user's index on startup. Is there a command line tool to do this?
-- Emmanuel Dreyfus manu@netbsd.org