Exchange 2007 IMCEAEX NDR 5.1.1 error

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

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

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

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

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

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....

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

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