[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 733
  • Last Modified:

Delivery failure when sending mail to specific domain with exchange 2003

I have a problem with sending mail to a specific external domain from exchange 2003. Mail sent to any address at that domain just sits in a queue until it eventually generates an NDR with status number 4.4.7.
The error message for the queue just says 'An SMTP protocol error occurred'
I found a couple of kb atticles relating to this error but they seem to be about open relays and I know the exchange box is not an open relay.
I can send mail to this domain from a hotmail account so I know the address is correct.
I'm new to exchange 2003 so I'm a bit stuck as to where to look.
Any suggestions?
0
howardphillis
Asked:
howardphillis
  • 6
  • 3
1 Solution
 
MicrotechCommented:
can you trace a route to the domain... find out how many hops there are to it from your domain... if there are too many then we can up the hop count

can you telnet to the server in question... if you can then we can troubleshoot some more. http://support.microsoft.com/default.aspx?scid=kb;en-us;153119

my first guess would be the hop count as in this doc http://support.microsoft.com/default.aspx?scid=kb;EN-US;284204
0
 
howardphillisAuthor Commented:
OK, I can telnet to the server and get the following results:
If I try to send mail to either the domain in question or to a hotmail address then I get a 550 unable to relay error
I can send to an internal address without problems

I've checked the MX records for the domain in question and mail is handled by smtp-antivirus.clara.net and mail2.clara.net
When I ran a traceroute to either of those servers fqdn or IP address using NetscanTools it failed. It also failed using the Mac OS X Network utility and a couple of online traceroute services.
What I dont understand is how I managed to send mail to that address from a hotmail account.
I could increase the max hop count to 30 but I can't really see it making a difference.
0
 
MicrotechCommented:
sorry the hop count was from the line above..got mixed up on the error message.

how about trying this ....setup a connector in Routing groups. you don't need to use the connector for all domains. If you drop the * and enter aol.com, hotmail.com, yahoo.com etc to the list  the connector will be used for just those domains.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
MicrotechCommented:
0
 
howardphillisAuthor Commented:
RDNS sounds interesting. Just one question - is it a setting you can switch off in exch2003 or is it on our internal DNS server? We currently have no Reverse Lookup Zones configured so I'm not quite sure how I would switch it off.

As for the Routing groups suggestion I remember having some success when I had a similar problem in Exchange 5.5 so I'll give it a try and report back
0
 
MicrotechCommented:
go to http://www.dnsstuff.com and do the reverse lookup test
You might also want to look at http://www.dnsreport.com and see how your domain looks.

0
 
MicrotechCommented:
if you have no PTR record then get your isp to set this up for you.
0
 
howardphillisAuthor Commented:
there is a ptr but it doesn't seem to be correct.

The MX record shows that mail for mydomian.com is handled by mail.mydomain.com

If I do a Reverse DNS lookup for the IP of mail.mydomain.com I get

111.111.111.111 PTR record: host-111-111-111-111.myisp.com

which seems wrong to me
0
 
MicrotechCommented:
you could try and set up a SMART host for this domain http://support.microsoft.com/default.aspx?kbid=297988&product=exch2k see how you go after that?
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now