On Tue, 3 Feb 2004, Tom Collins wrote: > > In 1.0.29, I see that letting the postmaster modify quotas enforces > > nothing; even if the domain has a default quota of 20MB, the postmaster > > can go in and set any user to 1000MB if they want. > > That's correct. If you had a domain quota of 100MB, then a user with a > 1000MB quota would be able to max out the domain so no one could > receive mail.
Just as a discussion point, does anyone else see that as a tech-support/customer-service nightmare? You sell accounts to an office that depends heavily on email, and one user who isn't very savvy is easily able to break mail delivery for the entire domain. Explaining to say, a law firm (or similarly email-dependent yet technically clueless) why this is so would be difficult, to say the least. > It's a good idea in that an ISP can limit a domain to a certain amount > of usage, and leave it up to the customer to use it as they see fit. That's why I was thinking it would be good to have a domain quota-like setting that qmailadmin understands, but that does not apply to the delivery agent. Keeping my above explanation in mind, assume that it worked as follows: -user signs up for a "domain account" that includes 20 accounts and a total "quota" of 200MB. -user logs into qmailadmin to setup the accounts. A total is shown at the top of the user-creation page that shows how much of that 200MB is left to be "given" to each user. -user sets up [EMAIL PROTECTED] with 10MB quota -user goes to user-creation page and the total shown at the top says "190MB left" -user creates [EMAIL PROTECTED], and since she handles sales and customer inquiries, he gives jane a 50MB quota -rinse and repeat until all users are created. If there's quota left over, user can assign the extra space to any existing users or keep it around for future use Does that sound like a good idea? In that scenario, if any one user goes over quota, only their mail is effected. Life goes on, everyone with the exception of one user is happy. The ISP is happy, as they didn't just break an entire domain's email, and they know that they can later up the quota and sell more space. > Your idea of a quota for the domain that the sum of all user quotas > can't exceed is another workable solution. I'm not sure which makes > more sense, and if we decide to support both then there will need to be > a clear way to choose between the two (and understand what will > happen). I'd love it if we could open a discussion on this either here or on the devel list. I haven't heard anything from current domain quota users. I'm also a bit curious about the system quota option (unix user per domain model), but I'm not really sure if the entire vpopmail suite understands system quotas, or if it really would solve any of the above problems. Thanks, Charles > -- > Tom Collins - [EMAIL PROTECTED] > QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ > Info on the Sniffter handheld Network Tester: http://sniffter.com/ > >
