idnits 2.17.1 draft-ietf-extra-sieve-fcc-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. -- The draft header indicates that this document updates RFC5429, but the abstract doesn't seem to mention this, which it should. -- The draft header indicates that this document updates RFC5230, but the abstract doesn't seem to mention this, which it should. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC5230, updated by this document, for RFC5378 checks: 2005-03-16) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 21, 2017) is 2380 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-05) exists of draft-ietf-extra-sieve-special-use-00 ** Obsolete normative reference: RFC 4234 (Obsoleted by RFC 5234) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 EXTRA K. Murchison 3 Internet-Draft B. Gondwana 4 Updates: 5230, 5429 (if approved) FastMail 5 Intended status: Standards Track September 21, 2017 6 Expires: March 25, 2018 8 Sieve Extension: File Carbon Copy (Fcc) 9 draft-ietf-extra-sieve-fcc-00 11 Abstract 13 The Sieve Email Filtering Language consists of action commands that 14 can reply to the sender of an incoming message with a generated 15 message. This document defines an extension to such commands to 16 allow a copy of the generated reply message to be filed into a target 17 mailbox. 19 Open Issues 21 o Should :fcc be allowed with reject/ereject? 23 o Should there be a separate capability string for each action that 24 uses :fcc (e.g. "vacation-fcc")? 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at https://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on March 25, 2018. 43 Copyright Notice 45 Copyright (c) 2017 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (https://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 62 3. The ":fcc" Argument . . . . . . . . . . . . . . . . . . . . . 3 63 3.1. Interaction with Fileinto Extensions . . . . . . . . . . 3 64 3.1.1. Imap4flags Extension . . . . . . . . . . . . . . . . 3 65 3.1.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 4 66 3.1.3. Special-Use Extension . . . . . . . . . . . . . . . . 4 67 3.1.4. Extended Example . . . . . . . . . . . . . . . . . . 4 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 70 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 72 6.2. Informative References . . . . . . . . . . . . . . . . . 5 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 75 1. Introduction 77 The Sieve Email Filtering Language [RFC5228] consists of action 78 commands that can reply to the sender of an incoming message with a 79 generated message. Three such commands are defined by the Vacation 80 Extension [RFC5230] and the Reject and Extended Reject Extensions 81 [RFC5429]. It is sometimes desirable to have an archive of these 82 auto-generated reply messages. 84 This extension defines a ":fcc" argument to action commands which 85 generate reply messages to allow a copy of the reply message to be 86 filed into a target mailbox. 88 The capability string associated with this extension is "fcc". 90 2. Conventions Used in This Document 92 Conventions for notations are as in Section 1.1 of [RFC5228], 93 including use of the "Usage:" label for the definition of action and 94 tagged arguments syntax. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 98 "OPTIONAL" in this document are to be interpreted as described in 99 [RFC2119]. 101 3. The ":fcc" Argument 103 Usage: ":fcc" FCC-OPTIONS 105 The positional FCC-OPTIONS argument is defined here in ABNF [RFC4234] 106 syntax so that it can be modified by other extensions. 108 FCC-OPTIONS = "" ; empty string 110 If the optional ":fcc" argument is specified with an action that 111 generates a reply message, it instructs the Sieve interpreter to file 112 a copy of the message into the target mailbox. If the specified 113 mailbox doesn't exist, the implementation MAY treat it as an error, 114 create the mailbox, or file the message into an implementation- 115 defined mailbox. 117 Example: 119 require ["reject", "fcc"]; 121 if header :contains "Subject" "Make Money Fast" { 122 reject :fcc "Junk" "Your message is considered junk email."; 123 } 125 3.1. Interaction with Fileinto Extensions 127 The "fcc" extension can be used with some tagged arguments defined in 128 extensions to the "fileinto" action. The sections below describe its 129 interaction with currently defined extensions. Tagged arguments in 130 future extensions to the "fileinto" command should describe their use 131 with ":fcc", if any. 133 3.1.1. Imap4flags Extension 135 This document extends the definition of the ":flags" [RFC5232] tagged 136 argument so that it can be used as an FCC-OPTIONS to the ":fcc" 137 argument. 139 FCC-OPTIONS =/ [":flags" ] 141 If the optional ":flags" argument is specified with ":fcc", it 142 instructs the Sieve interpreter to set the IMAP4 flags provided in 143 the subsequent argument when the the reply message is filed into the 144 target mailbox. 146 3.1.2. Mailbox Extension 148 This document extends the definition of the ":create" [RFC5490] 149 tagged argument so that it can be used as an FCC-OPTIONS to the 150 ":fcc" argument. 152 FCC-OPTIONS =/ [":create"] 154 If the optional ":create" argument is specified with ":fcc", it 155 instructs the Sieve interpreter to create the target mailbox, if 156 needed, before attempting to file the reply message into the target 157 mailbox. 159 3.1.3. Special-Use Extension 161 This document extends the definition of the ":specialuse" 162 [I-D.ietf-extra-sieve-special-use] tagged argument so that it can be 163 used as an FCC-OPTIONS to the ":fcc" argument. 165 FCC-OPTIONS =/ [":specialuse "] 167 If the optional ":specialuse" argument is specified with ":fcc", it 168 instructs the Sieve interpreter to check whether a mailbox exists 169 with the specific special-use flag assigned to it. If such a mailbox 170 exists, the reply message is filed into the special-use mailbox. 171 Otherwise, the reply message is filed into the target mailbox. 173 If both the optional ":specialuse" and ":create" arguments are 174 specified with ":fcc", the Sieve interpreter is instructed to create 175 the target mailbox per Section 4.1 of 176 [I-D.ietf-extra-sieve-special-use], if needed. 178 3.1.4. Extended Example 180 require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"]; 182 vacation :days 7 183 :fcc :specialuse "\\Sent" :create :flags ["\\Seen"] "INBOX.Sent" 184 :from "hemingway@example.com" "Gone Fishin'; 186 4. Security Considerations 188 The "fcc" extension does not raise any other security considerations 189 that are not already present in [RFC5228], [RFC5429], [RFC5230], and 190 [RFC6131]. 192 5. IANA Considerations 194 6. References 196 6.1. Normative References 198 [I-D.ietf-extra-sieve-special-use] 199 Bosch, S., "Sieve Email Filtering: Delivering to Special- 200 Use Mailboxes", draft-ietf-extra-sieve-special-use-00 201 (work in progress), September 2017. 203 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 204 Requirement Levels", BCP 14, RFC 2119, 205 DOI 10.17487/RFC2119, March 1997, 206 . 208 [RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax 209 Specifications: ABNF", RFC 4234, DOI 10.17487/RFC4234, 210 October 2005, . 212 [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email 213 Filtering Language", RFC 5228, DOI 10.17487/RFC5228, 214 January 2008, . 216 [RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering: 217 Vacation Extension", RFC 5230, DOI 10.17487/RFC5230, 218 January 2008, . 220 [RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags 221 Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008, 222 . 224 [RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and 225 Extended Reject Extensions", RFC 5429, 226 DOI 10.17487/RFC5429, March 2009, 227 . 229 [RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language -- 230 Extensions for Checking Mailbox Status and Accessing 231 Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March 232 2009, . 234 6.2. Informative References 236 [RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension: 237 "Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July 238 2011, . 240 Authors' Addresses 242 Kenneth Murchison 243 FastMail Pty Ltd 244 Level 2, 114 William Street 245 Melbourne, VIC 3000 246 Australia 248 Email: murch@fastmailteam.com 250 Bron Gondwana 251 FastMail Pty Ltd 252 Level 2, 114 William Street 253 Melbourne, VIC 3000 254 Australia 256 Email: brong@fastmailteam.com