Solved

Exchange 2007 IMCEAEX NDR 5.1.1 error

Posted on 2009-04-06
11
4,555 Views
Last Modified: 2012-05-06
Have Exchange 2007 Enterprise, user naming convention is first initial + last name (total of 8 characters or less).  For some reason we have a user that is having email sent to him generate a NDR - #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##.  The user is getting the email, it's just that whomever sends him the email is getting a NDR.  The actual address that is getting bounced is NOT an address that has ever been on the system and I don't know where to find it to get rid of it.  The whole NDR is cut and pasted below:

Delivery has failed to these recipients or distribution lists:

zz*Gil Singer
The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator.

  _____  

Sent by Microsoft Exchange Server 2007







Diagnostic information for administrators:

Generating server: exchserver.???????.COM

IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20Administrative+20Group_cn=Recipients_cn=GilSinger@???????.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

Original message headers:

Received: from exchserver.???????.COM ([192.168.0.18]) by
 exchserver.???????.COM ([192.168.0.18]) with mapi; Mon, 6 Apr 2009 12:12:32
 -0400
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Scott Moyes <SMoyes@???????.com>
To: zz*Gil Singer
      <IMCEAEX-_O=FIRST+20ORGANIZATION_OU=First+20Administrative+20Group_cn=Recipients_cn=GilSinger@???????.com>
Date: Mon, 6 Apr 2009 12:12:31 -0400
Subject: test
Thread-Topic: test
Thread-Index: Acm20nxAOscDdymFTkWr8Py9LhSPyw==
Message-ID: <4721E2D0C3412B498B174A275F02AB7001BD057DB2@exchserver.???????.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator: <4721E2D0C3412B498B174A275F02AB7001BD057DB2@exchserver.???????.COM>
acceptlanguage: en-US
MIME-Version: 1.0

The user is receiving the email at his address which is gsinger@???????.com.

Thanks,

Scott Moyes
0
Comment
Question by:kasslaw
  • 6
  • 5
11 Comments
 
LVL 40

Expert Comment

by:coolsport00
ID: 24080061
Scott, this may be an issue where you have a 'stray' SMTP address in your domain. I had this but couldn't use the typical "Find" feature in AD to find the SMTP address. I used this article to find my dup SMTP address and delete it for the error I was getting. This isn't quite the same issue I experienced, but may be similar in resolution:
http://flaphead.dns2go.com/archive/2007/11/09/550-5-1-4-resolver-adr-ambiguous-ambiguous-address.aspx

(My EE post: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23445951.html)

Regards.
~coolsport00
0
 

Author Comment

by:kasslaw
ID: 24080356
checked it out, didn't help.

The zz*Gil Singer that you see above was a contact pointing to a blackberry address that was forwarded to his blackberry.  It was deleted and this started.  The blackberry address that it pointed to wasn't even close to being the gilsinger@???????.com that it's saying it's pointing to.  I just don't know where or how that address got there and why when sending to his regular address (gsinger@???????.com) it also forwards to the bad address.

Thanks,

Scott Moyes
0
 
LVL 40

Expert Comment

by:coolsport00
ID: 24080536
That address seems to still be in AD somewhere. Maybe try using LDIFE and search for that address or ADEXPLORER (though I haven't used this before, http://technet.microsoft.com/en-us/sysinternals/bb963907.aspx) to search for that address. Let me know how that goes.

~coolsport00
0
 

Author Comment

by:kasslaw
ID: 24086439
Can't find it in there.  I did notice one thing though, the IMCEAEX- shows the FirstAdministrativeGroup on the line and I did move all mailboxes to new stores corresponding to their OU's in AD.  So, this person's email, was once in the First Administrative Group is now in a store called Attorneys.  The old information store is gone.
This happened way before this problem started.  Everything was fine till I deleted the blackberry forwarding.

Scott
0
 
LVL 40

Expert Comment

by:coolsport00
ID: 24086558
I don't remember the NDR error, but....another thing you can try is to have users delete their .nk2 entry in Outlook for this user (if that's how they're sending the email...the 'autopopulate' feature). Does this error also happen internally? When making a change, sometimes the cache needs reset. I've had an NDR generating when people used the cached info in Outlook after a name change was made. When attempting to send to this person, if his name shows up in the drop-down, hit your arrow down to highlight the user, then press Delete. Manually type in the person's email address and send to see if that generates the NDR still. I'm running out of ideas!.... :)

~coolsport00
0
Promote certifications in your email signature

Has your company recently won an award or achieved a certification? They'll no doubt want to show it off. Email signature images used to promote certifications & awards can instantly establish credibility with a recipient and provide you with numerous benefits.

 

Author Comment

by:kasslaw
ID: 24086664
I've checked that right off, not it.  Besides, it's not only occuring from internal users, but external as well.  Somehow, our exchange server thinks that this user has two email addresses and any email to the correct one, gets bounced by the incorrect one even though the good address gets delivered.  

Scott
0
 
LVL 40

Expert Comment

by:coolsport00
ID: 24086738
So, you went to the LDAP location shown in the error and didn't find the bad email address? And, I assume that bad email SMTP is not associated with the mailbox of the user as well? I know this seems elementary, but I hadn't asked if you checked those, nor did you share that you checked those areas yet, so I'm just trying to rule out everything.

That LDAP address: O=FIRST+20ORGANIZATION_OU=First+20Administrative+20Group_cn=Recipients_cn=GilSinger@???????.com
is in your domain structure somewhere, thus why you're getting the NDR. I'm not sure how else to locate it besides the way I suggested already....hmmm....
0
 

Author Comment

by:kasslaw
ID: 24087023
I really appreciate the replys.  This is the problem, I don't have an OU of First Administrative Group.  All our OU's are actual departments, makes it easier to assign policies.  The user in question is in the OU=Attorneys and has been since long before this problem started.  There is an storage group (and edb) for each OU, all are mounted and running LCR (which is healthy).  I saw somewhere that moving the user to a different storage group might work, what is your thoughts on that?

Thanks again,

Scott
0
 
LVL 40

Accepted Solution

by:
coolsport00 earned 500 total points
ID: 24087054
Well, you can move the user to a different storage group to try it...that won't hurt anything, but this seems to be an AD problem, not storage group or Exchg. Remember, Exchg works interactively with AD. That address is embedded into that canonical name path within AD. I had a problem with that (and posted on here like a yr ago), and had to drill down to find the SMTP address to delete it, which took care of my problem.

~coolsport00
0
 

Author Comment

by:kasslaw
ID: 24088945
Looking through Active Directory Explorer, I found some proxyaddresses and samaccountname with gilsinger, but they are all in the deleted section.  There is no way to delete it again.  Is there someway to find it anywhere else?

Thanks,

Scott
0
 
LVL 40

Expert Comment

by:coolsport00
ID: 24089033
Hmm...have you tried ADSIEDIT? I think that may be what I used (not LDIFE); and I think it fully deleted that SMTP Address...didn't put it in a 'deleted' area.

~coolsport00
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Suggested Solutions

"Migrate" an SMTP relay receive connector to a new server using info from an old server.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
To show how to generate a certificate request 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 Servers >> Certificates…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

707 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

18 Experts available now in Live!

Get 1:1 Help Now