idnits 2.17.1 draft-vaudreuil-1892bis-02.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3462 5 Title: The Multipart/Report Content Type for the 6 Reporting of Mail System Administrative Messages 7 Author(s): G. Vaudreuil 8 Status: Standards Track 9 Date: Janaury 2003 10 Mailbox: GregV@ieee.org 11 Pages: 7 12 Characters: 12186 13 Obsoletes: 1892 15 I-D Tag: draft-vaudreuil-1892bis-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3462.txt 19 The Multipart/Report Multipurpose Internet Mail Extensions (MIME) 20 content-type is a general "family" or "container" type for electronic 21 mail reports of any kind. Although this memo defines only the use of 22 the Multipart/Report content-type with respect to delivery status 23 reports, mail processing programs will benefit if a single 24 content-type is used to for all kinds of reports. 26 This document is part of a four document set describing the delivery 27 status report service. This collection includes the Simple Mail 28 Transfer Protocol (SMTP) extensions to request delivery status 29 reports, a MIME content for the reporting of delivery reports, an 30 enumeration of extended status codes, and a multipart container for 31 the delivery report, the original message, and a human-friendly 32 summary of the failure. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.