asked on 2/28/2007

Diagnostic-Code: smtp;550 No such address

One of my users is send a message to another user on another domain and the message is bouncing back. Now I personally don't have access to my exchange mail server thus I can't verify logs to make further analysis, however need to dig bit more so I can kick my IT a bit to do what I think they need to do. This is the error message (excluding the actual domain name for privacy purposes and all domain names are replaced with the word domain, and all domains are legally registered and the source domain uses MS Exchange 2003 and destination mail server type is unknown):

Reporting-MTA: dns;01-edge-01.domain.tv
Received-From-MTA: dns;01-casht-01.domain.TV
Arrival-Date: Wed, 28 Feb 2007 16:39:54 +0000

Final-Recipient: rfc822;user@domain.com
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;550 No such address
Remote-MTA: dns;mail12.domain.com

We all know depending on the server type that the status of 5.0.0. means few different but similar things and in this case again, the destination user address does exist, his or here's mail box is not full, and all domains in question don't have any DNS problems nor is any of them acting or attempting to act as a relaying spam capable domain.

Any feedback I can get is highly appreciated!

Regards,

Exchange

Last Comment

Sembee

3/1/2007

ASKER CERTIFIED SOLUTION

Sembee

2/28/2007

THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

sipankh

3/1/2007

ASKER

Simon, just as additional question/comment. I did some additional digging on this 5.0.0. error with action failed while advising my IT boys to check our server logs. Is there a possibility that the destination mail box might be full and the server is rejected messages due to that fact ? The reason I am asking this is the fact we can send messages to other users at this server destination (now what is interesting that the domain where we are sending messages is part of another domain [both public], however it appears that one is main domain in their infrastructure servicing the sub domain to which we are sending messages...not sure how they configured it, but as we send to user@domain1.com that bounce back error message I originally submitted for comments comes from domain2.com [again both legitimate domains and both owned by same company - large media company in US). To make it more interestin one of my users claims tey have sent to that address messaeg sin the past from other domains and it passed through, however I didn't do any independent tests yet.

If you have additional comments , they are welcome while I am digging into this more.

- SIPAnkh

Sembee

3/1/2007

If the email was being bounced due to a problem with a mailbox then I would hope it would reject the message with an error code that reflects the real reason. One of my pet hates is people who bounce email back without giving a good reason that helps the sender. It doesn't help any spammers who get the messages because they usually don't see the NDR.

If you can send email to other users at the same domain then it would appear the error is correct - so perhaps an error has been made on the recipients side. As the sender you are pretty restricted.

Simon.