Exchange 2013 users receiving NDR from user within same organization

Exchange 2013 with the latest CU.

There was a situation where an Exchange mailbox was accidentally deleted.  This, of course, also deleted the AD account (why MS does this is beyond me).  So the AD account was recreated and a new mailbox made.  The user's email was recovered to a PST file from backup.  So all is good.

When the new mailbox was created, the wrong alias was used so the alias was changed.  As of now the user can send and receive emails from the outside world.  However, the user cannot receive emails from within the organization.  When someone within the organization tries to email the user, an NDR is generated.

'550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'

The user clearly has a mailbox that works with the outside world.  What can be done to fix getting this NDR from coworkers within the same org?

NOTE:  This mailbox was not migrated from another org or from a previous version of Exchange.  All searches on the Internet point to migrations being the cause which is not the case here which is why I am posting on EE.

James
JamesNTAsked:
Who is Participating?
 
Riaz Alexander AnsaryEnterprise Infrastructure Systems EngineerCommented:
As guys mentioned above its the X500 issue. I have written an article about this that will guide you step by step on how to resolve this.

https://www.experts-exchange.com/articles/32052/How-to-Edit-and-Add-a-Legacy-X500-Address-Into-The-New-Mailbox.html
0
 
Wayne88Commented:
Does it happens to all internal emails sent to this recipient or just some?  If just one then my guess is that the autocomplete in the sender's outlook still points to the old X500 address.  In this case just simply delete that autocomplete entry then retype the email address then send and it should work.

In case where a lot of senders in the organization can't send to this one recipient then you will have to add the entry for the affected mailbox account.

http://www.askme4tech.com/exchange-server-x500-address-amazing-thing-know
0
 
timgreen7077Exchange EngineerCommented:
The internal users don't email based on smtp addresses, outlook actually emails based on the x500 address. You can 1 of 2 things:

1. the internal user will need to delete the old email address from their autocomplete cache in outlook and the manually retype the address or grab it from the GAL. That will resolve it.

2. you can get the failed email that is generated, and it will should an address that looks like this:"IMCEAEX-_O=EXCHANGELABS_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT
+29_CN=RECIPIENTS_CN=827865984d33455b8a289b007a37f400.com"

you will need to convert this address correctly and then add the converted address to the email proxy addresses on the newly created mailbox that was deleted and then recreated. see the below link to show you how to convert this address and add it to the user so that other users that email him will be able to successfully email without the need to clear that address from the autocomplete cache.

https://support.microsoft.com/en-us/help/2807779/imceaex-non-delivery-report-when-you-send-email-messages-to-an-interna

clearing the address from the autocomplete cache in outlook is the quickest way though.
1
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Wayne88Commented:
Similar solution provided.
0
 
JamesNTAuthor Commented:
Thank you all.
0
 
JamesNTAuthor Commented:
Thank you.
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.