mail-storage.c:2473 assertion failed: (!ctx->unfinished) (related to antispam?)

[Aki Tuomi]

On 27.09.2017 15:44, Stephan Bosch wrote:
> Op 9/27/2017 om 2:36 PM schreef Matthijs Kooijman:
>> Hey folks,
>>
>> apologies for the useless subject on my original mail, forgot to update
>> it.
>>
>> Two more bits of info. Here's the log output related to this crash:
>>
>> dovecot: imap-login: Login: user=<2014>, method=PLAIN, rip=217.122.126.195, lip=10.42.0.13, mpid=10569, TLS, session=<IsP37ypaFYHZen7D>
>> dovecot: imap(2014): Panic: file mail-storage.c: line 2473 (mailbox_copy_int): assertion failed: (!ctx->unfinished)
>> (I've omitted the raw backtrace)
>>
>> And, I just discovered that (it seems that) whenever such a crash
>> happens, an empty /tmp/antispam-mail-xyz directory is created, which
>> makes me suspect that at least the antispam plugin is involved in these
>> imap sessions, and might the the one causing the crash. I'm running the
>> latest antispam version from Debian (2.0+20170109-1+b2, which also seems
>> to be the latest upstream).
> That sounds plausible. However, since you're using a very recent Dovecot
> now, you should consider using IMAPSieve instead:
>
> https://wiki2.dovecot.org/HowTo/AntispamWithSieve
>
> Regards,
>
> Stephan.
>
>> Gr.
>>
>> Matthijs
>>
>>
>> On Wed, Sep 27, 2017 at 02:21:09PM +0200, Matthijs Kooijman wrote:
>>> (I'm not subscribed, please keep me CC'd)
>>>
>>> Hi,
>>>
>>> since a few months I'm experiencing repeated dovecot crashes. I mostly
>>> see them in the logs, I haven't had any users complain, so I haven't
>>> looked closely until now. I was originally using an older version fro
>>> mDebian and hoped that a newer future version would already fix this,
>>> but I just upgraded to version 1:2.2.32-2 from Debian testing, and the problem
>>> persists.
>>>
>>> This crash sometimes happens occasionally, but often happens repeatedly
>>> for some time (presumably a client keeps retrying) but can also be gone
>>> for hours or days (presumably the client no longer connects). I haven't
>>> been able to definitively figure out what client causes this, but based
>>> on the user ID I suspect it is Mail.app on OSX.
>>>
>>> I managed to get a core dump, which gave me the stacktrace below. I've also
>>> attached my config file. If any other details are relevant, just ask and I can
>>> squeeze them out of the core dump (but I'd rather not publicly share the file).
>>> I can probably set up rawlog to capture the actual IMAP session if needed,
>>> though I have no time for that right now.
>>>
>>> Gr.
>>>
>>> Matthijs
>>>
>>> 51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
>>> (gdb) bt
>>>

To verify whether it's caused by antispam plugin, you could copy/move
mail to Spam folder and see if it crashes?

Aki