This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 24 and 25
Revision 24 as of 2009-03-15 22:35:14
Size: 2513
Editor: localhost
Comment: converted to 1.6 markup
Revision 25 as of 2009-07-09 14:57:40
Size: 2740
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
There are different quota backends that Dovecot can use: Quota backend specifies the method how Dovecot keeps track of the current quota usage. They don't (usually) specify users' quota limits, that's done by returning extra fields from userdb. There are different quota backends that Dovecot can use:
Line 7: Line 7:
 * [[Quota/Dict|dict]]: Store quota in a dictionary (e.g. SQL).
 * [[Quota/Maildir|maildir]]: Maildir++ quota. This is the most commonly used quota for virtual users.
 * [[Quota/Dict|dict]]: Store quota usage in a dictionary (e.g. SQL).
 * [[Quota/Maildir|maildir]]: Stora quota usage in Maildir++ maildirsize files. This is the most commonly used quota for virtual users.

Quota

Quota backend specifies the method how Dovecot keeps track of the current quota usage. They don't (usually) specify users' quota limits, that's done by returning extra fields from userdb. There are different quota backends that Dovecot can use:

  • fs: Filesystem quota.

  • dirsize: The simplest and slowest quota backend, but it works quite well with mboxes.

  • dict: Store quota usage in a dictionary (e.g. SQL).

  • maildir: Stora quota usage in Maildir++ maildirsize files. This is the most commonly used quota for virtual users.

Enabling quota plugins

There are currently two quota related plugins:

  • quota: Implements the actual quota handling and includes also all the quota backends.
  • imap_quota: For reporting quota information via IMAP.

Usually you'd enable these by adding them to the mail_plugins settings in the config file:

protocol imap {
  mail_plugins = quota imap_quota
}
protocol pop3 {
  mail_plugins = quota
}
# In case you're using deliver:
protocol lda {
  mail_plugins = quota
} 

Configuration

The configuration is done differently for v1.0 and v1.1:

Quota and Trash mailbox

Standard way to expunge messages with IMAP works by:

  1. Marking message with \Deleted flag
  2. Actually expunging the message using EXPUNGE command

Both of these commands can be successfully used while user's quota is full. However many clients use a "move-to-Trash" feature, which works by:

  1. COPY the message to Trash mailbox
  2. Mark the message with \Deleted
  3. Expunge the message from the original mailbox.
  4. (Maybe later expunge the message from Trash when "clean trash" feature is used)

If user is over quota, the first COPY command will fail and user may get an unintuitive message about not being able to delete messages because user is over quota. The possible solutions for this are:

  • Disable move-to-trash feature from client
  • Dovecot v1.0 + Maildir++ quota: You can completely ignore Trash mailbox from quota calculation by appending :ignore=Trash to the quota line. Note that this would allow users to store messages infinitely to the mailbox.

  • Dovecot v1.1 or v1.0 quota rewrite: You can ignore Trash like with v1.0, but you can also give a separate quota rule giving Trash mailbox somewhat more quota (but not unlimited).

To make sure users don't start keeping messages permanently in Trash you can use a nightly cronjob or expire plugin (v1.1) to expunge old messages from Trash mailbox.

Quota (last edited 2018-07-27 07:33:57 by 2001:2060:49:110:b60:5467:7acd:478d)