Users receiving NDR from the System Attendant

[simonjcook]

I have an issue where users are reporting that they are receiving an NDR from the System Attendant when they send an email.

NDR below;
Your message did not reach some or all of the intended recipients. Subject: Sent: 1/13/2009 10:14 AM The following

recipient(s) could not be reached:

System Attendant on 1/13/2009 10:14 AM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a

mistake in the address. Check the address and try again.
<(FQDN of server) #5.1.7>

After investigating this I discovered that the proxyaddresses attribute is blank for the system attendant on the users' mailbox server.
Servers which do not exhibit this issue have valid data in the proxyaddresses attribute.

distinguishedname of the SA
CN=Microsoft System Attendant,CN=<server name>,CN=Servers,CN=<admin group>,CN=Administrative Groups,CN=<exchange org>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain prefix>,DC=<domain suffix>

The RUS does not appear to have stamped the proxyaddresses attribute of the affected server System Attendant.
When new users are created they are receiving proxyaddresses so the RUS is apparently working currently.

Running "update now" is not doing the trick - nor has a rebuild.
Does anyone know how to force the RUS to stamp the SA?

Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >

 

[TechyMcSe2k]

May just need to open adsiedit and add the proxy addresses manually.

Example: smtpservername)-SA@domain.com

 

[simonjcook]

Thanks for the feedback, I concluded the same.
However it would be preferable if I could get the RUS to stamp it.

The concern there is that if I don't address the root issue what happens when I commission another E2K3 server... I could end up having to manually edit the AD every time I deploy a new server.

Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >

 

[TechyMcSe2k]

Ok, will research, and I take it you have rebooted the SA service to no avail... hmmm

 

[TechyMcSe2k]

Is the RUS pointing at the correct exchange server?

Also, may need to check the permissions on that SA account to make sure it is not corrupted or modified.

http://support.microsoft.com/kb/254030

But, probably not this issue since all other accounts are updated.

Informative:
How the Recipient Update Service Populates Address Lists

http://support.microsoft.com/kb/253828/EN-US/

How the Recipient Update Service applies recipient policies

http://support.microsoft.com/kb/328738/en-us

 

[TechyMcSe2k]

I have also noted that; the ESM Recipient Policies have an email addresses (policy) tab within the Policy defined (Default or other). If the email address is in there but not checked, it will not show up on the proxy addresses for the SA for that Exchange server.