Solved

Exchange NDR when sending to active user

Posted on 2011-02-15
8
698 Views
Last Modified: 2012-05-11
Some (but not all) of my users are getting the following NDR when trying to email a user:

Fred Jones
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

IMCEAEX-_O=EXCHANGE_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Fred+2EJones@domain.com#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Fred Jones (fred.jones@domain.com) is a valid address though which is strange. And, like I said, some users can email him fine.

Can anyone shed any light on this? Running Exchange 2007/ Outlook.
0
Comment
Question by:kam_uk
  • 5
  • 2
8 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34901661
he problem here is likely that the people sending the mail that is getting rejected are using the auto-complete address which is cached in Outlook but that the user has changed on the Exchange Server and the Autocomplete cache has not been updated, so it is trying to send to the wrong internal address and this is being rejected.

If the senders type in the full email address (not using autocomplete), or pick the address from the GAL, can they send happily?

If so - get them to delete the entry from the autocomplete by starting to send a new message, start typing the recipient address then selecting the entry that corresponds to the right user from the list using the up and down cursor keys, then pressing the Delete key.

Should be problem solved.
0
 
LVL 3

Author Comment

by:kam_uk
ID: 34901719
Tried it on my laptop, which was having the problem...yes, if I pick from GAL, then the email goes through fine.

Is this the only fix though, from the client side? Is there anything I can do on the server to fix this?
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34901741
The problem is out-of-date cached information on the client(s).  You could globally remove everyone's .NK2 files when they login, but that would be overkill for a few internal address and you would also lose any other good addresses that your users might not have saved in their contacts.

I presume the user that was being emailed and was generating the NDR was moved internally?
0
 
LVL 3

Author Comment

by:kam_uk
ID: 34901797
I'm not sure what happened to the user, they just returned from a break from the company and I thought they had been given their old mailbox and AD account back. Possibly these users getting the NDR are trying to send to a cached entry for this name, I know that's the case for me.

Can I redirect his 'old' address to his new one in anyway, set some sort of forwarding?

0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34901926
The problem is the LegacyExchangeDN attribute on the user's account.  You could change the attribute using ADSIEDIT to match the entry in your question but anyone who has emailed the user and cached the existing LegacyExchangeDN value, would then have the same problem although you would have fixed the existing users problems.

Short answer would be to advise your users of the problem and how to correct it, then let time heal the problem.
0
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 500 total points
ID: 34902020
Okay - plan B!

Add a new Email Address to the users Account - but don't add an SMTP address, add a Custom Address, Type in 'X500' (minus the quote marks) as the Type and

/O=EXCHANGE/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=Fred.Jones@domain.com

as the address.  That should resolve the issue.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 34902035
Obviously change the domain.com part to reflect your domain name that you obscured.
0
 
LVL 42

Expert Comment

by:Amit
ID: 34904035
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you unable to connect or configure Hotmail email account in Microsoft Outlook 2010, 2007? Or Outlook.com emails are not downloading to Outlook? Lets’ see the problem and resolve Outlook Connector error syncing folder hierarchy (0x8004102A).
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now