Support for Sieve in Internet Message Access Protocol (IMAP4)
draft-ietf-sieve-imap-sieve-02
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 6785.
Expired & archived
|
|
---|---|---|---|
Author | Barry Leiba | ||
Last updated | 2011-03-30 (Latest revision 2010-09-27) | ||
Replaces | draft-ietf-lemonade-imap-sieve | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Reviews | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Pete Resnick | ||
Send notices to | sieve-chairs@tools.ietf.org, draft-ietf-sieve-imap-sieve@tools.ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in the IMAP protocol where messages are created or changed, adding the option of user- defined or installation-defined filtering (or, with Sieve extensions, features such as notifications).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)