System quotae were intended to keep users from storing too much on the machines in their HOME DIRECTORIES.
That was the intent of quota systems. So we can use it as a hack to limit mailboxes size. But recall that it's a hack, so we have to work around some of the quota intent of offering a hard ceiling. Users don't duplicate their home directories a lot. The Right Answer is not to (mis)use the system quotae, but rather, put the checking in the delivery agent and let it use the soft quota as an advisory - you could get the info from LDAP if you wanted. But it's work on your part, at this moment. Quoting Alan Brown ([EMAIL PROTECTED]): > 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. > > Server mode makes user.pop handling a lot safer, but you need to ensure > that there is no direct access to the spool (eg, pine or mail) (Pine can > be configured to use pop in /etc/pine.conf or /etc/pine.conf.fixed), or > the direct access program. > > As Chuck says, pop is not designed for a lot of this high-end stuff. > > AB >
