0

Last week we performed an inter-forest migration to a new domain but kept the same primary smtp addresses. I created mailboxes on the new Exchange server and exported the old mailboxes as psts and imported them to the corresponding mailboxes on the new server. We can send new emails to each other without issue (baring auto-fill which I have placed a workaround so their history is cleared) but when we reply to messages from before the domain cut-over we receive

IMCEAEX _O=NAME+20OF+20ORGANIZATION_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=FIRSTNAME+20LASTNAMEBCC@email.com #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

When looking this error up I get a lot of info about X500 records which didn't exist for many of the users on the old domain. I understand that the error means that it is hitting the server and the server doesn't know where to send the mail but why not? Shouldn't it just be using the smtp address? I should mention that from non-outlook programs it works fine. From phones it works fine, but from OWA or Outlook we just get the bounceback error message.

Zombian
  • 291
  • 2
  • 4
  • 14

3 Answers3

1

The behaviour you are seeing is what I would expect.

You have gone cross forest, so everyone has a new mailbox in a new domain. Hitting reply to old emails will give you invalid address. If you hit reply, then delete the recipient from the To line and find them fresh from the GAL, then it will work.

This article from the SBS team explains the problem as well (ignore it is SBS, Exchange is the same underneath). http://blogs.technet.com/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx

Sembee
  • 2,884
  • 1
  • 8
  • 11
  • This is correct and as I've been attempting to script something for this, the link provides a solution in ADModify.net. I'm surprised I couldn't find that article before. Hopefully if anyone comes across this in the future this will help them. Thanks! – Zombian Jul 23 '16 at 00:29
  • Because my Exchange server had appended names of mailboxes with a short, randomized (I think) hash, I wasn't able to use the ADModify.Net tool but through Powershell I was able to use the command Import-CSV .\Export.csv | Foreach { Get-ADUser $_.Name | Set-ADUser -Add @{proxyAddresses = ('x500:'+$_.proxy -split ";")} } which is slightly modified from a script I found on Technet after exporting a CSV of SAMAccountNames and LegacyAddresses from the old Exchange server. – Zombian Jul 23 '16 at 02:13
0

I was able to find a workaround though I'm still unsure of what caused the issue. from: ExRecipNotFound; not found after disabling / recreating mailbox in exchange - x500 not working

I saw the command:

Get-Mailbix someuser | fl LegacyExchangeDN

That followed the format that was being shown as not found. So I will have to build a script to export all users' LegacyExchangeDN and then import it to their new mailboxes. I tested with a couple users and it seems to be working well so far.

Community
  • 1
Zombian
  • 291
  • 2
  • 4
  • 14
0

This could also happen after restoring a mailbox from backup. Have a look at this for a solution: http://www.inthecloud247.com/exchange-error-550-5-1-1-resolver-adr-exrecipnotfound/

Peter
  • 1
  • 1
    Can you expand this answer to stand on its own? http://meta.stackexchange.com/questions/8231/are-answers-that-just-contain-links-elsewhere-really-good-answers – chicks Mar 01 '17 at 19:12