420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address

We  are in the middle of a migration from Exchange 2003 to Exchange 2010.  I see there that there are over 100 items in the submission queue for Exchange 2010.  All of the items are from the same address (exchange_server_name-IS@domain.com) to the same recipient address (_5@domain.com).  All of the messages have the same error:

Identity: CAS01\Submission\257062
Subject: Folder Content
Internet Message ID: <012033945802AC4AB8DF73C9A4EB19639B9657@echange_server_name.domain.com>
From Address: echange_server_name-IS@domain.com
Status: Retry
Size (KB): 42
Message Source Name: SMTP:Default CAS01
Source IP: x.x.x.x
SCL: -1
Date Received: 4/25/2011 4:03:09 PM
Expiration Time: 4/27/2011 4:03:09 PM
Last Error: 420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address
Queue ID: CAS01\Submission

I went through the following links:



When I do an LDAP search for the email recipient address (_5@domain.com) it doesn't come up in the search.  I confirmed my syntax was correct by finding an account that I know does exist.

I did find SMTP addresses on the System mailboxes in the storage groups of the Exchange 2003 server that had similar addresses like _2@domain.com  & _9@domain.com, so I'm wondering if the address _5@domain.com is a remnant.

Any help would be appreciated.

Who is Participating?
sillzConnect With a Mentor Author Commented:
We found the duplicate using the query in my original posting.  We just needed to make sure that we were searching across multiple domains
Tony JLead Technical ArchitectCommented:
Slightly different number in the error, but the remainder of the code is the same (ambiguous address) plus just gone through a migration:

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

sillzAuthor Commented:
I saw those docs too.  I tried searching for the recipient address, but it doesn't seem to exist as a user or contact.
sillzAuthor Commented:
we juts needed to search across our multiple domains
sillzAuthor Commented:
We resolved our own problem by running the query in my original posting.  We had to run the query in multiple domains to find the duplicates.  
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.