Article ID: 288109 - View products that this article applies to.
This article was previously published under Q288109
This article has been archived. It is offered "as is" and will no longer be updated.
This article lists the article numbers for Exchange 2000 Server transport bugs that have been fixed since Exchange 2000 was released.
For more information about how to obtain the fixes that are listed in this article, see the "More Information" section of this article, and then click the article number.
NOTE: Exchange 2000 fixes for a particular component are cumulative and contain all of the previous fixes for that component. Fixes with a particular version number contain all of the fixes that have an earlier version number.
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:
(https://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Transport fixes contain the following files:
Collapse this tableExpand this table
Fixes Released on February 3, 2001The following files are modified:
(https://support.microsoft.com/kb/275596/EN-US/ )XADM: MAPI Messages Stack Up in Send Queue to the Host Specified in Forward Unresolved Recipients
(https://support.microsoft.com/kb/278234/EN-US/ )XCON: SMTP Does Not Support the "Require TLS Encryption for Clear Text Authentication" Feature
(https://support.microsoft.com/kb/278235/EN-US/ )XADM: Exchange 2000 Can't Manage a Very Large Number of Domain Queues Simultaneously
(https://support.microsoft.com/kb/279209/EN-US/ )XCON: Leading Space in Distribution List Name Is Causing Non-Delivery Report
(https://support.microsoft.com/kb/279616/EN-US/ )XCON: Adding a Registry Key to Re-Categorize Messages