|
Size: 2014
Comment:
|
Size: 2229
Comment: minor linguistic improvements
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| * [wiki:Quota/FS fs]: Filesystem quota enforcing. * [wiki:Quota/Dirsize dirsize]: The simplest quota backend. It scans all the files from mail directories to calculate the quota. * [wiki:Quota/Dict dict]: Store quota in a dictionary. Currently the only dictionary backend is MySQL. |
* [wiki:Quota/FS fs]: Filesystem quota. * [wiki:Quota/Dirsize dirsize]: The simplest, but sometimes slow, quota backend. It scans all the files from mail directories to calculate the quota. * [wiki:Quota/Dict dict]: Store quota in a dictionary (table). |
| Line 10: | Line 10: |
| The quota is supported as a plugin for Dovecot. There exists a plugin named "quota" which does the actual work. For reporting quota information via IMAP there exists also "imap_quota" plugin. Usually you'd enable these by adding them to the `mail_plugins` settings in config file: | The quota backends are implemented as plugins for Dovecot. There is also a plugin named "quota" which does the actual work. For reporting quota information via IMAP, there is the "imap_quota" plugin. Usually you'd enable these by adding them to the `mail_plugins` settings in config file: |
| Line 26: | Line 26: |
| You can set the quota as kilobytes (named '''storage''') and/or as number of messages (named '''messages'''). Usually only the '''storage''' quota is used. Usually these can be given to the quota backend as parameters, eg.: | You can set the quota as kilobytes (named '''storage''') and/or as number of messages (named '''messages'''). Usually only the '''storage''' quota is used. Usually these limits can be given to the quota backend as parameters, e.g.: |
| Line 30: | Line 30: |
| # 10MB quota limit | # 10 MB quota limit |
| Line 34: | Line 34: |
| # 10MB + 1000 messages quota limit | # 10 MB + 1000 messages quota limit |
| Line 38: | Line 38: |
| The above example shows how to set the same quota globally for everone. You can override this for one or all users by returning `quota` field from userdb. See UserDatabase for more information about how to set them for the userdb you're using. Here's an example using SQL userdb: | The above example shows how to set the same quota globally for everyone. You can override this for one or all users by returning a `quota` field from the user database. See UserDatabase for more information about how to set them for the user database you are using. Here is an example using a SQL-based user database: |
| Line 43: | Line 43: |
| With LDAP use something like: | With LDAP, use something like: |
| Line 48: | Line 48: |
| user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota }}} | user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota # If you have the quota already as kilobytes in LDAP, there's a kludgy way to use it directly: user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota=dirsize:storage }}} |
Quota
There are different quota backends that Dovecot can use:
- [wiki:Quota/FS fs]: Filesystem quota.
- [wiki:Quota/Dirsize dirsize]: The simplest, but sometimes slow, quota backend. It scans all the files from mail directories to calculate the quota.
- [wiki:Quota/Dict dict]: Store quota in a dictionary (table).
- [wiki:Quota/Maildir maildir]: Maildir++ quota.
The quota backends are implemented as plugins for Dovecot. There is also a plugin named "quota" which does the actual work. For reporting quota information via IMAP, there is the "imap_quota" plugin. Usually you'd enable these by adding them to the mail_plugins settings in config file:
protocol imap {
mail_plugins = quota imap_quota
}
protocol pop3 {
mail_plugins = quota
}
# In case you're using Dovecot-LDA:
protocol lda {
mail_plugins = quota
} Most of the quota backends have a few things in common:
You can set the quota as kilobytes (named storage) and/or as number of messages (named messages). Usually only the storage quota is used. Usually these limits can be given to the quota backend as parameters, e.g.:
plugin {
# 10 MB quota limit
quota = maildir:storage=10240
# 1000 messages quota limit
quota = maildir:messages=1000
# 10 MB + 1000 messages quota limit
quota = maildir:storage=10240:messages=1000
} The above example shows how to set the same quota globally for everyone. You can override this for one or all users by returning a quota field from the user database. See UserDatabase for more information about how to set them for the user database you are using. Here is an example using a SQL-based user database:
user_query = SELECT home, uid, gid, 'dirsize:storage=' || quota_bytes AS quota FROM users WHERE userid = '%u'
With LDAP, use something like:
# quotaStorage must be in the format mentioned above # For example: dirsize:storage=10240 user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota # If you have the quota already as kilobytes in LDAP, there's a kludgy way to use it directly: user_attrs = uid,homeDirectory,,,uidNumber,gidNumber,quotaStorage=quota=dirsize:storage