Hi everyone,
the attached message does reliably crash my dovecot when trying to access a folder containing it.
Crash notice in mail.log: Apr 13 17:36:12 rafter dovecot: child 23215 (imap) killed with signal 11
My dovecot --version
says:
0.99.8
Has this problem been fixed in current dovecot? For now I have just quarantined the offending message but obviously I need to upgrade my dovecot soon because I don't like such kinda things to happen.
best regards!
MW
On Sun, 2003-04-13 at 19:20, Moe Wibble wrote:
Hi everyone,
the attached message does reliably crash my dovecot when trying to access a folder containing it.
Crash notice in mail.log: Apr 13 17:36:12 rafter dovecot: child 23215 (imap) killed with signal 11
My
dovecot --version
says: 0.99.8
Well, the version number isn't really up to date currently :) Is this CVS or -test? I don't think 0.99.8.1 yet had --version.
Has this problem been fixed in current dovecot? For now I have just quarantined the offending message but obviously I need to upgrade my dovecot soon because I don't like such kinda things to happen.
I couldn't get any crashes with it, neither with 0.99.8.1 nor current CVS. It would help if you got gdb backtrace from the crash:
Set "mail_drop_priv_before_exec = yes" in config file, so it dumps core to whatever directory you started dovecot in. Hmm. Actually I think I should change to mail root dir so it's written there..
gdb /usr/local/dovecot/libexec/dovecot/imap core bt
Or alternatively:
gdb /usr/.../imap <pid of running imap process> c <wait for crash> bt
FYI: That bug was fixed a while ago. After upgrading to latest CVS everything is fine now.
regards
MW
participants (2)
-
Moe Wibble
-
Timo Sirainen