Zbigniew Szalbot wrote:
>> >> Can you try to make a tcptraceroute on port 25 for the IPs of the yahoo >> MXes, it may give you a hint on where you are blocked. > > The issue is that no traceroute ever completes successfully: > > traceroute 209.191.118.103 > traceroute to 209.191.118.103 (209.191.118.103), 64 hops max, 40 byte packets > 1 * * * > 2 * * * > 3 * * * > 4 * * * > > I also tried traceroute -e 209.191.118.103. Same result. > > Our Dlink router has these two enabled: > ping-outbound ICMP: Echo (Ping) Return ICMP Errors > ping-inbound ICMP: Echo (Ping) > > No host responds to traceroute commands. Thanks! You should also ensure that traceroute works for other IPs, just in case your firewall blocks them, because echo-request,replies are not sufficient to do a successful traceroute. If they work for other IPs, then, it's probably your default gateway's fault. I suggested using tcptraceroute (not traceroute) on port 25 because this one has more chances to give you a real hint on the route your smtp packets are using.
smime.p7s
Description: S/MIME Cryptographic Signature
-- ## 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/
