dovecot - Nov 2014 - 2.2.15 Panic in mbox_sync_read_next_mail()

Has someone of you just found any kind of solution to this problem?

We first had only one user with this problem. But now there are two more
users expecting the same problems. And as Jernej said, doveadm "index"
and "force-resync" do not solve the problem at all. After a few hours
these users have the same kind of errors and crashes.

We have now reverted back to 2.2.13 but that could not be a permanent
solution.

Timo Sirainen, have you maybe given a look to this or any hint?

Best regards
Matthias
-- 
Matthias Egger
ETH Zurich
Department of Information Technology          maegger at ee.ethz.ch
and Electrical Engineering
IT Support Group (ISG.EE), ETL/F/24.1         Phone +41 (0)44 632 03 90
Physikstrasse 3, CH-8092 Zurich               Fax   +41 (0)44 632 11 95

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4099 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20141104/b03b57d2/attachment-0001.p7s>

On 11/04/2014 01:38 PM, Matthias Egger wrote:
> 
> Has someone of you just found any kind of solution to this problem?
Could the people experiencing this please send at least a) output of doveconf -n
b) anonymized mbox content for an affected mbox
( http://www.dovecot.org/tools/mbox-anonymize.pl ). Other details can not hurt
either.

br,
Teemu Huovila

On Tue, Nov 04, 2014 at 12:38:02PM +0100, Matthias Egger
wrote:
> Has someone of you just found any kind of solution to this problem?
We have been running some days with patches 31262a892ba7 and 80ed82a93c1a
from http://hg.dovecot.org/dovecot-2.2/

They are working fine, handling the previously paniced situations smoothly.
Thanks again to the folks at dovecot.org!

hmk