General discussion

Locked

Exchange 2K recipient policy not working

By Operagost ·
When a new user is created on our Exchange 2000 SP3 system, the recipient policies do not apply. This includes the default policy. I've left a new account untouched for 24 hrs and the E-mail addresses tab still shows no SMTP, X.400, or X.500 address. These must be added manually. I have a recipient update service for the enterprise, running on domain example.com. I also have a recipient service running for both domain example.com and example.net, another division's domain. There are several recipient policies in place, but the default has:

FAXMAKER: @example.com
SMTP: %G.%S@example.com
SMTP: @example1.com
X400: c=US;a= ;p=Example Corporation;o=EXCorp;

An X.500 address (which does not appear in any of the policies) IS being geenrated for new accounts. I don't see any errors in the Application log that would indicate a problem with the recipient policies. If someone can provide a walkthrough that helps me find the solution, the points are yours.

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Monice In reply to Exchange 2K recipient pol ...

One possible cause of this behavior is if the Recipient Update Service does not have appropriate rights to that mailbox or to the Organizational Unit (OU) in which this user account resides, which may occur if the Allow inheritable permissions from parent to propagate to this object check box is not selected.

See Q297124

Collapse -

by Monice In reply to

Oops didn't mean to submit the answer twice.

Collapse -

by Monice In reply to Exchange 2K recipient pol ...

One possible cause of this behavior is if the Recipient Update Service does not have appropriate rights to that mailbox or to the Organizational Unit (OU) in which this user account resides, which may occur if the Allow inheritable permissions from parent to propagate to this object check box is not selected.

See Q297124

Collapse -

by Operagost In reply to

Poster rated this answer.

Collapse -

by Operagost In reply to Exchange 2K recipient pol ...

The check was set to allow permissions to propagate in the OU, but I don't think the permissions at the higher levels are correct. Unfortunately, MS doesn't seem to say what these permissions should be- they just tell you to check the box. For example, "change properties" is not checked- I'm pretty sure that's a must.

Collapse -

by Operagost In reply to Exchange 2K recipient pol ...

This question was closed by the author

Back to Software Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums