Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XADM: Recipient Update Service Stamps Duplicate Proxy Addresses
Article ID: 315900 - View products that this article applies to.
This article was previously published under Q315900
The Recipient Update Service may stamp objects with proxy addresses with conflicting e-mail address proxies. Objects that may be affected include:
E-mail address proxies are run through a uniqueness checker before they are stamped onto the corresponding directory objects. In versions of Exchange that are earlier than Exchange 2000 Server Service Pack 2 (SP2), this uniqueness checker stops looking for additional duplicate proxies after it finds the first duplicate proxy address; therefore, any additional conflicting proxy addresses are accepted and conflicts are created. These conflicts cause duplicate proxy addresses to be created.
In this example, recipient policy for the following sample users is set as follows:
SMTP: @a.comActive Directory contains objects Y and Z with the following proxies:
Y: SMTP:email@example.comProxies are generated for a new object X. The first attempt at generating proxies (before the uniqueness check) produces the following:
X: SMTP:firstname.lastname@example.orgTo perform the uniqueness check, Exchange 2000 searches for any object with any of those proxies. One conflict is reported. The uniqueness check determines that these proxies cannot be used because object Y is using email@example.com. Therefore, the proxies are adjusted to:
X: SMTP:firstname.lastname@example.orgThe uniqueness checker does not recognize that email@example.com is also not unique because of object Z (the uniqueness checker only looks at Y).
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:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
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 2.
After you apply Exchange 2000 Server service pack, the uniqueness checker is modified to catch all of the instances of conflicting proxies, instead of just the first instance.
The expected results for the example in the "Cause" section of this article are that the user X is stamped so that all of the proxies are unique: