< draft-bosch-sieve-special-use-00.txt		draft-bosch-sieve-special-use-01.txt >
	Network Working Group S. Bosch		Network Working Group S. Bosch
	Internet-Draft Dovecot Oy		Internet-Draft Dovecot Oy
	Intended status: Standards Track April 4, 2016		Intended status: Standards Track October 10, 2016
	Expires: October 6, 2016		Expires: April 13, 2017
	Sieve Email Filtering: Delivering to Special-Use Mailboxes		Sieve Email Filtering: Delivering to Special-Use Mailboxes
	draft-bosch-sieve-special-use-00		draft-bosch-sieve-special-use-01
	Abstract		Abstract
	The SPECIAL-USE capability of the IMAP protocol (RFC 6154) allows		The SPECIAL-USE capability of the IMAP protocol (RFC 6154) allows
	clients to identify special-use mailboxes; e.g., where draft or sent		clients to identify special-use mailboxes; e.g., where draft or sent
	messages should be put. This simplifies client configuration. In		messages should be put. This simplifies client configuration. In
	contrast, the Sieve mail filtering language (RFC 5228) currently has		contrast, the Sieve mail filtering language (RFC 5228) currently has
	no such capability. This memo defines a Sieve extension that fills		no such capability. This memo defines a Sieve extension that fills
	this gap: it adds a test for checking whether a special-use attribute		this gap: it adds a test for checking whether a special-use attribute
	is assigned for a particular mailbox or any mailbox, and it adds the		is assigned for a particular mailbox or any mailbox, and it adds the
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 October 6, 2016.		This Internet-Draft will expire on April 13, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 20 ¶		skipping to change at page 2, line 20 ¶
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Conventions Used in This Document . . . . . . . . . . . . . . 3		2. Conventions Used in This Document . . . . . . . . . . . . . . 3
	3. Test "specialuse_exists" . . . . . . . . . . . . . . . . . . 3		3. Test "specialuse_exists" . . . . . . . . . . . . . . . . . . 3
	4. ":specialuse" Argument to "fileinto" Command . . . . . . . . 4		4. ":specialuse" Argument to "fileinto" Command . . . . . . . . 4
	4.1. Interaction with ":create" Argument to "fileinto" Command 5		4.1. Interaction with ":create" Argument to "fileinto" Command 5
	5. Sieve Capability Strings . . . . . . . . . . . . . . . . . . 5		5. Sieve Capability Strings . . . . . . . . . . . . . . . . . . 5
	6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5		6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 6		7. Security Considerations . . . . . . . . . . . . . . . . . . . 6
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
	9.1. Normative References . . . . . . . . . . . . . . . . . . 7		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	9.2. Informative References . . . . . . . . . . . . . . . . . 8		10.1. Normative References . . . . . . . . . . . . . . . . . . 7
			10.2. Informative References . . . . . . . . . . . . . . . . . 8
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
	1. Introduction		1. Introduction
	Commonly, several mailboxes in an IMAP message store [IMAP] have a		Commonly, several mailboxes in an IMAP message store [IMAP] have a
	special use; e.g. it is where the user's draft messages are stored,		special use; e.g. it is where the user's draft messages are stored,
	where a copy of sent messages are kept, or it is where spam messages		where a copy of sent messages are kept, or it is where spam messages
	are filed automatically at delivery. The SPECIAL-USE capability		are filed automatically at delivery. The SPECIAL-USE capability
	[SPECIAL-USE] of the IMAP protocol defines mailbox attributes that		[SPECIAL-USE] of the IMAP protocol defines mailbox attributes that
	identify these special mailboxes explicitly to the client. This way,		identify these special mailboxes explicitly to the client. This way,
	skipping to change at page 6, line 36 ¶		skipping to change at page 6, line 36 ¶
	}		}
	if allof(		if allof(
	environment "imap.cause" "COPY",		environment "imap.cause" "COPY",
	specialuse_exists "${mailbox}" "\\Junk") {		specialuse_exists "${mailbox}" "\\Junk") {
	redirect "spam-report@example.org";		redirect "spam-report@example.org";
	}		}
	7. Security Considerations		7. Security Considerations
	[FIXME]		Security considerations are discussed in [SIEVE] and [SPECIAL-USE].
			It is believed that this extension does not introduce any additional
	Additional security considerations are discussed in [SIEVE].		security concerns.
	8. IANA Considerations		8. IANA Considerations
	The following template specifies the IANA registration of the Sieve		The following template specifies the IANA registration of the Sieve
	extension specified in this document:		extension specified in this document:
	To: iana@iana.org		To: iana@iana.org
	Subject: Registration of new Sieve extension		Subject: Registration of new Sieve extension
	Capability name: special-use		Capability name: special-use
	skipping to change at page 7, line 21 ¶		skipping to change at page 7, line 21 ¶
	particular mailbox or any mailbox, and it adds		particular mailbox or any mailbox, and it adds
	the ability to file messages into an anonymous		the ability to file messages into an anonymous
	mailbox that has a particular IMAP special-use		mailbox that has a particular IMAP special-use
	attribute assigned.		attribute assigned.
	RFC number: this RFC		RFC number: this RFC
	Contact address: Sieve mailing list <sieve@ietf.org>		Contact address: Sieve mailing list <sieve@ietf.org>
	This information should be added to the list of sieve extensions		This information should be added to the list of sieve extensions
	given on http://www.iana.org/assignments/sieve-extensions.		given on http://www.iana.org/assignments/sieve-extensions.
	9. References		9. Acknowledgements
	9.1. Normative References		Thanks to Barry Leiba, Alexey Melnikov, Ken Murchison, and Ned Freed
			for reviews and suggestions.
			10. References
			10.1. Normative References
	[IMAP-METADATA]		[IMAP-METADATA]
	Daboo, C., "The IMAP METADATA Extension", RFC 5464, DOI		Daboo, C., "The IMAP METADATA Extension", RFC 5464, DOI
	10.17487/RFC5464, February 2009,		10.17487/RFC5464, February 2009,
	<http://www.rfc-editor.org/info/rfc5464>.		<http://www.rfc-editor.org/info/rfc5464>.
	[KEYWORDS]		[KEYWORDS]
	Bradner, S., "Key words for use in RFCs to Indicate		Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	skipping to change at page 8, line 5 ¶		skipping to change at page 8, line 9 ¶
	[SPECIAL-USE]		[SPECIAL-USE]
	Leiba, B. and J. Nicolson, "IMAP LIST Extension for		Leiba, B. and J. Nicolson, "IMAP LIST Extension for
	Special-Use Mailboxes", RFC 6154, DOI 10.17487/RFC6154,		Special-Use Mailboxes", RFC 6154, DOI 10.17487/RFC6154,
	March 2011, <http://www.rfc-editor.org/info/rfc6154>.		March 2011, <http://www.rfc-editor.org/info/rfc6154>.
	[VARIABLES]		[VARIABLES]
	Homme, K., "Sieve Email Filtering: Variables Extension",		Homme, K., "Sieve Email Filtering: Variables Extension",
	RFC 5229, January 2008.		RFC 5229, January 2008.
	9.2. Informative References		10.2. Informative References
	[IMAP] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION		[IMAP] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
	4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003,		4rev1", RFC 3501, DOI 10.17487/RFC3501, March 2003,
	<http://www.rfc-editor.org/info/rfc3501>.		<http://www.rfc-editor.org/info/rfc3501>.
	[IMAPSIEVE]		[IMAPSIEVE]
	Leiba, B., "Support for Internet Message Access Protocol		Leiba, B., "Support for Internet Message Access Protocol
	(IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785,		(IMAP) Events in Sieve", RFC 6785, DOI 10.17487/RFC6785,
	November 2012, <http://www.rfc-editor.org/info/rfc6785>.		November 2012, <http://www.rfc-editor.org/info/rfc6785>.
End of changes. 8 change blocks.
	13 lines changed or deleted		19 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/