The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SYMPTOMSYou may have difficulty delivering messages with the Microsoft Exchange Server message transfer agent (MTA). The symptoms for this problem are as follows:
CAUSEThis problem is caused by time consuming fuzzy proxy directory service searches on large global address lists. RESOLUTIONApply the fix mentioned in the "Status" section of this article. If this fix does not correct the problem, perform one of the following steps:
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. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD). SYSTEM\CurrentControlSet\Services\MSExchangeMTA\Parameters STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server, version 4.0. This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. 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 MORE INFORMATIONThis behavior may occur if the MTA attempts to deliver a message addressed to an X.400 proxy that does not exactly match an address in the global address list, and the proxy contains a substring that is similar to other addresses in the global address list. For example, message delivery may be slow if a message is addressed to an X.400 proxy that is similar to the following: X400:C=US;A= ;P=Microsoft;CN=PaulBonThis address does not fully match the defined X.400 address for that mailbox. The MTA makes a request for the DS to resolve the address if there are thousands of other X.400 proxies in the global address list that contain the following substring: X400:C=US;A= ;P=MicrosoftIf the directory service is unable to resolve the full address by means of an exact match, the directory service attempts to perform a fuzzy proxy search based on the parsed substrings. By default, the MTA attempts to perform a fuzzy proxy search if it is unable to match the O/R address when it performs a DS_Search. To disable the fuzzy proxy search, add the Allow fuzzy proxy search registry value and set it to 0. For additional information about the fuzzy proxy search in Microsoft Exchange Server versions 5.0 and 5.5, click the article number below to view the article in the Microsoft Knowledge Base: Q176046 XCON: Routing Issues with Microsoft Exchange Server, Version 5.0 Additional query words: DS
Keywords : kbfix4.00.sp4 XADM exc4 |
Last Reviewed: February 3, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |