A Protocol for Remotely Managing Sieve Scripts
draft-martin-managesieve-12
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexey Melnikov , Tim Martin | ||
| Last updated | 2008-10-21 (Latest revision 2008-09-13) | ||
| Replaced by | draft-ietf-sieve-managesieve | ||
| RFC stream | (None) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sieve-managesieve | |
| 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
Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This document describes a protocol "ManageSieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)