1 / 7

IMAP QUOTA extension

IMAP QUOTA extension. Dave Cridland Alexey Melnikov November 21, 2002. draft-cridland-imap-quota-00. Description. Quotas can be used to restrict clients for administrative reasons, but the QUOTA extension can also be used to indicate system limits and current usage levels to clients.

faunia
Télécharger la présentation

IMAP QUOTA extension

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMAP QUOTAextension Dave Cridland Alexey MelnikovNovember 21, 2002 draft-cridland-imap-quota-00

  2. Description • Quotas can be used to restrict clients for administrative reasons, but the QUOTA extension can also be used to indicate system limits and current usage levels to clients. • Based on RFC 2087 by John G. Myers and tries to be backward compatible where possible.

  3. Changes from RFC 2087 • Defines a registry of resources (existing STORAGE, MESSAGES and a new one: MAILBOXES). • Defines a registry of mappings and new mappings. • List all resources that can be set on a quota root: SUPPORTEDQUOTARES response on GETQUOTA in addition to QUOTA=RES- CAPABILITY responses.

  4. Changes from RFC 2087 (cont.) • Adds an untagged QUOTAMAP response that describes a relationship between the quota root and the mailbox (mapping). • Adds LISTQUOTA command that for a given quota root returns QUOTAMAP responses for all mailboxes accessible to the user that are governed by the quota root. • Adds DELQUOTA command: The resource limit associated with the resource name is removed (or reset to the underlying system limit), without affecting other limits.

  5. Changes from RFC 2087 (cont.) • Adds DELETED-MESSAGES and DELETED-STORAGE STATUS data items. • Minor clarifications

  6. Open Issues • Add OVERQUOTA NO response code • Define server behavior when the current usage is bigger than the limit provided in SETQUOTA (Another response code?) • Add GETUSAGE command? • Add QUOTARESINFO command that returns human readable text, measurement units, etc.? • Minor syntactical issues with SUPPORTEDQUOTARES untagged response (missing response, empty list of resources)

  7. Open Issues (cont.) • SETQUOTA/DELQUOTA: Should we be sending untagged QUOTA responses for all side effect changes? • Specify that a quota root name must uniquely identify a mapping [if any] - namespaces collision. • USER mapping - currently works with the logged in user only. Is it sufficient? • Interaction with ACL and ACL2

More Related