[Dovecot] Errmsgs b4 and after migration DC V1.0.15 to V1.1.8

[Timo Sirainen]

On Tue, 2009-01-20 at 10:52 -0500, Stewart Dean wrote:
> > Jan 14 11:49:23 mercury mail:warn|warning dovecot: imap-login: SSL_read() syscall failed: Connection reset by peer [69.180.200.184]
> > Jan 14 11:52:28 mercury mail:warn|warning dovecot: imap-login: SSL_read() syscall failed: Connection reset by peer [68.6.82.45]
> Which l took to be breakin attempts of some sort, except that I haven't 
> seen any since the migration!

That just means you set verbose_ssl=yes and the client disconnected
without sending a "SSL BYE" command. This is normal. Maybe v1.1 hides
these useless messages (I did something related to that at some point).

> After the migration====================================
> I see errors like this:
> > Jan 14 12:21:45 mercury mail:err|error dovecot: IMAP(eg115): Corrupted index cache file /var/dcindx/eg115/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 1934
> > Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(alexande): Corrupted index cache file /var/dcindx/alexande/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 132641
> > Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(ls454): Corrupted index cache file /var/dcindx/ls454/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 47
> > Jan 14 12:21:46 mercury mail:err|error dovecot: IMAP(tr489): Corrupted index cache file /var/dcindx/tr489/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 1
> > Jan 14 12:21:54 mercury mail:err|error dovecot: IMAP(bh265): Corrupted index cache file /var/dcindx/bh265/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 2
> > Jan 14 12:22:01 mercury mail:err|error dovecot: IMAP(crouch): Corrupted index cache file /var/dcindx/crouch/.imap/INBOX/dovecot.index.cache: Broken MIME parts for mail UID 4863
> >   
> It appears that this error appears the first time a folder is 
> referenced, then not again (I think but am not absolutely positive).  

If it happens only once then don't worry about it. Or perhaps you could
just go and delete all dovecot.index.cache files to avoid these errors
(but that again makes the performance worse temporarily for those whose
files are already fixed).

> Did the indexing method/format change in some way that would cause this 
> (and Dovecot heals itself!) ?  

Maybe, but I can't really think of any specific reason right now.

> Is there any continuing problem inherent 
> in this that needs to be dealt with? 

Hopefully not :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20090120/1c5d3f75/attachment.bin