Hello Hans
On 11/23/2014 05:57 PM, Hans Morten Kind wrote:
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
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
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
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 ).
On 30/10/14 15:44, Matthias Egger wrote:
On 10/29/2014 02:50 PM, Matthias Egger wrote:
As soon as i can catch a coredump i will send a gdb output.
Okay, here is the gdb ouput i could catch and some more information
about the system.
System Infos:
SunOS HOSTNAME 5.10 Generic_150400-10 sun4u
On 10/29/2014 02:50 PM, Matthias Egger wrote:
As soon as i can catch a coredump i will send a gdb output.
Okay, here is the gdb ouput i could catch and some more information
about the system.
System Infos:
SunOS HOSTNAME 5.10 Generic_150400-10 sun4u sparc SUNW,Sun-Fire-V440
Logfile Entries:
It might not be a fault in dovecot, as the user is accessing the folder locally
with alpine while also running imap-sessions. However it would have been nice
with a more graceful action than panic?
The panic is preceeded by
Error: Next message unexpectedly corrupted in mbox file PATH
Panic:
Interesting. We are expiring the same problem here. But our user is
currently traveling in the world and uses our roundcube to access its
emails:
The panic is preceeded by
Error: Next message unexpectedly corrupted in mbox file PATH
Panic: file mbox-sync.c: line 152
