Cyrus IMAP features a flexible Quota scheme with support for limiting various resources, such as storage or number of folders or messages.
.. toctree:: :maxdepth: 1 :glob: quotas/*
Monitor and Repair
Quotas may be monitored and repaired via the :cyrusman:`quota(8)` command:
Controlling Quota Behavior
How restrictive quotas will be may be tailored to the needs of different sites, via the use of several settings in :cyrusman:`imapd.conf(5)`:
Quota information is stored either in a database (i.e. twoskip,
skiplist) or in "quotalegacy" format, which is a filesystem hierarchy.
This is controlled by the
quota_db setting in
:cyrusman:`imapd.conf(5)`. Here's more about the pertinent settings:
Converting Quotas Database
The :cyrusman:`cvt_cyrusdb(8)` utility may be used to convert between
formats. It's usage with
quotalegacy is a special case, in that
the first argument ("<old db>") will be the path to the base of the
quotalegacy directory structure, not to a particular file.
For example, given this typical layout:
/var/lib/imap/ | /quota/ | /A/ | /user/ | /bob/
cvt_cyrusdb command would be:
cvt_cyrusdb /var/lib/imap/quota quotalegacy /var/lib/imap/quotas.db twoskip
Back to :ref:`imap-admin`