XADM: The Recipient Update Service Creates a Random SMTP Proxy Address If the Local Address Is a Single Digit; Fix Requires Exchange 2000 SP3 (326382)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q326382

SYMPTOMS

The Exchange 2000 Server Recipient Update Service may treat Simple Mail Transfer Protocol (SMTP) addresses that contain a single digit for the local part of the mailbox as an address that is not valid.

The local part of a mailbox SMTP address appears left of the at sign (@) if the address is in the form local@domain. The Recipient Update Service uses the system time to generate a random number for the local part of the SMTP proxy address. Therefore, if you create a mailbox in Exchange 2000 with an alias of "1" or "2", the SMTP proxy address for that mailbox may appear as an SMTP address in a form that is similar to "s51cf@domain.com."

Every time that the Recipient Update Service runs to update the recipient list after the default policy is applied, the Recipient Update Service looks at the %m, which in this case is the alias name set equal to a single digit (such as "1"). Even if that alias already has a randomly generated SMTP proxy address, the Recipient Update Service generates an additional randomly generated SMTP proxy address because the %m for the user has a single digit for its alias name. The newly generated random SMTP proxy is then set to be the new default SMTP proxy address for the mailbox. However, the old SMTP proxy address is also still present.

CAUSE

This problem occurs because the Exchange 2000 Server Recipient Update Service incorrectly determines that these single-digit local SMTP address parts are not valid and assigns a system time-generated SMTP address.

RESOLUTION

Cumulative Patch Information

To resolve this problem, obtain the March 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

813840 XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Component: Recipient Update Service

The English version of this fix has the file attributes (or later) that are listed in the following table.
   File name      Version    
   -------------------------
   Inproxy.dll    6.0.6301.0
   Mad.exe        6.0.6301.0
   X400prox.dll   6.0.6301.0
   Pcproxy.dll    6.0.6301.0
   Ccmproxy.dll   6.0.6301.0
				
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

MORE INFORMATION

An SMTP address that contains a single digit left of the at sign (@) is valid in accordance with the Request for Comments (RFC) 821 document.


Modification Type:MinorLast Reviewed:10/10/2005
Keywords:kbHotfixServer kbQFE kbbug kbExchange2000preSP3fix kbExchange2000preSP4fix kbExchange2000sp3fix kbfix kbQFE KB326382