Removing mail contact that's no longer part of Active Directory

Hello. We had a Mail Contact set up in Exchange 2007. He recently retired and I removed him from the system. Now when someone tries to email him directly, they get an NDR that looks like:

IMCEAEX-_O=MY+20COMPANY_OU=First+20Administrative+20Group_cn=Recipients_cn=hisname@mydomain.com
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

I have updated the GAB and deleted his name from the auto-populate (NK2) in Outlook 2007. When I begin a new message, I type in his external email address (hisaddress@yahoo.com), it automatically changes it to his name, underlined. Where is it getting this information? I have scoured AD. If I right click his name in the new email message and look at the Outlook Properties, the only information filled out is the Display Name. It says /o=My Company/ou=First Administrative Group/cn=Recipients/cn=HisName. We don't even have a First Administrative Group in AD. I can't use ADSIEdit because he's no longer in AD. So I'm clear, he was never a domain user. He was just a Mail Contact that was added so our users could email him at his yahoo address. How do I remove this information? I can tell you he's been in our system for a long time. We started out with Lotus Domino then moved to Exchange 2003. Since then, we've upgraded to Exchange 2007 SP3. If it makes any difference our Active Directory is at Windows 2008 functionality. If I have to use LDP in Windows Server 2008, how do I do it when that OU no longer exists?
outlookprop.JPG
CMWintersAsked:
Who is Participating?
 
Will SzymkowskiSenior Solution ArchitectCommented:
Yeah this is definitely something cached, either profile itself, OST, OAB. If this is happening for 20-30 users it might be OAB generation, rather than a local profile or OST, but than again anything is possible.

Will.
0
 
Simon Butler (Sembee)ConsultantCommented:
First Admin group is an Exchange Admin group, not AD. Therefore the message is to be expected.
There has to be a trace in the network somewhere. If you try it through OWA, does the same thing happen?

Simon.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
Does this happen when you are using OWA? If this is strictly when you are using Outlook using cached Exchange mode, then try re-creating your Outlook OST file and or Outlook profile.

If it is only giving you an issue in Cached Exchange mode for Outlook then you might have an issue with your OAB, and you might need to re-create it.

Will.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
CMWintersAuthor Commented:
It works fine when I use OWA. I would prefer not to recreate profiles on 20-30 computers. I guess I can try recreating the address book.
0
 
Simon Butler (Sembee)ConsultantCommented:
On one workstation, shutdown Outlook. Find the *.oab files and delete them.
Then restart Outlook.
Ensure the nicknames cache is flushed then test again.

Simon.
0
 
CMWintersAuthor Commented:
I recreated the address book. Plus, I had to add Authenticated Users to the webconfig file once the address book was created.
0
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.