Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XADM: The Recipient Update Service Creates a Random SMTP Proxy Address If the Local Address Is a Single Digit; Fix Requires Exchange 2000 SP3
Article ID: 326382 - View products that this article applies to.
This article was previously published under Q326382
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 "firstname.lastname@example.org."
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.
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.
Cumulative Patch InformationTo 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:
(http://support.microsoft.com/kb/813840/EN-US/ )XGEN: March 2003 Exchange 2000 Server Post-Service Pack 3 Rollup
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. Component: Recipient Update Service
The English version of this fix has the file attributes (or later) that are listed in the following table.
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:
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
(http://support.microsoft.com/kb/301378/EN-US/ )How to Obtain the Latest Exchange 2000 Server Service Pack
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
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.