SYMPTOMS
Consider this scenario:
- Server A, Server B, and Server C are located in three different Microsoft Exchange Server 2003 organizations.
- Each organization is Defense Message System (DMS)-enabled.
- Server A is connected to Server B by an X400 connector.
- Server B is connected to Server C by an X400 connector.
- An e-mail message is sent from an Exchange Server 2003 mailbox that is located on Server A to an invalid Exchange Server 2003 recipient that is located on Server B.
- The message is forwarded to a valid alternative recipient that is located on Server C.
In this scenario, a non-delivery report (NDR) is received by the message originator on Server A.
Additionally, you may experience the following symptoms:
- Exchange Server 2003 does not include the redirection history with the original recipient name on originator requested alternative recipient (ORAR) rerouting that uses the Extension 25 property.
- Address length padding is miscalculated when Exchange Server 2003 validates the PR_REDIRECTION_HISTORY property.
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:
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
Because of file dependencies, this hotfix requires that you install Microsoft Exchange Server 2003 Service Pack 1 and the following hotfixes in the order that they appear in:
883938 Redirection history is not included with the original recipient name on ORAR rerouting in Exchange Server 2003
883940 Address length padding may be miscalculated when Exchange Server 2003 validates the PR_REDIRECTION_HISTORY property
Restart requirement
You do not have to restart your computer after you apply this hotfix. However, all the following services are automatically stopped and then restarted when you apply this hotfix:
- Microsoft Exchange MTA Stacks
- Microsoft Exchange Information Store
Hotfix replacement information
This hotfix does not replace any other software updates.
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
--------------------------------------------------------------
25-Aug-2004 18:46 6.5.7232.30 3,591,680 Emsmta.exe
25-Aug-2004 18:35 6.5.7232.30 8,192 Maxapiv1.dll
25-Aug-2004 18:35 6.5.7232.30 7,168 Mtxapiv1.dll
25-Aug-2004 18:35 6.5.7232.30 30,720 X400omv1.dll