Quota clone plugin is useful when you want to store everybody's current quota usage to a database, but you don't want to use the database as the authoritative quota database.
For example you might want to access everybody's quota via Redis (or SQL) but you don't store the Redis database permanently so it could become empty once in a while.
Additionally, it is expensive to directly scan quota information from each individual user account, so quota-clone allows access to quota information that is less resource intensive.
In these example use-cases, you can use quota count backend as the authoritative quota database and make a copy of the quota usage to Redis. From Redis you could then once in a while gather everybody's current quota usage and send it to yet another place (e.g. for statistics handling).
Every time quota is updated, the value is updated to the cloned dict. There are race conditions with it so the quota may not always be 100% correct. The old value is always replaced with the new one though (not just incremented/decremented) so the cloned quota is never too much wrong.
quota_clone_dict| Default | [None] |
|---|---|
| Value | string |
The dictionary to update with quota clone information. This must be set for the plugin to be active.
See dictionary for dictionary configuration.
plugin {
quota_clone_dict = redis:host=127.0.0.1:port=6379
}quota_clone_unset| Default | [None] |
|---|---|
| Value | boolean |
| Changes |
|
| Advanced Setting; this should not normally be changed. | |
Unset quota information before updating. This is needed with some dict backends that do not support upserting, such as SQL with older SQLite.
The keys that are written:
| Key | Value |
|---|---|
priv/quota/messages | Count of messages |
priv/quota/storage | Storage usage (in bytes) |
mail_plugins = $mail_plugins quota quota_clone
plugin {
quota_clone_dict = redis:host=127.0.0.1:port=6379
}More complex example using SQL:
dict {
mysql = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
plugin {
quota_clone_dict = proxy::mysql
}