draft-ietf-sieve-managesieve-04.txt   draft-ietf-sieve-managesieve-05.txt 
Sieve Working Group A. Melnikov, Ed. Sieve Working Group A. Melnikov, Ed.
Internet-Draft Isode Limited Internet-Draft Isode Limited
Intended status: Standards Track T. Martin Intended status: Standards Track T. Martin
Expires: June 18, 2009 BeThereBeSquare Inc. Expires: June 19, 2009 BeThereBeSquare Inc.
December 15, 2008 December 16, 2008
A Protocol for Remotely Managing Sieve Scripts A Protocol for Remotely Managing Sieve Scripts
draft-ietf-sieve-managesieve-04 draft-ietf-sieve-managesieve-05
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 18, 2009. This Internet-Draft will expire on June 19, 2009.
Abstract Abstract
Sieve scripts allow users to filter incoming email. Message stores Sieve scripts allow users to filter incoming email. Message stores
are commonly sealed servers so users cannot log into them, yet users are commonly sealed servers so users cannot log into them, yet users
must be able to update their scripts on them. This document must be able to update their scripts on them. This document
describes a protocol "ManageSieve" for securely managing Sieve describes a protocol "ManageSieve" for securely managing Sieve
scripts on a remote server. This protocol allows a user to have scripts on a remote server. This protocol allows a user to have
multiple scripts, and also alerts a user to syntactically flawed multiple scripts, and also alerts a user to syntactically flawed
scripts. scripts.
skipping to change at page 3, line 6 skipping to change at page 3, line 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . 36 6. IANA Considerations . . . . . . . . . . . . . . . . . . . 36
6.1. ManageSieve Capability Registration Template . . . . . . . 37 6.1. ManageSieve Capability Registration Template . . . . . . . 37
6.2. Registration of Initial ManageSieve capabilities . . . . . 37 6.2. Registration of Initial ManageSieve capabilities . . . . . 37
6.3. ManageSieve Response Code Registration Template . . . . . 39 6.3. ManageSieve Response Code Registration Template . . . . . 39
6.4. Registration of Initial ManageSieve Response Codes . . . . 39 6.4. Registration of Initial ManageSieve Response Codes . . . . 39
7. Internationalization Considerations . . . . . . . . . . . 45 7. Internationalization Considerations . . . . . . . . . . . 45
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 45 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 45
9. References . . . . . . . . . . . . . . . . . . . . . . . . 45 9. References . . . . . . . . . . . . . . . . . . . . . . . . 46
9.1. Normative References . . . . . . . . . . . . . . . . . . . 45 9.1. Normative References . . . . . . . . . . . . . . . . . . . 46
9.2. Informative References . . . . . . . . . . . . . . . . . . 47 9.2. Informative References . . . . . . . . . . . . . . . . . . 47
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 48 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 48
Intellectual Property and Copyright Statements . . . . . . 49 Intellectual Property and Copyright Statements . . . . . . 49
1. Introduction 1. Introduction
1.1. Conventions used in this document 1.1. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 45, line 16 skipping to change at page 45, line 16
Author/Change controller: IESG. Author/Change controller: IESG.
7. Internationalization Considerations 7. Internationalization Considerations
The LANGUAGE capability (see Section 1.7) allows a client to discover The LANGUAGE capability (see Section 1.7) allows a client to discover
the current language used in all human readable responses that might the current language used in all human readable responses that might
be returned at the end of any OK/NO/BYE response. Human readable be returned at the end of any OK/NO/BYE response. Human readable
text in OK responses typically doesn't need to be shown to the user, text in OK responses typically doesn't need to be shown to the user,
unless it is returned in response to PUTSCRIPT or CHECKSCRIPT command unless it is returned in response to PUTSCRIPT or CHECKSCRIPT command
that also contain the WARNING response code Section 1.3. Human that also contain the WARNINGS response code Section 1.3. Human
readable text from NO/BYE responses SHOULD be shown to the user, readable text from NO/BYE responses is intended be shown to the user,
unless the client can automatically handle failure of the command unless the client can automatically handle failure of the command
that caused such response. Clients SHOULD use response codes that caused such response. Clients SHOULD use response codes
(Section 1.3) for automatic error handling. Response codes can also (Section 1.3) for automatic error handling. Response codes MAY also
be used by the client to present error messages in a language be used by the client to present error messages in a language
understood by the user, for example if the LANGUAGE capability understood by the user, for example if the LANGUAGE capability
doesn't return a language understood by the user. doesn't return a language understood by the user.
Note that the human readable text from OK (WARNINGS) or NO/BYE
responses for PUTSCRIPT/CHECKSCRIPT commands is intended for advanced
users that understand Sieve language. Such advanced users are often
sophisticated enough to be able to handle whatever language the
server is using, even if it is not their preferred language, and will
want to see error/warning text no matter what language the server
puts it in.
A client that generates Sieve script automatically, for example if
the script is generated without user intervention or from a UI that
presents an abstract list of conditions and corresponding actions,
SHOULD NOT present warning/error messages to the user, because the
user might not even be aware that the client is using Sieve
underneath. However if the client has a debugging mode, such
warnings/errors SHOULD be available in the debugging mode.
8. Acknowledgements 8. Acknowledgements
Thanks to Simon Josefsson, Larry Greenfield, Allen Johnson, Chris Thanks to Simon Josefsson, Larry Greenfield, Allen Johnson, Chris
Newman, Lyndon Nerenberg, Tim Showalter, Sarah Robeson, Walter Wong, Newman, Lyndon Nerenberg, Tim Showalter, Sarah Robeson, Walter Wong,
Barry Leiba, Arnt Gulbrandsen, Stephan Bosch, Ken Murchison, Phil Barry Leiba, Arnt Gulbrandsen, Stephan Bosch, Ken Murchison, Phil
Pennock, Ned Freed, Jeffrey Hutzelman, Mark E. Mallett, Dilyan Pennock, Ned Freed, Jeffrey Hutzelman, Mark E. Mallett, Dilyan
Palauzov, Dave Cridland, Aaron Stone, Robert Burrell Donkin, Patrick Palauzov, Dave Cridland, Aaron Stone, Robert Burrell Donkin, Patrick
Ben Koetter, Bjoern Hoehrmann and Martin Duerst for help with this Ben Koetter, Bjoern Hoehrmann and Martin Duerst for help with this
document. Special thank you to Phil Pennock for providing text for document. Special thank you to Phil Pennock for providing text for
the NOOP command, as well as finding various bugs in the document. the NOOP command, as well as finding various bugs in the document.
 End of changes. 7 change blocks. 
9 lines changed or deleted 25 lines changed or added

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