idnits 2.17.1 draft-vaudreuil-1894bis-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 3464 5 Title: An Extensible Message Format for Delivery Status 6 Notifications 7 Author(s): K. Moore, G. Vaudreuil 8 Status: Standards Track 9 Date: January 2003 10 Mailbox: moore@cs.utk.edu, GregV@ieee.org 11 Pages: 40 12 Characters: 83060 13 Obsoletes: 1894 15 I-D Tag: draft-vaudreuil-1894bis-02.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3464.txt 19 This memo defines a Multipurpose Internet Mail Extensions (MIME) 20 content-type that may be used by a message transfer agent (MTA) or 21 electronic mail gateway to report the result of an attempt to deliver 22 a message to one or more recipients. This content-type is intended as 23 a machine-processable replacement for the various types of delivery 24 status notifications currently used in Internet electronic mail. 26 Because many messages are sent between the Internet and other 27 messaging systems (such as X.400 or the so-called "Local Area Network 28 (LAN)-based" systems), the Delivery Status Notification (DSN) protocol 29 is designed to be useful in a multi-protocol messaging environment. 30 To this end, the protocol described in this memo provides for the 31 carriage of "foreign" addresses and error codes, in addition to those 32 normally used in Internet mail. Additional attributes may also be 33 defined to support "tunneling" of foreign notifications through 34 Internet mail. 36 This is now a Draft Standard Protocol. 38 This document specifies an Internet standards track protocol for 39 the Internet community, and requests discussion and suggestions 40 for improvements. Please refer to the current edition of the 41 "Internet Official Protocol Standards" (STD 1) for the 42 standardization state and status of this protocol. Distribution 43 of this memo is unlimited. 45 This announcement is sent to the IETF list and the RFC-DIST list. 46 Requests to be added to or deleted from the IETF distribution list 47 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 48 added to or deleted from the RFC-DIST distribution list should 49 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 51 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 52 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 53 help: ways_to_get_rfcs. For example: 55 To: rfc-info@RFC-EDITOR.ORG 56 Subject: getting rfcs 58 help: ways_to_get_rfcs 60 Requests for special distribution should be addressed to either the 61 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 62 specifically noted otherwise on the RFC itself, all RFCs are for 63 unlimited distribution.echo 64 Submissions for Requests for Comments should be sent to 65 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 66 Authors, for further information.