It means exactly what it says (and 550 isn't terribly generic). Domain.com is not a local host on the server you connected to and that server is also not a gateway for it. Either your DNS is fscked or one or more of their Mx records is improperly configured. Using telnet and the basic SMTP commands in RFC821 will allow you to confirm this for yourself if you'd like.[1]
[1] Essential skills to pick up, now is as good a time as any. On 2/12/03 7:42, "Jeffrey Dubyn" <[EMAIL PROTECTED]> wrote: I have an issue with an Exchange 2000 SP3 server where an email sent from inside the Exchange organization is not getting to some recipients in a specific domain. I have logging turned up, and found a strange message: 550+not+local+host+recipientdomain.com,+not+a+gateway The 550 error maps to a generic protocol error (SMTP error), but I can't make heads or tails out of the rest of the message. What is strange is that the domain comes up successfully in nslookup and from the Exchange server, I can connect via telnet to port 25. The users have had no trouble sending email to this recipient at this domain before or since, except for this most important email (or course). There was no NDR, no nothin' - just seems like the email went into a black hole. Thanks for any assistance! _________________________________________________________________ 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] _________________________________________________________________ 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]