On Fri, 2007-12-07 at 14:33 +0000, Daniel Watts wrote:
Following errors have happened quite a bit:
Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day@mydomain.com): Transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: marked corrupted
Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day@mydomain.com): Transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log.2: marked corrupted
These happen because of another error that caused them to be marked corrupted.
Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day@mydomain.com): Corrupted transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: Append with UID 50, but next_uid = 15870
This is the real error. What kind of a system do you have? Do you use NFS or other shared filesystem? Post your dovecot -n output?
Shouldn't Dovecot be able to recover from this?
It does, that's why there are those "marked corrupted" errors. But it probably does cause the current operation to fail. v1.1 handles this by logging the error but continuing anyway, so the operation shouldn't fail.
If you mean that it repeatedly fails with the same error, then the same error condition is created over and over again for some reason.