Re: Help needed with recipient policy

Tech-Archive recommends: Fix windows errors by optimizing your registry

De-selecting the auto email address generation won't cause any issues with existing email. Even when additional policies are applied to existing users, the old email addresses aren't automatically removed - they remain associated with the users. What can change, is new email addresses can be generated, and set as primary. This is the desired behavior. So, even if you get an unintended result from policy, email can still be sent and received.

Where you can run into delivery issues is when you remove addresses from a user. Once removed, email addressed such can't be delivered. This also causes issues with the pop3 connector, should you be using that.

Ace has given you the good stuff. Bottom line, the default policy should remain (and it applies to all users), and for the users that require a different primary email address - create another policy with a higher priority than the default, and apply it to just those users by keying on a field in the user properties (company name was suggested, and is a good one). Security groups can also be used in this way - one could apply a policy to a security group; as you make users members of that group they become subject to the policy that applies to that group and receive the corresponding email address.

--
-----------------------------------------------
Les Connor [SBS MVP]

"mcseman" <mcseman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:AF439506-3545-44DC-A184-2FB291AD99BC@xxxxxxxxxxxxxxxx
Hi Ace,
Thank you very much for your speedy and very detailed helpful reply. I
understand what you are saying and will consider following this thoroughly.
My only concern was that if I start playing around with the policies now way
after these new users have received substantial amounts of email under both
accounts I might mess up their existing email configuration.
Is there any chance of this if I go ahead with your proposal?

Thanks again

Colin

"Ace Fekay [MCT]" wrote:

"mcseman" <mcseman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:06DD70C9-FBE2-4B3C-8BE7-D0E8A63F34FE@xxxxxxxxxxxxxxxx
> Hi All,
>
> I need some advice with regard to recipient policies please.
> SBS 2003 premium, isa 2004 Exchange 2003 sp2.
>
> Several weeks ago after a company buy out we needed several new users > to
> have a second email domain address for which exchange is responsible. > We
> have
> 32 users with the main company addresses user@xxxxxxxxxxxx and the 11
> newer
> users having user@xxxxxxxxxxxx in addition to companya.com.
>
> The big mistake I made was in removing the tick box in each of the
> original
> users properties email addresses tab
> to "Automatically update email addresses based on recipient policy" so
> that
> existing users not needing companyb.com would not receive this address
> instead of the correct method of creating a second recipient policy and
> filtering on for example the company field for the new users so that > only
> the
> several users who need the companyb address actually receive it. Now > any
> new
> users requiring only the companya adddress receive the
> companyb address and we have to manually edit any new user and remove > the
> tick for recipient policy update.
>
> I would really like to add the second recipient policy with necessary
> filtering etc. to make the setup correct and make all users pull in the
> default recipient policy but as these addresses for all users have been > in
> use for several weeks now will this cause any problems with all user's
> existing mail and companya and companyb email addresses.
>
> Thanks for your help
>
> Colin


In the user account AD properties for all users, specify a company name for
their respective companies under the Organization tab. Then create two
recipient policies, only checking Email Address policy checkbox (not the
Mailbox Management checkbox), one for CompanyA, and one for ComanyB. In the
default policy, leave but uncheck the companya.com and companyb.com email
addresses. In the new CompanyA policy, add the email address companya.com,
and click on Modify Filter. Click on Advanced tab, click on User, select
Company, then select Conditon 'Is Exactly' and type in the company name,
making sure it matches the company name you've populated the Company name
field in the users' AD account properties.

I hope I didn't miss any steps, but that's the jest of it.

Take a look at the following links for more information on how to use
Recipient Policies, as well as using them to control email address
generation based on other requirements, such as first initial lastname, and
much more.

How to use recipient policies to control e-mail addresses
The default recipient policy acts on all objects in the Exchange Server
organization. Do not delete the default policy; however, you can create
additional policies ...
http://support.microsoft.com/kb/319201

HOW TO: Configure Recipient Policies in Exchange
http://support.microsoft.com/kb/249299

I hope that helps.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.


.

Relevant Pages

  • Re: SBS 2008 - "Exchange E-Mail address policy cannot be configured"...
    ... I verified all of that and do not see any policies that would cause ... Check Exchange 2003 policies" part of the following SBS ... " The Exchange E-mail address policy cannot be configured. ... ONLY Mailbox Manager policies and do not define e-mail addresses ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2008 - "Exchange E-Mail address policy cannot be configured"...
    ... I verified all of that and do not see any policies that would cause ... This issue occurs due to mailbox management policies or ... Check Exchange 2003 policies" part of the following SBS ... " The Exchange E-mail address policy cannot be configured. ...
    (microsoft.public.windows.server.sbs)
  • Re: Help needed with recipient policy
    ... get an unintended result from policy, email can still be sent and received. ... Security groups can also be used in this way - one could apply a ... My only concern was that if I start playing around with the policies now ... to "Automatically update email addresses based on recipient policy" so ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2008 - "Exchange E-Mail address policy cannot be configured"...
    ... I verified all of that and do not see any policies that would cause ... SMTP addresses in recipient policies. ... Check Exchange 2003 policies" part of the following SBS ... " The Exchange E-mail address policy cannot be configured. ...
    (microsoft.public.windows.server.sbs)
  • Re: Least User Priviledges for Network Administrators
    ... It makes sense to have a chain of command and approval policy to keep things ... the computer use policies, software purchasing policies, security ... upper management--both within the Network Technology group, ... driving the process of tightening down security. ...
    (microsoft.public.windowsxp.security_admin)