Doug Denault:
> > This command:---------+
> >
> > postcat -eq 7883F510EBC | grep warning_message_time
> >
> > If the output is empty, then you did not enable delay warnings.
> >
> > You may have to specify a different queue ID than 7883F510EBC, if
> > that message has already been returned to the sender.
>
> Thank you. It is not empty but I am not sure what I am looking at:
>
> postcat -eq 7883F510EBC | grep warning_message_time
> warning_message_time: Wed Dec 31 18:59:59 1969
This means that the warning message was already sent (assuming that
bounce messages haven't been disabled).
When delay warnings are enabled, the warning_message_time contains
a time in the future (time in seconds since 00:00:00 01/01/1970
UTC).
Once the warning is sent (assuming that bounce messages haven't
been disabled), the warning_message_time is reset to -1, i.e. one
second before 00:00:00 01/01/1970 UTC.
The warning may not have been sent because bounces are disabled
(with NOTIFY=NEVER, or by messing with the master.cf definition for
the bounce service).
Or the warning may have been sent but not logged, because systemd
rate limits makes logging disappear.
Wietse
