On Thu, 6 Mar 2003, Chuck Yerkes wrote:
> However, using the disk system to enforce mail quota's is inherently > a hack, given that there will be, for a moment, two spools.
The only way around system quotas is to have the files in 2 different partitions, but that is a _huge_ performance hit.
As bad as the hit is, it's not nearly as bad (or unmanageable) as user calling every day because they can't get their mail.
With the relatively low-cost of disk space, it may be best to simply give users an unlimited quota, and run scripts to erase any boxes not checked in an arbitrarily long amount of time.
Of course this also opens up DoS possibilities of someone's box getting flooded with mail.
We run on two different file systems to avoid so many quota issues, and it is not that bad of a performance hit.
It seems that there really is no absolute solution with the current software. Either a DoS opportunity is opened up or users are stuck, or mail is corrupted.
We run with the temp dir on a non-quota filesystem, and hard quota only 100k larger than soft quota on the spool partition and with about 10,000 users, there are no load problems from qpopper and mailbox corruption as described in this thread only occurs about once every few months for anyone.
Michael Kolos Colba.Net Inc.
