Any mail enabled contact I create with an external address from the Exchange 2007 GUI always fails with a DNR. I can create the contact on the existing Exchange 2003 system and it works fine. The DNR makes even makes less sense as the real address is replaced with gibberish. Note that the real SMTP address (my Gmail address was entered) is nowhere to be found. What could be causing this? Diagnostic information for administrators: Generating server:FQDN of cdomain IMCEAEX-_O=NT5_ou=B57FD40C9308F7479BF159E9F227E5DD_cn=377ECE0B4A7C8F4783EF39C4CE9ED02C@FQDN of cdomain#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ## Original message headers: Received: from mailbox server ([IP]) byCAS server with mapi; Wed, 7 Jan 2009 16:03:01 -0600Content-Type: application/ms-tnef; name="winmail.dat"Content-Transfer-Encoding: binaryFrom: my addressTo: Test Tester <IMCEAEX-_O=NT5_ou=B57FD40C9308F7479BF159E9F227E5DD_cn=377ECE0B4A7C8F4783EF39C4CE9ED02C@domain name>Date: Wed, 7 Jan 2009 16:03:00 -0600Subject: TestThread-Topic: TestThread-Index: AclxE7R8iBnYGxdzQ46okLzADqJDUw==Message-ID: <D1F27CE6E55190438E944C4AAE2AC01501A5A6D46D@email2>Accept-Language: en-USContent-Language: en-USX-MS-Has-Attach:X-MS-TNEF-Correlator: <D1F27CE6E55190438E944C4AAE2AC01501A5A6D46D@email2>MIME-Version: 1.0 SnoBoy

In Exchange Management Console, bring up the properties of the contact object and go to the Email Addresses tab. Post the results here.Neil Hobson, Exchange MVP

Hi, First please verify the recipient address is entered correctly when addressing the message. Verify personal address lists and contacts contain the correct address. You need to delete the contact in Exchange 2003 Server and then add it to exchange 2007 server. Then please follow the article below to reset the Outlook nickname cache How to reset the nickname and the automatic completion caches in Outlook http://support.microsoft.com/default.aspx/kb/287623 After that, please use ADSIedit to check value for LegacyExchangeDN on problematic contact. If you cannot find value, then please run Update-EmailAddressPolicy to update the LegacyExchangeDN and other Exchange attributes. If value still is none, then please try to manually add the value and then check the issue. How to change the legacyExchangeDN attribute in native mode with ADSI Edit http://support.microsoft.com/kb/273863 Hope it helps. Xiu

You are on target as to the cause - I got to thinking about this before I saw your reply and compared a working Contact to a non-working contact and saw the the difference was the one having the legacyExchangeDN entry set to the Exchange 2003 first admin group worked and the one missing the information did not work. And of course, if I manually added it via ADSIedit, it starts working.But every new Contact I create is missing the legacy domain information - so how do I fix that? Running Update-EmailAddressPolicy did not fix broken Contacts - the legacyExchangeDN entry is still not set. Is there a change I need to make to the Default E-mail Address Policy so that the legacy information is there until I remove the last Exchange 2003 server? Or is there some other undocument trick I need to do?The Exchange 2007 KB is silent on this issue as far as I can tell.SnoBoy

Hi, Then we can try to use ADModify to modify the value on attribute-LegacyExchangeDN. Using ADModify to Change Exchange Specific AD User Attributes in Bulk http://www.msexchange.org/articles/ADModify-Change-Exchange-Specific-AD-User-Attributes.html Windows Server 2003 - ADModify Support Tool Utility - http://www.computerperformance.co.uk/w2k3/utilities/admodify.htm http://www.codeplex.com/admodify/Release/ProjectReleases.aspx?ReleaseId=6065 Regards, Xiu

Hi, With deeply consulting and researching with my colleague Mike, we found the possible root cause of the issue. For detail information, please refer to the http://social.technet.microsoft.com/forums/en-US/exchangesvrdeploy/thread/ec9735f2-0ff2-4307-8544-8c973e616510 Regards,Xiu Quote answer from http://social.technet.microsoft.com/forums/en-US/exchangesvrdeploy/thread/ec9735f2-0ff2-4307-8544-8c973e616510:------------------------------------------------------------------------------ Hi SnoBoy, For Exchange 2003 and 2007 co-existence environment, the Exchange 2003 RUS (Recipient Update Service) is responsible to update object attributes (such as legacyexchangedn, homemdb and so on) in a co-exist environment. Based on my research, the issue may occur if the purportedsearch attribute is not configured correctly of the Mail Enable Recipient system policy. The Recipient Update Service has three System Policies that are installed by default when you install Exchange 2003. They are Mail Enable Recipient, Mailbox Enable User and Hidden DL membership. All of them have the same purpose of update a few attributes on each entry under certain circumstances. Please understand if the recipient update service identifies than a new entry was added (or modified), and it does have the mailNickname to be considered mail-enabled. Therefore, by default, the purportedsearch attribute should be below: (|(&(objectCategory=person)(objectClass=user)(mailnickname=*)(targetAddress=*))(&(objectCategory=person)(objectClass=contact)(mailnickname=*)(targetAddress=*))(&(objectCategory=group)(mailnickname=*))(&(objectCategory=publicFolder)(mailnickname=*))) You can locate the"Mail Enable Recipient" object by using Adsiedit.msc tool: CN=Mail Enable Recipient, CN=System Policies, CN=ORG_NAME, CN=Microsoft Exchange, CN=Services, CN=Configuration, DC=DOMAIN_NAME,DC=com The user, contact and public folder object which have mailnickname and targetaddress (not for public folder) attributes. Mike