Description of updates for problems with forwarded messages in DMS-enabled Exchange Server 2003 organizations

This article has been archived. It is offered "as is" and will no longer be updated.
Consider this scenario:
  • Server A, Server B, and Server C are located in three different Exchange organizations.
  • Each organization is Defense Message System (DMS)-enabled.
  • Server A is connected to Server B by an X.400 connector.
  • Server B is connected to Server C by an X.400 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, 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.
  • A non-delivery report (NDR) is received by the message originator on Server A.

Hotfix information

Three supported hotfixes are now available from Microsoft, but they are only intended to correct the problem that is described in this article. Only apply them to systems that are experiencing this specific problem. These hotfixes 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 these hotfixes.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfixes. For a complete list of Microsoft Product Support Services phone 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.


Because of file dependencies, these hotfixes require that you install Microsoft Exchange Server 2003 Service Pack 1.

Restart requirement

You do not have to restart your computer after you apply these hotfixes. However, all the following services are automatically stopped and then restarted when you apply these hotfixes:

  • IIS Admin
  • Microsoft Exchange MTA Stacks
  • Microsoft Exchange Information Store
  • Microsoft Exchange Routing Engine
  • Simple Mail Transfer Protocol (SMTP)
  • World Wide Web Publishing Service

Hotfix replacement information

These hotfixes replace the following software update: 871223.

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   --------------------------------------------------------------   18-Aug-2004  02:26  6.5.7232.27        46,080  E2kdsn.dll          18-Aug-2004  03:06  6.5.7232.27       456,704  Phatcat.dll         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        10-Sep-2004  00:42  6.5.7232.33     3,230,720  Mdbmsg.dll          10-Sep-2004  01:19  6.5.7232.33     5,132,800  Store.exe        

Hotfix installation information

To resolve this problem, you must install the following three 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

883949 Message originator may receive an NDR when a message is forwarded to a valid alternative recipient in Exchange Server 2003
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional 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
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
817903 New naming schema for Exchange Server software update packages

Article ID: 889463 - Last Review: 01/15/2015 08:08:48 - Revision: 1.3

Microsoft Exchange Server 2003 Standard Edition, Microsoft Exchange Server 2003 Enterprise Edition

  • kbnosurvey kbarchive kbtransport kbexchange2003presp2fix kbqfe kbfix kbbug KB889463