Brian Kolaci wrote: > > Brian Kolaci wrote: > > > > > Yes, however when that was done, there was never a > > > concept of enforcing limits back then. Justin just submitted > > > > Again, I think you're wrong. As early as 4.1 there was quotas of > some sort. > I believe the limits you're refering to those that are > specified in the > .qmailadmin-limits file, which are a function of > qmailadmin to limit how > many accounts, etc, a postmaster can > create. > > Not anymore. This has changed with 5.3. The .qmailadmin-limits > is now extended into vpopmail and is now enforced at the domain > level as well as setting default quotas for users. The old > method allowed you to set a single site-wide HARD_QUOTA.
And how does that apply to adding a user? > > > > > > a patch to actually enforce these limits at, yes, the API level > > > where it belongs. This *will* break if you insert into a > backing > > store directly. > > > > Exactly what limits are you refering to? > > quotas, permissions (limiting what a user can do), etc. I set the quota, and it's very easy to limit what a user can do as well, if you understand how it works. I'm not saying you don't have to write your own logic for some of this, but inserting a record into the mysql database to add a user is not only an acceptable method, but one supported by the developer. See Ken's post to the list. Dave
