RFC1653 on SMTP Size Declaration (fwd)
NIC
From jk...@ISI.EDU Fri Jul 15 18:10:13 1994
Message-Id: <1994071522...@zephyr.isi.edu>
To: rfc-...@nic.ddn.mil
Subject: RFC1653 on SMTP Size Declaration
Cc: jk...@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Fri, 15 Jul 94 15:11:00 PDT
From: "Joyce K. Reynolds" <jk...@ISI.EDU>
--NextPart
A new Request for Comments is now available in online RFC libraries.
RFC 1653:
Title: SMTP Service Extension for Message Size
Declaration
Author: J. Klensin, N. Freed & K. Moore
Mailbox: kle...@mci.net, n...@innosoft.com,
mo...@cs.utk.edu
Pages: 8
Characters: 17,883
Obsoletes: 1427
This memo defines an extension to the SMTP service whereby an SMTP
client and server may interact to give the server an opportunity to
decline to accept a message (perhaps temporarily) based on the
client's estimate of the message size. This RFC is the product of the
Internet Mail Extensions Working Group of the IETF.
This is now a Draft 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-R...@CNRI.RESTON.VA.US. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-R...@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-...@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-...@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 ad...@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-E...@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
--OtherAccess
Content-Type: Message/External-body;
access-type="mail-server";
server="mail...@ds.internic.net"
Content-Type: text/plain
Content-ID: <94071515...@ISI.EDU>
SEND /rfc/rfc1653.txt
--OtherAccess
Content-Type: Message/External-body;
name="rfc1653.txt";
site="ds.internic.net";
access-type="anon-ftp";
directory="rfc"
Content-Type: text/plain
Content-ID: <94071515...@ISI.EDU>
--OtherAccess--
--NextPart--