Sieve Email Filtering: Delivering to Special-Use Mailboxes
draft-bosch-sieve-special-use-02
Document | Type | Replaced Internet-Draft (individual in art area) | |
---|---|---|---|
Author | Stephan Bosch | ||
Last updated | 2017-04-21 | ||
Replaced by | RFC 8579 | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | Replaced by draft-ietf-extra-sieve-special-use | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alexey Melnikov | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-bosch-sieve-special-use-02.txt
Abstract
The SPECIAL-USE capability of the IMAP protocol (RFC 6154) allows clients to identify special-use mailboxes; e.g., where draft or sent messages should be put. This simplifies client configuration. In contrast, the Sieve mail filtering language (RFC 5228) currently has no such capability. This memo defines a Sieve extension that fills this gap: it adds a test for checking whether a special-use attribute is assigned for a particular mailbox or any mailbox, and it adds the ability to file messages into an anonymous mailbox that has a particular special-use attribute assigned.
Authors
Stephan Bosch (stephan.bosch@dovecot.fi)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)