We upgraded last month from 4.0B to 4.0D. There was a fix in
4.0B to make quotas work, even for mail.local, the local delivery
agent. Without the fix, it just worked for other processes, but
not mail.local. Our system programmer's can't figure out how to
apply it or what an equivalent fix is on 4.0D, so now we have
users with 100 MB mail spools and still receiving more mail.
I several possible solutions, best first:
1. Get a fix so quotas really work, even for the local delivery agent.
Does anyone know what how to do this?
2. Hack mail.local to check the users quota status before delivering
mail and then giving a fatal error if the user is over quota.
What system call returns quota information, e.g.
current usage, whether soft is now hard quota, etc.
I can't find anything relevant in the man pages.
3. Hack mail.local to stat the user's mail spool and give a
fatal error if it is over a fixed amount.
4. Use aliases to block incoming mail for these users.
This is easiest, but crudest.
- Jerry Berkman, UC Berkeley
jerry_at_uclink.berkeley.edu
Received on Fri Mar 27 1998 - 01:07:30 NZST