SMTP Submission Service Extension for Future Message Release
draft-ietf-lemonade-futuredelivery-04
| Document | Type |
Expired Internet-Draft
(lemonade WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Gregory A. White | ||
| Last updated | 2015-10-14 (Latest revision 2006-03-23) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ted Hardie | ||
| 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 memo defines an extension to the SMTP submission protocol for a client to indicate a future time for the message to be released for delivery. This extension permits a client to use server-based storage for a message that should be held in queue until an appointed time in the future. This is useful for clients which do not have local storage or are otherwise unable to release a message for delivery at an appointed time.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)