users are getting NDRs for an Exchange 2013 on premises organization after migrating from 2010 to 2013

Hello Experts,

I have a client who recently migrated from Exchange 2010 to Exchange 2013. As per the client, the migration was completed successfully, however some users are getting NDRs. This company is using EOP as Microsoft gateway spam inbound/outbound.
 
Any ideas?

It looks like the email address is wrong, but we have checked  user's email address on the exchange server and is correct. No misspending, perhaps something at the EOP?

Delivery has failed to these recipients or groups:

XXXXX.XXXXXX@DomainReceivingemail.com
The e-mail address you entered couldn't be found. Please check the recipient's e-mail address and try to resend the message. If the problem continues, please contact your helpdesk.


Diagnostic information for administrators:

Generating server: mailboxserver2.EMAILDOMAIN.com

xxxx.xxxxx@DomainReceivingemail.com
#< #5.1.1 smtp;550 5.1.1 RESOLVER.ADR.RecipNotFound; not found> #SMTP#

Original message headers:

Received: from VPIDEXS804.kzlnet.com (172.20.17.214) by APIMBX2.apinw.com
 (10.10.0.133) with Microsoft SMTP Server id 15.0.847.32; Wed, 14 Jan 2015
 19:09:37 -0500
Received: from VFLLEXS804.kzlnet.com (172.18.8.108) by VPIDEXS804.kzlnet.com
 (172.20.17.214) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 14 Jan
 2015 19:10:47 -0500
Received: from VFLLMBX810.kzlnet.com ([fe80::1ce5:23d:ac1b:3acf]) by
 vFLLEXS804.kzlnet.com ([172.18.8.108]) with mapi id 14.03.0195.001; Wed, 14
 Jan 2015 19:10:46 -0500
From: Murugan Sivaraj <xxxxxx@DomainSendingemail.com>
To: Irfan.Sajil <irfan.sajil@DomainReceivingemail.com>
CC: Amauris Rodriguez <xxxxx.xxxxx@DomainReceivingemail.com>, Rick.xxxxx
      <Rick.xxxx@DomainSendingemail.com>, Norman.Green <xxxxx.xxxxx@DomainSendingemail.com>,
      xxxxx.xxxx <xxxxx.xxxx@DomainReceivingemail.com>
Subject: RE: Emails from xxxxx
Thread-Topic: Emails from xxxxxx
Thread-Index: AdAwR3z1Ox0mv7BgSwCSITBlx8yH1wACQiiQAADGmsAAAAX7EAAAPyZSAABaUOIAACnmlAAAAZvA
Date: Thu, 15 Jan 2015 00:10:45 +0000
Message-ID: <E7A9224AD89A074181FFFE5208D7245C3CB4CDF4@vFLLMBX810.kzlnet.com>
References: <ee9bb4bd239f462393093d5485038555@APIMBX1.apinw.com>,<F1302857D42CFE458073B849114BFF1A0160F86FA4@PIDMBX801.kzlnet.com>
 <EC59EF4447729B41AFD0EB173D615D60015BD3977C@vFLLMBX810.kzlnet.com>,<E7A9224AD89A074181FFFE5208D7245C3CB4CD93@vFLLMBX810.kzlnet.com>,<EC59EF4447729B41AFD0EB173D615D60015BD397D3@vFLLMBX810.kzlnet.com>,<gbvqdsighrsti4s5wmdi83ki.1421279653939@email.android.com>
 <12A1F78B-F977-4BF2-8DF8-AE82DF235884@DomainReceivingemail.com>
In-Reply-To: <12A1F78B-F977-4BF2-8DF8-AE82DF235884@DomainReceivingemail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [172.18.16.2]
x-exclaimer-md-config: 2b2470de-eb1d-4d36-ac8e-37eb757a4387
Content-Type: multipart/related;
      boundary="_009_E7A9224AD89A074181FFFE5208D7245C3CB4CDF4vFLLMBX810kzlne_";
      type="multipart/alternative"
MIME-Version: 1.0
Return-Path: ssss.sss@DomainSendingemail.com
X-EXCLAIMER-MD-CONFIG: c2d0f4dc-cad3-4be7-b3f5-fd40a796e412
X-EXCLAIMER-MD-CONFIG: c9713400-f91f-49ba-b323-5ee43730ca61
Jerry SeinfieldAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Vasil Michev (MVP)Connect With a Mentor Commented:
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
You said this only happens to for some users? Have you tried to cleanup the NickName (auto complete) cached in Outlook?

If you specifically select the user from the GAL does this happen?

Will.
0
 
Jerry SeinfieldAuthor Commented:
Hi Will,

Just to clarify, the NDR above was generated when an external user sent email to my internal user[my client]

My client wants to know why. It seems like either Microsoft EOP is not recognizing his email address, or perhaps something else?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Will SzymkowskiSenior Solution ArchitectCommented:
Ah...sorry didn't see that. Can you try this.
- have the internal user send an Email to the external user
- have the external user replay back to the email

Does this work?

Will.
0
 
Vasil Michev (MVP)Commented:
Message doesnt reach EOP according to the header info. Does it happen only when replying? Did you clear the name cache as Will suggested above?
0
 
Jerry SeinfieldAuthor Commented:
what do you mean by clearing the name cache?
0
 
Jerry SeinfieldAuthor Commented:
Vasil, that link is broken
0
 
Vasil Michev (MVP)Commented:
Hm, works for me. Try looking it up on some search engine, the article title is "How to reset the nickname and the automatic completion caches in Outlook"
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.