Link to home
Start Free TrialLog in
Avatar of kam_uk
kam_uk

asked on

Exchange NDR when sending to active user

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.
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

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.
Avatar of kam_uk
kam_uk

ASKER

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?
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?
Avatar of kam_uk

ASKER

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?

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.
ASKER CERTIFIED SOLUTION
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Obviously change the domain.com part to reflect your domain name that you obscured.