|
Size: 2759
Comment:
|
Size: 2385
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 20: | Line 20: |
| mail_plugins = $mail_plugins quota | |
| Line 21: | Line 22: |
| mail_plugins = quota imap_quota | mail_plugins = $mail_plugins imap_quota |
| Line 23: | Line 24: |
| protocol pop3 { mail_plugins = quota } # In case you're using deliver: protocol lda { mail_plugins = quota } }}} |
}}} |
| Line 33: | Line 28: |
| The configuration is done differently for v1.0 and v1.1: * [[Quota/1.0|v1.0 quota configuration]] * [[Quota/1.1|v1.1 quota configuration]] |
* [[Quota/Configuration|v1.1 quota configuration]] |
| Line 55: | Line 47: |
| * Dovecot v1.0 + [[Quota/Maildir|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 [[Quota/1.1|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). |
* You can create a separate quota rule ignoring Trash mailbox's quota. Note that this would allow users to store messages infinitely to the mailbox. * You can create a separate quota rule giving Trash mailbox somewhat higher quota limit (but not unlimited). |
| Line 58: | Line 50: |
| To make sure users don't start keeping messages permanently in Trash you can use a nightly [[Plugins/Expire|cronjob or expire plugin (v1.1)]] to expunge old messages from Trash mailbox. | To make sure users don't start keeping messages permanently in Trash you can use a nightly [[Plugins/Expire|cronjob]] to expunge old messages from Trash mailbox. |
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: Store 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:
mail_plugins = $mail_plugins quota
protocol imap {
mail_plugins = $mail_plugins imap_quota
}
Configuration
Quota and Trash mailbox
Standard way to expunge messages with IMAP works by:
- Marking message with \Deleted flag
- 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:
- COPY the message to Trash mailbox
- Mark the message with \Deleted
- Expunge the message from the original mailbox.
- (Maybe later expunge the message from Trash when "clean trash" feature is used)
If user is over quota (or just under it), 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
- You can create a separate quota rule ignoring Trash mailbox's quota. Note that this would allow users to store messages infinitely to the mailbox.
- You can create a separate quota rule giving Trash mailbox somewhat higher quota limit (but not unlimited).
To make sure users don't start keeping messages permanently in Trash you can use a nightly cronjob to expunge old messages from Trash mailbox.