dovecot - Dec 2008 - mbox "Next message unexpectedly lost" bug fixed

Good news, everyone!

The most annoying bug in v1.1 series should finally be fixed by these
patches:

http://hg.dovecot.org/dovecot-1.1/rev/f28348c5201e
http://hg.dovecot.org/dovecot-1.1/rev/74c47fcfb420
http://hg.dovecot.org/dovecot-1.1/rev/a28520d26b5a
http://hg.dovecot.org/dovecot-1.1/rev/539f8d983285
http://hg.dovecot.org/dovecot-1.1/rev/9b7af230f9f0

They also make sure that mbox is never read while it's not locked. I
think that could have happened in some situations with v1.1. Hopefully
mbox handling will now finally be as stable in v1.1 as it was in v1.0.

I'll make a new v1.1 release after seeing what bug fixes are coming from
Apple, so probably next week.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20081213/a9cee61d/attachment-0002.bin>

Timo Sirainen wrote:
> Good news, everyone!
>
> The most annoying bug in v1.1 series should finally be fixed by these
> patches:
>
> http://hg.dovecot.org/dovecot-1.1/rev/f28348c5201e
> http://hg.dovecot.org/dovecot-1.1/rev/74c47fcfb420
> http://hg.dovecot.org/dovecot-1.1/rev/a28520d26b5a
> http://hg.dovecot.org/dovecot-1.1/rev/539f8d983285
> http://hg.dovecot.org/dovecot-1.1/rev/9b7af230f9f0
>
> They also make sure that mbox is never read while it's not locked. I
> think that could have happened in some situations with v1.1. Hopefully
> mbox handling will now finally be as stable in v1.1 as it was in v1.0.
>
> I'll make a new v1.1 release after seeing what bug fixes are coming
from
> Apple, so probably next week.
>   
Hi,

could I ask when is planned to release new dovecot 1.1 version?
In Fedora there are users affected by this issue, so I'd like to know
if I should release new dovecot rpm with this patch or wait for new
dovecot version.

Cheers,
Michal

First the good news: with these patches, the "Next message
unexpectedly lost" bugs I got so far were all caused reading a mbox
written by a previous version of dovecot.

So I think this time you really fixed the last annoying 1.1.x bug :)

Then another doubt: with these patches I'm still getting some:

FETCH for mailbox Sent UID 1077 got too little data: 1380 vs 3541
Corrupted index cache file
/mailhome/username/.imap/Sent/dovecot.index.cache: Broken virtual size
for mail UID 1077

These mails were written by a hg version pulled Dec 14 (that includes
the mbox patches).

Any suggestion for the kind of debug I can add to help solving these ones?

Regards,
Diego.