E2K3 Multiple recipient policies
BruceE
policy for SMTP addresses and a new policy for Mailbox Management. Based on
what I read in KB 319201 will the Primary AND the MM policies both get
applied properly, or do I need one or more policies that does both email
addresses and MM in the same policy. Both the Primary and MM policies broke,
but possibly for different reasons. Now the gory details.
We had two policies in our E2K3 environment. Default, which did SMTP
@phoenix.gov and X.400. For our standard of firstname...@phoenix.gov I
used another policy (Primary). That policy also did Mailbox Management and
deleted everyones email after 32 days.
We needed to change the MM, so I removed it from the Primary policy but left
the SMTP template in place to continues generating the email addresses. I
then built a new recipient policy to just do MM and not email addresses. I
based the new policy on a group that everyone who needed to delete email
after 32 days would belong to (I found KB 304516 about using memberOf and I
am evaluating my options for that issue).
What I discovered yesterday is that email addresses were not longer being
generated by the Primary policy, but by the Default as al...@phoenix.gov.
This first showed up as we are part of the City's Domino domain so we import
their directory entries as Contacts and generate the SMTP address. The
Contact records were switching over to al...@phoenix.gov . I then found that
if I built a new user account, the SMTP address appeared as al...@phoenix.gov
instead of firstname...@phoenix.gov.
I finally got the Primary policy to "reactivate" by adding the MSMail
address to the template but I didnt reapply the policy as I didn't to break
any manually created SMTP addresses. Everyone who's account or Contact was
set to Automatically update got a MSMail address though. Oh well, we don't
use that. Then I fixed the Contacts by have the Lotus Notes Connector do a
full directory reload and those addresses went back to
firstname...@phoenix.gov.
That was the biggest issue. A second issue was with Mailbox Management.
After the initial build of the seperate policy, all the mailboxes that were
supposed to get cleaned were, during the first run. Then I noticed several
days later that fewer and fewer mailboxes were getting cleaned. One of them
that was getting skipped was mine and I could see the older email in my
mailbox. Now I find KB 304516 that talks about the memberOf issue and that
is what I used for MM.
Thanks in advance.
--
Bruce R. Ellefritz
Lead User Tech. Spec.
Computer Services Bureau
Phoenix Police Dept.
bruce.e...@phoenix.gov
602-262-1893
Rich Matheisen [MVP]
>Order of precendence question. We have the Default policy, also Primary
>policy for SMTP addresses and a new policy for Mailbox Management. Based on
>what I read in KB 319201 will the Primary AND the MM policies both get
>applied properly,
Yes, but you may need to apply the MM policy manually (depends on
where it is in the priorities list)
>or do I need one or more policies that does both email
>addresses and MM in the same policy.
No.
>Both the Primary and MM policies broke,
>but possibly for different reasons. Now the gory details.
>
>We had two policies in our E2K3 environment. Default, which did SMTP
>@phoenix.gov and X.400. For our standard of firstname...@phoenix.gov I
>used another policy (Primary). That policy also did Mailbox Management and
>deleted everyones email after 32 days.
>
>We needed to change the MM, so I removed it from the Primary policy but left
>the SMTP template in place to continues generating the email addresses.
It probably would have been cleaner to just remove the whole policy
and replace it with what you wanted. But that advice needs to be taken
with a grain of salt because it assumes that you don't have a
gazillion mail- and mailbox-enabled objects in the AD, and that the AD
objects all have the necessary attributes so they'll be found by the
LDAP filter on the policy.
>I
>then built a new recipient policy to just do MM and not email addresses. I
>based the new policy on a group that everyone who needed to delete email
>after 32 days would belong to (I found KB 304516 about using memberOf and I
>am evaluating my options for that issue).
>
>What I discovered yesterday is that email addresses were not longer being
>generated by the Primary policy, but by the Default as al...@phoenix.gov.
Assuming the "Primary" policy has a higher priority (i.e. numerically
lower value) than the "Default" policy that sounds like the LDAP
filter is wrong, or the AD objects don't have the correct attributes.
>This first showed up as we are part of the City's Domino domain so we import
>their directory entries as Contacts and generate the SMTP address. The
>Contact records were switching over to al...@phoenix.gov . I then found that
>if I built a new user account, the SMTP address appeared as al...@phoenix.gov
>instead of firstname...@phoenix.gov.
>
>I finally got the Primary policy to "reactivate" by adding the MSMail
>address to the template but I didnt reapply the policy as I didn't to break
>any manually created SMTP addresses.
Any addresses that are in violation of the policy should have the
check box cleared to avoid problems like this.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.p...@getronics.com
Or to these, either: mailto:h.p...@pinkroccade.com mailto:melvin.mcp...@getronics.com mailto:melvin.mcp...@pinkroccade.com