Hi Nick, I appreciate you and Erik for looking into this with alacrity.
I didn't actually experience a situation where domain quotas were not working. It's just that in looking for the answer to an unrelated question, I came across the paragraph Claiming domain quotas are broken, and not to use them. That is very important for us, in that it not working is not an option. So my main reason for asking was to confirm the statement made in the README.quotas file, and, figure out an easy way of fixing that if possible. 'Cause the suggested fix, didn't sound so easy. But I am glad to know that this is an issue, and that, for some reason, the README.quotas file is wrong about that--at least as far as the version of vpopmail that comes with the toaster. Thanks again... Dairenn Lombard BroadSpire Systems Administration Dept. "Security, Scalability & Automation" > -----Original Message----- > From: Nick Hemmesch [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 25, 2006 2:21 PM > To: [email protected] > Subject: Re: [qmailtoaster] Vpopmail Domain quotas > > > Hi again, > > --enable-domainquotas is no longer a build option. The quotas > set in /home/vpopmail/etc/vlimits.default are used unless you > have modified them at domain or user level. > > Regards, > > Nick > > > Hi, > > > > I will take a look at this . . . It was my belief that I had it > > enabled. It will be, if it isn't. > > > > Thanks . . . > > > > Regards, > > > > Nick > > > >> Dairenn, > >> > >> I wasn't aware that domain quotas was broken. We are using the > >> .qmailadmin-limits file to enforce quotas, but you are > correct. The > >> vpopmail-toaster package does not have > --enable-domainquotas enabled. > >> > >> Have you confirmed that the domain quotas are broken? If > so, this is > >> a trivial thing for us to fix. > >> > >> Thanks, > >> Erik > >> > >> On 5/25/06, Dairenn Lombard <[EMAIL PROTECTED]> wrote: > >>> This is very important. > >>> > >>> According to vpopmail's README.quotas file: > >>> > >>> * DOMAIN QUOTAS > >>> > >>> ** NOTE: Domain quotas are currently broken. Do not > use them. > >>> ** > >>> > >>> If you want to implement a quota for a whole domain, > you have 2 > >>> options. > >>> You can either put the domain under a unique system id and > >>> implement > >>> system quotas, or (as of 5.3.18) you can use a > non-system domain > >>> quota. To > >>> implement the former, just use 'vadddomain -u <system user> > >>> <domain>' and > >>> set the system quota for that user. To implement the latter, > >>> you must first > >>> compile vpopmail with "--enable-domainquotas=y". > Then, you can > >>> add this to > >>> your .qmailadmin-limits file > >>> > >>> Does the spec file for the source RPM for vpopmail from > >>> qmailtoaster.com have --enable-domainquotas=y set, or > must we edit > >>> that file, and then rebuild and re-install the vpopmail RPM after > >>> editing the spec file to enable this? And why isn't this on by > >>> default? Is that why it's "broken?" > >>> > >>> Please advise. > >>> Thanks in advance. > >>> > >>> > >>> Dairenn Lombard <[EMAIL PROTECTED]> - BroadSpire Systems > >>> Administration Dept. BroadSpire, Inc. - http://www.broadspire.com/ > >>> "Security, Scalability & Automation" --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
