XCON: Adding a Registry Key to Re-Categorize Messages (279616)

SUMMARY

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:

250-hostname Hello [IP Address]
250-TURN
250-ATRN
250-SIZE
250-ETRN
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-8bitmime
250-BINARYMIME
250-CHUNKING
250-VRFY
250-X-EXPS GSSAPI NTLM LOGIN
250-X-EXPS=LOGIN
250-AUTH GSSAPI NTLM LOGIN
250-AUTH=LOGIN
250-XEXCH50
250-X-LINK2STATE
250 OK

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 additional information about the latest service pack for Microsoft Exchange 2000 Server, click the article number below to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Implement the following registry key that will cause re-categorization of mail sitting in the pre-routing queue.

Start Registry Editor (Regedt32.exe).
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SMTPSVC\Queuing\
On the Edit menu, click Add Value, and then add the following registry value:
Value Name: ResetMessageStatus
Data Type: REG_DWORD
Radix: Hexadecimal
Value: 1
Quit Registry Editor.

After you add the preceding registry value:

Re-install Exchange 2000 to restore the proper Exchange 2000 configuration.
During the upgrade, SMTPSVC will be stopped and restarted. After SMTPSVC is automatically restarted, the previously queued messages to be enumerated and reprocessed.
After upgrade is completed and SMTPSVC has been restarted, you can delete the ResetMessageStatus registry key.

If Exchange 2000 has already been reinstalled without setting the ResetMessageStatus registry key, some of the messages will remain stuck in the pre-routing queue. To resolve this:

At a command prompt, run the following command:
net stop SMTPSVC
Set the ResetMessageStatus registry key to a value of 1.
At a command prompt, run the following command:
net start SMTPSVC
Previously queued messages will be enumerated and reprocessed.
Delete the ResetMessageStatus registry key.

NOTE: Unless you implement the ResetMessageStatus registry entry, all mail that was categorized without Exchange 2000 will eventually generate non-delivery reports (NDRs).

For additional information about how to download the fix that contains this feature, click the article number below to view the article in the Microsoft Knowledge Base:

291222 XGEN: Rollup of Selected Exchange 2000 Server Post-Release Fixes

The English version of this feature should have the following file attributes or later:

Component: Transport

File name	Version
Phatq.dll	6.0.4418.25