Monday, August 29, 2011, 4:32:55 AM, Joseph wrote:
> On Mon, 29 Aug 2011, Timo Sirainen wrote:
>>> Actually, this gives me pause that maybe I should not enirely remove
>>> the dotlocking method
>>>
>>>
>>> http://mailman2.u.washington.edu/pipermail/alpine-info/2008-July/000996.html
>>>
>>>
On Mon, 29 Aug 2011, Timo Sirainen wrote:
Actually, this gives me pause that maybe I should not enirely remove
the dotlocking method
http://mailman2.u.washington.edu/pipermail/alpine-info/2008-July/000996.html
Any comments on the (sole) use of POSIX fcntl() type locking?
As long as
On Fri, 2011-08-26 at 18:30 -0700, Joseph Tam wrote:
> On Fri, 26 Aug 2011, Joseph Tam wrote:
>
> > Thanks to all who've made suggestions. It seems removing dotlocks as
> > a locking method is the way to go.
>
> Actually, this gives me pause that maybe I should not enirely remove
> the dotlockin
On Fri, 26 Aug 2011, Joseph Tam wrote:
Thanks to all who've made suggestions. It seems removing dotlocks as
a locking method is the way to go.
Actually, this gives me pause that maybe I should not enirely remove
the dotlocking method
http://mailman2.u.washington.edu/pipermail/alpine
Thanks to all who've made suggestions. It seems removing dotlocks as
a locking method is the way to go. There is another dotlock locking
variant mentioned in 10-mail.conf that seems to address this situation
for those that can't get away from dotlocks:
# dotlock_try: Same as dotlock,
On 08/25/2011 07:38 AM, Timo Sirainen wrote:
> On 25.8.2011, at 5.12, David Warden wrote:
>
>> In your mail_location you can specify a different control and index
>> directory as a place where the user has no quotas. I'm not quite sure which
>> it is (control or index) that says where the dotloc
On 25.8.2011, at 5.12, David Warden wrote:
> In your mail_location you can specify a different control and index directory
> as a place where the user has no quotas. I'm not quite sure which it is
> (control or index) that says where the dotlock file goes but it should be one
> of them.
Nope,
On Aug 24, 2011, at 5:52 PM, Joseph Tam wrote:
>
> A mail user reported that he filled up his INBOX (despite reminders he
> was approaching his filesystem quota), and furthermore, he could not
> fix the situation because he couldn't expunge message he marked for
> deletion.
>
> The dovecot logs
Don't use dotlock files.
Method that generally works nice also is to start rejecting email for
the user when they are at 99% capacity, so you leave just alittle room
for that kind of thing left.
Quoting Joseph Tam :
A mail user reported that he filled up his INBOX (despite reminders he
w
A mail user reported that he filled up his INBOX (despite reminders he
was approaching his filesystem quota), and furthermore, he could not
fix the situation because he couldn't expunge message he marked for
deletion.
The dovecot logs revealed the cause
dovecot: imap(user): Error: open(
10 matches
Mail list logo
