cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
423
Views
0
Helpful
2
Replies

exchange recepient policy and unity

ciscoforum
Level 1
Level 1

Is there a way to use a different receipient policy for the users in another exchange server within the same exchange orgnization? My customer has 3 smtp addresses for mailbox users. say primary one is abc.com in the recepient policy. Now we are going to install a vm only unity into the exchange orgnization,a dedicated exchange server will be used, for a very special reason we want to use anther email def.com as primary for those vm mailboxes. Can we create a new recepient policy on the exchange and apply them to the new vm only users? thanks

2 Replies 2

Ginger Dillon
VIP Alumni
VIP Alumni

Hi -

These Microsoft links might help.

1. This will tell you how to filter by group membership:

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

2. Read this one also - in particular steps 8 - 11, which the previous link does not cover and are important items. http://support.microsoft.com/default.aspx?scid=kb;en-us;325921

Caveat - if you have a test or lab environment, it would be good to test here first. Recipient policies can alter/affect the flow of e-mail in your Exchange organization if not done correctly.

Regards,

Ginger

I would just add a caveat, http://support.microsoft.com/kb/304516 explains why, in many circumstances, you should not apply recipient policy filters against a 'backlinked' attribute such as group membership, but rather should choose an expressly configured AD data field.

Essentially the article states that group membership is an attribute of the group - not the user - so the results of filtering on group membership can be unpredictable. If, for example, after configuring a recipient policy, a user is added to the filtered group and the policy is not re-applied, that user may not be affected by the recipient policy.

The reverse is also true - if you remove a user from a group that removal is not dynamic to the recipient policy and you can unexpectedly apply a recipient policy to someone you did not intend. Unfortunately I learned this one the hard way!