On 19/06/2020 09:48, Frank Elsner via Exim-users wrote:
> Ok, it is not a repro of the initial case.
> But it is not nomal as it delays the massege.
>
> But can you explain this please
>
> 22937 tick check: 1592491915.156500 1592491548.933500
> 22937 waiting 366.223500 sec
Exim uses the system time as part of generating unique identifiers.
To do that it waits, if needed, for the granularity of the time
it is using for that purpose. That should be something in the
millisecond range. To end up having to wait for six minutes
suggests that your system time jumped backwards by that much.
Exim is not designed to work in that environment. It assumes that
time only goes forwards, and that it does move. If you are
deliberately changing the system time backwards I suggest that
at the very least you need to stop Exim first and restart after.
Even doing that could result in unintended behaviour for the
doubly-covered apparent period.
--
Cheers,
Jeremy
