This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
Messages on an Exchange 2000 server may get stuck in the pre-routing queue if Microsoft Internet Information Service (IIS) has overwritten the Exchange 2000 configuration. It is very unlikely that this can happen, however, if this does occur, all the messages will not get routed. To correct this problem, refer to the "More Information" section.
The following error message may be logged in the Application event log:
Event Type: Warning Event Source: smtpsvc Event Category: None Event ID: 4000 Date: 10/30/2000 Time: 2:10:10 PM User: N/A Computer: SERVERNAME Description: Message delivery to the remote domain '_c78290b817c75f4bac724d36582fdeea_D' failed. The error message is 'Unable to bind to the destination server in DNS.
You can use a telnet connection to the server on port 25 to identify if the wrong version of the .dll file is used. At a command prompt, type telnet hostname 25. You will receive a response such as
"220 hostname Microsoft ESMTP MAIL Service, Version: 5.0.2195.1600 ready at Thu, 16 Nov 2000 12:25:39 -0600" [User name]
Next, type ehlo. You will see a list of supported commands, such as following:
If you are missing commands such as X-LINK2STATE OR XEXCH50, the Microsoft Windows 2000 version of the .dll is in use instead of the Exchange 2000 version.
For more information about the latest service pack for Microsoft Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Implement the following registry key that will cause recategorization of mail sitting in the pre-routing queue.