The X.400 connector does not add an entry to the message tracking log when you forward an e-mail message from Exchange 2000 Server to another mail server through an X.400 connector

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
You receive a Simple Mail Transfer Protocol (SMTP) e-mail message from an external organization. When you forward the message from Microsoft Exchange 2000 Server to another mail server through an X.400 connector, the X.400 connector does not add an entry to the message tracking log.
Cause
The SMTP service uses the Request for Comments (RFC) 822 message ID to write the message tracking logs. However, the message transfer agent (MTA) service uses the message transfer system ID (MTS-ID) to write the message tracking logs. To relate the message tracking log entries with the RFC 822 message ID and with the MTS-ID, each entry can contain a linked message ID field.

In a pure SMTP submission, an MTS-ID is not added until the message is submitted to the Microsoft Exchange Information Store service for gateway delivery. Therefore, a link is not established in the message tracking logs. When the MTA service writes the message tracking logs for the outgoing X.400 transfer, the MTA service does not write the RFC 822 message ID in the linked message ID field.
Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Because of file dependencies, this hotfix requires Microsoft Windows 2000 Service Pack 4 (SP4). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to obtain the latest Windows 2000 service pack

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version      Size      File name   -------------------------------------------------------   14-Jul-2004   19:59   6.0.6611.0   331,776   Exsmtp.dll     
Status
Microsoft has confirmed that this is a problem in Exchange 2000 Server.
More information
After you apply this hotfix, an MTS-ID is added before a message is submitted to the Microsoft Exchange Information Store service for gateway delivery. Therefore, the MTA service will write the RFC 822 message ID in the linked message ID field.
XCON
Właściwości

Identyfikator artykułu: 830369 — ostatni przegląd: 11/02/2013 18:17:00 — zmiana: 3.0

  • Microsoft Exchange 2000 Server Standard Edition
  • Microsoft Exchange 2000 Enterprise Server
  • kbnosurvey kbarchive kbautohotfix kbexchcoexistmigration kbfix kbexchange2000presp4fix kbbug kbhotfixserver kbqfe KB830369
Opinia