Exchange Server Forums

Recipient Policies

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2003] >> Message Routing >> Recipient Policies

Page: [1]

Message

<< Older Topic Newer Topic >>

Recipient Policies - 21.May2012 3:23:51 PM

tecboy

Posts: 44
Joined: 1.May2006
Status: offline

I current have 2 recipient policies on my Exchange server. Policy1 (which has 4 SMTP @ domain names) and Default Policy (which has 1 of the 4 SMTP @ domain listed). Policy1 is highest and Default Policy is lowest. I would like to add a 5th SMTP @domain but not have it apply to any AD accounts and manually add the new @ SMTP address . When i add a new policy, the SMTP and x400 from the default policy are already listed. When i add the @5thdomain.com to the email addresses tab, what should i do with the existing @domain from the Default policy? Uncheck it, delete it? or ?

Post #: 1

Featured Links*

RE: Recipient Policies - 22.May2012 8:31:30 AM

uemurad

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline

Assuming you want Exchange to act authoritatively for the 5th domain, you'll need it to appear in at least one of your Policies, and mark it as such (check the "The Exchange Organization is responsible for all mail delivery to this address" box on the SMTP Address properties tab). It sounds like you understand that part.

Since you're not going to automatically stamp any objects with that 5th domain, it doesn't have to be in a policy by itself. You can add it to an existing policy and leave the box unchecked. The check boxes indicate which addresses you want the RUS to stamp in each policy.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to tecboy)

Post #: 2

RE: Recipient Policies - 22.May2012 9:24:24 AM

tecboy

Posts: 44
Joined: 1.May2006
Status: offline

so to clarify what you are saying..my policies contain the following(cc and ms left over from old systems during upgrades)
Company Policy(highest priority)
CC Mail xxxxx
MS xxxxx
SMTP @domain1.com
SMTP @domain2.com
SMTP @domain3.com
X400 xxxxxx

Default Policy(lowest Priority)
CC Mail xxxxx
MS xxxxx
SMTP @domain1.com
X400 xxxxxx
When i add the new policy(with no filter rules)...i will see the following..

New Policy
CC Mail xxxxx
MS xxxxx
SMTP @domain1.com
SMTP @domain4.com -----(New Domain)
X400 xxxxxx
Since the new policy will have no filter rules, it sounds like it doesnt make any difference if i leave all checkboxes checked in the new policy or just leave the domain4.com checkbox checked if you are saying the only thing the checkbox accomplishes is if it is added via RUS but since there will be no filter rules in new policy, it doesnt make any difference? What would happen if i deleted everything in the new policy except SMTP @domain4.com and X400

(in reply to uemurad)

Post #: 3

RE: Recipient Policies - 22.May2012 10:04:55 AM

uemurad

Posts: 8232
Joined: 7.Jan.2004
From: California, USA
Status: offline

Recipient policies serve two purposes.

First, it tells the Recipient Update Service (RUS) which addresses to stamp onto a newly created AD object. The RUS applies exactly one policy to each object. It checks in Policy priority order if the LDAP query defined in the policy matches the object. Once a match is made, the RUS doesn't look at any additional policies for that object. The Default Policy LDAP query cannot be changed, matches everything, and is the lowest priority. This ensures that every AD object has a policy applied. When a policy match is made, the addresses in the list that have checkmarks are created for that object.

The second purpose of the Recipient Policies is to define for which SMTP domains your Exchange Organization acts authoritatively. In other words, this is where you define the domains Exchange will consider internal. It's obvious that if you want any of the policies to "stamp" an address, it is going to have to appear in its list, but what's not obvious is the scenario you describe. You want Exchange to "own" the domain, but you don't want to automatically stamp the address into any of the objects. It doesn't matter in which of the policies such a domain is defined. You could put it in the Default Policy if you choose, or you can put it in a policy you've created. As long as it appears once, and you've checked the "authoritative" box I mentioned previously, Exchange will know that messages sent to that domain are internal.

The reason to have separate policies is when you need Exchange to act upon a set of objects differently. That could be a difference in address stamping, or to define Mailbox Management. What you're proposing (creating a separate policy) is acceptable, but not strictly necessary for what you are trying to accomplish.

Finally, the Default Policy will ALWAYS be the lowest priority. You'll notice the LDAP query is (mailNickname=*) which means it matches everything and that it cannot be changed. Any policy you create by definition has to have a higher priority.

_____________________________

Regards,

Dean T. Uemura
Microsoft MVP - Exchange (2007-2011)
exchangeguy.blogspot.com
uemurad@yahoo.com

(in reply to tecboy)

Post #: 4