Microsoft KB Archive/323484

= XCON: Description of the Multipart/Report Internet Message Format in Exchange 2000 =

Article ID: 323484

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q323484



SUMMARY
This article describes the multipart/report Internet message format content type.



MORE INFORMATION
The multipart/report content type is defined for returning delivery status notifications that include optional messages. Exchange 2000 uses the Content-Type: multipart/report for a host of report types, including non-delivery reports (NDRs), delivery receipts, read receipts, delay notifications, relay notification, and non-read notifications.

NDRs
In Exchange 2000, an NDR might have the original message embedded in the report as a message/rfc822 content-type attachment because the RET parameters are set to FULL (for example, RET=FULL). An Exchange 2000 NDR looks similar to the following example:

Your message did not reach some or all of the intended recipients.

Subject: test message Sent: 12/15/2002 3:09 PM

The following recipient(s) could not be reached:

user@example.com on 12/15/2002 3:09 PM           The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. 

Note You can limit the size of the delivery status notification in Exchange 2000 by editing the MaxDsnSize value in the following registry subkey:

Value name: MaxDSNSize

Value type: REG_DWORD

Value data:

Note A message may be returned for a number of reasons. The three digit NDR code is noted at the end of the report.

The following example is MIME header in an NDR:

MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=&quot;_=_NextPart_001_01C21F9D.448286CC&quot; Subject: Undeliverable: RE: --reply at 2:46pm content-class: urn:content-classes:dsn To: user@example.com Return-Path:

--_=_NextPart_001_01C21F9D.448286CC Content-Type: message/delivery-status Content-Transfer-Encoding: 7bit

--_=_NextPart_001_01C21F9D.448286CC Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit

Non-Read Notifications
A non-read notification is sent back to the message sender if the Request a read receipt for this message tracking option is enabled, and the message was deleted or purged without being read. The report is typically generated in the Charset 7-Bit or UTF 7-Bit format. The following example is a non-read notification:

Your message

To:  user@example.com Subject: test message Sent: 12/17/2002 9:02 AM

was deleted without being read on 12/17/2002 9:04 AM.

The following example is a MIME header of a non-read notification:

Subject: Not read: test message Date: Tue, 17 Dec 2002 09:11:08 -0800 Message-ID:  X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary=&quot;_=_NextPart_001_01C2A5EF.4AB815A0&quot; X-MS-TNEF-Correlator: Thread-Topic: NRR Thread-Index: AcKl6qHrWqeamqhrQomyrF7S1Hw6dQABKjNR From: &quot;Contact&quot;  content-class: urn:content-classes:mdn X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 To: &quot;User&quot;  Return-Path: contact@domain.com --_=_NextPart_001_01C2A5EF.4AB815A0 Content-Type: text/plain; charset=&quot;iso-8859-1&quot; Content-Transfer-Encoding: quoted-printable

--_=_NextPart_001_01C2A5EF.4AB815A0 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit

--_=_NextPart_001_01C2A5EF.4AB815A0--

Delivery Receipts
A delivery receipt is sent back to the sender when the message arrives at the destination message transfer agent (MTA) or SMTP gateway. The sender requests a delivery receipt by stamping a Return Receipt To or Transport-Neutral Encapsulation Format (TNEF) equivalent of PR_ORIGINATOR_DELIVERY_REPORT_REQUESTED to TRUE through the messaging client. The Exchange 2000 transport subsequently transmits this request by specifying a NOTIFY parameter in the SMTP RCPT TO command. For example:

RCPT TO: NOTIFY=SUCCESS,DELAY,FAILURE

The following example is a delivery receipt:

Your message

To:  User; 'user@example.com' Subject: test message Sent: 12/17/2002 8:53 AM

was delivered to the following recipient(s):

User on 12/17/2002 8:53 AM

The following example is a MIME header of a delivery receipt:

