[Dovecot] corrupted transaction log error resulting in multiple deliveries

[Timo Sirainen]

On Fri, 2007-03-16 at 09:01 -0400, Justin McAleer wrote:
> Mar 16 08:45:37 node7 deliver(user at example.com): Corrupted transaction 
> log file /var/indexes/example/com/u/us/user/.INBOX/dovecot.index.log: 
> Append with UID 3, but next_uid = 15368
..
> So, as you can see deliver has the problem and defers delivery. Is 
> dovecot supposed to be able to recover from a corrupted log file on its 
> own? It repeated this until I manually wiped out the index directory 

Yes, it's supposed to recover from that. I couldn't reproduce this. It
always fixed the problem with the next try, or 3rd try at latest. If
this happens again, could you send me the dovecot.index and
dovecot.index.log files?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20070316/cfc9f590/attachment.pgp