[Dovecot] different users with different quota

Sven Hartge sven at svenhartge.de
Wed Mar 23 21:58:50 EET 2011

Jim Knuth <jk at jkart.de> wrote:
> am 23.03.11 18:38 schrieb Dennis Guhl <dg at dguhl.org>:
>> On Wed, Mar 23, 2011 at 05:44:51PM +0100, Jim Knuth wrote:
>>> am 23.03.11 17:33 schrieb Sven Hartge<sven at svenhartge.de>:

>>>> How your different user quotas are configured depends on the userdb
>>>> backend you use.

>>> it`s via pam

>> PAM is no userdb: http://wiki2.dovecot.org/PasswordDatabase/PAM
>> "Usually PAM is used with passwd (NSS) or static user databases." is
>> a direct quote from this link and should tell you which example to
>> follow in Sven's links.

> ok, than

> plugin {
>   quota = maildir:UserONE quota
>   quota_rule = *:storage=1G
>   quota_rule2 = Trash:storage=100M
>   quota = maildir:UserTWO quota
>   quota_rule = *:storage=5M
>   quota_rule2 = Trash:storage=50M
> }


Think logical for a moment: Would such a configuration scale to 10
users? 100 users? 10000 users?

No, it would not. So without knowing if this _could_ work, you can
outright deduce this one as wrong.

Ask yourself one question:

a) "Do I have different quota_rules for my users?"
b) "Are my quota_rules the same for every user?"

If a) then you need to setup a userdb with this information in it (This
is documented in the wiki for a text-, LDAP- any SQL-based one, with the
LDAP-based one being a bit strange to configure, but I asked a question
concerning the syntax not long ago, so the archive is your friend.)

If b) then you can hardcode your quota_rule inside the config, just as
you are trying to do.

I would suggest to start with b) and if this works, _then_ work your way
up to a).

Hardcoding a "fall back" quota_rule inside the config has also the added
benefit of, well, having a fall back, in case the quote inside your
userdb is not set for a user.


Sig lost. Core dumped.

More information about the dovecot mailing list