XADM: A Requested Delivery Receipt Contains the Message Attachment That You Sent (817299)

SYMPTOMS

When you send a message that contains an attachment, and you request a delivery receipt for that message, the delivery receipt message that you receive contains the message attachment. The delivery receipt message is not expected to contain the attachment.

this problem occurs after you configure the following registry key to remove attachments from returned messages:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SMTPSVC

For additional information about this registry key, click the following article number to view the article in the Microsoft Knowledge Base:

308303 XCON: Option to Strip Attachments for Messages That Generate an NDR

CAUSE

This problem occurs if you request a delivery receipt for a message that you sent from a Microsoft Exchange Server 5.5 organization to an Exchange 2000 Server organization.

The registry key configuration that is described in the Knowledge Base article 308303 works correctly when you from an Exchange 2000 computer to another Exchange 2000 computer. However, when you request delivery receipts for messages that are sent from an Exchange Server computer to an Exchange 2000 computer, the registry key configuration does not work correctly unless the destination mailbox is not located on the bridgehead server.

Note This issue also occurs when you receive a non-delivery report (NDR).

RESOLUTION

Cumulative Rollup Information

To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information

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

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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
-----------------------------------------------------------
20-Mar-2003  19:32  6.0.6442.0        499,712  Phatq.dll

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack