IMAP Message Submission
draft-gellens-lemonade-push-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Randall Gellens | ||
| Last updated | 2003-12-10 | ||
| 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
This document describes an IMAP protocol extension allowing clients to submit new messages using IMAP. This is the so-called 'IMAP Push' approach currently being considered by the lemonade working group as one solution to the 'forward without download' problem (that is, as a means for clients to send new messages consisting of or containing all or parts of previously received messages without having to download and upload the data). This proposal relies on additional IMAP extensions, including CATENATE and Annotations. The IMAP extension described here requires that the message to be submitted be already composed and ready to go at the time of submission.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)