< draft-ietf-extra-sieve-fcc-01.txt		draft-ietf-extra-sieve-fcc-02.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 January 11, 2018		Intended status: Standards Track April 29, 2018
	Expires: July 15, 2018		Expires: October 31, 2018
	Sieve Extension: File Carbon Copy (Fcc)		Sieve Extension: File Carbon Copy (Fcc)
	draft-ietf-extra-sieve-fcc-01		draft-ietf-extra-sieve-fcc-02
	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 July 15, 2018.		This Internet-Draft will expire on October 31, 2018.
	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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Conventions Used in This Document . . . . . . . . . . . . . . 2		2. Conventions Used in This Document . . . . . . . . . . . . . . 3
	3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3		3. Tagged Argument ":fcc" . . . . . . . . . . . . . . . . . . . 3
	3.1. Interaction with the Vacation Action . . . . . . . . . . 3		3.1. Format of Filed Messages . . . . . . . . . . . . . . . . 3
	3.2. Interaction with the Notify Action . . . . . . . . . . . 4		3.2. Interaction with the Vacation Action . . . . . . . . . . 4
	3.3. Compatibility with the Reject and Extended Reject		3.3. Interaction with the Notify Action . . . . . . . . . . . 4
	Actions . . . . . . . . . . . . . . . . . . . . . . . . . 4		3.4. Compatibility with the Reject and Extended Reject
	3.4. Compatibility with Other Actions . . . . . . . . . . . . 4		Actions . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3.5. Interaction with Fileinto Extensions . . . . . . . . . . 4		3.5. Compatibility with Other Actions . . . . . . . . . . . . 5
	3.5.1. Imap4flags Extension . . . . . . . . . . . . . . . . 5		3.6. Interaction with Fileinto Extensions . . . . . . . . . . 6
	3.5.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 5		3.6.1. Imap4flags Extension . . . . . . . . . . . . . . . . 6
	3.5.3. Special-Use Extension . . . . . . . . . . . . . . . . 5		3.6.2. Mailbox Extension . . . . . . . . . . . . . . . . . . 6
	3.5.4. Extended Example . . . . . . . . . . . . . . . . . . 6		3.6.3. Special-Use Extension . . . . . . . . . . . . . . . . 6
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 6		3.6.4. Extended Example . . . . . . . . . . . . . . . . . . 7
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
	5.1. Registration of Sieve Extension . . . . . . . . . . . . . 6		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6		5.1. Registration of Sieve Extension . . . . . . . . . . . . . 7
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
	7.1. Normative References . . . . . . . . . . . . . . . . . . 6		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7.2. Informative References . . . . . . . . . . . . . . . . . 7		7.1. Normative References . . . . . . . . . . . . . . . . . . 8
			7.2. Informative References . . . . . . . . . . . . . . . . . 9
	Appendix A. Change History (To be removed by RFC Editor before		Appendix A. Change History (To be removed by RFC Editor before
	publication) . . . . . . . . . . . . . . . . . . . . 8		publication) . . . . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	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. Two such commands are defined by the Vacation		behalf of the user. Two such commands are defined by the Vacation
	[RFC5230] and Notify [RFC5435] extensions. It is sometimes desirable		[RFC5230] and Notify [RFC5435] extensions. It is sometimes desirable
	to have an archive of the messages generated by these commands.		to have an archive of 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
	skipping to change at page 3, line 12 ¶		skipping to change at page 3, line 18 ¶
	including use of the "Usage:" label for the definition of action and		including use of the "Usage:" label for the definition of action and
	tagged arguments syntax.		tagged arguments syntax.
	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		"OPTIONAL" in this document are to be interpreted as described in
	[RFC2119].		[RFC2119].
	3. Tagged Argument ":fcc"		3. Tagged Argument ":fcc"
	Usage: ":fcc" FCC-OPTIONS <mailbox: string>		For convenience, the "FCC" syntax element is defined here using ABNF
			[RFC4234] so that it can be augmented by other extensions.
	The positional FCC-OPTIONS argument is defined here in ABNF [RFC4234]
	syntax so that it can be modified by other extensions.
	FCC-OPTIONS = "" ; empty 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. If		to file a copy of the generated message into the target mailbox. If
	the specified mailbox doesn't exist, the implementation MAY treat it		the specified mailbox doesn't exist, the implementation MAY treat it
	as an error, create the mailbox, or file the message into an		as an error, create the mailbox, or file the message into an
	implementation-defined mailbox.		implementation-defined mailbox.
	3.1. Interaction with the Vacation Action		3.1. Format of Filed Messages
			Copies of messages filed into a mailbox via this extension are
			REQUIRED to be in Internet Message Format [RFC5322]. Some messages
			generated by Sieve actions might already conform to this format and
			MAY be filed without modification. Messages generated in other
			formats MUST be encapsulated using constructs from [RFC5322] and MIME
			([RFC2045], [RFC2046], [RFC2047]).
			The general requirements for encapsulating the copies of messages to
			be filed are the following:
			o Date: The Date header field is REQUIRED and SHOULD be set to the
			date and time when the message was generated.
			o From: The From header field is REQUIRED and SHOULD be set to the
			email address of the owner of the Sieve script, unless explicitly
			overridden by rules for encapsulating a particular message type.
			o To: The To header field is OPTIONAL and MAY be set to the email
			address of the recipient of the generated message, if available.
			o Subject: The Subject header field is OPTIONAL and MAY be generated
			as follows: The subject is set to the characters "Fcc: " followed
			by the subject of the message being processed by the Sieve
			interpreter.
			o In-Reply-To: The In-Reply-To header field is OPTIONAL and MAY be
			set to the Message-ID of the message being processed by the Sieve
			interpreter.
			o Message Body: The body of the filed message is REQUIRED and is
			composed of one or more MIME-parts containing the generated
			message and any related metadata. The Content-Type header
			field(s) MUST be set to the appropriate MIME types. If any of the
			MIME-parts include 8-bit or binary data, the Content-Transfer-
			Encoding header field(s) MUST be set accordingly.
			3.2. Interaction with the Vacation Action
	This document extends the "vacation" [RFC5230] action (see also		This document extends the "vacation" [RFC5230] action (see also
	"vacation-seconds" [RFC6131]) to optionally store a copy of the auto-		"vacation-seconds" [RFC6131]) to optionally store a copy of the auto-
	reply messages into a target mailbox.		reply messages into a target mailbox.
	Usage: vacation [":days" number | ":seconds" number]		Usage: vacation [FCC]
			[":days" number | ":seconds" number]
	[":subject" string]		[":subject" string]
	[":from" string]		[":from" string]
	[":addresses" string-list]		[":addresses" string-list]
	[":mime"]		[":mime"]
	[":handle" string]		[":handle" string]
	[":fcc" FCC-OPTIONS <mailbox: string>]
	<reason: string>		<reason: string>
	Example:		Example:
	require ["vacation", "fcc"];		require ["vacation", "fcc"];
	vacation :days 7		vacation :days 7
	:fcc "INBOX.Sent"		:from "hemingway@example.com" "Gone Fishin'"
	:from "hemingway@example.com" "Gone Fishin'";		:fcc "INBOX.Sent";
	3.2. Interaction with the Notify Action		Vacation auto-reply messages are MIME-compliant and MAY be filed into
			the target mailbox without modification.
			3.3. Interaction with the Notify Action
	This document extends the "notify" [RFC5435] action to optionally		This document extends the "notify" [RFC5435] action to optionally
	store a copy of the notification messages into a target mailbox.		store a copy of the notification messages into a target mailbox.
	Usage: notify [":from" string]		Usage: notify [FCC]
			[":from" string]
	[":importance" <"1" / "2" / "3">]		[":importance" <"1" / "2" / "3">]
	[":options" string-list]		[":options" string-list]
	[":message" string]		[":message" string]
	[":fcc" FCC-OPTIONS <mailbox: string>]
	<method: string>		<method: string>
	Example:		Example:
	require ["enotify", "fcc"];		require ["enotify", "fcc"];
	notify :message "You got mail!"		notify :fcc "INBOX.Sent"
	:fcc "INBOX.Sent"		:message "You got mail!"
	"mailto:ken@example.com";		"mailto:ken@example.com";
	3.3. Compatibility with the Reject and Extended Reject Actions		Messages generated using the "mailto" [RFC5436] notification method
			are MIME-compliant and MAY be filed into the target mailbox without
			modification.
			Messages generated by other notification methods (e.g. "xmpp"
			[RFC5437]) MUST be encapsulated per Section 3.1 before being filed.
			The body of the filed message MUST include the :message parameter and
			MAY include one or more of the :from, :importance, or :options
			parameters. The MIME-type(s) of the body part(s) used to encapsulate
			the parameters is an implementation decision.
			3.4. Compatibility with the Reject and Extended Reject Actions
	"fcc" MUST be incompatible with the "reject" and "ereject" [RFC5429]		"fcc" MUST be incompatible with the "reject" and "ereject" [RFC5429]
	actions. Making "fcc" compatible with these actions violates the		actions. Making "fcc" compatible with these actions violates the
	SMTP [RFC5321] principle that a message is either delivered or		SMTP [RFC5321] principle that a message is either delivered or
	bounced back to the sender. Namely, the saved copy of the rejection		bounced back to the sender. Namely, the saved copy of the rejection
	message will contain the original message.		message will contain the original message.
	It is an error for a script to use the ":fcc" tagged argument with		It is an error for a script to use the ":fcc" tagged argument with
	either "reject" or "ereject".		either "reject" or "ereject".
	3.4. Compatibility with Other Actions		3.5. Compatibility with Other Actions
	The "fcc" extension is not compatible with any Sieve action that does		The "fcc" extension is not compatible with any Sieve action that does
	not generate an additional message on behalf of the user. It is an		not generate an additional message on behalf of the user. It is an
	error for a script to use the ":fcc" tagged argument with any such		error for a script to use the ":fcc" tagged argument with any such
	action.		action.
	Future extensions that define actions that generate additional		Future extensions that define actions that generate additional
	messages on behalf of the user should describe their compatibility		messages on behalf of the user should describe their compatibility
	with ":fcc".		with ":fcc", and how to MIME-encapsulate the message, if required.
	3.5. Interaction with Fileinto Extensions		3.6. Interaction with Fileinto Extensions
	The "fcc" extension can be used with some tagged arguments defined in		The "fcc" extension can be used with some tagged arguments defined in
	extensions to the "fileinto" action. The sections below describe its		extensions to the "fileinto" action. The sections below describe its
	interaction with currently defined extensions. Tagged arguments in		interaction with currently defined extensions. Tagged arguments in
	future extensions to the "fileinto" command should describe their		future extensions to the "fileinto" command should describe their
	interaction with ":fcc", if any.		interaction with ":fcc", if any.
	3.5.1. Imap4flags Extension		3.6.1. Imap4flags Extension
	This document extends the definition of the ":flags" [RFC5232] tagged		This document extends the definition of the ":flags" [RFC5232] tagged
	argument so that it can be used as an FCC-OPTIONS to the ":fcc"		argument so that it can optionally be used with the ":fcc" argument.
	argument.
	FCC-OPTIONS =/ [":flags" <list-of-flags: string-list>]		FCC =/ [":flags" <list-of-flags: string-list>]
	If the optional ":flags" argument is specified with ":fcc", it		If the optional ":flags" argument is specified with ":fcc", it
	instructs the Sieve interpreter to set the IMAP4 flags provided in		instructs the Sieve interpreter to set the IMAP4 flags provided in
	the subsequent argument when the generated message is filed into the		the subsequent argument when the generated message is filed into the
	target mailbox.		target mailbox.
	3.5.2. Mailbox Extension		3.6.2. Mailbox Extension
	This document extends the definition of the ":create" [RFC5490]		This document extends the definition of the ":create" [RFC5490]
	tagged argument so that it can be used as an FCC-OPTIONS to the		tagged argument so that it can optionally be used with the ":fcc"
	":fcc" argument.		argument.
	FCC-OPTIONS =/ [":create"]		FCC =/ [":create"]
	If the optional ":create" argument is specified with ":fcc", it		If the optional ":create" argument is specified with ":fcc", it
	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.6.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 be		[I-D.ietf-extra-sieve-special-use] tagged argument so that it can
	used as an FCC-OPTIONS to the ":fcc" argument.		optionally be used with the ":fcc" argument.
	FCC-OPTIONS =/ [":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
	[I-D.ietf-extra-sieve-special-use], if needed.		[I-D.ietf-extra-sieve-special-use], if needed.
	3.5.4. Extended Example		3.6.4. Extended Example
	require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"];		require ["vacation", "fcc", "mailbox", "special-use", "imap4flags"];
	vacation :days 7		vacation :days 7
	:fcc :specialuse "\\Sent" :create :flags ["\\Seen"] "INBOX.Sent"		:from "hemingway@example.com" "Gone Fishin'"
	:from "hemingway@example.com" "Gone Fishin'";		:fcc "INBOX.Sent" :specialuse "\\Sent" :create :flags ["\\Seen"];
	4. Security Considerations		4. Security Considerations
	The "fcc" extension does not raise any other security considerations		The "fcc" extension does not raise any other security considerations
	that are not already present in [RFC5228], [RFC5230], [RFC5435], and		that are not already present in [RFC5228], [RFC5230], [RFC5435], and
	[RFC6131].		[RFC6131].
	5. IANA Considerations		5. IANA Considerations
	5.1. Registration of Sieve Extension		5.1. Registration of Sieve Extension
	skipping to change at page 6, line 40 ¶		skipping to change at page 7, line 45 ¶
	that generate additional messages.		that generate additional messages.
	RFC number: RFC XXXX		RFC number: RFC XXXX
	Contact address: The Sieve discussion list <sieve@ietf.org>		Contact address: The Sieve discussion list <sieve@ietf.org>
	6. Acknowledgments		6. Acknowledgments
	The authors would like to thank the following individuals for		The authors would like to thank the following individuals for
	contributing their ideas and support for writing this specification:		contributing their ideas and support for writing this specification:
	Ned Freed, Stan Kalisch.		Ned Freed, Stan Kalisch, and Alexey Melnikov.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[I-D.ietf-extra-sieve-special-use]		[I-D.ietf-extra-sieve-special-use]
	Bosch, S., "Sieve Email Filtering: Delivering to Special-		Bosch, S., "Sieve Email Filtering: Delivering to Special-
	Use Mailboxes", draft-ietf-extra-sieve-special-use-01		Use Mailboxes", draft-ietf-extra-sieve-special-use-02
	(work in progress), January 2018.		(work in progress), March 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,
			<https://www.rfc-editor.org/info/rfc2045>.
			[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
			Extensions (MIME) Part Two: Media Types", RFC 2046,
			DOI 10.17487/RFC2046, November 1996,
			<https://www.rfc-editor.org/info/rfc2046>.
			[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions)
			Part Three: Message Header Extensions for Non-ASCII Text",
			RFC 2047, DOI 10.17487/RFC2047, November 1996,
			<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		[RFC4234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
	Specifications: ABNF", RFC 4234, DOI 10.17487/RFC4234,		Specifications: ABNF", RFC 4234, DOI 10.17487/RFC4234,
	October 2005, <https://www.rfc-editor.org/info/rfc4234>.		October 2005, <https://www.rfc-editor.org/info/rfc4234>.
	skipping to change at page 7, line 26 ¶		skipping to change at page 8, line 47 ¶
	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>.
			[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
			DOI 10.17487/RFC5322, October 2008,
			<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>.
	skipping to change at page 7, line 47 ¶		skipping to change at page 9, line 26 ¶
	[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,		[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
	DOI 10.17487/RFC5321, October 2008,		DOI 10.17487/RFC5321, October 2008,
	<https://www.rfc-editor.org/info/rfc5321>.		<https://www.rfc-editor.org/info/rfc5321>.
	[RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and		[RFC5429] Stone, A., Ed., "Sieve Email Filtering: Reject and
	Extended Reject Extensions", RFC 5429,		Extended Reject Extensions", RFC 5429,
	DOI 10.17487/RFC5429, March 2009,		DOI 10.17487/RFC5429, March 2009,
	<https://www.rfc-editor.org/info/rfc5429>.		<https://www.rfc-editor.org/info/rfc5429>.
			[RFC5436] Leiba, B. and M. Haardt, "Sieve Notification Mechanism:
			mailto", RFC 5436, DOI 10.17487/RFC5436, January 2009,
			<https://www.rfc-editor.org/info/rfc5436>.
			[RFC5437] Saint-Andre, P. and A. Melnikov, "Sieve Notification
			Mechanism: Extensible Messaging and Presence Protocol
			(XMPP)", RFC 5437, DOI 10.17487/RFC5437, January 2009,
			<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:
	"Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July		"Seconds" Parameter", RFC 6131, DOI 10.17487/RFC6131, July
	2011, <https://www.rfc-editor.org/info/rfc6131>.		2011, <https://www.rfc-editor.org/info/rfc6131>.
	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-01:
			o Added text discussing how to handle generated messages that are
			not in MIME format.
			o Adjusted ABNF so that tagged arguments that supplement :fcc no
			longer appear as positional.
	Changes since draft-ietf-extra-sieve-fcc-00:		Changes since draft-ietf-extra-sieve-fcc-00:
	o Updated abstract with text from Ned.		o Updated abstract with text from Ned.
	o Added support for :fcc to notify extension.		o Added support for :fcc to notify extension.
	o Prohibit use of :fcc with reject and ereject extensions.		o Prohibit use of :fcc with reject and ereject extensions.
	o Added registration of the extension with IANA.		o Added registration of the extension with IANA.
End of changes. 37 change blocks.
	62 lines changed or deleted		147 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/