Solved

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

Posted on 2014-11-10
5
223 Views
Last Modified: 2014-11-10
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?
0
Comment
Question by:bhieb
  • 2
  • 2
5 Comments
 
LVL 19

Expert Comment

by:Adam Farage
Comment Utility
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
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 500 total points
Comment Utility
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
 

Author Comment

by:bhieb
Comment Utility
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
 
LVL 37

Expert Comment

by:Jamie McKillop
Comment Utility
Correct. Outlook will resolve the SMTP address to the contact object.

-JJ
0
 

Author Comment

by:bhieb
Comment Utility
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

Featured Post

Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now