#5.5.0 smtp;553 #5.1.8 Domain of sender address does not resolve

I have a client running SBS 2003.  They are hosting their own mail internallly on Exhange and everything has been fine for years.  For the last couple days one user on the domain has been getting mail rejected back intermittently from one recipient domain.  The error is "#5.5.0 smtp;553 #5.1.8 Domain of sender address does not resolve".  I've seen a lot of questions with a similar error that the domain does not exist, but this one says the domain does not resolve.

What has made this hard is it might work fine for a half hour and then all of a sudden a message will be rejected again.
accelinetAsked:
Who is Participating?
 
accelinetConnect With a Mentor Author Commented:
In the process of having our T1 provider get the reverse DNS in place I checked the domain one more time with dnsstuff.com and it showed the reverse DNS to be just fine.  The T1 tech support guyhad not yet made any changes.  I think the culprit of the issue was a third party mail scanning service who seemed to be having DNS issues.  Although the issue they noted didn't seem to include our configuration it seems rather coincidental that our problems started when theirs did and normal service resumed when they fixed things on their end.

I'm not sure what to do with points on this one.  Thank you both again for your fast response and willingness to assist.
0
 
tjdabombCommented:
a user specific dns issue, sounds like.  have their AD credentials been changed recently?
0
 
Alan HardistyCo-OwnerCommented:
Please check the Sending domain to make sure it is configured correctly (if it is RCC Compliant), which my article should help you to achieve:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/A_2427-Problems-sending-mail-to-one-or-more-external-domains.html
0
Cloud Class® Course: C++ 11 Fundamentals

This course will introduce you to C++ 11 and teach you about syntax fundamentals.

 
accelinetAuthor Commented:
tjdabomb - No, the user's credentials have not changed.

alanhardisty - a check on the domain showed no reverse dns entry so I'm working with out T1 provider to get that in place now.  I'll report back once that's complete.

Thank you both for your prompt responses.
0
 
Alan HardistyCo-OwnerCommented:
No problems - will await your feedback.

Alan
0
 
tjdabombCommented:
good luck, acce
0
 
Alan HardistyCo-OwnerCommented:
Good that the problem is solved.

Based on what you have said - we didn't solve the problem for you as the problem wasn't yours to fix.  You should accept your last comment as the solution as you have provided the 'fix' albeit not in your control but good for anyone in the future who finds this question and has a similar issue.

Alan
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
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.

All Courses

From novice to tech pro — start learning today.