Also note that if the message that gets the connect timeout is an error message, it is "Unfrozen by errmsg timer" and retried at the normal retry intervals. If it is not an error message though it is not retried.
Also please see A. Wik's post "[Exim] Frozen deferred messages" which I just now saw that looks to ask the same question I'm asking here :)
> -----Original Message-----
> From: Mike Bethune
> Sent: Tuesday, April 13, 2004 1:29 PM
> To: exim-users@???
> Subject: [Exim] frozen after connect timeout
>
>
> Hello,
> I'm not sure if this is expected behaviour, but it doesn't
> seem right to me.
> I get a lot of these:
> smtp transport process returned non-zero status 0x000e:
> terminated by signal 14
>
> I understand that to mean there was a timeout (caught
> SIGALRM), which seems normal and consistent with the option I
> have set for connect_timeout, and I can also verify that the
> connection does actually timeout when trying it manually.
> But the problem is that message is always frozen after this
> and so no retries are attempted until timeout_frozen_after is
> reached and the message is removed. Shouldn't normal retry
> rules apply to this condition?
>
> Relevant options I have set:
> - timeout_frozen_after = 2d
> - the transport has set:
> connect_timeout = 1m
> command_timeout = 1m
> data_timeout = 1m
> final_timeout = 1m
> - default retry config
>
> Should I have to set auto_thaw?
> Noticed the issue with 4.24, upgraded to 4.31 and see the same.
>
> Thanks,
> mike
>
> --
>
> ## List details at
http://www.exim.org/mailman/listinfo/exim-users Exim details at
http://www.exim.org/ ##
