Delivery has failed on new contacts and distribution lists
Hi,
Whenever I create new distribution groups or contacts in exchange 2007 I have to go into ADSI Edit and manually update the legacyexchangedn before I can use them otherwise I recieve
#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##
Any ideas why this happens and what I can change to prevent this happening in future?
Thanks
Alan
November 16th, 2010 10:07am
HI Alan,
Error msg "550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##" occure same object name assign to any object before and creating duplicate onem, You need to check this in your case here.
You can also change X.500 address when create mail enable object by go to the E-Mail Addresses property page, and add a new custom address.
http://www.simple-talk.com/sysadmin/exchange/exchange-e-mail-addresses-and-the-outlook-address-cache/
Anil
Free Windows Admin Tool Kit Click here and download it now
November 16th, 2010 10:55am
When you say you have to manually update the legacyExchangeDn field, do you mean it doesn't exist, or its formatted in such a way that you need to tweak it?
Also are you mail-enabling/creating the objects through an Exchange Management Shell or the Exchange Management Console?
Lastly are you adding the objects in the same site that the Exchange server that is generating the NDRs is in?
November 16th, 2010 10:31pm
Hi
I create the object through the EMC and it only seems to happen for Contacts and Distribution Groups. After creating the object the legachexchangedn field is blank so I have to manually put an entry in there.
Yes the exchange server is in the same site.
Alan
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2010 4:52am
Please reproduce the issue with -verbose switch via PowerShell, and then check the output and application log
Possible cause: New LegacyExchangeDN was not populated on new objects because these objects
were not processed by System Policy (Mail-Enabled Recipient Policy). New recipient objects were skipped during the Recipient Update Services’ call to process new recipient
Resolution: Correct the filter in the “Mail-Enabled Recipient Policy”
a.
Launch ADSI Editor
b.
Expand to “Configuration” container->”CN=Services”->”CN=Microsoft Exchange”->”CN=OrganizationName”->”CN=System
Policies”
c.
In the middle-pane, go to “Properties” of “CN=Mail Enable Recipient” entry
d.
In the “Attribute Editor” tab, open the “purportedSearch” attribute, and verify the value exactly same as below:
(|(&(objectCategory=person)(objectClass=user)(mailnickname=*)(targetAddress=*))(&(objectCategory=person)(objectClass=contact)(mailnickname=*)(targetAddress=*))(&(objectCategory=group)(mailnickname=*))(&(objectCategory=publicFolder)(mailnickname=*)))
e.
Please also use the same procedure to verify the “purportedSearch” attribute of “CN=Mailbox Enable User” entry
(|(&(objectCategory=person)(objectClass=user)(mailnickname=*)(msExchHomeServerName=*))(&(objectCategory=person)(objectClass=user)(mailnickname=*)(homeMdb=*))(&(objectCategory=person)(objectClass=user)(mailnickname=*)(homeMta=*)))
Resources:
Understanding Recipient Resolution
Refer same thread from where i have copied above content::
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/77e35461-a5bf-45d2-824a-ccf5d92af602/
Anil
November 17th, 2010 5:32am
Please reproduce the issue with -verbose switch via PowerShell, and then check the output and application log
Possible cause: New LegacyExchangeDN was not populated on new objects because these objects
were not processed by System Policy (Mail-Enabled Recipient Policy). New recipient objects were skipped during the Recipient Update Services’ call to process new recipient
Resolution: Correct the filter in the “Mail-Enabled Recipient Policy”
a.
Launch ADSI Editor
b.
Expand to “Configuration” container->”CN=Services”->”CN=Microsoft Exchange”->”CN=OrganizationName”->”CN=System
Policies”
c.
In the middle-pane, go to “Properties” of “CN=Mail Enable Recipient” entry
d.
In the “Attribute Editor” tab, open the “purportedSearch” attribute, and verify the value exactly same as below:
(|(&(objectCategory=person)(objectClass=user)(mailnickname=*)(targetAddress=*))(&(objectCategory=person)(objectClass=contact)(mailnickname=*)(targetAddress=*))(&(objectCategory=group)(mailnickname=*))(&(objectCategory=publicFolder)(mailnickname=*)))
e.
Please also use the same procedure to verify the “purportedSearch” attribute of “CN=Mailbox Enable User” entry
(|(&(objectCategory=person)(objectClass=user)(mailnickname=*)(msExchHomeServerName=*))(&(objectCategory=person)(objectClass=user)(mailnickname=*)(homeMdb=*))(&(objectCategory=person)(objectClass=user)(mailnickname=*)(homeMta=*)))
Resources:
Understanding Recipient Resolution
Refer same thread from where i have copied above content::
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/77e35461-a5bf-45d2-824a-ccf5d92af602/
Anil
Hi Anil,
I changed the value for mail enable recipient and it worked a treat. Thank you so much for your help
Alan
Free Windows Admin Tool Kit Click here and download it now
November 17th, 2010 9:41am