On 07/18/03 10:30, "Phillips, Alan" <[EMAIL PROTECTED]> wrote:
>> Your downstream MTA is supposed to accept all mail from your >> MTA. That's why >> the option says ..forward ALL mail... (emphasis added). To >> resolve this >> issue, mail for domains which this external MTA is >> authoritative should be >> sent through another connector. > > Aha. Yes, I see what you mean - anything that the downstream MTA can validate > goes out using a connector set to "use DNS", which will end up in the same MTA > because the MX records will take it there, and fails here will not cause > link-downing. > > BUT - what about the case where a user types a syntactically-invalid address? > Something like "[EMAIL PROTECTED],com" (note the comma). That will also get a 550 > response from the MTA and trigger a link down.... My Outlook client won't even let me try and send a message to [EMAIL PROTECTED],com and when trying to route the same through Exchange using a POP3 client (SMTP) the Exchange SMTP refuses to accept it for delivery. So, I think[1] the risk is relatively low. [1] Not much thought admittedly, I'm in the process of building a new lab. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
