Daniel Senie wrote:
At 03:04 PM 9/26/2005, Edward Chase wrote:
I'm having issues with my users blowing their storage quotas while
checking
their mail.
Consider this...
User is at storage limit.
User checks mail.
/var/mail/user gets copied to /var/spool/poptemp/.user.pop
New mail comes into /var/mail/user
System cannot combine the 2 files back because it exceeds storage
limit for
user.
Obviously user is leaving mail behind on server...
I haven't figured out a way around this.
Anyone run into this and figure out a way around it?
The only solutions I've seen involve putting the temp storage on a
separate machine.
The real answer, IMO, and one I haven't chased yet is to have the SMTP
server (sendmail, etc.) handle mailbox sizing issues, and bounce
messages when people are over quota. It should be possible to integrate
such without that much effort, but the sendmail/procmail universe seems
to lack such (I'm certainly open to pointers if folks have solutions to
this).
Ultimately, I really don't want to use the file system quota mechanism
to deal with limiting users' mailbox sizes. Perhaps quotas work for you
(other than the obvious qpopper question you asked about) but they seem
like the wrong tool for the job.
The real bugger is fastupdate w/quotas. It is nice feature, and speeds
up qpopper quite a bit, but depends on being on the same partition,
which means quotas won't work, since a user can't even check pop mail if
they are over quota, since qpopper can't create a temp file. procmail
will work, but only if temp drop is on a different partition that
doesn't enforce quotas.
I've found it best to stay away from hard quotas and just use a
combination of notification and/or mailbox pruning mechanism.
One helpful script is expire_mail.pl:
http://www.cpan.org/scripts/mailstuff/expire_mail.pl
Ken A
