draft-ietf-sieve-managesieve-01.txt   draft-ietf-sieve-managesieve-02.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: May 5, 2009 BeThereBeSquare Inc. Expires: June 3, 2009 BeThereBeSquare Inc.
November 1, 2008 November 30, 2008
A Protocol for Remotely Managing Sieve Scripts A Protocol for Remotely Managing Sieve Scripts
draft-ietf-sieve-managesieve-01 draft-ietf-sieve-managesieve-02
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 May 5, 2009. This Internet-Draft will expire on June 3, 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 2, line 18 skipping to change at page 2, line 18
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Conventions used in this document . . . . . . . . . . . . 4 1.1. Conventions used in this document . . . . . . . . . . . . 4
1.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Response Codes . . . . . . . . . . . . . . . . . . . . . . 4 1.3. Response Codes . . . . . . . . . . . . . . . . . . . . . . 4
1.4. Active Script . . . . . . . . . . . . . . . . . . . . . . 7 1.4. Active Script . . . . . . . . . . . . . . . . . . . . . . 7
1.5. Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.5. Quotas . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.6. Script Names . . . . . . . . . . . . . . . . . . . . . . . 7 1.6. Script Names . . . . . . . . . . . . . . . . . . . . . . . 7
1.7. Capabilities . . . . . . . . . . . . . . . . . . . . . . . 8 1.7. Capabilities . . . . . . . . . . . . . . . . . . . . . . . 8
1.8. Link Level . . . . . . . . . . . . . . . . . . . . . . . . 10 1.8. Link Level . . . . . . . . . . . . . . . . . . . . . . . . 10
2. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 10 2. Commands . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1. AUTHENTICATE Command . . . . . . . . . . . . . . . . . . . 11 2.1. AUTHENTICATE Command . . . . . . . . . . . . . . . . . . . 11
2.1.1. Use of SASL PLAIN mechanism over TLS . . . . . . . . . . . 16 2.1.1. Use of SASL PLAIN mechanism over TLS . . . . . . . . . . . 16
2.2. STARTTLS Command . . . . . . . . . . . . . . . . . . . . . 16 2.2. STARTTLS Command . . . . . . . . . . . . . . . . . . . . . 16
2.2.1. Server Identity Check . . . . . . . . . . . . . . . . . . 17 2.2.1. Server Identity Check . . . . . . . . . . . . . . . . . . 17
2.3. LOGOUT Command . . . . . . . . . . . . . . . . . . . . . . 19 2.3. LOGOUT Command . . . . . . . . . . . . . . . . . . . . . . 20
2.4. CAPABILITY Command . . . . . . . . . . . . . . . . . . . . 20 2.4. CAPABILITY Command . . . . . . . . . . . . . . . . . . . . 20
2.5. HAVESPACE Command . . . . . . . . . . . . . . . . . . . . 20 2.5. HAVESPACE Command . . . . . . . . . . . . . . . . . . . . 20
2.6. PUTSCRIPT Command . . . . . . . . . . . . . . . . . . . . 20 2.6. PUTSCRIPT Command . . . . . . . . . . . . . . . . . . . . 21
2.7. LISTSCRIPTS Command . . . . . . . . . . . . . . . . . . . 22 2.7. LISTSCRIPTS Command . . . . . . . . . . . . . . . . . . . 23
2.8. SETACTIVE Command . . . . . . . . . . . . . . . . . . . . 23 2.8. SETACTIVE Command . . . . . . . . . . . . . . . . . . . . 23
2.9. GETSCRIPT Command . . . . . . . . . . . . . . . . . . . . 23 2.9. GETSCRIPT Command . . . . . . . . . . . . . . . . . . . . 24
2.10. DELETESCRIPT Command . . . . . . . . . . . . . . . . . . . 24 2.10. DELETESCRIPT Command . . . . . . . . . . . . . . . . . . . 24
2.11. Recommended extensions . . . . . . . . . . . . . . . . . . 24 2.11. RENAMESCRIPT Command . . . . . . . . . . . . . . . . . . . 25
2.11.1. RENAMESCRIPT Command . . . . . . . . . . . . . . . . . . . 25 2.12. CHECKSCRIPT Command . . . . . . . . . . . . . . . . . . . 26
2.11.2. CHECKSCRIPT Command . . . . . . . . . . . . . . . . . . . 26 2.13. NOOP Command . . . . . . . . . . . . . . . . . . . . . . . 27
2.11.3. NOOP Command . . . . . . . . . . . . . . . . . . . . . . . 27 2.14. Recommended extensions . . . . . . . . . . . . . . . . . . 27
2.11.4. UNAUTHENTICATE Command . . . . . . . . . . . . . . . . . . 27 2.14.1. UNAUTHENTICATE Command . . . . . . . . . . . . . . . . . . 27
3. Sieve URL Scheme . . . . . . . . . . . . . . . . . . . . . 28 3. Sieve URL Scheme . . . . . . . . . . . . . . . . . . . . . 28
4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 30 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . 30
5. Security Considerations . . . . . . . . . . . . . . . . . 35 5. Security Considerations . . . . . . . . . . . . . . . . . 36
6. IANA Considerations . . . . . . . . . . . . . . . . . . . 36 6. IANA Considerations . . . . . . . . . . . . . . . . . . . 36
6.1. Manage Sieve Capability Registration Template . . . . . . 37 6.1. ManageSieve Capability Registration Template . . . . . . . 37
6.2. Registration of Initial Manage Sieve capabilities . . . . 37 6.2. Registration of Initial ManageSieve capabilities . . . . . 37
6.3. Manage Sieve Response Code Registration Template . . . . . 39 6.3. Manage Sieve Response Code Registration Template . . . . . 39
6.4. Registration of Initial Manage Sieve Response Codes . . . 40 6.4. Registration of Initial ManageSieve Response Codes . . . . 39
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 44 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 44
8. References . . . . . . . . . . . . . . . . . . . . . . . . 44 8. References . . . . . . . . . . . . . . . . . . . . . . . . 45
8.1. Normative References . . . . . . . . . . . . . . . . . . . 44 8.1. Normative References . . . . . . . . . . . . . . . . . . . 45
8.2. Informative References . . . . . . . . . . . . . . . . . . 46 8.2. Informative References . . . . . . . . . . . . . . . . . . 47
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 47
Intellectual Property and Copyright Statements . . . . . . 48 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",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [KEYWORDS]. document are to be interpreted as described in [KEYWORDS].
In examples, "C:" and "S:" indicate lines sent by the client and In examples, "C:" and "S:" indicate lines sent by the client and
skipping to change at page 5, line 38 skipping to change at page 5, line 38
authentication identity and mechanism. authentication identity and mechanism.
QUOTA QUOTA
If this response code is returned in the NO/BYE response, it means If this response code is returned in the NO/BYE response, it means
that the command would have placed the user above the site-defined that the command would have placed the user above the site-defined
quota constraints. If this response code is returned in the OK quota constraints. If this response code is returned in the OK
response, it can mean that the user's storage is near its quota, or response, it can mean that the user's storage is near its quota, or
it can mean that the account exceeded its quota but that that it can mean that the account exceeded its quota but that that
condition is being allowed by the server (the server supports so condition is being allowed by the server (the server supports so
called "soft quotas"). called "soft quotas"). The QUOTA response code has 2 more detailed
variants: "QUOTA/MAXSCRIPTS" (the maximum number of per-user scripts)
and "QUOTA/MAXSIZE" (the maximum script size).
REFERRAL REFERRAL
This response code may be returned with a BYE result from any This response code may be returned with a BYE result from any
command, and includes a mandatory parameter that indicates what command, and includes a mandatory parameter that indicates what
server to access to manage this user's sieve scripts. The server server to access to manage this user's sieve scripts. The server
will be specified by a Sieve URL (see Section 3). The scriptname will be specified by a Sieve URL (see Section 3). The scriptname
portion of the URL MUST NOT be specified. The client should portion of the URL MUST NOT be specified. The client should
authenticate to the specified server and use it for all further authenticate to the specified server and use it for all further
commands in the current session. commands in the current session.
skipping to change at page 6, line 37 skipping to change at page 6, line 40
response code only makes sense when returned in a NO/BYE response. response code only makes sense when returned in a NO/BYE response.
ACTIVE ACTIVE
A command failed because it is not allowed on the active script. For A command failed because it is not allowed on the active script. For
example DELETESCRIPT on the active script. This response code only example DELETESCRIPT on the active script. This response code only
makes sense when returned in a NO/BYE response. makes sense when returned in a NO/BYE response.
NONEXISTENT NONEXISTENT
A command failed because the references script name doesn't exist. A command failed because the referenced script name doesn't exist.
This response code only makes sense when returned in a NO/BYE This response code only makes sense when returned in a NO/BYE
response. response.
ALREADYEXISTS ALREADYEXISTS
A command failed because the references script name already exists. A command failed because the referenced script name already exists.
This response code only makes sense when returned in a NO/BYE This response code only makes sense when returned in a NO/BYE
response. response.
TAG TAG
This response code name is followed by a string specified in the This response code name is followed by a string specified in the
command. See Section 2.11.3 for a possible use case. command. See Section 2.13 for a possible use case.
WARNINGS WARNINGS
This response code MAY be returned by the server in the OK response This response code MAY be returned by the server in the OK response
(but it might be returned with the NO/BYE response as well) and (but it might be returned with the NO/BYE response as well) and
signals the client that even though the script is syntactically signals the client that even though the script is syntactically
valid, it might contain errors not indended by the script writer. valid, it might contain errors not intended by the script writer.
This response code is typically returned in response to PUTSCRIPT This response code is typically returned in response to PUTSCRIPT
and/or CHECKSCRIPT commands. A client seeing such response code and/or CHECKSCRIPT commands. A client seeing such response code
SHOULD present the returned warning text to the user. SHOULD present the returned warning text to the user.
1.4. Active Script 1.4. Active Script
A user may have multiple Sieve scripts on the server, yet only one A user may have multiple Sieve scripts on the server, yet only one
script may be used for filtering of incoming messages. This is the script may be used for filtering of incoming messages. This is the
active script. Users may have zero or one active scripts and MUST active script. Users may have zero or one active scripts and MUST
use the SETACTIVE command described below for changing the active use the SETACTIVE command described below for changing the active
skipping to change at page 7, line 40 skipping to change at page 7, line 41
overflowing available storage. If a command would place a user over overflowing available storage. If a command would place a user over
a quota setting, servers that impose such quotas MUST reply with a NO a quota setting, servers that impose such quotas MUST reply with a NO
response containing the QUOTA response code. Client implementations response containing the QUOTA response code. Client implementations
MUST be able to handle commands failing because of quota MUST be able to handle commands failing because of quota
restrictions. restrictions.
1.6. Script Names 1.6. Script Names
A Sieve script name is a sequence of Unicode characters encoded in A Sieve script name is a sequence of Unicode characters encoded in
UTF-8 [UTF-8]. A script name MUST comply with Net-Unicode Definition UTF-8 [UTF-8]. A script name MUST comply with Net-Unicode Definition
(Sectio 2 of [NET-UNICODE]), with the following additional (Section 2 of [NET-UNICODE]), with the additional restriction of
restrictions: prohibiting the following Unicode characters:
o 0000-001F; [CONTROL CHARACTERS] o 0000-001F; [CONTROL CHARACTERS]
o 007F; DELETE o 007F; DELETE
o 0080-009F; [CONTROL CHARACTERS] o 0080-009F; [CONTROL CHARACTERS]
o 2028; LINE SEPARATOR o 2028; LINE SEPARATOR
o 2029; PARAGRAPH SEPARATOR o 2029; PARAGRAPH SEPARATOR
Sieve script names MUST be at least one octet (and hense Unicode Sieve script names MUST be at least one octet (and hense Unicode
character) long. Zero octets script name has a special meaning (see character) long. Zero octets script name has a special meaning (see
Section 2.8). Servers MUST allow names of up to 128 Unicode Section 2.8). Servers MUST allow names of up to 128 Unicode
characters in length (which can take up to 512 bytes when encoded in characters in length (which can take up to 512 bytes when encoded in
UTF-8, not counting the terminating NUL), and MAY allow longer names. UTF-8, not counting the terminating NUL), and MAY allow longer names.
A server that receives a script name longer than its internal limit A server that receives a script name longer than its internal limit
MUST rejects the corresponding operation, in particular it MUST NOT MUST rejects the corresponding operation, in particular it MUST NOT
truncate the script name. truncate the script name.
1.7. Capabilities 1.7. Capabilities
skipping to change at page 8, line 18 skipping to change at page 8, line 20
UTF-8, not counting the terminating NUL), and MAY allow longer names. UTF-8, not counting the terminating NUL), and MAY allow longer names.
A server that receives a script name longer than its internal limit A server that receives a script name longer than its internal limit
MUST rejects the corresponding operation, in particular it MUST NOT MUST rejects the corresponding operation, in particular it MUST NOT
truncate the script name. truncate the script name.
1.7. Capabilities 1.7. Capabilities
Server capabilities are sent automatically by the server upon a Server capabilities are sent automatically by the server upon a
client connection, or after successful STARTTLS and AUTHENTICATE client connection, or after successful STARTTLS and AUTHENTICATE
(which establishes a SASL security layer) commands. Capabilities may (which establishes a SASL security layer) commands. Capabilities may
change immediately after a successfully completed STARTTLS command change immediately after a successfully completed STARTTLS command,
and/or immediately after a successfully completed AUTHENTICATE and/or immediately after a successfully completed AUTHENTICATE
command. Capabilities MUST remain static at all other times. command, and/or after a successfully completed UNAUTHENTICATE command
(see Section 2.14.1). Capabilities MUST remain static at all other
times.
Clients MAY request the capabilities at a later time by issuing the Clients MAY request the capabilities at a later time by issuing the
CAPABILITY command described later. The capabilities consist of a CAPABILITY command described later. The capabilities consist of a
series of lines each with one or two strings. The first string is series of lines each with one or two strings. The first string is
the name of the capability, which is case-insensitive. The second the name of the capability, which is case-insensitive. The second
optional string is the value associated with that capability. Order optional string is the value associated with that capability. Order
of capabilities is arbitrary, but each capability name can appear at of capabilities is arbitrary, but each capability name can appear at
most once. most once.
The following capabilities are defined in this document: The following capabilities are defined in this document:
skipping to change at page 8, line 49 skipping to change at page 9, line 5
will list a non empty list of SASL mechanisms. will list a non empty list of SASL mechanisms.
SIEVE - List of space separated Sieve extensions (as listed in Sieve SIEVE - List of space separated Sieve extensions (as listed in Sieve
"require" action [SIEVE]) supported by the Sieve engine. This "require" action [SIEVE]) supported by the Sieve engine. This
capability MUST always be returned by the server. capability MUST always be returned by the server.
STARTTLS - If TLS [TLS] is supported by this implementation. Before STARTTLS - If TLS [TLS] is supported by this implementation. Before
advertising this capability a server MUST verify to the best of its advertising this capability a server MUST verify to the best of its
ability that TLS can be successfully negotiated by a client with ability that TLS can be successfully negotiated by a client with
common cipher suites. Specifically, a server should verify that a common cipher suites. Specifically, a server should verify that a
server certificate has be installed and that the TLS subsystem has server certificate has been installed and that the TLS subsystem has
successfully initialized. successfully initialized. This capability SHOULD NOT be advertised
once STARTTLS or AUTHENTICATE command completes successfully.
MAXREDIRECTS - Specifies the limit on the number of Sieve "redirect" MAXREDIRECTS - Specifies the limit on the number of Sieve "redirect"
actions a script can perform during a single evaluation. Note, that actions a script can perform during a single evaluation. Note, that
this is different from the total number of "redirect" actions a this is different from the total number of "redirect" actions a
script can contain. The value is a non-negative number represented script can contain. The value is a non-negative number represented
as a ManageSieve string. as a ManageSieve string.
NOTIFY - A space separated list of URI schema parts for supported NOTIFY - A space separated list of URI schema parts for supported
notification methods. This capability MUST be specified if the Sieve notification methods. This capability MUST be specified if the Sieve
implementation supports the "enotify" extension [NOTIFY]. implementation supports the "enotify" extension [NOTIFY].
skipping to change at page 9, line 26 skipping to change at page 9, line 30
used for human readable error messages. If this capability is not used for human readable error messages. If this capability is not
returned, the "i-default" [RFC2277] language is assumed. Note that returned, the "i-default" [RFC2277] language is assumed. Note that
the current language MAY be per-user configurable (i.e. it MAY change the current language MAY be per-user configurable (i.e. it MAY change
after authentication). after authentication).
OWNER - The canonical name of the logged in user (SASL "authorization OWNER - The canonical name of the logged in user (SASL "authorization
identity") encoded in UTF-8. This capability MUST NOT be returned in identity") encoded in UTF-8. This capability MUST NOT be returned in
unauthenticated state and SHOULD be returned once the AUTHENTICATE unauthenticated state and SHOULD be returned once the AUTHENTICATE
command succeeds. command succeeds.
Section 2.11 defines some additional ManageSieve extensions and their VERSION - This capability MUST be returned by servers compliant with
this document or its successor. For servers compliant with this
document the capability value is the string "1.0". Lack of this
capability means that the server predates this specification and thus
doesn't support the following commands: RENAMESCRIPT, CHECKSCRIPT and
NOOP.
Section 2.14 defines some additional ManageSieve extensions and their
respective capabilities. respective capabilities.
A server implementation MUST return SIEVE and IMPLEMENTATION A server implementation MUST return SIEVE, IMPLEMENTATION and VERSION
capabilities. capabilities.
A client implementation MUST ignore any listed capabilities that it A client implementation MUST ignore any listed capabilities that it
does not understand. does not understand.
Example: Example:
S: "IMPlemENTATION" "Example1 ManageSieved v001" S: "IMPlemENTATION" "Example1 ManageSieved v001"
S: "SASl" "DIGEST-MD5 GSSAPI" S: "SASl" "DIGEST-MD5 GSSAPI"
S: "SIeVE" "fileinto vacation" S: "SIeVE" "fileinto vacation"
S: "StaRTTLS" S: "StaRTTLS"
S: "NOTIFY" "xmpp mailto" S: "NOTIFY" "xmpp mailto"
S: "MAXREdIRECTS" "5" S: "MAXREdIRECTS" "5"
S: "VERSION" "1.0"
S: OK S: OK
After successful authentication this might look like this: After successful authentication this might look like this:
Example: Example:
S: "IMPlemENTATION" "Example1 ManageSieved v001" S: "IMPlemENTATION" "Example1 ManageSieved v001"
S: "SASl" "DIGEST-MD5 GSSAPI" S: "SASl" "DIGEST-MD5 GSSAPI"
S: "SIeVE" "fileinto vacation" S: "SIeVE" "fileinto vacation"
S: "StaRTTLS"
S: "NOTIFY" "xmpp mailto" S: "NOTIFY" "xmpp mailto"
S: "OWNER" "alexey@example.com" S: "OWNER" "alexey@example.com"
S: "MAXREdIRECTS" "5" S: "MAXREdIRECTS" "5"
S: "VERSION" "1.0"
S: OK S: OK
1.8. Link Level 1.8. Link Level
The ManageSieve protocol assumes a reliable data stream such as that The ManageSieve protocol assumes a reliable data stream such as that
provided by TCP. When TCP is used, a ManageSieve server typically provided by TCP. When TCP is used, a ManageSieve server typically
listens on port 2000. [[anchor6: IANA registration of port 2000 is listens on port 2000. [[anchor6: IANA registration of port 2000 is
pending.]] pending.]]
Before opening the TCP connection, the ManageSieve client first MUST Before opening the TCP connection, the ManageSieve client first MUST
skipping to change at page 11, line 5 skipping to change at page 11, line 17
2. If the SRV lookup fails, the fallback SHOULD be a normal IPv4 or 2. If the SRV lookup fails, the fallback SHOULD be a normal IPv4 or
IPv6 address record resolution to determine the IP address, where IPv6 address record resolution to determine the IP address, where
the port used is the default ManageSieve port of 2000. the port used is the default ManageSieve port of 2000.
2. Commands 2. Commands
This section and its subsections describes valid ManageSieve This section and its subsections describes valid ManageSieve
commands. Upon initial connection to the server the client's session commands. Upon initial connection to the server the client's session
is in non-authenticated state. Prior to successful authentication is in non-authenticated state. Prior to successful authentication
only the AUTHENTICATE, CAPABILITY, STARTTLS, LOGOUT and NOOP (see only the AUTHENTICATE, CAPABILITY, STARTTLS, LOGOUT and NOOP (see
Section 2.11.3) commands are valid. ManageSieve extensions MAY Section 2.13) commands are valid. ManageSieve extensions MAY define
define other commands which are valid in non-authenticated state. other commands which are valid in non-authenticated state. Servers
Servers MUST reject all other commands with a NO response. Clients MUST reject all other commands with a NO response. Clients may
may pipeline commands (send more than one command at a time without pipeline commands (send more than one command at a time without
waiting for completion of the first command ). However, a group of waiting for completion of the first command ). However, a group of
commands sent together MUST NOT have an AUTHENTICATE (*), a STARTTLS commands sent together MUST NOT have an AUTHENTICATE (*), a STARTTLS
or a HAVESPACE command anywhere but the last command in the list. or a HAVESPACE command anywhere but the last command in the list.
(*) - The only exception to this rule is when the AUTHENTICATE (*) - The only exception to this rule is when the AUTHENTICATE
command contains an initial response for a SASL mechanism that allows command contains an initial response for a SASL mechanism that allows
clients to send data first, the mechanism is known to complete in one clients to send data first, the mechanism is known to complete in one
round-trip and the mechanism doesn't negotiate a SASL security layer. round-trip and the mechanism doesn't negotiate a SASL security layer.
Two examples of such SASL mechanisms are PLAIN [PLAIN] and EXTERNAL Two examples of such SASL mechanisms are PLAIN [PLAIN] and EXTERNAL
[SASL]. [SASL].
skipping to change at page 12, line 21 skipping to change at page 12, line 34
The service name specified by this protocol's profile of SASL is The service name specified by this protocol's profile of SASL is
"sieve". "sieve".
Reauthentication is not supported by ManageSieve protocol's profile Reauthentication is not supported by ManageSieve protocol's profile
of SASL. I.e. after a successfully completed AUTHENTICATE command, of SASL. I.e. after a successfully completed AUTHENTICATE command,
no more AUTHENTICATE commands may be issued in the same session. no more AUTHENTICATE commands may be issued in the same session.
After a successful AUTHENTICATE command completes, a server MUST After a successful AUTHENTICATE command completes, a server MUST
reject any further AUTHENTICATE commands with a NO reply. However reject any further AUTHENTICATE commands with a NO reply. However
note that a server may implement UNAUTHENTICATE extension described note that a server may implement UNAUTHENTICATE extension described
in Section 2.11.4. in Section 2.14.1.
If a security layer is negotiated through the SASL authentication If a security layer is negotiated through the SASL authentication
exchange, it takes effect immediately following the CRLF that exchange, it takes effect immediately following the CRLF that
concludes the successful authentication exchange for the client, and concludes the successful authentication exchange for the client, and
the CRLF of the OK response for the server. the CRLF of the OK response for the server.
When a security layer takes effect, the ManageSieve protocol is reset When a security layer takes effect, the ManageSieve protocol is reset
to the initial state (the state in ManageSieve after a client has to the initial state (the state in ManageSieve after a client has
connected to the server). The server MUST discard any knowledge connected to the server). The server MUST discard any knowledge
obtained from the client which was not obtained from the SASL (or obtained from the client which was not obtained from the SASL (or
skipping to change at page 12, line 38 skipping to change at page 13, line 4
When a security layer takes effect, the ManageSieve protocol is reset When a security layer takes effect, the ManageSieve protocol is reset
to the initial state (the state in ManageSieve after a client has to the initial state (the state in ManageSieve after a client has
connected to the server). The server MUST discard any knowledge connected to the server). The server MUST discard any knowledge
obtained from the client which was not obtained from the SASL (or obtained from the client which was not obtained from the SASL (or
TLS) negotiation itself. Likewise, the client MUST discard any TLS) negotiation itself. Likewise, the client MUST discard any
knowledge obtained from the server, such as the list of ManageSieve knowledge obtained from the server, such as the list of ManageSieve
extensions, which was not obtained from the SASL (or TLS) negotiation extensions, which was not obtained from the SASL (or TLS) negotiation
itself. (Note that a client MAY compare the advertised SASL itself. (Note that a client MAY compare the advertised SASL
mechanisms before and after authentication in order to detect an mechanisms before and after authentication in order to detect an
active down-negotiation attack. See below.) active down-negotiation attack. See below.)
Once a SASL security layer is established, the server MUST re-issue Once a SASL security layer is established, the server MUST re-issue
the capability results, followed by an OK response. This is the capability results, followed by an OK response. This is
necessary to protect against man-in-the-middle attacks which alter necessary to protect against man-in-the-middle attacks which alter
the capabilities list prior to SASL negotiation. The capability the capabilities list prior to SASL negotiation. The capability
results MUST include all SASL mechanisms the server was capable of results MUST include all SASL mechanisms the server was capable of
negotiating with that client. This is done in order to allow the negotiating with that client. This is done in order to allow the
client to detect active down-negotiation attack. client to detect active down-negotiation attack.
When both [TLS] and SASL security layers are in effect, the TLS When both [TLS] and SASL security layers are in effect, the TLS
encoding MUST be applied (when sending data) after the SASL encoding, encoding MUST be applied (when sending data) after the SASL encoding.
regardless of the order in which the layers were negotiated.
Server implementations SHOULD support SASL proxy authentication so Server implementations SHOULD support SASL proxy authentication so
that an administrator can administer a user's scripts. Proxy that an administrator can administer a user's scripts. Proxy
authentication is when a user authenticates as herself/himself but authentication is when a user authenticates as herself/himself but
requests the server to act (authorize) as another user. requests the server to act (authorize) as another user.
The authorization identity generated by this [SASL] exchange is a The authorization identity generated by this [SASL] exchange is a
"simple username" (in the sense defined in [SASLprep]), and both "simple username" (in the sense defined in [SASLprep]), and both
client and server MUST use the [SASLprep] profile of the [StringPrep] client and server MUST use the [SASLprep] profile of the [StringPrep]
algorithm to prepare these names for transmission or comparison. If algorithm to prepare these names for transmission or comparison. If
skipping to change at page 13, line 26 skipping to change at page 13, line 38
If an AUTHENTICATE command fails with a NO response, the client MAY If an AUTHENTICATE command fails with a NO response, the client MAY
try another authentication mechanism by issuing another AUTHENTICATE try another authentication mechanism by issuing another AUTHENTICATE
command. In other words, the client may request authentication types command. In other words, the client may request authentication types
in decreasing order of preference. in decreasing order of preference.
Note that a failed (NO) response to the AUTHENTICATE command may Note that a failed (NO) response to the AUTHENTICATE command may
contain one of the following response codes: AUTH-TOO-WEAK, ENCRYPT- contain one of the following response codes: AUTH-TOO-WEAK, ENCRYPT-
NEEDED or TRANSITION-NEEDED. See Section 1.3 for detailed NEEDED or TRANSITION-NEEDED. See Section 1.3 for detailed
description of the relevant conditions. description of the relevant conditions.
To ensure interoperability, client and server implementations of this To ensure interoperability, both client and server implementations of
extension MUST implement the [SCRAM] SASL mechanism. the ManageSieve protocol MUST implement the SCRAM-HMAC-SHA-1 [SCRAM]
SASL mechanism, as well as [PLAIN] over [TLS].
Note: use of PLAIN over TLS reflects current use of PLAIN over TLS in
other email related protocols, however a longer term goal is to
migrate email related protocols from using PLAIN over TLS to SCRAM-
HMAC-SHA-1 mechanism.
Implementations MAY advertise the ANONYMOUS SASL mechanism Implementations MAY advertise the ANONYMOUS SASL mechanism
[SASL-ANON]. This indicates that the server supports ANONYMOUS SIEVE [SASL-ANON]. This indicates that the server supports ANONYMOUS SIEVE
script syntax verification. Only the CAPABILITY, PUTSCRIPT and script syntax verification. Only the CAPABILITY, PUTSCRIPT and
LOGOUT commands are available to the anonymous user. All other LOGOUT commands are available to the anonymous user. All other
commands defined in the base ManageSieve protocol MUST give NO commands defined in the base ManageSieve protocol MUST give NO
responses, however ManageSieve extensions MAY allow other commands in responses, however ManageSieve extensions MAY allow other commands in
the ANONYMOUS Sieve script verification mode. Furthermore the the ANONYMOUS Sieve script verification mode. Furthermore the
PUTSCRIPT command MUST NOT persistently store any data. In this mode PUTSCRIPT command MUST NOT persistently store any data. In this mode
a positive response to the PUTSCRIPT command indicates that the given a positive response to the PUTSCRIPT command indicates that the given
script does not have any syntax errors. script does not have any syntax errors.
Examples (Note that long lines are folded for readability and are not Examples (Note that long lines are folded for readability and are not
part of protocol exchange): part of protocol exchange):
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "SASL" "DIGEST-MD5 GSSAPI" S: "SASL" "DIGEST-MD5 GSSAPI"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "STARTTLS" S: "STARTTLS"
S: "VERSION" "1.0"
S: OK S: OK
C: Authenticate "DIGEST-MD5" C: Authenticate "DIGEST-MD5"
S: "cmVhbG09ImVsd29vZC5pbm5vc29mdC5leGFtcGxlLmNvbSIsbm9uY2U9Ik S: "cmVhbG09ImVsd29vZC5pbm5vc29mdC5leGFtcGxlLmNvbSIsbm9uY2U9Ik
9BNk1HOXRFUUdtMmhoIixxb3A9ImF1dGgiLGFsZ29yaXRobT1tZDUtc2Vz 9BNk1HOXRFUUdtMmhoIixxb3A9ImF1dGgiLGFsZ29yaXRobT1tZDUtc2Vz
cyxjaGFyc2V0PXV0Zi04" cyxjaGFyc2V0PXV0Zi04"
C: "Y2hhcnNldD11dGYtOCx1c2VybmFtZT0iY2hyaXMiLHJlYWxtPSJlbHdvb2 C: "Y2hhcnNldD11dGYtOCx1c2VybmFtZT0iY2hyaXMiLHJlYWxtPSJlbHdvb2
QuaW5ub3NvZnQuZXhhbXBsZS5jb20iLG5vbmNlPSJPQTZNRzl0RVFHbTJo QuaW5ub3NvZnQuZXhhbXBsZS5jb20iLG5vbmNlPSJPQTZNRzl0RVFHbTJo
aCIsbmM9MDAwMDAwMDEsY25vbmNlPSJPQTZNSFhoNlZxVHJSayIsZGlnZX aCIsbmM9MDAwMDAwMDEsY25vbmNlPSJPQTZNSFhoNlZxVHJSayIsZGlnZX
N0LXVyaT0ic2lldmUvZWx3b29kLmlubm9zb2Z0LmV4YW1wbGUuY29tIixy N0LXVyaT0ic2lldmUvZWx3b29kLmlubm9zb2Z0LmV4YW1wbGUuY29tIixy
ZXNwb25zZT1kMzg4ZGFkOTBkNGJiZDc2MGExNTIzMjFmMjE0M2FmNyxxb3 ZXNwb25zZT1kMzg4ZGFkOTBkNGJiZDc2MGExNTIzMjFmMjE0M2FmNyxxb3
A9YXV0aA==" A9YXV0aA=="
S: OK (SASL "cnNwYXV0aD1lYTQwZjYwMzM1YzQyN2I1NTI3Yjg0ZGJhYmNkZ S: OK (SASL "cnNwYXV0aD1lYTQwZjYwMzM1YzQyN2I1NTI3Yjg0ZGJhYmNkZ
mZmZA==") mZmZA==")
A slightly different variant of the same authentication exchange: A slightly different variant of the same authentication exchange:
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "SASL" "DIGEST-MD5 GSSAPI" S: "SASL" "DIGEST-MD5 GSSAPI"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "VERSION" "1.0"
S: "STARTTLS" S: "STARTTLS"
S: OK S: OK
C: Authenticate "DIGEST-MD5" C: Authenticate "DIGEST-MD5"
S: {136} S: {136}
S: cmVhbG09ImVsd29vZC5pbm5vc29mdC5leGFtcGxlLmNvbSIsbm9uY2U9Ik S: cmVhbG09ImVsd29vZC5pbm5vc29mdC5leGFtcGxlLmNvbSIsbm9uY2U9Ik
9BNk1HOXRFUUdtMmhoIixxb3A9ImF1dGgiLGFsZ29yaXRobT1tZDUtc2Vz 9BNk1HOXRFUUdtMmhoIixxb3A9ImF1dGgiLGFsZ29yaXRobT1tZDUtc2Vz
cyxjaGFyc2V0PXV0Zi04 cyxjaGFyc2V0PXV0Zi04
C: {300+} C: {300+}
C: Y2hhcnNldD11dGYtOCx1c2VybmFtZT0iY2hyaXMiLHJlYWxtPSJlbHdvb2 C: Y2hhcnNldD11dGYtOCx1c2VybmFtZT0iY2hyaXMiLHJlYWxtPSJlbHdvb2
QuaW5ub3NvZnQuZXhhbXBsZS5jb20iLG5vbmNlPSJPQTZNRzl0RVFHbTJo QuaW5ub3NvZnQuZXhhbXBsZS5jb20iLG5vbmNlPSJPQTZNRzl0RVFHbTJo
skipping to change at page 15, line 6 skipping to change at page 15, line 33
S: {56} S: {56}
S: cnNwYXV0aD1lYTQwZjYwMzM1YzQyN2I1NTI3Yjg0ZGJhYmNkZmZmZA== S: cnNwYXV0aD1lYTQwZjYwMzM1YzQyN2I1NTI3Yjg0ZGJhYmNkZmZmZA==
C: "" C: ""
S: OK S: OK
Another example demonstrating use of SASL PLAIN mechanism under TLS. Another example demonstrating use of SASL PLAIN mechanism under TLS.
This example also demonstrate use of SASL "initial response" (the This example also demonstrate use of SASL "initial response" (the
second parameter to the Authenticate command): second parameter to the Authenticate command):
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "VERSION" "1.0"
S: "SASL" "" S: "SASL" ""
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "STARTTLS" S: "STARTTLS"
S: OK S: OK
C: STARTTLS C: STARTTLS
S: OK S: OK
<TLS negotiation, further commands are under TLS layer> <TLS negotiation, further commands are under TLS layer>
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "VERSION" "1.0"
S: "SASL" "PLAIN" S: "SASL" "PLAIN"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: OK S: OK
C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xu" C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xu"
S: NO S: NO
C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xz" C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xz"
S: NO S: NO
C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xy" C: Authenticate "PLAIN" "QJIrweAPyo6Q1T9xy"
S: BYE "Too many failed authentication attempts" S: BYE "Too many failed authentication attempts"
<Server closes connection> <Server closes connection>
skipping to change at page 15, line 45 skipping to change at page 16, line 24
/yzpAy9p+Y0LanLskOTvMc0MnjgAa4YEr3eJ6 /yzpAy9p+Y0LanLskOTvMc0MnjgAa4YEr3eJ6
C: {0+} C: {0+}
C: C:
S: {44} S: {44}
S: BQQF/wAMAAwAAAAAYRGFAo6W0vIHti8i1UXODgEAEAA= S: BQQF/wAMAAwAAAAAYRGFAo6W0vIHti8i1UXODgEAEAA=
C: {44+} C: {44+}
C: BQQE/wAMAAwAAAAAIsT1iv9UkZApw471iXt6cwEAAAE= C: BQQE/wAMAAwAAAAAIsT1iv9UkZApw471iXt6cwEAAAE=
S: OK S: OK
<Further commands/responses are under SASL security layer> <Further commands/responses are under SASL security layer>
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "VERSION" "1.0"
S: "SASL" "PLAIN DIGEST-MD5 GSSAPI" S: "SASL" "PLAIN DIGEST-MD5 GSSAPI"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "LANGUAGE" "ru" S: "LANGUAGE" "ru"
S: "MAXREDIRECTS" "3" S: "MAXREDIRECTS" "3"
S: ok S: ok
2.1.1. Use of SASL PLAIN mechanism over TLS 2.1.1. Use of SASL PLAIN mechanism over TLS
This section is normative for ManageSieve client implementations that This section is normative for ManageSieve client implementations that
support SASL [PLAIN] over [TLS]. support SASL [PLAIN] over [TLS].
skipping to change at page 17, line 13 skipping to change at page 17, line 32
capabilities after STARTTLS. capabilities after STARTTLS.
Example: Example:
C: StartTls C: StartTls
S: oK S: oK
<TLS negotiation, further commands are under TLS layer> <TLS negotiation, further commands are under TLS layer>
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "SASL" "PLAIN DIGEST-MD5 GSSAPI" S: "SASL" "PLAIN DIGEST-MD5 GSSAPI"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "VERSION" "1.0"
S: "LANGUAGE" "fr" S: "LANGUAGE" "fr"
S: ok S: ok
2.2.1. Server Identity Check 2.2.1. Server Identity Check
During the TLS negotiation, the ManageSieve client MUST check its During the TLS negotiation, the ManageSieve client MUST check its
understanding of the server hostname/IP address against the server's understanding of the server hostname/IP address against the server's
identity as presented in the server Certificate message, in order to identity as presented in the server Certificate message, in order to
prevent man-in-the-middle attacks. In this section, the client's prevent man-in-the-middle attacks. In this section, the client's
understanding of the server's identity is called the "reference understanding of the server's identity is called the "reference
identity". identity".
Checking is performed according to the following rules: Checking is performed according to the following rules:
o If the reference identity is a hostname: o If the reference identity is a hostname:
1. If a subjectAltName extension of the SRVName [X509-SRV], 1. If a subjectAltName extension of the SRVName [X509-SRV],
dNSName [X509] (in that order of preference) type is present dNSName [X509] (in that order of preference) type is present
in the server's certificate, than it SHOULD be used as the in the server's certificate, then it SHOULD be used as the
source of the server's identity. Matching is performed as source of the server's identity. Matching is performed as
described in Section 2.2.1.1, with the exception that no described in Section 2.2.1.1, with the exception that no
wildcard matching is allowed for SRVName type. If the wildcard matching is allowed for SRVName type. If the
certificate contains multiple names (e.g., more than one certificate contains multiple names (e.g., more than one
dNSName field), then a match with any one of the fields is dNSName field), then a match with any one of the fields is
considered acceptable. considered acceptable.
2. The client MAY use other types of subjectAltName for 2. The client MAY use other types of subjectAltName for
performing comparison. performing comparison.
skipping to change at page 20, line 14 skipping to change at page 20, line 32
2.4. CAPABILITY Command 2.4. CAPABILITY Command
The CAPABILITY command requests the server capabilities as described The CAPABILITY command requests the server capabilities as described
earlier in this document. It has no parameters. earlier in this document. It has no parameters.
Example: Example:
C: CAPABILITY C: CAPABILITY
S: "IMPLEMENTATION" "Example1 ManageSieved v001" S: "IMPLEMENTATION" "Example1 ManageSieved v001"
S: "SASL" "PLAIN KERBEROS_V4 GSSAPI" S: "VERSION" "1.0"
S: "SASL" "PLAIN OTP GSSAPI"
S: "SIEVE" "fileinto vacation" S: "SIEVE" "fileinto vacation"
S: "STARTTLS" S: "STARTTLS"
S: OK S: OK
2.5. HAVESPACE Command 2.5. HAVESPACE Command
Arguments: String - name Arguments: String - name
Number - script size Number - script size
The HAVESPACE command is used to query the server for available The HAVESPACE command is used to query the server for available
skipping to change at page 20, line 40 skipping to change at page 21, line 10
Note that the OK response from the HAVESPACE command does not Note that the OK response from the HAVESPACE command does not
constitute a guarantee of success as server disk space conditions constitute a guarantee of success as server disk space conditions
could change between the client issuing the HAVESPACE and the client could change between the client issuing the HAVESPACE and the client
issuing the PUTSCRIPT commands. A QUOTA response code (see issuing the PUTSCRIPT commands. A QUOTA response code (see
Section 1.3) remains a possible (albeit unlikely) response to a Section 1.3) remains a possible (albeit unlikely) response to a
subsequent PUTSCRIPT with the same name and size. subsequent PUTSCRIPT with the same name and size.
Example: Example:
C: HAVESPACE "myscript" 999999 C: HAVESPACE "myscript" 999999
S: NO (QUOTA) "Quota exceeded" S: NO (QUOTA/MAXSIZE) "Quota exceeded"
C: HAVESPACE "foobar" 435 C: HAVESPACE "foobar" 435
S: OK S: OK
2.6. PUTSCRIPT Command 2.6. PUTSCRIPT Command
Arguments: String - Script name Arguments: String - Script name
String - Script content String - Script content
The PUTSCRIPT command is used by the client to submit a Sieve script The PUTSCRIPT command is used by the client to submit a Sieve script
skipping to change at page 21, line 18 skipping to change at page 21, line 36
This command places the script on the server. It does not affect This command places the script on the server. It does not affect
whether the script is processed on incoming mail, unless it replaces whether the script is processed on incoming mail, unless it replaces
the script which is already active. The SETACTIVE command is used to the script which is already active. The SETACTIVE command is used to
mark a script as active. mark a script as active.
When submitting large scripts clients SHOULD use the HAVESPACE When submitting large scripts clients SHOULD use the HAVESPACE
command beforehand to query if the server is willing to accept a command beforehand to query if the server is willing to accept a
script of that size. script of that size.
The server MUST check the submitted script for syntactic validity, The server MUST check the submitted script for validity, which
which includes checking that all Sieve extensions mentioned in Sieve includes checking that the script complies with the Sieve grammar
script "require" statement(s) are supported by the Sieve interpreter. [SIEVE], that all Sieve extensions mentioned in script's "require"
(Note that if the Sieve interpreter supports the Sieve "ihave" statement(s) are supported by the Sieve interpreter. (Note that if
extension [I-HAVE], any unrecognized/unsupported extension mentioned the Sieve interpreter supports the Sieve "ihave" extension [I-HAVE],
in the "ihave" test MUST NOT cause the syntactic validation failure.) any unrecognized/unsupported extension mentioned in the "ihave" test
If the script fails this test the server MUST reply with a NO MUST NOT cause the validation failure.) Other checks such as
validating the supplied command arguments for each command MAY be
performed. Essentially, the performed validation SHOULD be the same
as performed when compiling the script for execution.
Implementations that use a binary representation to store compiled
scripts can extend the validation to a full compilation, in order to
avoid validating uploaded scripts multiple times.
If the script fails the validation the server MUST reply with a NO
response. Any script that fails the validity test MUST NOT be stored response. Any script that fails the validity test MUST NOT be stored
on the server. The message given with a NO response MUST be human on the server. The message given with a NO response MUST be human
readable and SHOULD contain a specific error message giving the line readable and SHOULD contain a specific error message giving the line
number of the first error. Implementors should strive to produce number of the first error. Implementors should strive to produce
helpful error messages similar to those given by programming language helpful error messages similar to those given by programming language
compilers. Client implementations should note that this may be a compilers. Client implementations should note that this may be a
multiline literal string with more than one error message separated multiline literal string with more than one error message separated
by CRLFs. The human readable message is in the language returned in by CRLFs. The human readable message is in the language returned in
the latest LANGUAGE capability (or in "i-default", see Section 1.7), the latest LANGUAGE capability (or in "i-default", see Section 1.7),
encoded in UTF-8 [UTF-8]. encoded in UTF-8 [UTF-8].
An OK response MAY contain the WARNINGS response code. In such case An OK response MAY contain the WARNINGS response code. In such case
the message that follows the OK response SHOULD contain a specific the message that follows the OK response SHOULD contain a specific
warning message (or messages) giving the line number(s) in the script warning message (or messages) giving the line number(s) in the script
that might contain errors not indended by the script writer. A that might contain errors not intended by the script writer. A
client seeing such response code SHOULD present the message to the client seeing such response code SHOULD present the message to the
user. user.
Examples: Examples:
C: Putscript "foo" {31+} C: Putscript "foo" {31+}
C: #comment C: #comment
C: InvalidSieveCommand C: InvalidSieveCommand
C: C:
S: NO "line 2: Syntax error" S: NO "line 2: Syntax error"
skipping to change at page 24, line 44 skipping to change at page 25, line 13
disable the script first. disable the script first.
Example: Example:
C: Deletescript "foo" C: Deletescript "foo"
S: Ok S: Ok
C: Deletescript "baz" C: Deletescript "baz"
S: No (ACTIVE) "You may not delete an active script" S: No (ACTIVE) "You may not delete an active script"
2.11. Recommended extensions 2.11. RENAMESCRIPT Command
This Section defines several extensions support for which is
RECOMMENDED.
The RENAME extension (advertised as the "RENAME" capability with no
parameters) defines a new RENAMESCRIPT command.
The CHECKSCRIPT extension (advertised as the "CHECKSCRIPT" capability
with no parameters) defines a new CHECKSCRIPT command.
The NOOP extension (advertised as the "NOOP" capability with no
parameters) defines a new NOOP command.
The UNAUTHENTICATE extension (advertised as the "UNAUTHENTICATE"
capability with no parameters) defines a new UNAUTHENTICATE command,
which allows a client to return the server to non-authenticated
state.
2.11.1. RENAMESCRIPT Command
Arguments: String - Old Script name Arguments: String - Old Script name
String - New Script name String - New Script name
This command is used to rename a user's Sieve script. Servers MUST This command is used to rename a user's Sieve script. Servers MUST
reply with a NO response if the old script does not exist (in which reply with a NO response if the old script does not exist (in which
case the NONEXISTENT response code SHOULD be included), or a script case the NONEXISTENT response code SHOULD be included), or a script
with the new name already exists (in which case the ALREADYEXISTS with the new name already exists (in which case the ALREADYEXISTS
response code SHOULD be included). Renaming the active script is response code SHOULD be included). Renaming the active script is
allowed, the renamed script remains active. allowed, the renamed script remains active.
skipping to change at page 26, line 4 skipping to change at page 25, line 48
whether to abort the operation, to replace the script (by issuing whether to abort the operation, to replace the script (by issuing
the DELETESCRIPT <newname> after that) or to chose a different the DELETESCRIPT <newname> after that) or to chose a different
name. name.
2. Download the old script with GETSCRIPT <oldname>. 2. Download the old script with GETSCRIPT <oldname>.
3. Upload the old script with the new name: PUTSCRIPT <newname>. 3. Upload the old script with the new name: PUTSCRIPT <newname>.
4. If the old script was active (as reported by LISTSCRIPTS in step 4. If the old script was active (as reported by LISTSCRIPTS in step
1), then make the new script active: SETACTIVE <newname> 1), then make the new script active: SETACTIVE <newname>
5. Delete the old script: DELETESCRIPT <oldname> 5. Delete the old script: DELETESCRIPT <oldname>
Note that these steps don't describe how to handle various other Note that these steps don't describe how to handle various other
error conditions (for example NO response containing QUOTA response error conditions (for example NO response containing QUOTA response
code in step 3). Error handling is left as an excercise for the code in step 3). Error handling is left as an excercise for the
reader. reader.
2.11.2. CHECKSCRIPT Command 2.12. CHECKSCRIPT Command
Arguments: String - Script content Arguments: String - Script content
The CHECKSCRIPT command is used by the client to verify Sieve script The CHECKSCRIPT command is used by the client to verify Sieve script
validity without storing the script on the server. validity without storing the script on the server.
The server MUST check the submitted script for syntactic validity, The server MUST check the submitted script for syntactic validity,
which includes checking that all Sieve extensions mentioned in Sieve which includes checking that all Sieve extensions mentioned in Sieve
script "require" statement(s) are supported by the Sieve interpreter. script "require" statement(s) are supported by the Sieve interpreter.
(Note that if the Sieve interpreter supports the Sieve "ihave" (Note that if the Sieve interpreter supports the Sieve "ihave"
skipping to change at page 26, line 49 skipping to change at page 26, line 45
C: InvalidSieveCommand C: InvalidSieveCommand
C: C:
S: NO "line 2: Syntax error" S: NO "line 2: Syntax error"
A ManageSieve server supporting this command MUST NOT check if the A ManageSieve server supporting this command MUST NOT check if the
script will put the current user over its quota limit. script will put the current user over its quota limit.
An OK response MAY contain the WARNINGS response code. In such case An OK response MAY contain the WARNINGS response code. In such case
the message that follows the OK response SHOULD contain a specific the message that follows the OK response SHOULD contain a specific
warning message (or messages) giving the line number(s) in the script warning message (or messages) giving the line number(s) in the script
that might contain errors not indended by the script writer. A that might contain errors not intended by the script writer. A
client seeing such response code SHOULD present the message to the client seeing such response code SHOULD present the message to the
user. user.
The CHECKSCRIPT command is available in the ANONYMOUS Sieve script The CHECKSCRIPT command is available in the ANONYMOUS Sieve script
verification mode. verification mode.
2.11.3. NOOP Command 2.13. NOOP Command
Arguments: String - tag to echo back (optional) Arguments: String - tag to echo back (optional)
The NOOP command does nothing, beyond returning a response to the The NOOP command does nothing, beyond returning a response to the
client. It may be used by clients for protocol re-synchronisation or client. It may be used by clients for protocol re-synchronisation or
to reset any inactivity auto-logout timer on the server. to reset any inactivity auto-logout timer on the server.
The NOOP command is available in the ANONYMOUS Sieve script The NOOP command is available in the ANONYMOUS Sieve script
verification mode. verification mode.
The response to the NOOP command is always OK, followed by the TAG The response to the NOOP command is always OK, followed by the TAG
response code together with the supplied string; if no string was response code together with the supplied string; if no string was
supplied in the NOOP command, the TAG response code MUST NOT be supplied in the NOOP command, the TAG response code MUST NOT be
included. included.
Older servers may not understand the NOOP client and robust clients
SHOULD be prepared to receive a NO response.
Examples: Examples:
C: NOOP C: NOOP
S: OK "NOOP completed" S: OK "NOOP completed"
C: NOOP "STARTTLS-SYNC-42" C: NOOP "STARTTLS-SYNC-42"
S: OK (TAG {16} S: OK (TAG {16}
S: STARTTLS-SYNC-42) "Done" S: STARTTLS-SYNC-42) "Done"
2.11.4. UNAUTHENTICATE Command 2.14. Recommended extensions
The UNAUTHENTICATE extension (advertised as the "UNAUTHENTICATE"
capability with no parameters) defines a new UNAUTHENTICATE command,
which allows a client to return the server to non-authenticated
state. Support for this extension is RECOMMENDED.
2.14.1. UNAUTHENTICATE Command
The UNAUTHENTICATE command returns the server to the non- The UNAUTHENTICATE command returns the server to the non-
authenticated state. It doesn't affect any previously established authenticated state. It doesn't affect any previously established
TLS [TLS] or SASL (Section 2.1) security layer. TLS [TLS] or SASL (Section 2.1) security layer.
The UNAUTHENTICATE command is only valid in authenticated state. If The UNAUTHENTICATE command is only valid in authenticated state. If
issued in a wrong state, the server MUST reject it with a NO issued in a wrong state, the server MUST reject it with a NO
response. response.
The UNAUTHENTICATE command has no parameters. The UNAUTHENTICATE command has no parameters.
skipping to change at page 28, line 20 skipping to change at page 28, line 20
URI scheme syntax: URI scheme syntax:
Described using ABNF [ABNF] and ABNF entities from [URI-GEN]. Described using ABNF [ABNF] and ABNF entities from [URI-GEN].
sieveurl = sieveurl-server / sieveurl-list-scripts / sieveurl = sieveurl-server / sieveurl-list-scripts /
sieveurl-script sieveurl-script
sieveurl-server = "sieve://" authority sieveurl-server = "sieve://" authority
sieveurl-list-scripts = "sieve://" [ authority ] ["/"] sieveurl-list-scripts = "sieve://" authority ["/"]
sieveurl-script = "sieve://" [ authority ] "/" sieveurl-script = "sieve://" authority "/"
[owner "/"] scriptname [owner "/"] scriptname
sub-delims-sh = "!" / "$" / "'" / "(" / ")" / sub-delims-sh = "!" / "$" / "'" / "(" / ")" /
"*" / "+" / "," "*" / "+" / ","
;; Same as [URI-GEN] sub-delims, ;; Same as [URI-GEN] sub-delims,
;; but without ";", "&" and "=". ;; but without ";", "&" and "=".
uchar = unreserved / pct-encoded / sub-delims-sh uchar = unreserved / pct-encoded / sub-delims-sh
;; Same as [URI-GEN] ;; Same as [URI-GEN]
;; 'unreserved / pct-encoded / sub-delims', ;; 'unreserved / pct-encoded / sub-delims',
;; but without ";", "&" and "=". ;; but without ";", "&" and "=".
ochar = uchar / ":" / "@" ochar = uchar / ":" / "@"
;; Same as [URI-GEN] 'pchar' ;; Same as [URI-GEN] 'pchar'
;; but without ";", "&" and "=". ;; but without ";", "&" and "=".
owner = 1*ochar owner = *ochar
;; %-encoded version of [IMAP4] authorization ;; %-encoded version of [IMAP4] authorization
;; identity (owner) or "userid". ;; identity (owner) or "userid".
;;
;; Empty owner is used to reference
;; global scripts.
;;
;; Note that ASCII characters such as " ", ";", ;; Note that ASCII characters such as " ", ";",
;; "&", "=", "/" and "?" MUST be %-encoded. ;; "&", "=", "/" and "?" MUST be %-encoded.
scriptname = 1*ochar scriptname = 1*ochar
;; %-encoded version of UTF-8 representation ;; %-encoded version of UTF-8 representation
;; of the script name. ;; of the script name.
;; Note that ASCII characters such as " ", ";", ;; Note that ASCII characters such as " ", ";",
;; "&", "=", "/" and "?" MUST be %-encoded. ;; "&", "=", "/" and "?" MUST be %-encoded.
URI scheme semantics: URI scheme semantics:
skipping to change at page 32, line 43 skipping to change at page 32, line 47
;; A 32-bit unsigned number. ;; A 32-bit unsigned number.
;; (0 <= n < 4,294,967,296) ;; (0 <= n < 4,294,967,296)
number-str = string number-str = string
;; <number> encoded as a <string>. ;; <number> encoded as a <string>.
quoted = DQUOTE *1024QUOTED-CHAR DQUOTE quoted = DQUOTE *1024QUOTED-CHAR DQUOTE
;; limited to 1024 octets between the <">s ;; limited to 1024 octets between the <">s
resp-code = "AUTH-TOO-WEAK" / "ENCRYPT-NEEDED" / resp-code = "AUTH-TOO-WEAK" / "ENCRYPT-NEEDED" /
"QUOTA" / resp-code-sasl / "QUOTA" ["/" ("MAXSCRIPTS" / "MAXSIZE")] /
resp-code-sasl /
resp-code-referral / resp-code-referral /
"TRANSITION-NEEDED" / "TRYLATER" / "TRANSITION-NEEDED" / "TRYLATER" /
"ACTIVE" / "NONEXISTENT" / "ACTIVE" / "NONEXISTENT" /
"ALREADYEXISTS" / "WARNINGS" / "ALREADYEXISTS" / "WARNINGS" /
"TAG" SP string / "TAG" SP string /
resp-code-ext resp-code-ext
resp-code-referral = "REFERRAL" SP sieveurl resp-code-referral = "REFERRAL" SP sieveurl
resp-code-sasl = "SASL" SP string resp-code-sasl = "SASL" SP string
resp-code-name = iana-token resp-code-name = iana-token
;; The response code name is hierarchical, ;; The response code name is hierarchical,
;; separated by '/'. ;; separated by '/'.
;; The response code name MUST NOT start ;; The response code name MUST NOT start
;; with '/'. ;; with '/'.
resp-code-ext = resp-code-name [SP extension-data] resp-code-ext = resp-code-name [SP extension-data]
;; unknown response codes MUST be tolerated ;; unknown response codes MUST be tolerated
skipping to change at page 34, line 4 skipping to change at page 34, line 10
capability-name = string capability-name = string
;; Note that literal-s2c is allowed. ;; Note that literal-s2c is allowed.
initial-capabilities = DQUOTE "IMPLEMENTATION" DQUOTE SP string / initial-capabilities = DQUOTE "IMPLEMENTATION" DQUOTE SP string /
DQUOTE "SASL" DQUOTE SP sasl-mechs / DQUOTE "SASL" DQUOTE SP sasl-mechs /
DQUOTE "SIEVE" DQUOTE SP sieve-extensions / DQUOTE "SIEVE" DQUOTE SP sieve-extensions /
DQUOTE "MAXREDIRECTS" DQUOTE SP number-str / DQUOTE "MAXREDIRECTS" DQUOTE SP number-str /
DQUOTE "NOTIFY" DQUOTE SP notify-mechs / DQUOTE "NOTIFY" DQUOTE SP notify-mechs /
DQUOTE "STARTTLS" DQUOTE / DQUOTE "STARTTLS" DQUOTE /
DQUOTE "LANGUAGE" DQUOTE SP language / DQUOTE "LANGUAGE" DQUOTE SP language /
DQUOTE "RENAME" DQUOTE / DQUOTE "VERSION" DQUOTE SP version /
DQUOTE "CHECKSCRIPT" DQUOTE /
DQUOTE "NOOP" DQUOTE /
DQUOTE "OWNER" DQUOTE SP string DQUOTE "OWNER" DQUOTE SP string
;; Each capability conforms to ;; Each capability conforms to
;; the syntax for single-capability. ;; the syntax for single-capability.
;; Also note that the capability name ;; Also note that the capability name
;; can be returned as either literal-s2c ;; can be returned as either literal-s2c
;; or quoted, even though only "quoted" ;; or quoted, even though only "quoted"
;; string is shown above. ;; string is shown above.
version = DQUOTE "1.0" DQUOTE
sasl-mechs = string sasl-mechs = string
; space separated list of SASL mechanisms, ; space separated list of SASL mechanisms,
; each SASL mechanism name complies with rules ; each SASL mechanism name complies with rules
; specified in [SASL]. ; specified in [SASL].
; Can be empty. ; Can be empty.
sieve-extensions = string sieve-extensions = string
; space separated list of supported SIEVE extensions, ; space separated list of supported SIEVE extensions,
; can be empty. ; can be empty.
skipping to change at page 36, line 39 skipping to change at page 36, line 44
6. IANA Considerations 6. IANA Considerations
IANA is requested to reserve TCP port number 2000 for use with the IANA is requested to reserve TCP port number 2000 for use with the
Manage Sieve protocol described in this document. Manage Sieve protocol described in this document.
IANA is requested to register the "sieve" URI scheme defined in IANA is requested to register the "sieve" URI scheme defined in
Section 3 of this document. Section 3 of this document.
IANA is requested to create a new registry for Manage Sieve IANA is requested to create a new registry for Manage Sieve
capabilities. The registration template for Manage Sieve capabilities. The registration template for ManageSieve capabilities
capabilities is specified in Section 6.1. Manage Sieve protocol is specified in Section 6.1. ManageSieve protocol capabilities MUST
capabilities MUST be specified in a standards track or IESG approved be specified in a standards track or IESG approved experimental RFC.
experimental RFC.
IANA is requested to create a new registry for Manage Sieve response IANA is requested to create a new registry for Manage Sieve response
codes. The registration template for Manage Sieve response codes is codes. The registration template for Manage Sieve response codes is
specified in Section 6.3. Manage Sieve protocol response codes MUST specified in Section 6.3. Manage Sieve protocol response codes MUST
be specified in a standards track or IESG approved experimental RFC. be specified in a standards track or IESG approved experimental RFC.
6.1. Manage Sieve Capability Registration Template 6.1. Manage Sieve Capability Registration Template
To: iana@iana.org To: iana@iana.org
Subject: Manage Sieve Capability Registration Subject: Manage Sieve Capability Registration
skipping to change at page 38, line 47 skipping to change at page 38, line 47
currently logged in user ("authorization identity" according to currently logged in user ("authorization identity" according to
RFC 4422). RFC 4422).
Relevant publications: this RFC, Section 1.7. Relevant publications: this RFC, Section 1.7.
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Capability name: RENAME Capability name: VERSION
Description: This capability is returned if the server supports
the RENAMESCRIPT command.
Relevant publications: this RFC, Section 2.11.1.
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG.
Capability name: CHECKSCRIPT
Description: This capability is returned if the server supports
the CHECKSCRIPT command.
Relevant publications: this RFC, Section 2.11.1.
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG.
Capability name: NOOP
Description: This capability is returned if the server supports Description: This capability is returned if the server is
the NOOP command. compliant with RFCXXXX, i.e. that it supports RENAMESCRIPT,
CHECKSCRIPT and NOOP commands.
Relevant publications: this RFC, Section 2.11.3. Relevant publications: this RFC, Section 2.11.
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
6.3. Manage Sieve Response Code Registration Template 6.3. Manage Sieve Response Code Registration Template
To: iana@iana.org To: iana@iana.org
Subject: Manage Sieve Response Code Registration Subject: Manage Sieve Response Code Registration
skipping to change at page 41, line 18 skipping to change at page 40, line 42
that the user exceeded its quota, but the server supports soft that the user exceeded its quota, but the server supports soft
quotas. quotas.
Published Specification(s): [RFCXXXX] Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Response Code: QUOTA/MAXSCRIPTS
Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): NONE
Purpose: If this response code is returned in the NO/BYE response,
it means that the command would have placed the user above the
site-defined limit on the number of Sieve scripts. If this
response code is returned in the OK response, it can mean that the
user is near its quota or that the user exceeded its quota, but
the server supports soft quotas. This response code is a more
specific version of the QUOTA response code.
Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG.
Response Code: QUOTA/MAXSIZE
Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): NONE
Purpose: If this response code is returned in the NO/BYE response,
it means that the command would have placed the user above the
site-defined maximum script size. If this response code is
returned in the OK response, it can mean that the user is near its
quota or that the user exceeded its quota, but the server supports
soft quotas. This response code is a more specific version of the
QUOTA response code.
Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG.
Response Code: REFERRAL Response Code: REFERRAL
Arguments (use ABNF to specify syntax, or the word NONE if none Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): <sieveurl> can be specified): <sieveurl>
Purpose: This response code may be returned with a BYE result from Purpose: This response code may be returned with a BYE result from
any command, and includes a mandatory parameter that indicates any command, and includes a mandatory parameter that indicates
what server to access to manage this user's sieve scripts. The what server to access to manage this user's sieve scripts. The
server will be specified by a Sieve URL (see Section 3). The server will be specified by a Sieve URL (see Section 3). The
scriptname portion of the URL MUST NOT be specified. The client scriptname portion of the URL MUST NOT be specified. The client
skipping to change at page 43, line 17 skipping to change at page 43, line 33
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Response Code: NONEXISTENT Response Code: NONEXISTENT
Arguments (use ABNF to specify syntax, or the word NONE if none Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): NONE can be specified): NONE
Purpose: A command failed because the references script name Purpose: A command failed because the referenced script name
doesn't exist. This response code only makes sense when returned doesn't exist. This response code only makes sense when returned
in a NO/BYE response. in a NO/BYE response.
Published Specification(s): [RFCXXXX] Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Response Code: ALREADYEXISTS Response Code: ALREADYEXISTS
Arguments (use ABNF to specify syntax, or the word NONE if none Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): NONE can be specified): NONE
Purpose: A command failed because the references script name Purpose: A command failed because the referenced script name
already exists. This response code only makes sense when returned already exists. This response code only makes sense when returned
in a NO/BYE response. in a NO/BYE response.
Published Specification(s): [RFCXXXX] Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Response Code: WARNINGS Response Code: WARNINGS
Arguments (use ABNF to specify syntax, or the word NONE if none Arguments (use ABNF to specify syntax, or the word NONE if none
can be specified): NONE can be specified): NONE
Purpose: This response code MAY be returned by the server in the Purpose: This response code MAY be returned by the server in the
OK response (but it might be returned with the NO/BYE response as OK response (but it might be returned with the NO/BYE response as
well) and signals the client that even though the script is well) and signals the client that even though the script is
syntactically valid, it might contain errors not indended by the syntactically valid, it might contain errors not intended by the
script writer. script writer.
Published Specification(s): [RFCXXXX] Published Specification(s): [RFCXXXX]
Person & email address to contact for further information: Alexey Person & email address to contact for further information: Alexey
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
Response Code: TAG Response Code: TAG
skipping to change at page 44, line 35 skipping to change at page 45, line 4
Melnikov <alexey.melnikov@isode.com> Melnikov <alexey.melnikov@isode.com>
Author/Change controller: IESG. Author/Change controller: IESG.
7. Acknowledgements 7. 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 and Robert Burrell Donkin for Palauzov, Dave Cridland, Aaron Stone, Robert Burrell Donkin and
help with this document. Special thank you to Phil Pennock for Patrick Ben Koetter for help with this document. Special thank you
providing text for the NOOP command, as well as finding various bugs to Phil Pennock for providing text for the NOOP command, as well as
in the document. finding various bugs in the document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 5234, January 2008. Specifications: ABNF", RFC 5234, January 2008.
[ACAP] Newman, C. and J. Myers, "ACAP -- Application [ACAP] Newman, C. and J. Myers, "ACAP -- Application
Configuration Access Protocol", RFC 2244, November 1997. Configuration Access Protocol", RFC 2244, November 1997.
skipping to change at page 46, line 8 skipping to change at page 46, line 24
[SASL-ANON] [SASL-ANON]
Zeilenga, K., "Anonymous Simple Authentication and Zeilenga, K., "Anonymous Simple Authentication and
Security Layer (SASL) Mechanism", RFC 4505, June 2006. Security Layer (SASL) Mechanism", RFC 4505, June 2006.
[SASLprep] [SASLprep]
Zeilenga, K., "SASLprep: Stringprep Profile for User Names Zeilenga, K., "SASLprep: Stringprep Profile for User Names
and Passwords", RFC 4013, February 2005. and Passwords", RFC 4013, February 2005.
[SCRAM] Menon-Sen, A., Ed. and C. Newman, "Salted Challenge [SCRAM] Menon-Sen, A., Ed. and C. Newman, "Salted Challenge
Response Authentication Mechanism (SCRAM)", Response Authentication Mechanism (SCRAM)",
draft-newman-auth-scram-05.txt (work in progress), draft-newman-auth-scram-07.txt (work in progress),
December 2007. November 2008.
[SIEVE] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email [SIEVE] Guenther, P., Ed. and T. Showalter, Ed., "Sieve: An Email
Filtering Language", RFC 5228, January 2008. Filtering Language", RFC 5228, January 2008.
[StringPrep] [StringPrep]
Hoffman, P. and M. Blanchet, "Preparation of Hoffman, P. and M. Blanchet, "Preparation of
Internationalized Strings ("stringprep")", RFC 3454, Internationalized Strings ("stringprep")", RFC 3454,
December 2002. December 2002.
[TLS] Dierks, T. and E. Rescorla, "The Transport Layer Security [TLS] Dierks, T. and E. Rescorla, "The Transport Layer Security
skipping to change at page 46, line 51 skipping to change at page 47, line 19
[DIGEST-MD5] [DIGEST-MD5]
Leach, P. and C. Newman, "Using Digest Authentication as a Leach, P. and C. Newman, "Using Digest Authentication as a
SASL Mechanism", RFC 2831, May 2000. SASL Mechanism", RFC 2831, May 2000.
[I-HAVE] Freed, N., "Sieve Email Filtering: Ihave Extension", [I-HAVE] Freed, N., "Sieve Email Filtering: Ihave Extension",
draft-freed-sieve-ihave-03.txt (work in progress), draft-freed-sieve-ihave-03.txt (work in progress),
October 2008. October 2008.
[IANA-GUIDELINES] [IANA-GUIDELINES]
Narten, T. and H. Alvestrand, "Guidelines for Writing an Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
October 1998. May 2008.
[IMAP4rev1] [IMAP4rev1]
Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003. 4rev1", RFC 3501, March 2003.
[LDAP] Zeilenga, K., "Lightweight Directory Access Protocol [LDAP] Zeilenga, K., "Lightweight Directory Access Protocol
(LDAP): Technical Specification Road Map", RFC 4510, (LDAP): Technical Specification Road Map", RFC 4510,
June 2006. June 2006.
[PLAIN] Zeilenga, K., "The PLAIN Simple Authentication and [PLAIN] Zeilenga, K., "The PLAIN Simple Authentication and
 End of changes. 71 change blocks. 
135 lines changed or deleted 174 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/