Sieve Email Filtering: Snooze Extension
draft-ietf-extra-sieve-snooze-00
EXTRA K. Murchison
Internet-Draft R. Signes
Updates: 5232 (if approved) N. Jenkins
Intended status: Standards Track Fastmail
Expires: February 8, 2021 August 7, 2020
Sieve Email Filtering: Snooze Extension
draft-ietf-extra-sieve-snooze-00
Abstract
This document describes the "snooze" extension to the Sieve email
filtering language. The "snooze" extension gives Sieve the ability
to postpone the filing of an incoming into a target mailbox until a
later point in time.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 8, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Murchison, et al. Expires February 8, 2021 [Page 1]
Internet-Draft Sieve Snooze August 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 2
3. Snooze Action . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Mailbox Argument . . . . . . . . . . . . . . . . . . . . 3
3.2. Weekdays Argument . . . . . . . . . . . . . . . . . . . . 4
3.3. Times and TZID Arguments . . . . . . . . . . . . . . . . 4
3.3.1. Awaken Times Examples . . . . . . . . . . . . . . . . 4
3.4. Interaction with Extensions to the Fileinto Action . . . 5
3.4.1. Imap4flags Extension . . . . . . . . . . . . . . . . 6
3.4.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 6
3.4.3. Special-Use Extension . . . . . . . . . . . . . . . . 7
3.4.4. MailboxID Extension . . . . . . . . . . . . . . . . . 7
4. Mechanics of Snoozing Messages . . . . . . . . . . . . . . . 7
4.1. SMTP Future Message Release . . . . . . . . . . . . . . . 8
4.2. "Snoozed" Mailbox . . . . . . . . . . . . . . . . . . . . 8
5. Implementation Status . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8.1. Registration of Sieve Extension . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 11
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
Users are not always ready, willing, or able to read and respond to
email messages at the time of their arrival. Sometimes it is
desirable to have messages appear in a mailbox at a more convenient
time for the user to act upon them.
This document defines a new Sieve action command "snooze" that
postpones filing a message into a target mailbox until a later point
in time. The capability string associated with this extension is
"snooze".
2. Conventions Used in This Document
Conventions for notations are as in Section 1.1 of [RFC5228],
including use of the "Usage:" label for the definition of action and
tagged arguments syntax.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
Murchison, et al. Expires February 8, 2021 [Page 2]
Show full document text