Ken Murchison wrote:
> Jules Agee wrote:
> > Notifying the user who has exceeded quota so they can fix the problem
> > immediately, instead of wondering why they haven't any messages for two
> > days, and then calling tech support complaining that "their account is
> > broken". My experience has been that most of the time that people exceed
> > quota is because someone sent them a gargantuan attachment, so they
> > often never receive the quotawarn message - the big attachment took them
> > directly from 75% to 110% of quota.
>
> As Larry stated, an ALERT message is sent out each time the user SELECTs
> a mailbox. If your client is not displaying them, then your client is
> broken. You should refer the author(s) to section of 3.4.11 of RFC2683.
>
> Other than than, you can write a script (I think one has been posted to
> the list previously) which can detect overquota and quotawarn conditions
> and post a message to a user's INBOX (via 'deliver -q').
>
Actually, Jules has already written that script :-) Those you are interested
can find it at cyrus-utils, it's called quotacheck:
http://sourceforge.net/projects/cyrus-utils
with the direct URL:
http://prdownloads.sourceforge.net/cyrus-utils/quotacheck.tar.gz
