We have 2 domains, domainA.com and domainB.cn. novetlyinc.cn moved into our environment so we created accounts and email boxes for domainB.cn in our AD / exchange. Things were working fine. Now domainB.cn has moved to a different location, out side of novetly. We've got the MX records and DNS records forwarded, and I've removed the domainB.cn domain from recipient Policy, deleted the accounts from AD, and created contacts in AD for the email addresses. but our exchange server still thinks domainB.cn is hosted by the exchange server here. I've rebuilt the RUS's after taking the domains out of the Recipient Policy. whenever we send emails to domiainB.cn , we get this: Your message did not reach some or all of the intended recipients. Subject: test 12:07 Sent: 4/21/2010 12:07 PM The following recipient(s) cannot be reached: Lily Wan on 4/21/2010 12:07 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <*domainA's exchange server* #5.1.1>

You will want to into each account and manually remove the SMTP address which removing the policy doesn't do for you. ADMODIFY.NET will do this for you in bulk so it's, fortunately, not as big a job as you might think. "Novelty" wrote in message news:0ef649b6-e41e-4c99-bcd5-910b70c7732c...We have 2 domains, domainA.com and domainB.cn. novetlyinc.cn moved into our environment so we created accounts and email boxes for domainB.cn in our AD / exchange. Things were working fine. Now domainB.cn has moved to a different location, out side of novetly. We've got the MX records and DNS records forwarded, and I've removed the domainB.cn domain from recipient Policy, deleted the accounts from AD, and created contacts in AD for the email addresses. but our exchange server still thinks domainB.cn is hosted by the exchange server here. I've rebuilt the RUS's after taking the domains out of the Recipient Policy. whenever we send emails to domiainB.cn , we get this:Your message did not reach some or all of the intended recipients. Subject: test 12:07 Sent: 4/21/2010 12:07 PM The following recipient(s) cannot be reached: Lily Wan on 4/21/2010 12:07 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <*domainA's exchange server* #5.1.1>Mark Arnold, Exchange MVP.

I've completely removed the entire account from AD. I created contact cards for them instead, so that I can keep their email addresses in some distribution groups.

Heck. You did. I read that now. Sorry.Test for you. Can you email an address that you never had an account or contact for? Attempt to create an email for "something(todaysdate)@domain.com - which you know won't exist. Where does the NDR come back from? You, or them?"Novelty" wrote in message news:afe90688-797e-42eb-9946-f699188ea318...I've completely removed the entire account from AD. I created contact cards for them instead, so that I can keep their email addresses in some distribution groups.Mark Arnold, Exchange MVP.

the NDR is still coming from the .com (us domain) server, not the China domain server. So our mail server is still trying to take care of domainB.cn for some reason.

And it's a fresh smtp address that cannot possibly exist in your system? In that case I'd say to review the recipient policy to make sure you have indeed removed the old domain."Novelty" wrote in message news:62b65845-20a2-4325-8b2c-b43305d5e8d7...the NDR is still coming from the .com (us domain) server, not the China domain server. So our mail server is still trying to take care of domainB.cn for some reason.Mark Arnold, Exchange MVP.

After many hours of dealing with this, we finally figured out its a client cache issue. Everything is setup correctly on the exchange server, but when you type in the address, it will resolve the name to an old MS record. We've deleted the N2K file with outlook closed, etc, but it will still resolve to the MS record. How do we get rid of this? The ONLY email address it should be coming up is a user@domainB.cn address, but it has everything else cached from when they had user accounts here. example: when you type in your TO: user1 and hit tab, it will autofill that info for the user. Double click on it and go to the email addresses tab, it shows: ms:domainDIS/domainEXC/user SMTP:user@domainB.cn x400: blah blah smtp:user@domainA.com smtp:user@domainC.com.cn (a seperate domain we dont really care about) The only thing we want for these email addresses is the smtp:user@domainB.cn, everything else needs to be gone! :)

Ahh, the old Outlook NK2 file killing you."Novelty" wrote in message news:290fd38e-42d5-4a08-a365-1618ce9a1236...After many hours of dealing with this, we finally figured out its a client cache issue. Everything is setup correctly on the exchange server, but when you type in the address, it will resolve the name to an old MS record. We've deleted the N2K file with outlook closed, etc, but it will still resolve to the MS record.How do we get rid of this? The ONLY email address it should be coming up is a user@domainB.cn address, but it has everything else cached from when they had user accounts here.example: when you type in your TO: user1 and hit tab, it will autofill that info for the user. Double click on it and go to the email addresses tab, it shows:ms:domainDIS/domainEXC/userSMTP:user@domainB.cnx400: blah blahsmtp:user@domainA.comsmtp:user@domainC.com.cn (a seperate domain we dont really care about)The only thing we want for these email addresses is the smtp:user@domainB.cn, everything else needs to be gone! :)Mark Arnold, Exchange MVP.

I've already deleted that while outlook was closed. It seems like the addresses are being pulled in from the global address list on exchange. Is there a way to edit that list?

Hi Novelty, Per your description, it seems the client cach the legacyexchangedn for the old email address of the domainb user account. So, you could remove the old cach emailaddresses on each client, Or you could reset the *.nk2 file. You could refer to below link: http://support.microsoft.com/kb/287623 You also could recreate the GAL refer to: http://technet.microsoft.com/en-us/library/dd535387(EXCHG.80).aspx Regards! gavin