Message Composition
draft-newman-lemonade-compose-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Chris Newman | ||
| Last updated | 2004-02-11 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| 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 submission profile of Simple Mail Transfer Protocol (SMTP) provides a standard way for an email client to submit a complete message for delivery. The chunking extension provides a way for a client to compose a message for submission from a series of client provided pieces. This specification further extends the chunking facility so that a client can compose a message from additional sources. For example, a client could use this facility to forward a message from an IMAP server or forward a web page as an attachment to a new message.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)