SMTP Mail and Exchange Issue

We have two sites that we look after who are experiencing email problems.

Only a select number of senders who send mail to either domain get the following response after they have sent an email to the intended...

recipient@domain_name.co.nz
    SMTP error from remote mail server after RCPT
TO:<recipient@domain_name.co.nz>:
    host mx.clear.net.nz [IP_ADDRESS]: 501 #5.1.1 bad address
recipient@domain_name.co.nz

I've Googled this to there and back but nothing of much use.

I spoke to the ISP and they made changes to the A and MX Records and stated the problem would fix itself 3 to 24 hours when the changes had propagated whatever it needs to update. They said the issue was down to the MX record not pointing correctly to the A record.

The affected senders then experienced that not only was thier mail not making the destination but they were now not getting a reply to say so. All the while the majority of senders were having no issues at all.

I phoned the ISP again. They said they found another mistake and had rectified it. The affect was almost immedicate and now the organisations are receiving no mail at all!

Out of curiosity I downloaded a wonderful DNS look up tool called Dig. I entered the domain name for one of the affected companies and found it could not resolve the domain name to an IP address. Same happened for the other. I tried domains for other organisations, both customers and non-customers and in every case Dig was able to resolve the domain name to an IP address. So I added smtp to the domain name for the affected companies so it looked something like this smtp.domain_name.co.nz - surprise surprise! The domain names can be resolved now.

So what is broken? Is it Exchange at each of the sites or is it their ISP???

Anyone?
MSLCNSAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PowerComputersCommented:
Check the REVERSE DNS lookup for the problem domain. Some ISPs require a successful Reverse DNS lookup when relaying smtp traffic. Go to http://www.dnsgoodies.com, they have great DNS tools.

As for your ISP the smtp.domain_name.com record is irrelevant if it is not the MX record target. From a command prompt, run NSLOOKUP enter
SET TYPE=MX  enter
type DOMAIN_NAME.COM  (use the domain name in question, don't use a prefix)
this will return the domain's MX records in order. make sure the lowest number, usually 10, matches the A record and IP address of your mail server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MSLCNSAuthor Commented:
It seems propogation took a lot longer than 24 hours. With changes made to the MX record the issue did eventuall come right. Thanks for reponding.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Internet / Email Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.