Browse Prior Art Database

The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages (RFC3462)

IP.com Disclosure Number: IPCOM000011357D
Original Publication Date: 2003-Jan-01
Included in the Prior Art Database: 2003-Feb-14
Document File: 8 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Vaudreuil: AUTHOR

Abstract

The Multipart/Report Multipurpose Internet Mail Extensions (MIME) content-type is a general "family" or "container" type for electronic mail reports of any kind. Although this memo defines only the use of the Multipart/Report content-type with respect to delivery status reports, mail processing programs will benefit if a single content- type is used to for all kinds of reports.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Network Working Group                                       G. Vaudreuil

Request for Comments: 3462                           Lucent Technologies

Obsoletes: 1892                                             January 2003

Category: Standards Track

                   The Multipart/Report Content Type

                         for the Reporting of

                  Mail System Administrative Messages

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   The Multipart/Report Multipurpose Internet Mail Extensions (MIME)

   content-type is a general "family" or "container" type for electronic

   mail reports of any kind.  Although this memo defines only the use of

   the Multipart/Report content-type with respect to delivery status

   reports, mail processing programs will benefit if a single content-

   type is used to for all kinds of reports.

   This document is part of a four document set describing the delivery

   status report service.  This collection includes the Simple Mail

   Transfer Protocol (SMTP) extensions to request delivery status

   reports, a MIME content for the reporting of delivery reports, an

   enumeration of extended status codes, and a multipart container for

   the delivery report, the original message, and a human-friendly

   summary of the failure.

Vaudreuil                   Standards Track                     [Page 1]

RFC 3462                    Multipart/Report                January 2003

Table of Contents

   Document Conventions................................................2

   1. The Multipart/Report Content Type................................2

   2. The Text/RFC822-Headers..........................................4

   3. Security Considerations..........................................4

   4. Normative References.............................................5

   Appendix A - Changes from RFC 1893..................................6

   Author's Address....................................................6

   Full Copyright Statement............................................7

Document Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

   document are to be interpreted as described in BCP 14, RFC 2119

   [RFC2119].

1. The Multipart/Report Content Type

®..