Article ID: 883949 - View products that this article applies to.
Consider this scenario:
In this scenario, a non-delivery report (NDR) is received by the message originator on Server A.
Additionally, you may experience the following symptoms:
This problem occurs because the X.500 distinguished name is removed from the ORAR in Exchange Server 2003.
Hotfix informationA 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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, contact 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
PrerequisitesBecause 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:
(http://support.microsoft.com/kb/883938/ )Redirection history is not included with the original recipient name on ORAR rerouting in Exchange Server 2003
(http://support.microsoft.com/kb/883940/ )Address length padding may be miscalculated when Exchange Server 2003 validates the PR_REDIRECTION_HISTORY property
Restart requirementYou 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:
Hotfix replacement informationThis hotfix does not replace any other software updates.
File informationThe 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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information about this scenario, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/889463/ )Description of updates for problems with forwarded messages in DMS-enabled Exchange Server 2003 organizations
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
(http://support.microsoft.com/kb/817903/ )New naming schema for Exchange Server software update packages
Article ID: 883949 - Last Review: October 25, 2007 - Revision: 2.3
Contact us for more help
Connect with Answer Desk for expert help.