Morning all, I had a complaint from a customer of a bounce from our backup MX this morning following a apparently transient routing burp. I was wondering if anyone knew a way to catch "No route to host" errors and having exim apply its normal retry rules on that message.
The log entries looked like: 2009-09-04 07:19:30 1MjT50-0005G2-Ng <= local_p...@yahoo H=(web23704.mail.ird.yahoo) [87.248.115.62] P=smtp S=2236 [email protected] 2009-09-04 07:19:33 1MjT50-0005G2-Ng a.mx.customer.domain [89.16.x.x] No route to host 2009-09-04 07:19:34 1MjT50-0005G2-Ng == [email protected] R=dnslookup T=remote_smtp defer (113): No route to host 2009-09-04 07:19:34 1MjT50-0005G2-Ng ** [email protected]: retry timeout exceeded 2009-09-04 07:19:34 1MjT50-0005G2-Ng Completed Having had a look at the docs, it appears that such an error isn't listed amongst the specific errors for retry rules. At the moment our rule looks like # Domain Error Retries # ------ ----- ------- * * F,1d,15m; F,1w,2h and we're running Exim 4.63. Thanks! -- Patrick J Cherry Bytemark Hosting Support http://www.bytemark.co.uk/ tel: +44 (0) 1904 890 890 -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
