XADM: Recipient Update Service Creates Duplicate Proxy Addresses

Article translations Article translations
Article ID: 321507 - View products that this article applies to.
This article was previously published under Q321507
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

You may notice that similarly named user accounts contain the same proxy address. For example JOE USER in DomainA and JOE USER in DomainB may both have the same Simple Mail Transfer Protocol (SMTP) proxy address:
Juser@EMailDomainName.com
You may also receive non-delivery reports (NDRs) for all mail that is addressed to one of these mailboxes.

CAUSE

When an user object in Active Directory is mailbox-enabled, the Recipient Update Service generates proxy addresses for the object. Before the proxy addresses are actually stamped on the object, temporary proxy addresses are created, and then verified for uniqueness. To do this, the Recipient Update Service compares the temporary addresses that are generated for the object with other objects in the domain and forest. If the Recipient Update Service finds another object that contains a proxy address that conflicts with the temporary addresses, new proxies are generated for the addresses that conflict. If this conflict occurs in the same domain, the Recipient Update Service stamps the object with unique addresses but never checks other domains to make sure that the address is unique across all of the forest.

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 should have the following file attributes or later:

Collapse this tableExpand this table
File nameVersion
Mad.exe6.0.5770.98

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server 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.

Properties

Article ID: 321507 - Last Review: October 24, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB321507

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com