ManageSieve Registries

Created
2009-01-29
Last Updated
2015-05-27
Available Formats

XML

HTML

TXT

Registries Included Below

ManageSieve Capabilities

Registration Procedure(s)
Standards Track or IESG-Approved Experimental RFC
Reference
[RFC 5804]
Available Formats

CSV
Capability name Description Relevant publications Person and email address to contact for further information Author/Change controller
IMPLEMENTATION Its value contains name of server implementation and its version. [RFC 5804], Section 1.8. Alexey Melnikov (alexey.melnikov@isode.com) IESG
SASL Its value contains a space separated list of SASL mechanisms supported by server. [RFC 5804], Section 1.8 and Section 2.1. Alexey Melnikov (alexey.melnikov@isode.com) IESG
SIEVE Its value contains a space separated list of supported SIEVE extensions [RFC 5804], Section 1.8. Also [RFC 5228]. Alexey Melnikov (alexey.melnikov@isode.com) IESG
STARTTLS This capability is returned if server supports TLS (STARTTLS command). [RFC 5804], Section 1.8 and Section 2.2. Alexey Melnikov (alexey.melnikov@isode.com) IESG
NOTIFY This capability is returned if server supports 'enotify' [RFC 5435] Sieve extension. [RFC 5804], Section 1.8. Alexey Melnikov (alexey.melnikov@isode.com) IESG
MAXREDIRECTS This capability returns the limit on the number of Sieve "redirect" actions a script can perform during a single evaluation. The value is a non-negative number represented as a ManageSieve string. [RFC 5804], Section 1.8. Alexey Melnikov (alexey.melnikov@isode.com) IESG
LANGUAGE The language (<Language-Tag> from [RFC 4646]) currently used for human readable error messages. [RFC 5804], Section 1.8. Alexey Melnikov (alexey.melnikov@isode.com) IESG
OWNER Its value contains UTF-8 encoded name of the currently logged in user ("authorization identity" according to [RFC 4422]). [RFC 5804], Section 1.8. Alexey Melnikov (alexey.melnikov@isode.com) IESG
VERSION This capability is returned if the server is compliant with [RFC 5804], i.e. that it supports RENAMESCRIPT, CHECKSCRIPT and NOOP commands. [RFC 5804], Section 2.11. Alexey Melnikov (alexey.melnikov@isode.com) IESG
EXTLISTS This capability is returned if the server supports the "extlists" [RFC 6134] Sieve extension. [RFC 6134], Section 2.8. Sieve mailing list (sieve@ietf.org) IESG

ManageSieve Response Codes

Registration Procedure(s)
Standards Track or IESG-Approved Experimental RFC
Reference
[RFC 5804]
Available Formats

CSV
Response code Arguments (use ABNF to specify syntax, or the word NONE if none can be specified) Purpose Published specification(s) Person and email address to contact for further information Author/Change controller
AUTH-TOO-WEAK NONE This response code is returned in the NO response from an AUTHENTICATE command. It indicates that site security policy forbids the use of the requested mechanism for the specified authentication identity. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
ENCRYPT-NEEDED NONE This response code is returned in the NO response from an AUTHENTICATE command. It indicates that site security policy requires the use of a strong encryption mechanism for the specified authentication identity and mechanism. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
QUOTA NONE 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 quota constraints. 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. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
QUOTA/MAXSCRIPTS NONE 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. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
QUOTA/MAXSIZE NONE 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. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
REFERRAL <sieveurl> This response code may be returned with a BYE result from any command, and includes a mandatory parameter that indicates what server to access to manage this user's sieve scripts. The server will be specified by a Sieve URL (see Section 3). The scriptname portion of the URL MUST NOT be specified. The client should authenticate to the specified server and use it for all further commands in the current session. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
SASL <string> This response code can occur in the OK response to a successful AUTHENTICATE command and includes the optional final server response data from the server as specified by [RFC 4422]. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
TRANSITION-NEEDED NONE This response code occurs in a NO response of an AUTHENTICATE command. It indicates that the user name is valid, but the entry in the authentication database needs to be updated in order to permit authentication with the specified mechanism. This is typically done by establishing a secure channel using TLS, followed by authenticating once using the PLAIN [RFC 4616] authentication mechanism. The selected mechanism SHOULD then work for authentications in subsequent sessions. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
TRYLATER NONE A command failed due to a temporary server failure. The client MAY continue using local information and try the command later. This response code only make sense when returned in a NO/ BYE response. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
ACTIVE NONE A command failed because it is not allowed on the active script. For example DELETESCRIPT on the active script. This response code only makes sense when returned in a NO/BYE response. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
NONEXISTENT NONE A command failed because the referenced script name doesn't exist. This response code only makes sense when returned in a NO/BYE response. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
ALREADYEXISTS NONE A command failed because the referenced script name already exists. This response code only makes sense when returned in a NO/BYE response. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
WARNINGS NONE 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 signals the client that even though the script is syntactically valid, it might contain errors not intended by the script writer. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG
TAG string This response code name is followed by a string specified in the command that caused this response. It is typically used for client state synchronization. [RFC 5804] Alexey Melnikov (alexey.melnikov@isode.com) IESG