Browse Prior Art Database

IMAP4 QUOTA extension (RFC2087)

IP.com Disclosure Number: IPCOM000002639D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2019-Feb-16
Document File: 5 page(s) / 6K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Myers: AUTHOR

Related Documents

10.17487/RFC2087: DOI

Abstract

The QUOTA extension of the Internet Message Access Protocol [IMAP4] permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Network Working Group J. Myers Request for Comments: 2087 Carnegie Mellon Category: Standards Track January 1997

IMAP4 QUOTA extension

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

1. Abstract

The QUOTA extension of the Internet Message Access Protocol [IMAP4] permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol.

Table of Contents

1. Abstract........................................... 1 2. Conventions Used in this Document.................. 1 3. Introduction and Overview.......................... 2 4. Commands........................................... 2 4.1. SETQUOTA Command................................... 2 4.2. GETQUOTA Command................................... 2 4.3. GETQUOTAROOT Command............................... 3 5. Responses.......................................... 3 5.1. QUOTA Response..................................... 3 5.2. QUOTAROOT Response................................. 4 6. Formal syntax...................................... 4 7. References......................................... 5 8. Security Considerations............................ 5 9. Author’s Address................................... 5

2. Conventions Used in this Document

In examples, "C:" and "S:" indicate lines sent by the client and server respectively.

Myers Standards Track [Page 1]

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’ RFC822.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...

Processing...
Loading...