[Dovecot] cram-md5 problem re-post

[Richard Stockton]

At 11:20 AM 2/2/2009, Timo Sirainen wrote:
> > dovecot: Jan 29 16:35:03 Error: uid specified multiple times for jennshinjo
>
>Right, that's the one.
>
> > and very occasionally I'll see an NFS error or a "Broken header", but
> > neither seems to relate to the cram-MD5 problems.
>
>These shouldn't happen either, could you show some of them?


dovecot: Jan 30 10:20:32 Error: IMAP(mx3ga04): 
lseek(/mail/m/x/mxxxx/Maildir/dovecot-uidlist) failed: Stale NFS file handle

dovecot: Jan 30 10:41:17 Error: IMAP(syxxx): 
mail/s/y/syxxx/Maildir/.Trash/dovecot-uidlist: Broken header 
(uidvalidity = 0, next_uid=67)

The "Broken header" messages are only happening on my webmail
servers which are still running dovecot version 1.0.7.  I will
get those updated soon.  The errors look like this:

dovecot: Jan 14 15:50:50 Error: IMAP(puxxxx): 
/mail/p/u/pxxxx/Maildir/.Sent/dovecot-uidlist: Broken header 
(uidvalidity = 0, next_uid=28)

dovecot: Jan 29 06:04:46 Error: IMAP(doxx): 
/mail/d/o/dxxx/Maildir/.Sent/dovecot-uidlist: Broken header 
(uidvalidity = 0, next_uid=14)


>I mean you call the info log so logically dovecot-info.log, why not
>error log dovecot-error.log? :) I'd think that you could easily forget
>to look at pop.log when errors happen.


I called the main dovecot log "dovecot-info.log" because that was the
default, but you are undoubtedly correct, I will change the error log
to "dovecot-error.log".

Thanks again for all your help.
  - Richard