So, I have mail for a user that was bounced by exim
(...)
2002-08-01 05:17:40 17aEkW-0000od-00 mx9.sun.com [192.18.98.34]: Connection timed out
2002-08-01 05:20:49 17aEkW-0000od-00 mx8.sun.com [192.18.98.36]: Connection timed out
2002-08-01 05:23:58 17aEkW-0000od-00 mx2.sun.com [192.18.98.43]: Connection timed out
2002-08-01 05:23:58 17aEkW-0000od-00 == marco.walther@??? R=lookuphost T=remote_smtp defer (110): Connection timed out
2002-08-01 05:23:58 17aEkW-0000od-00 ** marco.walther@???: retry timeout exceeded
Ok, we've all seen this, but mail to him was working less than 24H previous
to that:
2002-07-31 17:33:18 17a3tx-0006Vt-01 => marco.walther@??? F=<svlug-bounces+marco.walther=sun.com@???> R=lookuphost T=remote_smtp S=5049 H=mx1.sun.com [192.18.98.31] C="250 SAA17437 Message accepted for delivery"
So, I'm trying to find out why exim gave up delivery to him before the 4
days expired _and_ a delivery worked soon before that?
(I know exim can fail someone right away if deliveries have been failing for
a while)
I have exim 4 with the standard:
begin retry
* * F,2h,15m; G,16h,2h,1.5; F,4d,8h
You can find a longer history of delivery to this receipient here:
http://marc.merlins.org/tmp/eximbounce
You'll see that there are some connection timeouts by some MXes, but MX1
also returned a lot more C="250 GAA24313 Message accepted for delivery"
Could it be that the failure cache is by MX, and that when the delivery
failed, an MX lookup didn't return MX1, and all the other MXes failed (they
apparently always do)?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@??? for PGP key
