On 30/06/2020 16:01, Marc Haber via Exim-users wrote: > Is this the possible cause of the issue showing up on at least three
> Debian systems since we upgraded to exim 4.94?
It does sound plausible that it is related.
How was the message given exim - command-line or smtp?
Was it first given to exim before, or after, the suspend/resume?
How long was the suspend?
How long did you wait, in the hung-at-final-dot condition, before
using pkill?
An experiment of a short suspend, and waiting for longer than that,
would be of interest - assuming the issue can be created on demand.
I'm not a regular user of suspend myself, and don't trust it to
function well enough on this system. If you can easily repro and
are prepared to build & test variants, this would be useful.
Even just disbling the CLOCK_MONOTONIC code would be a good step.
--
Cheers,
Jeremy