XCON: Routing Issues with Microsoft Exchange Server, Version 5.0

 Last reviewed: February 12, 1998
Article ID: Q176046
The information in this article applies to:
  • Microsoft Exchange Server, version 5.0

SYMPTOMS

A message from a Microsoft Exchange user to a recipient on a remote X.400 system may be routed to a local recipient. This can happen if the address of the local recipient and the recipient on the remote X.400 system are similar. For example, the local recipient has the following X.400 address: 

   C=US;A=PTT;P=COMPANY;S=USER1
and the address of the remote X.400 recipient is: 

   C=US;A=PTT;S=USER1
Note that the remote address matches the address of the local recipient, except that there is no Private Management Domain (P=...) defined. Both addresses are syntactically correct and valid.

CAUSE

Microsoft Exchange Server, version 5.0 uses a slightly different algorithm for address resolution. Even if the registry key Allow Fuzzy Proxy Search is disabled, it still uses a fuzzy algorithm in certain cases.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K

RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

To resolve this problem, apply the fix referenced below. You will also need to create a new entry in the Windows NT registry. To do this:

  1. Start the Windows NT Registry Editor.
2. Go to the following subkey: 

   \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMTA\
    Parameters

  • Create the new registry value as: 

          Allow fuzzy proxy search

    and set it to 2. This case-sensitive registry value is a DWORD.

    If this Registry value does not exist in the registry, the Microsoft Exchange Message Transfer Agent (MTA) will assume a value of 1 for this setting and thus fuzzy proxy searches are enabled.

    This value has three possible settings:

    1. Allow fuzzy proxy search=0. Restricted fuzzy proxy search allowed. A unique match on the Surname and the Given Name or an exact match is allowed.
    2. Allow fuzzy proxy search=1. Full fuzzy proxy search. 3. Allow fuzzy proxy search=2. No fuzzy proxy search at all, only an exact 
       match is allowed.

    REFERENCES

    For more information about the Fuzzy proxy search in Microsoft Exchange Server, version 4.0, please refer to the following article in the Microsoft Knowledge Base: 

       ARTICLE-ID: Q159184
   TITLE: XADM: MTA Fails to Deliver Messages with High DS Activity

    • Additional query words:
    Keywords : kbbug5.00 kbfix5.00.sp2 XCON buglist
    Version : 5.0
    Platform : winnt
    Issue type : kbbug
    Solution Type : kbfix

    THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

    Last reviewed: February 12, 1998
    © 1998 Microsoft Corporation. All rights reserved. Terms of Use.