On Sun, 2008-10-05 at 19:20 -0400, Steven Winikoff wrote:
Oct 3 17:52:21 alcor dovecot: imap[14973] , NNN.NNN.NN.NNN: Corrupted
transaction log file /home//mail/.imap/sent-mail/dovecot.index.log:
record size too small (type=0xcd91, offset=8180, size=0)
This and some other bugs
On Fri, 2008-10-10 at 14:22 -0400, Steven Winikoff wrote:
Oct 10 04:48:46 alcor dovecot: Panic: pop3-login: file
client-authenticate.c: line 163 (sasl_callback): assertion failed:
(!client-destroyed || reply == SASL_SERVER_REPLY_CLIENT_ERROR || reply ==
SASL_SERVER_REPLY_MASTER_FAILED)
This and some other bugs are now fixed by this:
http://hg.dovecot.org/dovecot-1.1/rev/262c52055f2a
Thank you! Both for this and for
http://hg.dovecot.org/dovecot-1.1/rev/a0693aec0245
- Steven
Steven Winikoff
2) recompiled dovecot without optimization (ie, gcc -O0 instead of -O2)
(as per http://www.mail-archive.com/dovecot@dovecot.org/msg12936.html)
The problem here turned out to be a bug in Sun CC (and gcc -O2
apparently worked after all, so maybe a problem with testing).
Thanks. I'll
On Oct 10, 2008, at 9:22 PM, Steven Winikoff wrote:
I had hoped v1.1.3 would have fixed this. But perhaps this is also
related to the disk quota issues. Are there any other errors that are
logged before the assert?
Nothing obvious, I'm afraid. For example, this occurence is typical
of
the
[...]
Oct 8 13:56:40 alcor dovecot: Panic: imap[15143] USER4,
NNN.NNN.NNN.NNN: file index-mail.c: line 1091 (index_mail_close):
assertion failed: (!mail-data.destroying_stream)
Hmm. I think I thought of a different assert before when commenting.
This assert should be fixed by 1.1.4 /
On Tue, 2008-09-30 at 02:08 -0400, Steven Winikoff wrote:
Sep 30 00:09:56 alcor dovecot: pop3[5006] , NNN.NNN.NN.NNN: Corrupted
transaction log file /home//.imap/INBOX/dovecot.index.log: record size
too small (type=0x40, offset=12224, size=0)
..
I've been working around the
I've been working around the problem by deleting the contents of
~user/.imap for affected users, but I'd really prefer to fix it
properly. :-) Any suggestions would be gratefully received.
I think this should get fixed by itself? Although the first login fails,
the next one should succeed.
I recently upgradeded dovecot on one of our servers from version 1.0.10
to version 1.1.3. Ever since, we've been seeing occasional errors
similar to this sequence (with the username and IP addresses elided):
Sep 30 00:09:56 alcor dovecot: pop3-login: Login: [4954], ,
NNN.NNN.NN.NNN
