Shulou(Shulou.com)06/03 Report--

This article mainly introduces the method to solve the problem of Exchange mail return in detail, the picture and text explanation is easy to learn, if you encounter this problem at work, you can refer to this article, I hope it will be helpful to you.

Problem description:

In the environment of Exchange 2013, a customer disabled a user's mailbox test@abc.com, then wanted to connect to the mailbox a few days later, but could not find the disabled mailbox, and then the customer recreated a mailbox test@abc.com with the same name on Enable-MailBox.

After re-enabling the new mailbox, you can log in to OWA normally, but there is no previous historical mail, and users in the domain send mail and return mail: '550 5.1.11 RESOLVER.ADR.ExRecipNotFound; external mailbox is sent normally

Solution:

We know that after disabling mailboxes, it usually takes 24 hours for ECP to synchronize the disabled mailboxes. If we want to see the disabled mailboxes immediately, we need to run the following command to force the Exchange storage state to synchronize with Active Directory:

Get-MailboxStatistics-Database MDB02 | ForEach {Update-StoreMailboxState-Database $.Database-Identity $.MailboxGuid-Confirm:$false}

After that, we will see the previously disabled mailbox account test@abc.com in the connected mailbox. Now let's disable the user's re-created mailbox test@abc.com, open the linked mailbox again, and link the previously disabled mailbox test@abc.com (note: mailbox disabled time) to the test account. Then open the IIS, the application, and recycle the OWAapplicationPool pool; so we open OWA again, log in to the test@abc.com mailbox, and we will see that all the previous historical messages have been restored.

However, when users in the domain send an email to test, they will still report an error:

IMCEAEX-_o=First+20Organization_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=03497328d46c4f93b327663d66644a05-info@kaiyunmotors.com

'550 5.1.11 RESOLVER.ADR.ExRecipNotFound

So how to solve this mistake?

This is because every time we send / receive email within the organization, he will look for the value of ID found in LegacyExchangeDN.

However, if we delete this mailbox and create it again, another ID will be generated again

So, at this point, we can rebuild X.500 based on the NDR (bounce email) sent to us by Exchange. The reconstruction of X.500 is as follows:

Copy the Powershell

$Direccion = Read-Host "Ingrese IMCEAEX"

$Remplazo= @ ("", "/"), @ ("+ 20", "), @ (" + 28 "," ("), @ (" + 29 ",") "), @ (" + 2C ",", "), @ (" + 3F ","? "), @ (" + 5F ","), @ ("+ 40", "@"), @ ("+ 2e", "."))

$Remplazo | ForEach {$Direccion = $Direccion-replace $[0], $[1]}

$Direccion = "X500:$Direccion"-replace "IMCEAEX-", ""-replace "@. * $", ""

Write-Host $Direccion

And run in Powershell ISE

Then we type IMCEAEX, and we can copy it from the bounce email, as follows:

IMCEAEX-_o=First+20Organization_ou=Exchange+20Administrative+20Group+20+28FYDIBOHF23SPDLT+29_cn=Recipients_cn=03497328d46c4f93b327663d66644a05-info@kaiyunmotors.com

Paste into PS ISE

Get the X.500 address

X500:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) / cn=Recipients/cn=03497328d46c4f93b327663d66644a05-info

Then, look for the proxyAddresses attribute in the AD user attribute-attribute Editor

Edit and add X.500 address

Let's test it again, and then we can send the mail to the test mailbox.

The above is the solution to the problem of Exchange mail return, after reading it, do you have anything to gain? If you want to know more about it, you are welcome to follow the industry information!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.