Bug#1004740: exim4: SIGSEGV (maybe attempt to write to immutable memory) when sending a mail; message frozen

Vincent Lefevre vincent at vinc17.net
Thu Feb 3 02:29:24 GMT 2022

On 2022-02-02 18:20:48 +0100, Andreas Metzler wrote:
> Yeah from exim's POV this workes out as designed. Something very much
> unexpected happened, let's freeze the message and tell the admin. The
> message is not lost. It is still in queue.

Yes, once the issue occurs, exim works as designed. But this makes
the issue particularly problematic. Note that on a multi-user machine,
the user typically doesn't have access to the status of the queue,
so doesn't know that the mail has not been sent, and will probably
never know the reason.

> Is this reproducible, happening with a specific host?

Not reproduced yet. I wonder whether this is due to the "SMTP error
from remote mail server after DATA: 450 [S09] Try Again Later".

> Any chance of getting a coredump?

exim didn't leave a coredump. I could see that Mutt disables coredumps
after some time. I don't know under which condition.

Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

More information about the Pkg-exim4-maintainers mailing list