A new Request for Comments is now available in online RFC libraries.


        RFC 1891:

        Title:      SMTP Service Extension
                    for Delivery Status Notifications
        Author:     K. Moore
        Date:       January 1996
        Mailbox:    moore@cs.utk.edu
        Pages:      31
        Characters: 65,192
        Obsoletes/Updates: none

        URL:        ftp://ds.internic.net/rfc/rfc1891.txt


This memo defines an extension to the SMTP (Simple Mail Transfer
Protocol) service, which allows an SMTP client to specify (a) that
delivery status notifications (DSNs) should be generated under certain
conditions, (b) whether such notifications should return the contents
of the message, and (c) additional information, to be returned with a
DSN, that allows the sender to identify both the recipient(s) for
which the DSN was issued, and the transaction in which the original
message was sent.  This RFC is the product of the Notifications and
Acknowledgements Requirements Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
USC/Information Sciences Institute