The Use of URIs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
draft-moonesamy-rfc2369bis-04
| Document | Type |
Expired Internet-Draft
(individual in app area)
Expired & archived
|
|
|---|---|---|---|
| Authors | S Moonesamy , Grant Neufeld , Joshua D. Baer | ||
| Last updated | 2015-10-14 (Latest revision 2012-02-19) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Pete Resnick | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The mailing list command specification and identification header fields are a set of structured fields to be added to email messages sent by email distribution lists. Command header fields typically contain URIs (usually including "mailto") locating the relevant information or performing the command directly. The three core command header fields described in this document are List-Help, List- Subscribe, and List-Unsubscribe. There are three other header fields described here which, although not as widely applicable, will have utility for a sufficient number of mailing lists to justify their formalization here. These are List-Post, List-Owner and List-Archive. By including these header fields, mailing list managers can make it possible for mail user agents to provide automated tools for users to perform list functions.
Authors
S Moonesamy
Grant Neufeld
Joshua D. Baer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)