At 18/02/03 18/02/03 -0500, Brian Kolaci wrote:
I use standard "setuserquota()" function, already used in qmailadmin, so this schema is pretty compliant with all qmailadmin, vpopmail and qmail requests.Just make sure this new enhancement does not disturb the current domain quotas as specified in the qmailadmin-limits API. Make sure you add a new attribute rather than change the usage of the current implementation. I actually use these to implement real quotas on my system. We ensure that all users of a domain get at least 50 Meg each, but the domain starts at 150M through gigabytes. Most users rarely exceed 10 Meg (at least in my sampling, but this arrangement allows them to get large TIFF files and consume typically 30-40M each. They can get one or two, then download/delete them and get more.
Pooled way is an analitic solution that uses only standard qmailadmin features. 100% natural.
Pooled quota it's not the unique solution, but it's another solution that may be provided together with system quotas, not limited quotas and fixed quotas. It's another answer to customers (and providers) needs.The pooled limits in my opinion doesn't fit how most of my customers use email. System quotas (set from scripts) allow you to easily enforce quota restrictions with optimized O/S monitoring. And having a soft and hard limit, you can set the soft limit at some percentage, say 75% and then send them an email when their domain quota.
Most of my customers want single user quotas, not a unique domain quota.
The "pooled" way let them manage their single quotas as they want, and let me control the space I give them.
I agree with you, but what you say may be told against any kind of not system based quotas, not only this pooled way.System quotas are also more reliable in that it enforces the quota even from external sources such as .qmail files or any other local delivery agent.
Ciao,
Tonino
Thanks,
Brian
>
> Following the qmailadmin-1.0.10, and using (thanks!!!) Justin Hopper's code
> as starting framework, I've just realized a domain pooled quota management,
> that I'ld like could be integrated in the standard qmailadmin code.
>
> I followed the advice someone did a lot of time ago in this list. I cannot
> find those messages, so I don't know who I should thank.
>
> The base idea is the following:
>
> postmaster has the pooled quota against which all user's quota are
> subtracted or added. So, when a domain is created, postmaster has the whole
> domain's quota. Each time a user is added, the user's quota is decreased
> from postmaster's quota. The contrary when a user is deleted. Same
> adjustements when a user's quota is modified, increasing or decreasing
> postmaster's quota depending on user modifications. Minimum quota for each
> user or postmaster is 1 MB.
>
> This mechanism helps providers giving customers a fixed amount of space for
> the domain, then each domain administrator may manage users' quota as he
needs.
>
> It works if "--enable-quota=y" is specified, and "disable_pooled_quota"
> does not exist in .qmailadmin-limits.
>
> Additionally, a small bug on quota handling have been fixed and a couple of
> additional .qmailadmin-limits flags ("bounce_mail" and "disable_smtp") have
> been added.
>
> I've published both the integral tar, with all original sources and
> changes, and the tar with patches only, in:
>
> www.interazioni.it/qmail
>
> All is strictly based on qmailadmin-1.0.10.
>
> I'ld like that Ken and Bill could insert these features in a next public
> version of qmailadmin.
>
> Tonino
>
>
>
>
> ------------------------------------------------------------
> Inter@zioni Interazioni di Antonio Nati
> http://www.interazioni.it [EMAIL PROTECTED]
> ------------------------------------------------------------
>
>
------------------------------------------------------------
Inter@zioni Interazioni di Antonio Nati
http://www.interazioni.it [EMAIL PROTECTED]
------------------------------------------------------------
