--- 1/draft-ietf-extra-sieve-fcc-04.txt 2018-09-10 18:13:09.873616117 -0700 +++ 2/draft-ietf-extra-sieve-fcc-05.txt 2018-09-10 18:13:09.901616797 -0700 @@ -1,19 +1,19 @@ EXTRA K. Murchison Internet-Draft B. Gondwana Updates: 5230, 5435 (if approved) FastMail -Intended status: Standards Track August 12, 2018 -Expires: February 13, 2019 +Intended status: Standards Track September 10, 2018 +Expires: March 14, 2019 Sieve Extension: File Carbon Copy (Fcc) - draft-ietf-extra-sieve-fcc-04 + draft-ietf-extra-sieve-fcc-05 Abstract The Sieve Email Filtering Language provides a number of action commands, some of which can generate additional messages on behalf of the user. This document defines an extension to such commands to allow a copy of any generated message to be filed into a target mailbox. Status of This Memo @@ -24,21 +24,21 @@ 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 13, 2019. + This Internet-Draft will expire on March 14, 2019. Copyright Notice Copyright (c) 2018 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 @@ -52,45 +52,45 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Conventions Used in This Document . . . . . . . . . . . . . . 3 3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3 3.1. Format of Filed Messages . . . . . . . . . . . . . . . . 3 3.2. Interaction with the Vacation Action . . . . . . . . . . 4 3.3. Interaction with the Notify Action . . . . . . . . . . . 5 3.3.1. Notification-Capability "fcc" . . . . . . . . . . . . 5 3.4. Compatibility with Other Actions . . . . . . . . . . . . 6 3.5. Interaction with Fileinto Extensions . . . . . . . . . . 6 - 3.5.1. Imap4flags Extension . . . . . . . . . . . . . . . . 6 + 3.5.1. Imap4flags Extension . . . . . . . . . . . . . . . . 7 3.5.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 7 3.5.3. Special-Use Extension . . . . . . . . . . . . . . . . 7 - 3.5.4. Extended Example . . . . . . . . . . . . . . . . . . 7 + 3.5.4. Extended Example . . . . . . . . . . . . . . . . . . 8 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8 - 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 - 6.1. Registration of Sieve Extension . . . . . . . . . . . . . 8 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 + 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 + 6.1. Registration of Sieve Extension . . . . . . . . . . . . . 9 6.2. Registration of Notification-Capability Parameter . . . . . . . . . . . . . . . . . . . . . . . . 9 - 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 - 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 8.1. Normative References . . . . . . . . . . . . . . . . . . 9 + 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 + 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 + 8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.2. Informative References . . . . . . . . . . . . . . . . . 11 - 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11 + 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix A. Change History (To be removed by RFC Editor before publication) . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction The Sieve Email Filtering Language [RFC5228] provides a number of action commands, some of which can generate additional messages on - behalf of the user. It is sometimes desirable to have an archive of - the messages generated by these commands. + behalf of the user. It is sometimes desirable for a Sieve user to + maintain an archive of the messages generated by these commands. This extension defines a new optional tagged argument ":fcc" to action commands which generate additional messages to allow a copy of the generated message to be filed into a target mailbox. The capability string associated with this extension is "fcc". Each action that generates additional messages will need to specify how it interfacts with :fcc. This document also specifies the interaction of :fcc with the Vacation [RFC5230] and Notify [RFC5435] @@ -234,20 +234,24 @@ values: yes A copy of the notification message sent using the method identified by the notification-uri can be filed into a target mailbox. no A copy of the notification message sent using the method identified by the notification-uri can not be filed into a target mailbox. + Note that the "fcc" notify_method_capability test does not require + the notification-uri argument to specify anything other than a + scheme. + Example: require ["enotify", "fcc"]; if notify_method_capability "xmpp:" "Fcc" "yes" { notify :fcc "INBOX.Sent" :message "You got mail" "xmpp:ken@example.com?message;subject=SIEVE"; } else { notify :fcc "INBOX.Sent" @@ -268,28 +272,30 @@ 3.5. Interaction with Fileinto Extensions The "fcc" extension can be used with some tagged arguments defined in extensions to the "fileinto" action. The sections below describe its interaction with currently defined extensions. Tagged arguments in future extensions to the "fileinto" command should describe their interaction with ":fcc", if any. When any "fileinto" extension arguments are used with ":fcc", the - MUST have the same syntax and semantics as they do with "fileinto". + corresponding extension MUST be enabled, and the arguments MUST have + the same syntax and semantics as they do with "fileinto". 3.5.1. Imap4flags Extension This document extends the definition of the ":flags" [RFC5232] tagged argument so that it can optionally be used with the ":fcc" argument. FCC =/ [":flags" ] + If the optional ":flags" argument is specified with ":fcc", it instructs the Sieve interpreter to set the IMAP4 flags provided in the subsequent argument when the generated message is filed into the target mailbox. 3.5.2. Mailbox Extension This document extends the definition of the ":create" [RFC5490] tagged argument so that it can optionally be used with the ":fcc" argument. @@ -355,20 +361,29 @@ 4.1. Cyrus Server The open source Cyrus Server [2] project is a highly scalable enterprise mail system which supports Sieve email filtering at the point of final delivery. This production level Sieve implementation supports all of the requirements described in this document. This implementation is freely distributable under a BSD style license from Computing Services at Carnegie Mellon University [3]. +4.2. Oracle Communications Messaging Server + + The Oracle Communications Messaging Server [4] is a highly scalable, + reliable, and available messaging platform. This production level + product supports the :fcc extension in conjunction with both the + notify and vacation extensions. The implementation meets all the + requirements given in this document. The product also supports the + imap4flags extension so the :flags may be used in conjunction :fcc. + 5. Security Considerations The "fcc" extension does not raise any other security considerations that are not already present in [RFC5228], [RFC5230], [RFC5435], and [RFC6131]. 6. IANA Considerations 6.1. Registration of Sieve Extension @@ -410,22 +426,22 @@ The authors would like to thank the following individuals for contributing their ideas and support for writing this specification: Ned Freed, Stan Kalisch, and Alexey Melnikov. 8. References 8.1. Normative References [I-D.ietf-extra-sieve-special-use] Bosch, S., "Sieve Email Filtering: Delivering to Special- - Use Mailboxes", draft-ietf-extra-sieve-special-use-02 - (work in progress), March 2018. + Use Mailboxes", draft-ietf-extra-sieve-special-use-03 + (work in progress), September 2018. [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, DOI 10.17487/RFC2045, November 1996, . [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, DOI 10.17487/RFC2046, November 1996, . @@ -504,27 +520,36 @@ . 8.3. URIs [1] https://tools.ietf.org/html/bcp14 [2] http://www.cyrusimap.org/ [3] http://www.cmu.edu/computing/ + [4] https://www.oracle.com/industries/communications/enterprise/ + products/messaging-server/index.html + Appendix A. Change History (To be removed by RFC Editor before publication) Changes since draft-ietf-extra-sieve-fcc-03: o Fixed typo in ABNF. + Changes since draft-ietf-extra-sieve-fcc-04: + + o Editorial changes from Ned Freed. + + o Added information on Oracle implementation. + Changes since draft-ietf-extra-sieve-fcc-02: o Updated Keywords boilerplate. o Noted that :fcc mailbox argument and any fileinto extension arguments used wth :fcc have the same syntax and semantics as they have with fileinto. o Removed section on [e]Reject.