ACAP Profile for Sieve Script Access
draft-gellens-acap-sieve-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Randall Gellens | ||
| Last updated | 2000-02-28 | ||
| 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 | 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 Sieve [SIEVE] language provides a very useful interoperable syntax for mail filtering. The Email Account Dataset Class [ACAP-EMAIL] provides an extensible and interoperable means of accessing and controlling Sieve scripts, but requires an ACAP [ACAP] server. This memo proposes a profile of ACAP which is suitable for accessing Sieve scripts, very easy to implement in clients and servers, and upwardly compatible with ACAP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)