#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found # Error when replying to imported PST messages

We had an EDB from another organization that we needed some messages from. I used a 3rd party tool Lepide Exchange Recovery Manager to export the messages to a pst and then imported them to the Exchange 2010 mailbox.

The messages are there and look fine, but when replying to one it throws the above error. After searching I've found a lot of posts regarding X500 and LegacyExchangeDN, but the kicker here is that this is being replied to an external user NOT internal so that shouldn't be an issue. It does this from OWA and Outlook so it isn't an autocomplete issue either.

Thoughts?
bhiebAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
Its a possibility when you reimported the mail items into the mailbox, it striped out attributes from that message. I would look using MFCMAPI at one of the messages and see if the PR_SENDER_ADDRESS is valid on the message that is giving the NDR.
0
Jamie McKillopIT ManagerCommented:
Hello,

This is definitely a legacyExchangeDN issue. The reason you are getting it, even though this is an external address, is that there was a contact created for this address.

See my article here on how to resolve:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_9650-NDRs-and-the-legacyExchangeDN.html

You will need to create a new contact in your GAL and add the legacyExchangeDN in the NDR as an X500 address on the contact.

-JJ
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bhiebAuthor Commented:
I read that, very good by the way. So if there is a contact created anywhere in exchange it will cause this? Even a users contact?
0
Jamie McKillopIT ManagerCommented:
Correct. Outlook will resolve the SMTP address to the contact object.

-JJ
0
bhiebAuthor Commented:
I had a senior moment DOH! The test I ran I did a reply to all, and there was an exchange object in the cc. Ooops. The external address worked fine, it was the exchange object generating the NDR.   Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

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.