RFC 2087 (rfc2087) - Page 2 of 5


IMAP4 QUOTA extension



Alternative Format: Original Text Document



RFC 2087                         QUOTA                      January 1997


3.   Introduction and Overview

   The QUOTA extension is present in any IMAP4 implementation which
   returns "QUOTA" as one of the supported capabilities to the
   CAPABILITY command.

   An IMAP4 server which supports the QUOTA capability may support
   limits on any number of resources.  Each resource has an atom name
   and an implementation-defined interpretation which evaluates to an
   integer.  Examples of such resources are:

      Name       Interpretation

      STORAGE    Sum of messages' RFC 822.SIZE, in units of 1024 octets
      MESSAGE    Number of messages


   Each mailbox has zero or more implementation-defined named "quota
   roots".  Each quota root has zero or more resource limits.  All
   mailboxes that share the same named quota root share the resource
   limits of the quota root.

   Quota root names do not necessarily have to match the names of
   existing mailboxes.

4.   Commands

4.1. SETQUOTA Command

   Arguments:  quota root
               list of resource limits

   Data:       untagged responses: QUOTA

   Result:     OK - setquota completed
               NO - setquota error: can't set that data
               BAD - command unknown or arguments invalid

   The SETQUOTA command takes the name of a mailbox quota root and a
   list of resource limits. The resource limits for the named quota root
   are changed to be the specified limits.  Any previous resource limits
   for the named quota root are discarded.

   If the named quota root did not previously exist, an implementation
   may optionally create it and change the quota roots for any number of
   existing mailboxes in an implementation-defined manner.





Myers                       Standards Track