This Internet Draft is replaced by K. Moore Expires 21 September 1994 [Page 12] MIME Notifications 21 March 1994 Appendix: Example delivery notification From: postmaster@netlib2.cs.utk.edu To: j.random.user@cs.utk.edu Subject: delivery notification Content-type: multipart/notification; boundary=xyzzy MIME-Version: 1.0 --xyzzy Content-type: text/plain; charset=us-ascii Your mail message could not be delivered to some of the recipients listed below. The message has been returned to you. --xyzzy Content-type: message/notifications; type=delivery-status Envelope-ID: 09834 Issuing-MTA: netlib2.cs.utk.edu Notification-Date: Sun, 20 Mar 1994 18:43:03 -0400 (EST) Recipient-Info: for="bogus.user@cs.utk.edu" ; status=550 (no such user); action=failed ; orig="bogus.user@netlib2.cs.utk.edu" ; source=cs.utk.edu Recipient-Info: for="moore@cs.utk.edu" ; status=601 (cs.utk.edu does not support delivery report requests); action=relayed; orig="moore@netlib2.cs.utk.edu" ; source=cs.utk.edu Recipient-Info: for="big-mailing-list@netlib2.cs.utk.edu" ; status=200 (message sent to list recipients) ; action=delivered ; orig="big-mailing-list@netlib2.cs.utk.edu" ; source=netlib2.cs.utk.edu --xyzzy MIME-Version: 1.0 Content-type: message/rfc822 Content-id: <0xffcc8090@netlib2.cs.utk.edu> Received: by netlib2.cs.utk.edu; Thu, 24 Jun 1993 18:43:03 -0400 To: bogus.user@netlib2.cs.utk.edu, remote.user@netlib2.cs.utk.edu, big-mailing-list@netlib2.cs.utk.edu, moore@netlib2.cs.utk.edu From: j.random.user@cs.utk.edu Date: Thu, 24 Jun 1993 18:42:09 -0400 Subject: quote Message-id: <930624.AA09834@cs.utk.edu> "Don't sweat it -- it's not real life. It's only ones and zeroes." -- spaf --xyzzy-- K. Moore Expires 21 September 1994 [Page 13] MIME Notifications 21 March 1994 Appendix: changes since the last draft [1] renamed multipart/delivery-status-notification to multipart/notification, allowing it to be a general container. type. [2] rename "returned message" body part to message/sample. [3] remove "links" that referred to the content-id of other body parts. [4] rename message/delivery-report to message/notification. [5] use 822 headers instead of STIF; tweaked some of the fields. [6] added "motivations" paragraph to introduction. [7] rearranged the parameters for the report, moved date from per-recipient to per-report (was this a good idea?), distinguished "source" of an error from "issuing mta". removed "text", instead recommended a comment. [8] added additional smtp-like status codes for conditions that SMTP doesn't ever have to report. To Do: [1] The current pair of drafts doesn't ensure one notification per sender-specified-recipient. We need to decide how to handle mail forwarding to multiple recipients. [2] The recipient addresses may need to be encoded to fit in ASCII; how best to do this? It's probably best to encode the fields of the message/notification body part in the same was as suggested for ESMTP, rather than encoding the entire body part. [3] Either define some extension suffixes for 3-digit SMTP codes, or get rid of them. [4] Do we need a place to put more human-readable stuff? A field for text explanation for an error code in-addition-to and separate-from text returned by the remote MTA? [5] Should we add a place for "delayed" notifications? If so, we need to elaborate on the use of 4yz status-codes (sometimes they would mean "delivery abandoned due to persistent temporary failure conditions" and sometimes they just mean "delayed due to temporary failure conditions") K. Moore Expires 21 September 1994 [Page 14] MIME Notifications 21 March 1994 [6] The draft needs lots of additional examples. K. Moore Expires 21 September 1994 [Page 15]