< draft-ietf-extra-sieve-fcc-05.txt   draft-ietf-extra-sieve-fcc-06.txt >
EXTRA K. Murchison EXTRA K. Murchison
Internet-Draft B. Gondwana Internet-Draft B. Gondwana
Updates: 5230, 5435 (if approved) FastMail Updates: 5230, 5435 (if approved) FastMail
Intended status: Standards Track September 10, 2018 Intended status: Standards Track October 1, 2018
Expires: March 14, 2019 Expires: April 4, 2019
Sieve Extension: File Carbon Copy (Fcc) Sieve Extension: File Carbon Copy (Fcc)
draft-ietf-extra-sieve-fcc-05 draft-ietf-extra-sieve-fcc-06
Abstract Abstract
The Sieve Email Filtering Language provides a number of action The Sieve Email Filtering Language provides a number of action
commands, some of which can generate additional messages on behalf of commands, some of which can generate additional messages on behalf of
the user. This document defines an extension to such commands to the user. This document defines an extension to such commands to
allow a copy of any generated message to be filed into a target allow a copy of any generated message to be filed into a target
mailbox. mailbox.
This document updates RFC5230 and RFC5435 by adding a new tagged
argument to the "vacation" and "enotify" actions respectively.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 14, 2019. This Internet-Draft will expire on April 4, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 32 skipping to change at page 2, line 34
4. Implementation Status . . . . . . . . . . . . . . . . . . . . 8 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. Registration of Sieve Extension . . . . . . . . . . . . . 9 6.1. Registration of Sieve Extension . . . . . . . . . . . . . 9
6.2. Registration of Notification-Capability 6.2. Registration of Notification-Capability
Parameter . . . . . . . . . . . . . . . . . . . . . . . . 9 Parameter . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . 11
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Change History (To be removed by RFC Editor before Appendix A. Change History (To be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 12 publication) . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
The Sieve Email Filtering Language [RFC5228] provides a number of The Sieve Email Filtering Language [RFC5228] provides a number of
action commands, some of which can generate additional messages on action commands, some of which can generate additional messages on
behalf of the user. It is sometimes desirable for a Sieve user to behalf of the user. It is sometimes desirable for a Sieve user to
maintain an archive of the messages generated by these commands. maintain an archive of the messages generated by these commands.
skipping to change at page 3, line 22 skipping to change at page 3, line 25
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [1] [RFC2119] [RFC8174] when, and only when, they appear in all 14 [1] [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Tagged Argument ":fcc" 3. Tagged Argument ":fcc"
For convenience, the "FCC" syntax element is defined here using ABNF For convenience, the "FCC" syntax element is defined here using ABNF
[RFC4234] so that it can be augmented by other extensions. [RFC5234] so that it can be augmented by other extensions.
FCC = ":fcc" <mailbox: string> FCC = ":fcc" <mailbox: string>
If the optional ":fcc" argument is specified with an action that If the optional ":fcc" argument is specified with an action that
generates an additional message, it instructs the Sieve interpreter generates an additional message, it instructs the Sieve interpreter
to file a copy of the generated message into the target mailbox. The to file a copy of the generated message into the target mailbox. The
syntax and semantics of the mailbox argument MUST match those of the syntax and semantics of the mailbox argument MUST match those of the
mailbox argument to the "fileinto" action specified in Section 4.1 of mailbox argument to the "fileinto" action specified in Section 4.1 of
[RFC5228]. If the specified mailbox doesn't exist, the [RFC5228]. If the specified mailbox doesn't exist, the
implementation MAY treat it as an error, create the mailbox, or file implementation MAY treat it as an error, create the mailbox, or file
skipping to change at page 8, line 7 skipping to change at page 8, line 7
exists, the generated message is filed into the special-use mailbox. exists, the generated message is filed into the special-use mailbox.
Otherwise, the generated message is filed into the target mailbox. Otherwise, the generated message is filed into the target mailbox.
If both the optional ":specialuse" and ":create" arguments are If both the optional ":specialuse" and ":create" arguments are
specified with ":fcc", the Sieve interpreter is instructed to create specified with ":fcc", the Sieve interpreter is instructed to create
the target mailbox per Section 4.1 of the target mailbox per Section 4.1 of
[I-D.ietf-extra-sieve-special-use], if needed. [I-D.ietf-extra-sieve-special-use], if needed.
3.5.4. Extended Example 3.5.4. Extended Example
require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"]; require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"];
vacation :days 7 vacation :days 7
:from "hemingway@example.com" "Gone Fishin'" :from "hemingway@example.com" "Gone Fishin'"
:fcc "INBOX.Sent" :specialuse "\\Sent" :create :flags ["\\Seen"]; :fcc "INBOX.Sent" :specialuse "\\Sent" :create
:flags ["\\Seen"];
4. Implementation Status 4. Implementation Status
< RFC Editor: before publication please remove this section and the < RFC Editor: before publication please remove this section and the
reference to [RFC7942] > reference to [RFC7942] >
This section records the status of known implementations of the This section records the status of known implementations of the
protocol defined by this specification at the time of posting of this protocol defined by this specification at the time of posting of this
Internet-Draft, and is based on a proposal described in [RFC7942]. Internet-Draft, and is based on a proposal described in [RFC7942].
The description of implementations in this section is intended to The description of implementations in this section is intended to
skipping to change at page 10, line 40 skipping to change at page 10, line 40
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions)
Part Three: Message Header Extensions for Non-ASCII Text", Part Three: Message Header Extensions for Non-ASCII Text",
RFC 2047, DOI 10.17487/RFC2047, November 1996, RFC 2047, DOI 10.17487/RFC2047, November 1996,
<https://www.rfc-editor.org/info/rfc2047>. <https://www.rfc-editor.org/info/rfc2047>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 4234, DOI 10.17487/RFC4234,
October 2005, <https://www.rfc-editor.org/info/rfc4234>.
[RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email [RFC5228] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email
Filtering Language", RFC 5228, DOI 10.17487/RFC5228, Filtering Language", RFC 5228, DOI 10.17487/RFC5228,
January 2008, <https://www.rfc-editor.org/info/rfc5228>. January 2008, <https://www.rfc-editor.org/info/rfc5228>.
[RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering: [RFC5230] Showalter, T. and N. Freed, Ed., "Sieve Email Filtering:
Vacation Extension", RFC 5230, DOI 10.17487/RFC5230, Vacation Extension", RFC 5230, DOI 10.17487/RFC5230,
January 2008, <https://www.rfc-editor.org/info/rfc5230>. January 2008, <https://www.rfc-editor.org/info/rfc5230>.
[RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags [RFC5232] Melnikov, A., "Sieve Email Filtering: Imap4flags
Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008, Extension", RFC 5232, DOI 10.17487/RFC5232, January 2008,
<https://www.rfc-editor.org/info/rfc5232>. <https://www.rfc-editor.org/info/rfc5232>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008, DOI 10.17487/RFC5322, October 2008,
<https://www.rfc-editor.org/info/rfc5322>. <https://www.rfc-editor.org/info/rfc5322>.
[RFC5435] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T. [RFC5435] Melnikov, A., Ed., Leiba, B., Ed., Segmuller, W., and T.
Martin, "Sieve Email Filtering: Extension for Martin, "Sieve Email Filtering: Extension for
Notifications", RFC 5435, DOI 10.17487/RFC5435, January Notifications", RFC 5435, DOI 10.17487/RFC5435, January
2009, <https://www.rfc-editor.org/info/rfc5435>. 2009, <https://www.rfc-editor.org/info/rfc5435>.
[RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language -- [RFC5490] Melnikov, A., "The Sieve Mail-Filtering Language --
Extensions for Checking Mailbox Status and Accessing Extensions for Checking Mailbox Status and Accessing
Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March Mailbox Metadata", RFC 5490, DOI 10.17487/RFC5490, March
2009, <https://www.rfc-editor.org/info/rfc5490>. 2009, <https://www.rfc-editor.org/info/rfc5490>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
DOI 10.17487/RFC5321, October 2008,
<https://www.rfc-editor.org/info/rfc5321>.
[RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and
Extended Reject Extensions", RFC 5429,
DOI 10.17487/RFC5429, March 2009,
<https://www.rfc-editor.org/info/rfc5429>.
[RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism: [RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism:
mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009, mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009,
<https://www.rfc-editor.org/info/rfc5436>. <https://www.rfc-editor.org/info/rfc5436>.
[RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification [RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification
Mechanism: Extensible Messaging and Presence Protocol Mechanism: Extensible Messaging and Presence Protocol
(XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009, (XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009,
<https://www.rfc-editor.org/info/rfc5437>. <https://www.rfc-editor.org/info/rfc5437>.
[RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension: [RFC6131] George, R. and B. Leiba, "Sieve Vacation Extension:
skipping to change at page 12, line 24 skipping to change at page 12, line 13
[2] http://www.cyrusimap.org/ [2] http://www.cyrusimap.org/
[3] http://www.cmu.edu/computing/ [3] http://www.cmu.edu/computing/
[4] https://www.oracle.com/industries/communications/enterprise/ [4] https://www.oracle.com/industries/communications/enterprise/
products/messaging-server/index.html products/messaging-server/index.html
Appendix A. Change History (To be removed by RFC Editor before Appendix A. Change History (To be removed by RFC Editor before
publication) publication)
Changes since draft-ietf-extra-sieve-fcc-03: Changes since draft-ietf-extra-sieve-fcc-05:
o Fixed typo in ABNF. o Editorial changes from Jiankang Yao.
Changes since draft-ietf-extra-sieve-fcc-04: Changes since draft-ietf-extra-sieve-fcc-04:
o Editorial changes from Ned Freed. o Editorial changes from Ned Freed.
o Added information on Oracle implementation. o Added information on Oracle implementation.
Changes since draft-ietf-extra-sieve-fcc-03:
o Fixed typo in ABNF.
Changes since draft-ietf-extra-sieve-fcc-02: Changes since draft-ietf-extra-sieve-fcc-02:
o Updated Keywords boilerplate. o Updated Keywords boilerplate.
o Noted that :fcc mailbox argument and any fileinto extension o Noted that :fcc mailbox argument and any fileinto extension
arguments used wth :fcc have the same syntax and semantics as they arguments used wth :fcc have the same syntax and semantics as they
have with fileinto. have with fileinto.
o Removed section on [e]Reject. o Removed section on [e]Reject.
skipping to change at page 13, line 29 skipping to change at page 13, line 21
o Added registration of the extension with IANA. o Added registration of the extension with IANA.
o Added Acknowledgments. o Added Acknowledgments.
o Minor editorial changes. o Minor editorial changes.
Authors' Addresses Authors' Addresses
Kenneth Murchison Kenneth Murchison
FastMail US LLC FastMail US LLC
1315 Walnut Street - Suite 320 1429 Walnut Street
Philadelphia, PA 19107 Philadelphia, PA 19107
USA USA
Email: murch@fastmailteam.com Email: murch@fastmailteam.com
Bron Gondwana Bron Gondwana
FastMail Pty Ltd FastMail Pty Ltd
Level 2, 114 William Street Level 2, 114 William Street
Melbourne, VIC 3000 Melbourne, VIC 3000
Australia Australia
 End of changes. 15 change blocks. 
26 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/