draft-ietf-extra-sieve-fcc-03.txt		draft-ietf-extra-sieve-fcc-04.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 August 3, 2018		Intended status: Standards Track August 12, 2018
	Expires: February 4, 2019		Expires: February 13, 2019
	Sieve Extension: File Carbon Copy (Fcc)		Sieve Extension: File Carbon Copy (Fcc)
	draft-ietf-extra-sieve-fcc-03		draft-ietf-extra-sieve-fcc-04
	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.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 February 4, 2019.		This Internet-Draft will expire on February 13, 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 35 ¶		skipping to change at page 2, line 35 ¶
	6.1. Registration of Sieve Extension . . . . . . . . . . . . . 8		6.1. Registration of Sieve Extension . . . . . . . . . . . . . 8
	6.2. Registration of Notification-Capability		6.2. Registration of Notification-Capability
	Parameter . . . . . . . . . . . . . . . . . . . . . . . . 9		Parameter . . . . . . . . . . . . . . . . . . . . . . . . 9
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	8.1. Normative References . . . . . . . . . . . . . . . . . . 9		8.1. Normative References . . . . . . . . . . . . . . . . . . 9
	8.2. Informative References . . . . . . . . . . . . . . . . . 11		8.2. Informative References . . . . . . . . . . . . . . . . . 11
	8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 11		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 . . . . . . . . . . . . . . . . . . . . . . . 12		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 to have an archive of		behalf of the user. It is sometimes desirable to have an archive of
	the messages generated by these commands.		the messages generated by these commands.
	This extension defines a new optional tagged argument ":fcc" to		This extension defines a new optional tagged argument ":fcc" to
	action commands which generate additional messages to allow a copy of		action commands which generate additional messages to allow a copy of
	skipping to change at page 7, line 28 ¶		skipping to change at page 7, line 28 ¶
	instructs the Sieve interpreter to create the target mailbox, if		instructs the Sieve interpreter to create the target mailbox, if
	needed, before attempting to file the generated message into the		needed, before attempting to file the generated message into the
	target mailbox.		target mailbox.
	3.5.3. Special-Use Extension		3.5.3. Special-Use Extension
	This document extends the definition of the ":specialuse"		This document extends the definition of the ":specialuse"
	[I-D.ietf-extra-sieve-special-use] tagged argument so that it can		[I-D.ietf-extra-sieve-special-use] tagged argument so that it can
	optionally be used with the ":fcc" argument.		optionally be used with the ":fcc" argument.
	FCC =/ [":specialuse <special-use-flag: string>"]		FCC =/ [":specialuse" <special-use-flag: string>]
	If the optional ":specialuse" argument is specified with ":fcc", it		If the optional ":specialuse" argument is specified with ":fcc", it
	instructs the Sieve interpreter to check whether a mailbox exists		instructs the Sieve interpreter to check whether a mailbox exists
	with the specific special-use flag assigned to it. If such a mailbox		with the specific special-use flag assigned to it. If such a mailbox
	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
	skipping to change at page 12, line 8 ¶		skipping to change at page 12, line 8 ¶
	[1] https://tools.ietf.org/html/bcp14		[1] https://tools.ietf.org/html/bcp14
	[2] http://www.cyrusimap.org/		[2] http://www.cyrusimap.org/
	[3] http://www.cmu.edu/computing/		[3] http://www.cmu.edu/computing/
	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:
			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.
End of changes. 6 change blocks.
	6 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/