Microsoft Mail Internet Headers Version 2.0 From: postmaster@example.com To: user@example.com Date: Tue, 17 Dec 2002 10:52:39 -0600 MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=&quot;9B095B5ADSN=_01C20D2FE25765E1000A8D4Aclt?msg?01.north&quot; X-DSNContext: Subject: Delivery Status Notification (Success)

Return-Path: --9B095B5ADSN=_01C20D2FE25765E1000A8D4Aclt?msg?01.north Content-Type: text/plain; charset=unicode-1-1-utf-7 --9B095B5ADSN=_01C20D2FE25765E1000A8D4Aclt?msg?01.north Content-Type: message/delivery-status --9B095B5ADSN=_01C20D2FE25765E1000A8D4Aclt?msg?01.north Content-Type: message/rfc822

Return-Receipt-To: adef@microsoft.com MIME-Version: 1.0 Content-Type: application/ms-tnef; name=&quot;winmail.dat&quot; Content-Transfer-Encoding: binary content-class: urn:content-classes:message Subject: test message Date: Tue, 17 Dec 2002 10:52:39 -0600 Message-ID: message ID

From: userf@example.com To: contact@domain.com Return-Path: user@example.com

Read Receipts
A read receipt is sent back to the message sender if a request for a read receipt is stamped on the message. The sender requests this by setting the Disposition-Notification-To header in the message to the sender or the TNEF equivalent of PR_READ_RECEIPT_REQUESTED. The following example of a read receipt:

Your message

To:   user@example.com Subject:

was read on 12/17/2002 9:58 AM.

The following example is a MIME header of a read receipt:

Microsoft Mail Internet Headers Version 2.0

Subject: Read: test message Date: Tue, 17 Dec 2002 09:57:53 -0800 Message-ID: <D558A6DD2C314D42AA20CFD97918912C016892@server.domain.com> X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: multipart/report; report-type=disposition-notification; boundary=&quot;_=_NextPart_001_01C2A5F5.D275F240&quot; X-MS-TNEF-Correlator: Thread-Topic: test message Thread-Index: AcKl9b1Bswu6VA+wR7WlTk6KwIWqQAAABU3S From: &quot;Contact&quot; <contact@domain.com> content-class: urn:content-classes:mdn X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 To: &quot;User&quot; <user@example.com> Return-Path: contact@domain.com X-OriginalArrivalTime: 17 Dec 2002 17:57:54.0603 (UTC) FILETIME=[D30A3FB0:01C2A5F5]

--_=_NextPart_001_01C2A5F5.D275F240 Content-Type: text/plain; charset=&quot;iso-8859-1&quot; Content-Transfer-Encoding: quoted-printable

--_=_NextPart_001_01C2A5F5.D275F240 Content-Type: message/disposition-notification Content-Transfer-Encoding: 7bit

--_=_NextPart_001_01C2A5F5.D275F240--

Relay Delivery Status Notifications
The following example is a relay delivery status notification:

<pre class="fixed_text">This is an automatically generated Delivery Status Notification.

Your message has been successfully relayed to the following recipients, but the requested delivery status notifications may not be generated by the destination.

user@example.com

The following example is a MIME header of a relay delivery status notification:

<pre class="fixed_text">Microsoft Mail Internet Headers Version 2.0

From: postmaster@example.com To: user@example.com Date: Tue, 17 Dec 2002 08:52:40 -0800 MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=&quot;9B095B5ADSN=_01C291DC6A7FD62100009369inet?hub?01.redm&quot; X-DSNContext: 7ce717b1 - 1130 - 00000008 - 00000000 Message-ID: <J6pN7jmF800000eae@inet-hub-01.redmond.example.com> Subject: Delivery Status Notification (Relay) Return-Path: <> X-OriginalArrivalTime: 17 Dec 2002 16:52:41.0121 (UTC) FILETIME=[B66C4910:01C2A5EC]

