Craig, I wholly agree with the concepts of which you speak regarding the detail of network transmission.
However just because the underlying network works that way it does not necessarily follow that the application (in this case email) actually makes use of it fully or in that manner. The reason for saying this is that I believe I have a an above average grasp of the methodologies employed in network routing and address resolution. The reason for my question was that I did not appreciate routing within Exchange as well. If the mail for one of the mx records is routed to a smart host that is not responsible for that domain it will do one of two things: 1. Send an NDR 2. Route it out to a server that handles other addresses Neither of these actions is desirable as number 2 could cause many hops before the packets got to their intended recipient(if at all). I can't see MX records being referred to to resolve this as email routings works on resolved names (i.e. ip addresses) or resolving a name of a smart host to send the message to and NOT a resolution of the MX record. I think I am right here. I have not seen your thread "happy charts" (just joined this list two days ago). I will certainly look at it to see if it helps. Regards RB _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
