Microsoft KB Archive/925004

= A non-delivery report message does not contain all the supplemental information in Exchange Server 2003 =

Article ID: 925004

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-



SYMPTOMS
Consider the following scenario in Microsoft Exchange Server 2003:
 * The Locale ID property of your mailbox is set to a language that is not English.

Note This condition occurs after you previously logged on to the mailbox from a Microsoft Outlook client or a computer whose language setting is other than English.
 * You send an e-mail message to an external address that does not exist in order to obtain a non-delivery report (NDR).

In this scenario, the NDR message may not contain all the supplemental information.

For example, if the Locale ID property of your mailbox is set to English, the NDR message resembles the following message:

Your message did not reach some or all of the intended recipients. Subject:  Sent:   The following recipient(s) could not be reached:   on  The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. 

However, if the Locale ID property of your mailbox is set to a language that is not English, the NDR message resembles the following message:

Your message did not reach some or all of the intended recipients. Subject:  Sent:   The following recipient(s) could not be reached:   on   The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator.



CAUSE
This problem occurs because the supplemental information is stored in the PR_SUPPLEMENTARY_INFO MAPI property of the NDR message. If the Locale ID property of the mailbox is set to a language that is not English, the supplementary information is discarded when the NDR is processed.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2 (SP2) to be installed on the server.

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

836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, the following services are automatically stopped and then restarted when you apply this hotfix:
 * Microsoft Search
 * Microsoft Exchange Information Store
 * World Wide Web Publishing Service
 * Simple Mail Transfer Protocol (SMTP)
 * Microsoft Exchange Routing Engine
 * Network News Transfer Protocol (NNTP)
 * HTTP SSL
 * IIS Admin Service

Hotfix replacement information
This hotfix does not replace any other hotfix.

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 item in Control Panel.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



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

812806 Exchange user unexpectedly receives a standard NDR instead of a custom NDR

Keywords: kbexpertisebeginner kbexchtransport kbqfe KB925004

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.