Also, nslookup -q=mx shirevalleydesign.com from my workstation failed the first time but worked the 2nd - mxtoolbox (www.mxtoolbox.com) failed 3 or 4 times, then worked when looking up the MX.
Not completely propagated yet? Or slow DNS response? -----Original Message----- From: Don Andrews [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:39 PM To: MS-Exchange Admin Issues Subject: RE: Hosting Multiple domains in Exchange 2003 It looks to me like bellsouth.com uses messagelabs. bellsouth.com MX preference = 20, mail exchanger = cluster7a.us.messagelabs.com bellsouth.com MX preference = 30, mail exchanger = cluster7b.us.messagelabs.com bellsouth.com MX preference = 10, mail exchanger = cluster7.us.messagelabs.com not sure where you got mail.bellsouth.com -----Original Message----- From: Jonathan Gruber [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 2:18 PM To: MS-Exchange Admin Issues Subject: RE: Hosting Multiple domains in Exchange 2003 DomainB is shirevalleydesign.com DNS entries are correct as far as I can tell. ESM error message is "An SMTP protocol error occurred." I get a delay message and then a failure message "Could not deliver the message in the time limit specified." I can't telnet into mail.bellsouth.net from that server, but I also tried to telnet from a different location and couldn't there either. Jonathan Gruber Network Administrator J.B. Long Inc. 610-944-8840 x.213 484-637-1978 direct -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 11:18 AM To: MS-Exchange Admin Issues Subject: Re: Hosting Multiple domains in Exchange 2003 On Fri, May 23, 2008 at 11:20 AM, Jonathan Gruber <[EMAIL PROTECTED]> wrote: > A user has sent an email to a bellsouth account using domainb which is > also hosted on this server and the mail is timing out. What's the exact error message? Have you checked Event Viewer for more info? Have you tried using Exchange SMTP diagnostic logging? Have you tried doing the SMTP dialog manually with the TELNET command? > When a test is sent from domain to the bellsouth.net > address it goes through, so I assume that the reverse dns lookup bellsouth > is doing is failing. That doesn't sound like a reverse lookup issue. Reverse lookup is done against the IP address of your mail server. If the problem was with that, it would affect all mail sent from your mail server, regardless of the sender domain name. It might be that the forward lookup of your "domainb.com" is slow or faulty. Many SMTP servers check the name submitted in MAIL FROM for validity, so a DNS problem there can cause trouble. If you let us know the actual "domainb.com", we could check it. -- Ben ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~