Hi all... I have an Exchange 2003 server (SP2), and need to add a new domain name that we just acquired. I have added the new domain name to the default recipients policy (and checked the check box). However, I do not see any new email addresses being generated for any of my mailboxes / mail enabled users. Is there some additional step I am missing? Thanks, David

The recipient update service (RUS) is responsible for this, it will happen in the background. If you need to update right away, you can force it to run by right clicking on it in ESM, under recipient update services, and select 'update now'.

They won't be automatically generated unless you say to do so by selecting "Apply this policy now". If you right-click the policy that should be an option.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "david.levine" wrote in message news:fab562d9-a474-43d6-9a0b-31d66ceea17a... Hi all... I have an Exchange 2003 server (SP2), and need to add a new domain name that we just acquired. I have added the new domain name to the default recipients policy (and checked the check box). However, I do not see any new email addresses being generated for any of my mailboxes / mail enabled users. Is there some additional step I am missing? Thanks, David Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

The RUS will stamp new recipients only.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "Mike Pfeiffer" wrote in message news:8d7b17eb-6a39-4b5d-ae5f-35b5a85c0f8b...The recipient update service (RUS) is responsible for this, it will happen in the background. If you need to update right away, you can force it to run by right clicking on it in ESM, under recipient update services, and select 'update now'. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

The RUS will stamp new recipients only. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Mike Pfeiffer" wrote in message news:8d7b17eb-6a39-4b5d-ae5f-35b5a85c0f8b ... The recipient update service (RUS) is responsible for this, it will happen in the background. If you need to update right away, you can force it to run by right clicking on it in ESM, under recipient update services, and select 'update now'. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." ah you're right...for some reason I forgot about the 'apply now' option and had it confused with 'update now'

Thanks for the responses! So - yes - I have hit the "Apply Now" option on my recipient policy. I turned diagnostics logging up to high for all MSExchangeAL activity. I don't see any errors in the event log. However, none of my mail enabled users are getting new email addresses assigned to them. It is mentioned that the RUS will apply the new domain's SMTP address to *new* recipients only. Is this the case? My org isn't that big, but I have about 600 mail enabled users, and would hate to have to write a script or whatever to add a new email address to all of the existing users...? Am I understanding this correctly? Thanks! David

Ok. So the new recipient policy is still not adding email addresses to existing mailboxes, but I just added a new test user from scratch and the recipient policy in question didn't add the desired email address to that on either. So I am doing something wrong I am sure - so I will be a bit verbose in the hopes someone can help me be not so stupid.. :) I have many recipient policies. Most of which were created to allow our Exchange server to accept incoming mail for specific domains that we use with our customers. So traditionally I have not set any filter rules on these policies - since there may only be one or two mailboxes / public folders that I would assign corresponding email addresses to... no big deal. In this case I have created a new recipient policy where I *do* want to have it update (add) an email address to all mail enabled users on my server. For this policy I did specify a filter rule: (&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList) )))) In my hierarchy of recipient policies, this new policy is priority 2. The only policy above it has the same name as my ESM Administrative Group. This is a policy I did not generate myself. It has a filter rule as follows: (&(mailNickname=*)(legacyExchangeDN=/O=NAPCO/OU=NAGLENVIEW/*)) NAGLENVIEW is our administrative group name. So here is what it looks like... Policy: NAGLENVIEW Priority: Highest Filter Rule: (&(mailNickname=*)(legacyExchangeDN=/O=NAPCO/OU=NAGLENVIEW/*)) Email Addresses(Policy): SMTP @nacorporation.com; X400 c=US;a= ;p=NAPCO;o=NAGLENVIEW (The addresses generation rules above are both checked and set as primary) Policy: NACOM Priority: 2 Filter Rule: (&(&(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList) )))) Email Addresses (Policy): SMTP @nacorporation.com; SMTP @na.com; X400 c=US;a= ;p=NAPCO;o=NAGLENVIEW (In the addresses above, @nacorporation is primary for SMTP) Sooo... When I create a new user now, this user only gets an X400 address and one SMTP address for @nacorporation.com. I can only assume that I am being silly with my recipient policies... Maybe I should just add the new domain name (@na.com) to the highest priority policy and see what happens?

My suspicion was right... I was being silly and the email addresses were not being applied because of recipient policy priority and filter rules. I actually moved the newest policy to the top - priority 1. I am curious about the X400 addresses though. We had upgraded over the years from Exchange 5.5 to Exchange 2000 and then to Exchange 2003. Our domain is still running in compatibility mode (can you believe it - one NT4 BDC still exists - I gotta migrate an app off it and kill that thing!), but our Exchange Org is running in native mode (no pre Exchange 2000 servers). Do I even need the X400 stuff anymore? I can't think that I do... ?

Do I even need the X400 stuff anymore? I can't think that I do... ? Yes. Leave it alone. It's certainly not hurting anything. :)

Missy the Kos is right. The address is still required for Exchange 2003 but it can be anything. When you're Exchange 2007 native you can get rid of them.-- Ed Crowley MVP"There are seldom good technological solutions to behavioral problems.". "MissyKos" wrote in message news:9082d7ab-9e2a-4ec1-960c-33c5792100a6... Do I even need the X400 stuff anymore? I can't think that I do... ?Yes. Leave it alone. It's certainly not hurting anything. :) Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."