Re: [nznog] Continued problems with xtra email

On 1/09/2007, at 8:35 PM, Hamish MacEwan wrote:

On 8/31/07, Joe Abley wrote:

...

[A] --------- [B] \ / X / X / \ / [C]

[A], [B] and [C] are different networks on the Internet. I have a priority-0 MX installed at [A], and another one at [B]. The MX at [A] has a lower number in its RDATA than the one at [B] (i.e. the one at [B] is the backup).

Suppose some device at [C] tries to send me mail, and at the time it chooses to attempt delivery, there's a network problem which prevents traffic from getting through. It instead delivers to the backup MX at [B]. There is no network problem between [B] and [A], so mail is forwarded on straight away.

I'm just curious what reasons, and they may be myriad, explain why SMTP will route around the damage using the MX priority, but TCP/IP won't? Ie, I can send mail where I can't send a packet?

IP doesn't have the ability to re-route, routing protocols (BGP, OSPF, IS-IS) etc. that are built on top of IP, do. If these hosts are all in different ASes, A or C simply may not have a route for one another, due to damping, prefix lists being broken, etc. -- Nathan Ward