Microsoft KB Archive/326096

= XADM: The Recipient Update Service Creates a Random SMTP Proxy Address If the Local Address Contains Characters That Are Not Alphanumeric; Fix Requires Exchange 2000 SP2 =

Article ID: 326096

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q326096





SYMPTOMS
The Exchange 2000 Server Recipient Update Service may treat a Simple Mail Transfer Protocol (SMTP) address that contains any characters that are not valid as an address that is not valid.

The local part of the SMTP address of a mailbox appears to the left of the at sign (@) (if the address is in the form @ ). The Recipient Update Service uses the system time to generate a random number for the local part of the SMTP proxy address. Therefore, if a mailbox was created in Exchange with an alias that is similar to &quot;bb&quot;, the SMTP proxy address for that mailbox may appear as an SMTP address with a form that is similar to &quot;s51cf@domain.com.&quot;

Every time that the Recipient Update Service runs to update the recipient list after the default policy has been applied, the Recipient Update Service looks at the %m, which in this case is the alias name equal to &quot;bb&quot;. Even if that alias already has a randomly generated SMTP proxy address, the Recipient Update Service generates an additional randomly generated SMTP proxy address. 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 determines that these SMTP address parts are not valid without stripping off the characters that are not valid &quot;(&quot; and &quot;)&quot;. Therefore, the Recipient Update Service assigns an SMTP address that was generated by using the system time.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend 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:

http://support.microsoft.com/contactus/?ws=support

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:

The English version of this fix has the file attributes (or later) that are listed in the following table.

  File name                 Version -  Ccmproxy.dll              6.0.5771.31 Davex.dll                6.0.5771.31 Drviis.dll               6.0.5771.31 Dsaccess.dll             6.0.5771.31 Dscmsg.dll               6.0.5771.31 Ese.dll                  6.0.5771.31 Eseperf.dll              6.0.5771.31 Eseperf.hxx              N/A Eseperf.ini              N/A Excdo.dll                6.0.5771.31 Eximap4.dll              6.0.5771.31 Exmgmt.exe               6.0.5771.31 Exnntp.dll               6.0.5771.31 Exoledb.dll              6.0.5771.31 Expop3.dll               6.0.5771.31 Exproto.dll              6.0.5771.31 Exprox.dll               6.0.5771.31 Exres.dll                6.0.5771.31 Exsmtp.dll               6.0.5771.31 Exsp.dll                 6.0.5771.31 Exwmi.dll                6.0.5771.31 Febecfg.dll              6.0.5771.31 Iisif.dll                6.0.5771.31 Iisproto.dll             6.0.5771.31 Imap4be.dll              6.0.5771.31 Imap4evt.dll             6.0.5771.31 Imap4fe.dll              6.0.5771.31 Imap4svc.dll             6.0.5771.31 Jcb.dll                  6.0.5771.31 Mad.exe                  6.0.5771.31 Madmsg.dll               6.0.5771.31 Mdbmsg.dll               6.0.5771.31 Mdbsz.dll                6.0.5771.31 Msgtrack.dll             6.0.5771.31 Nntpex.dll               6.0.5771.31 Pcproxy.dll              6.0.5771.31 Phatcat.dll              6.0.5771.31 Pop3be.dll               6.0.5771.31 Pop3evt.dll              6.0.5771.31 Pop3fe.dll               6.0.5771.31 Pop3svc.dll              6.0.5771.31 Protomsg.dll             6.0.5771.31 Store.exe                6.0.5771.31 Tokenm.dll               6.0.5771.31 X400prox.dll             6.0.5771.31 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.



MORE INFORMATION
This particular fix package was created as a post-Exchange 2000 Server Service Pack 2 (SP2) fix. However, the actual fix is not included in Exchange 2000 Server Service Pack 3 (SP3). A separate fix package is available that resolves this problem on Exchange 2000 Server SP3 computers.

Additional query words: RUS

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB326096

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.