                                                                ManageSieve Registries

   Created
           2009-01-29

   Last Updated
           2009-01-29

   This registry is also available in XML and plain text formats.

   Registries included below

     * ManageSieve Capabilities
     * ManageSieve Response Codes

ManageSieve Capabilities

   Reference
           [RFC-ietf-sieve-managesieve-09]

   Registration Procedures
           Standards Track or IESG-Approved Experimental RFC

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

ManageSieve Response Codes

   Reference
           [RFC-ietf-sieve-managesieve-09]

   Registration Procedures
           Standards Track or IESG-Approved Experimental RFC

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