Browse Prior Art Database

SMTP Service Extensions (RFC1425)

IP.com Disclosure Number: IPCOM000002252D
Original Publication Date: 1993-Feb-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 10 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Klensin: AUTHOR [+5]

Related Documents

10.17487/RFC1425: DOI

Abstract

This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 19% of the total text.

Network Working Group J. Klensin, WG Chair Request for Comments: 1425 United Nations University N. Freed, Editor Innosoft International, Inc. M. Rose Dover Beach Consulting, Inc. E. Stefferud Network Management Associates, Inc. D. Crocker The Branch Office February 1993

SMTP Service Extensions

Status of this Memo

This RFC specifies an IAB standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "IAB Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.

1. Abstract

This memo defines a framework for extending the SMTP service by defining a means whereby a server SMTP can inform a client SMTP as to the service extensions it supports. Standard extensions to the SMTP service are registered with the Internet Assigned Numbers Authority (IANA). This framework does not require modification of existing SMTP clients or servers unless the features of the service extensions are to be requested or provided.

2. Introduction

The Simple Mail Transfer Protocol (SMTP) [1] has provided a stable, effective basis for the relay function of message transfer agents. Although a decade old, SMTP has proven remarkably resilient. Nevertheless, the need for a number of protocol extensions has become evident. Rather than describing these extensions as separate and haphazard entities, this document enhances SMTP in a straightforward fashion that provides a framework in which all future extensions can be built in a single consistent way.

3. Framework for SMTP Extensions

For the purpose of service extensions to SMTP, SMTP relays a mail object containing an envelope and a content.

Klensin, Freed, Rose, Stefferud & Crocker [Page 1]

RFC 1425 SMTP Service Extensions February 1993

(1) The SMTP envelope is straightforward, and is sent as a series of SMTP protocol units: it consists of an originator address (to which error reports should be directed); a delivery mode (e.g., deliver to recipient mailboxes); and, one or more recipient addresses.

(2) The SMTP content is sent in the SMTP DATA protocol unit and has two parts: the headers and the body. The headers form a collection of field/value pairs structured according to RFC 822 [2], whilst the body, if structured, is defined according to MIME [3]. The content is textual in nature, expressed using the US ASCII repertoire (ANSI X3.4-1986). Although extensions (such as MIME) may relax this restriction for the content body, the content headers are always encoded using the US ASCII repertoire. The algorithm defined in [4] is used to represent header values outside the US ASCII repertoire, whilst still encoding them using the US ASCII repertoire.

Although SMTP is widely and robustly deployed, some parts of the Internet community might wish to extend the SMTP service. This memo defines a means whereby both an extended SMTP client and server may recognize each other as suc...

Processing...
Loading...