Sieve Email Filtering: delivery by mailboxid
draft-gondwana-sieve-mailboxid-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Bron Gondwana | ||
| Last updated | 2019-02-13 (Latest revision 2018-08-12) | ||
| Replaced by | draft-ietf-extra-sieve-mailboxid, RFC 9042 | ||
| RFC stream | (None) | ||
| 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 OBJECTID capability of the IMAP protocol (I-D.ietf-extra-imap- objectid) allows clients to identify mailboxes by a unique identifier which survives rename. 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 method for specifying the unique identifier of a mailbox as a target for fileinto rules, and a method for testing the existence of a mailbox by its unique identifier.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)