#550 5.1.1 RESOLVER.ADR.RecipNotFound

When I try to send an email to an external address (different domain), my Exchange 2007 Server replies with the NDR below. I can send to other recipients at that external domain, just no to this specific user. I am also not able to send it from OWA.  Any Ideas?

Thanks in advance

Diagnostic information for administrators:
Generating server: MyDomain.COM
#550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ##
Original message headers:
Received: from MyDomain.COM ([fe80::3842:f81e:b98:ffb4]) by
 MyDomain.COM ([fe80::3842:f81e:b98:ffb4%10]) with mapi; Fri, 1 May
 2015 07:56:53 -0800
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Tracy Thomas <Sender@MyDomain.com>
To: "USER@OtherDomain" <USER@OtherDomain>
Date: Fri, 1 May 2015 07:56:52 -0800
Subject: test
Thread-Topic: test
Thread-Index: AdCEJ2/cH6f2ja69QL6apvN2g4yppg==
Message-ID: <558C49C134BA9340B71221CC29728ED1925E54D36A@MLA03.MAPPINGALASKA.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-TNEF-Correlator: <558C49C134BA9340B71221CC29728ED1925E54D36A@MLA03.MAPPINGALASKA.COM>
MIME-Version: 1.0
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Michael MachieIT SupervisorCommented:
It looks like it is something as simple as the address (on that domain) is not a legit address. For instance, if you are trying to email Pault@domain.com but Paul's address is actually ptuttle@domain.com, you will get that message. You would still be able to send emails to that same domain but the individual's address is not correct.

To fully identify if this if you or them, you can call the person and verify the address is correct or send another email from a different email domain to that address and see if it bounces back. If so, it would def be a wrong address issue.  

The message is specifically saying that the particular email address you used is not found on the receiving server.
mapalaska2003Author Commented:
I verified the address. Something on my server seems to be the problem. Any other ideas?
Michael MachieIT SupervisorCommented:
I also recently had a similar but different issue and discovered it to be related to a TLS 1.0 request that was failing - It was the same exact message.

Someone was sending an email to one of the Domains I support and they kept receiving that message when sending to my supported Domain. It ended up being specific to that one User and was related to a TLS 1.0 request being sent by his email to our Domain and our Domain rejected it.

It was only a single User not within my supported Domain and that person ended up leaving their employment after only a short time. I did nothing about it and have never heard of anything like that from anyone either before, or since. I suppose it could be related to the Server certificate they have on their email Server not supporting a TLS 1.0 request because I heard recently that any Domains with a .local in their internal Domain name (ie/ domainname.local) will have these TLS 1.0 request issues starting this year.

Perhaps that is the problem?
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

You need to configure reverse DNS (an PTR record in the DNS). In some cases this have to be done by the ISP
Michael MachieIT SupervisorCommented:
@matrix8086: Would you please clarify why this would be the case? In my instance we have the PTR record in DNS and still had the issue with someone emailing one of my Domains. I am interested in hearing more about that.
mapalaska2003Author Commented:
I don't understand why Id need to change anything in the DNS. I can send mail to everyone else at that domain, just this one user is the problem. I've checked the users Gmail account as I have administrative access to it.

I have added the user as a Contact in Active Directory, but that did not work either.
I will explain mail + reverse DNS. Every mail server can be configured to check reverse DNS when a message arrives, this is the sysadmin option.

There are spammers who send mail messages in behalf of others. If I am a spammer I will send messages in behalf of good@example.com from anywhere in the Internet, through different hacked or open relay mail servers. But the mail server mail.example.com have only one unique IP address (let's say and there are sysadmins who tell their mail servers: when a message arrive check if the IP is corresponding with real name (this is the reverse DNS which assume a PTR record in the DNS zone). So in this case, when such a mail server receive a message from good@example.com, it checks if -> mail.example.com. If a spammer send an email in behalf of good@example.com from IP, the receiving mail server check the IP (in fact it checks at the first moment when sending server ask for connection)  and discover another name, or nothing (I will comeback at "nothing") and drop the connection. Te sending server think that the recipient sever does not respond (is down, don't exist, etc).

But if example.com has no PTR record (no reverse DNS, which means "nothing" from above)  it won't be able to send messages to such mail servers which check for reverse DNS, because the recipient server receive no answer of reverse DNS request (and it is considered spammer even if is not!) - and that could be the case of mapalaska2003.

But if thats's not the case and the user address is correct, then it could be only one problem: the receiver has a big infrastructure with more than one mail server and somehow in that infrastructure the routing path to the user is broken. It can be happening when a user mail database is moved from a server to another or some changes occurs in that infrastructure.

As 550 5.1.1 is described by Microsoft, this last paragraph seems to be the case.

But as I type I know how to check this: if it is a reverse DNS issue, the error is received after a while (by default 4 hours, because the sender don't find the recipient server). If it's a user issue on the other/recipient side, the error occurs in few minutes
Best regards!

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
mapalaska2003Author Commented:
Thanks for the info Matrix.

I do have some more information however. If I use an email account outside of my domain, it delivers fine (ie: Yahoo).

There are other users on the external domain that can receive it just fine. I created a test account on the external domain and it failed as well.

It's got to be something in my domain / Exchange that's causing this.
mapalaska2003Author Commented:
I figured it out. Since there are users within my domain that also have email accounts on the external domain and use Outlook for both accounts. I had to add the external user as a Mail Contact in Recipient Configuration in the Exchange Management Console. That took care of it.

Thanks to Both of you.
Michael MachieIT SupervisorCommented:
Nice job geting to the bottom of it.
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

From novice to tech pro — start learning today.