The secondary SMTP proxy e-mail address is not stamped on migrated objects

When you migrate users from a Microsoft Exchange 2000 Server or Microsoft Exchange Server 2003 organization in one forest to an Exchange 2000 or Exchange 2003 organization in a separate forest, the secondary SMTP proxy e-mail address from the recipient policy of the destination domain is not stamped on the migrated user accounts.

This behavior may occur if all the following conditions are true:

• You configure the same SMTP e-mail address as the primary e-mail address policy in the Exchange 2000 or Exchange 2003 recipient policy in each forest (shared SMTP-namespace).
  
  Note This is the typical configuration in a cross-forest Exchange 2000 or Exchange 2003 deployment.
• You configure secondary forest-specific SMTP e-mail addresses (type, smtp) in the Exchange 2000 or Exchange 2003 recipient policy in each forest.
• You synchronize the forests.
• You migrate a user from one forest to the other.

This behavior occurs because the Recipient Update Service determines that the migrated user already has the proxyAddresses attribute populated. Because the attribute is populated, secondary SMTP addresses are not generated. Secondary proxies are added only when one of the following conditions is true:

• The recipient has nothing at all in the proxyAddresses attribute. For example, the recipient is brand new in the organization or the recipient wasn’t migrated.
• The secondary proxies are present in the gatewayProxy attribute on the domainNC Recipient Update Service object. This means that the recipient policy is being applied against the organization.

To work around this behavior, manually apply the recipient policy. To do so, follow these steps:

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand Recipients, right-click the policy that you want to apply, and then click Apply this policy now.

Microsoft Exchange Server 2003 Service Pack 1 (SP1) adds new functionality to the Recipient Update Service. When the Exchange Server 2003 SP1 Migration Wizard is used to migrate a user, a new GUID is added to the MSExchPoliciesIncluded attribute of that user. The GUID that is added to the MSExchPoliciesIncluded attribute is the following:When the Recipient Update Service is running on an Exchange Server 2003 SP1 server, the Recipient Update Service will recognize that specific GUID and act as if the policy has been applied to that user. This causes the secondary proxy addresses to be added to the recipient.

If recipients were not migrated by using the Exchange Server 2003 SP1 Migration Wizard and if your Recipient Update Service is running on an Exchange Server 2003 SP1 server, you can still take advantage of this new functionality. To do this, add the GUID that was mentioned earlier to the MSExchPoliciesIncluded attribute of those recipients whose proxy addresses should be generated. The MSExchPoliciesIncluded attribute can either be manually set or set in bulk by using a script or an LDIFDE import.

For more information about the steps that are used by the Recipient Update Service to evaluate recipients, click the following article number to view the article in the Microsoft Knowledge Base: When you create a new account, there is no proxy address. The Recipient Update Service applies all policies to the mailbox and all the proxy addresses are stamped. However, when you migrate a user who already has the proxy addresses stamped, when the Recipient Update Service parses this account, it does not change the addresses that already exist. The Recipient Update Service only stamps the account with recipient policy proxy addresses that are not present. For more information about how the Recipient Update Service applies recipient policies, click the following article number to view the article in the Microsoft Knowledge Base: