----- Original Message -----
From: "Daniel Einspanjer" <daniel-ml@???>
To: <exim-users@???>
Sent: Sunday, May 13, 2001 1:19 AM
Subject: [Exim] Delivery failure to fedex.com
One of my mail clients is trying to send mail to a person at fedex.com. He
regularly gets bounces on most of the mail he sends out, but occasionally it
goes through. It goes through when it tries the MX record with a 300
preference, but exim does not appear to regularly try this record. Could
anyone help me out with this?
Here is what I have discovered so far in my examination:
1. fedex.com has three MX records numbered from 100 to 300 in priority.
They are
fedex.com preference = 100, mail exchanger = mapper.mail.fedex.com
fedex.com preference = 200, mail exchanger = smtp.zmd.fedex.com
fedex.com preference = 300, mail exchanger = smtp.dmz.fedex.com
2. All of the failures are Connection Refused, and they are to the first two
addresses. (mapper and zmd).
3. All of the successful deliveries go through the last one, dmz.
4. I am running with the default retry rule: * * F,2h,15m; G,16h,1h,1.5;
F,4d,8h
5. Exim does not appear to be paying attention to this retry rule.
As far as I can tell you're doing nothing wrong, attempting to telnet to
the Fedex mail servers gives:
[mike@gate mike]$ telnet mapper.mail.fedex.com 25
Trying 199.81.10.25...
telnet: connect to address 199.81.10.25: Connection refused
Trying 199.81.10.26...
telnet: Unable to connect to remote host: Connection refused
[mike@gate mike]$
which is consistent. So either (a) their servers are broken or (b) they
have over zellous firewall rules and accept connections from a very
few.
If host "smtp.dmz.fedex.com" works well for you, then you might consider
adding a hardwired route in the Exim configuration, something like:
broken_fedex:
driver=domainlist
transport=remote_smtp
route_list="fedex.com smtp.dmz.fedex.com bydns_a"
near the start of the "routers section". You should then be able deliver to
the
third host reliably, this will allow you to complain about them being
broken....
Mike
