Re: quota on /var/spool/mail
I think your logic has a slight flaw. It checks to see if the mailbox IS
CURRENTLY over quota, not if it WILL BE over quota AFTER the mail is
delivered.
In other words, mail comes in, the mailbox is checked to see if it is over
quota. It is not so the mail is added. Then next mail arrives. The mailbox
is now over quota from the previous mail so no more mail is delivered.
On Wed, 10 Feb 1999, Juergen Nagler wrote:
> After some users filled /dev/sda8 which is mounted as /var/spool/mail I
> introduced quotas. This worked fine up to two weeks ago because a user
> received a mail greater than his hardlimit. How could this happen?
>
> We're using smail 3.2.0.101-4.5 out of the hamm distribution.
>
> I observed the process of incoming mails. First the incoming mail is
> spooled to /var/spool/smail/input and then appended to
> /var/spool/mail/username, whether or not this exceeds the hardlimit of
> quota. Every next mail for this user is blocked because of the quota
> but this one was enough to fill /var/spool/mail.
>
> Any suggestions?
>
>
> TIA, Juergen Nagler
>
> ------
> Juergen.Nagler@student.uni-ulm.de
> students residence server admin
> Heilmeyersteige, Ulm, Germany
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
>
George Bonser
>From our family to you, a toast. Peace, Health, and Prosperity.
Reply to: