The Recipient Update Service may occasionally stamp users with addresses that are based on incorrect recipient policies.
For example, user accounts that are created with a legacyExchangeDN that starts with /o=
Org/ou=AG2 are stamped with the AG2.
Org.com SMTP address if three recipient policies are defined that are configured to stamp addresses based on the legacyExchangeDN attribute (in the order of priority):
Policy 1: /o=Org/ou=AG1 - SMTP:@AG1.Org.com
Policy 2: /o=Org/ou=AG2 - SMTP:@AG2.Org.com
Default Policy: SMTP:@Org.com
If a fourth policy is introduced (for example, Policy 3: /o=
Org/ou=AG3 - SMTP:@AG3.
Org.com), the new policy list is typically (in the order of priority):
Policy 1: /o=Org/ou=AG1 - SMTP:@AG1.Org.com
Policy 2: /o=Org/ou=AG2 - SMTP:@AG2.Org.com
Policy 3: /o=Org/ou=AG3 - SMTP:@AG3.Org.com
Default Policy: SMTP:@Org.com
Therefore, a user account that is created with a legacyExchangeDN that starts with /o=
Org/ou=AG3 is stamped with the AG3.
Org.com SMTP address (the third policy in the list). However, for a short time after the new policy is introduced, the policy list may look similar to (in the order of priority):
Policy 1: /o=Org/ou=AG1 - SMTP:@AG1.Org.com
Policy 2: /o=Org/ou=AG2 - SMTP:@AG2.Org.com
Default Policy: SMTP:@Org.com
Policy 3: /o=Org/ou=AG3 - SMTP:@AG3.Org.com
During this time, the Recipient Update Service may stamp new or existing user accounts that are created with a legacyExchangeDN that start with /o=
Org/ou=AG3 with the third policy in the list, which is the default policy in this example.