On 06/12/13 20:22, Anne M. Hammond wrote:
> We have configured delay_warning.
> delay_warning_condition is the default.
>
> We are not receiving a warning that a message has not been delivered after 1h.
>
> The delay_warning_condition must be wrong.
>
> root@int [/]# exim -bP | grep delay_warning
> delay_warning = 1h:4h:1d
> delay_warning_condition = ${if or {{ !eq{$h_list-id:$h_list-post:$h_list-subscribe:}{} }{ match{$h_precedence:}{(?i)bulk|list|junk} }{ match{$h_auto-submitted:}{(?i)auto-generated|auto-replied} }} {no}{yes}}
>
> Here is the exim_mainlog:
>
> +++ 1Vp0G4-0005Vz-TB has not completed +++
> 2013-12-06 12:36:13 1Vp0G4-0005Vz-TB <= admin@??? U=txadmin P=local S=558 T="testing email" for admin@???
> 2013-12-06 12:37:16 1Vp0G4-0005Vz-TB receiving.com [255.255.255.255] Connection timed out
> 2013-12-06 12:37:16 1Vp0G4-0005Vz-TB == admin@??? R=lookuphost T=remote_smtp defer (110): Connection timed out
> 2013-12-06 13:34:35 1Vp0G4-0005Vz-TB receiving.com [255.255.255.255] Connection timed out
> 2013-12-06 13:34:35 1Vp0G4-0005Vz-TB == admin@??? R=lookuphost T=remote_smtp defer (110): Connection timed out
Delay messages are only considered when a delivery is attempted. This
in turn depends on your retry configuration and your queue-runner
activity.
You log shows a first delivery retry at just under an hour. Since you
have configured to send a warning only after one hour, one would not
be sent as a result of this delivery attempt failing.
I'll see about clarifying the documentation for this.
--
Cheers,
Jeremy
