I've run into the issue you describe quite a few times, with users who
get large quantities of email but insist on leaving messages on the
server (or even sometimes with users who haven't checked email in some
time and thus have a large amount piled up). I'm thus quite curious what
changed would be needed to do this, and how would one retroactively
apply the change (short of touching each user in the interface).
Thanks.
-Albert C.
P.S.-Sorry for being delayed in this-I seem to be having issues with the
list's digest mode, and just saw this mentioned when looking through the
list archives.
>Date: Wed, 1 Mar 2006 08:18:26 +0800 (SGT)
>From: patricko (at mark) staff.singnet.com.sg
>Subject: [coba-e:04208] Oops - typo: Should we set user account - hard quota to double?
>To: coba-e (at mark) bluequartz.org
>Message-Id: <Pine.LNX.4.44.0603010815470.6984-100000 (at mark) staff.singnet.com.sg>
>In-Reply-To: <20060228111334.48018415 (at mark) localhost.localdomain>
>X-Mail-Count: 04208
>
>Blues any coments?
>
>
>Double hard quota for not?
>Give users for grace quota?
>
>
>
>
>
>In case, you need the following for comment:
>
>Hard Limit
>The hard limit defines the absolute maximum amount of disk space that a
>user or group can use. Once this limit is reached, no further disk space
>can be used.
>
>Soft Limit
>The soft limit defines the maximum amount of disk space that can be used.
>However, unlike the hard limit, the soft limit can be exceeded for a
>certain amount of time. That time is known as the grace period.
>
>Grace Period
>The grace period is the time during which the soft limit may be exceeded.
>The grace period can be expressed in seconds, minutes, hours, days, weeks,
>or months, giving the system administrator a great deal of freedom in
>determining how much time to give users to get their disk usage below
>their soft limit.
>
>
>Cheers
>patrick
>
>
>
>On Tue, 28 Feb 2006, patricko wrote:
>
>> Hi,
>>
>> Since another partition serving as non-quota temporary mail spool,
>> a normal mailbox will be copied over to mail spool.
>>
>>
>> Therefore the actual quota needed will be more than actual quota.
>>
>>
>>
>> Why?
>>
>>
>>
>> While the qpopper is serving - user popping mails, New mails will enter the mailboxes and
>> qpopper session will not be able to secure the required space in user quota to write back the remaining mails from the mail spool.
>>
>>
>> I am suggestion we set the linux hard quota x2 of actual quota.
>>
>> eg: patricko's 1MB mailbox
>>
>> Disk quotas for user patricko (uid 1604):
>> Filesystem blocks soft hard inodes soft hard
>> /dev/sda8 26716 1025 2048 9 0 0
>>
>>
>> I think by doing so, mail grossly overquota maildrop - lock issue will be lessen!?
>>
>>
>>
>>
>>
>> Request for comment.
>> Thanks
>>
>>
>>
>>
>>
>> Cheers
>> patrick
>>
>
>