How to stop "RESOLVER.ADR.ExRecipNotFound; not found ##" bouncbacks

The CEO is getting these errors as he has sent emails to several users and included a user no longer in the company (Meaning that email no longer exists) But he still from time to time received emails from exchange (Bounce backs). How can I get it to stop? Its emails that were sent months ago and he is still getting these bounce backs below?

From: Microsoft Outlook <MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@Abc.com<mailto:MicrosoftExchange329e71ec88ae4615bbc36ab6ce41109e@Abc.com>>
Date: November 8, 2013 at 2:11:23 PM EST
To: <WMM@Abc.com<mailto:WAM@Abc.com>>
Subject: Undeliverable: FW: NMHC Update: New White Paper Outlining Key Copyright and Music Licensing Principles Available


Delivery has failed to these recipients or groups:

JOHN SMITH<mailto:IMCEAEX-_O%3DTHE%2B20ABC_OU%3DEXCHANGE%2B20ADMINISTRATIVE%2B20GROUP%2B20%2B28FYDIBOHF23SPDLT%2B29_CN%3DRECIPIENTS_CN%3DJSMITH@Abc.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: DH8.Abc.com<http://DH8.Abc.com>

IMCEAEX-_O=THE+20ABC_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=JSMITH@Abc.com<mailto:IMCEAEX-_O=THE+20ABC_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=JSMITHJ@Abc.com>
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from DH8.Abc.com<http://DH8.Abc.com> ([fe80::8818:8e72:ebe0:ca46%13])  by DH8.Abc.com<http://DH8.Abc.com> ([fe80::8818:8e72:ebe0:ca46%13]) with  Microsoft SMTP Server id 14.01.0355.002; Fri, 8 Nov 2013 14:11:23 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: "WMM" <WMM@Abc.com<mailto:WMM@Abc.com>>
To: SS <ss@Abc.com<mailto:smorris@Abc.com>>, JOHN SMITH
        <IMCEAEX-_O=THE+20ABC_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=JSMITH@Abc.com<mailto:IMCEAEX-_O=THE+20ABCOU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=JSMITH@Abc.com>>
Subject: FW: NMHC Update: New White Paper Outlining Key Copyright and Music  Licensing Principles Available
Thread-Topic: NMHC Update: New White Paper Outlining Key Copyright and Music  Licensing Principles Available
Thread-Index: AQHO3LZQEm6q9mpxHUihVhzwon9iMQ==
References: <0.0.0.66.1CEDCB5F8516826.273FD@mail78.magnetmail.net<mailto:0.0.0.66.1CEDCB5F8516826.273FD@mail78.magnetmail.net>>
In-Reply-To: <0.0.0.66.1CEDCB5F8516826.273FD@mail78.magnetmail.net<mailto:0.0.0.66.1CEDCB5F8516826.273FD@mail78.magnetmail.net>>
X-MS-Has-Attach:
X-MS-Exchange-Inbox-Rules-Loop: wmm@abc.com<mailto:wmm@abc.com>
X-MS-TNEF-Correlator: 823646ce-2101-4f49-9521-600e43752066
MIME-Version: 1.0
Date: Fri, 8 Nov 2013 14:11:23 -0500
Message-Id: <288009d0b57f418d83076e518d982256@DH8.Abc.com<mailto:288009d0b57f418d83076e518d982256@DH8TYDN1-VS2.Abc.com>>
IT_FanaticAsked:
Who is Participating?
 
IT_FanaticConnect With a Mentor Author Commented:
He wasnt a delegate but I looked at all the rules in the CEOs mailbox and it forwards that user some emails. So the issue was due to being in a forward rule on OWA.
0
 
Simon Butler (Sembee)ConsultantCommented:
You can't stop them, other than telling users to stop sending to invalid addresses.
There isn't a way to stop Exchange from generating them.

The most common reason for this error is auto complete information being used - so clearing out the entries from there would probably help.

Simon.
0
 
IT_FanaticAuthor Commented:
That's the thing.  The user does not send emails to this user.  These messages are coming from emails that were sent a while back from what he says.  I've deleted the users email from his contacts so he does not select it by mistake
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Simon Butler (Sembee)ConsultantCommented:
That can only mean it is a delegate somewhere and needs to be tracked down.

Simon.
0
 
IT_FanaticAuthor Commented:
Any ideas on how to accomplish this?
0
 
Leon FesterSenior Solutions ArchitectCommented:
User the message tracking tool on Exchange and specify the failed recipients' email address and a date range overlapping the times that the emails were sent so then you should pickup who sent it.

N.B. Don't enter anything under the sender's email address.
0
 
IT_FanaticAuthor Commented:
This is what worked for me
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.