Solved

Exchange NDR when sending to active user

Posted on 2011-02-15
8
705 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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
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.

 
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
 
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 43

Expert Comment

by:Amit
ID: 34904035
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

Changing a few Outlook Options can help keep you organized!
There are times when we need to generate a report on the inbox rules, where users have set up forwarding externally in their mailbox. In this article, I will be sharing a script I wrote to generate the report in CSV format.
how to add IIS SMTP to handle application/Scanner relays into office 365.
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…
Suggested Courses

617 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