Exchange Server 2003 may generate NDRs for messages that are routed to another organization when you connect Exchange Server 2003 to multiple organizations by using X.400 connectors (911029)

SYMPTOMS

Consider the following scenario. You connect Microsoft Exchange Server 2003 to multiple organizations by using X.400 connectors. These organizations use third-party mail transfer agents (MTAs). In this scenario, Exchange Server 2003 may generate non-delivery reports (NDR) for some messages that are sent to the third-party MTA if the destination server of the primary X.400 connector is unavailable. You expect Exchange Server 2003 to deliver messages to the destination MTA over the secondary X.400 connector if the destination server of the primary X.400 connector is unavailable.

CAUSE

This problem occurs if a message includes a private extension in the message envelope. Exchange Server 2003 identifies a private extension in the message envelope by using an object identifier instead of an integer. This behavior does not strictly comply with the 1988 X.400 standards. According to these standards, an object identifier can be used to identify a private extension in the message envelope only in and between private management domains (PRMDs). However, only an integer can be used to identify a private extension in the message envelope in an administrative management domain (ADMD). Therefore, a third-party MTA that strictly enforces the X.400 protocol may reject a message that contains a private extension in the message envelope if that message is routed to another organization.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, the Microsoft Exchange Information Store service together with its dependant services are automatically stopped and then restarted when 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.

File name	File version	File size	Date	Time	Platform
Mdbmsg.dll	6.5.7234.4	3,269,632	03-Mar-2006	23:31	x86
Redir.asp	Not applicable	3,304	29-Jan-2006	20:50	Not applicable
Store.exe	6.5.7234.4	5,201,408	04-Mar-2006	00:03	x86

MORE INFORMATION

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates