Article ID: 307846
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q307846
SYMPTOMS
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.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix has the following file attributes or later:
Component: Recipient Update Service
| File name | Version |
|---|---|
| Davex.dll | 6.0.5770.98 |
| Dsaccess.dll | 6.0.5770.98 |
| Dscmsg.dll | 6.0.5770.98 |
| Excdo.dll | 6.0.5770.98 |
| Exmgmt.exe | 6.0.5770.98 |
| Exoledb | 6.0.5770.98 |
| Exprox.dll | 6.0.5770.98 |
| Exres.dll | 6.0.5770.98 |
| Exsp.dll | 6.0.5770.98 |
| Exwmi.dll | 6.0.5770.98 |
| Jcb.dll | 6.0.5770.98 |
| Mad.exe | 6.0.5770.98 |
| Mdbmsg.dll | 6.0.5770.98 |
| Mdbsz.dll | 6.0.5770.98 |
| Phatcat.dll | 6.0.5770.98 |
| Store.exe | 6.0.5770.98 |
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 2.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
Additional query words: RUS
Keywords: kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB307846