--9B095B5ADSN=_01C291DC6A7FD62100009369inet?hub?01.redm Content-Type: text/plain; charset=unicode-1-1-utf-7

--9B095B5ADSN=_01C291DC6A7FD62100009369inet?hub?01.redm Content-Type: message/delivery-status

--9B095B5ADSN=_01C291DC6A7FD62100009369inet?hub?01.redm Content-Type: message/rfc822

Received: from server.domain.com ([100.0.0.0]) by internet-xxx-00001.server.example.com with Microsoft SMTPSVC(5.0.2195.5600); Tue, 17 Dec 2002 08:52:40 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.6803.0 Content-class: urn:content-classes:message Return-Receipt-To: &quot;User&quot; <user@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=&quot;_=_NextPart_001_01C2A5EC.B52CE306&quot; Disposition-Notification-To: &quot;User&quot; <user@example.com> Subject: test message Date: Tue, 17 Dec 2002 10:52:39 -0600 Message-ID: <C1DCE947398EDF4CBBF4996496268B7405F7ABE4@server.domain.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: test message Thread-Index: AcKl7Erc8kt0mdKuSreEWGbzByvkaQAAEqPQ From: &quot;User&quot; <user@example.com> To: &quot;Contact&quot; <contact@domain.com Reply-To: &quot;User&quot; <user@example.com> Return-Path: user@example.com X-OriginalArrivalTime: 17 Dec 2002 16:52:40.0371 (UTC) FILETIME=[B5F9D830:01C2A5EC]

--_=_NextPart_001_01C2A5EC.B52CE306 Content-Type: text/plain; charset=&quot;US-ASCII&quot; Content-Transfer-Encoding: quoted-printable

--_=_NextPart_001_01C2A5EC.B52CE306 Content-Type: text/html; charset=&quot;US-ASCII&quot; Content-Transfer-Encoding: quoted-printable

Delay Notifications
Delay notifications are generated for messages that cannot be delivered in a timely manner. The notification is sent according to the delay notification interval that is configured on the SMTP virtual server. If the transport requests a delay notification from the target server by using the RCPT TO:<ser@example.com> NOTIFY=FAILURE,DELAY parameter, the target server returns a delay notification if the message is not delivered to the recipient in a timely manner. The following example is the MIME header of a delay notification:

<pre class="fixed_text">Microsoft Mail Internet Headers Version 2.0 Received From: postmaster@example.com

To: user@example.com Date: Wed, 10 Apr 2002 20:16:44 -0700 MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; X-DSNContext: Message-ID: Subject: Delivery Status Notification (Delay) Return-Path:

--9B095B5ADSN=_boundary Content-Type: text/plain; charset=unicode-1-1-utf-7 --9B095B5ADSN=_boundary Content-Type: message/delivery-status

--9B095B5ADSN=_boundary. Content-Type: message/rfc822 Received: X-MimeOLE: Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed;

boundary=&quot;boundary&quot; Disposition-Notification-To: user@example.com Subject: RE: Test message Date: Wed, 10 Apr 2002 15:40:25 -0500 Message-ID: thread-index: AcHgyTOFUg626BmvQRuaHma5lfChhAABrcbg From: user@example.com To: contact@domain.com Return-Path: user@example.com

Content-Type: multipart/alternative; boundary=&quot;_=_NextPart_001_01C1E0CF.F170F875&quot; --_=_NextPart_001_01C1E0CF.F170F875 Content-Type: text/plain; charset=&quot;us-ascii&quot; Content-Transfer-Encoding: quoted-printable --_=_NextPart_001_01C1E0CF.F170F875

Content-Type: text/html; charset=&quot;us-ascii&quot; Content-Transfer-Encoding: quoted-printable

For more information, read RFC 1891, 1894, and 2298 on the following Internet Engineering Task Force (IETF) Web site: www.ietf.org

Keywords: kbinfo KB323484

-

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

© Microsoft Corporation. All rights reserved.