On 12.8.2014 13:04, Jochen Bern wrote:
On -10.01.-28163 20:59, Jiri Bourek wrote:
On 10.8.2014 06:18, Will Yardley wrote:
Depends on the environment; in many cases, the admin could, or may even
be expected to, raise the quota.
If you're expected to raise the quota in case it's exceeded, don't
On -10.01.-28163 20:59, Jiri Bourek wrote:
> On 10.8.2014 06:18, Will Yardley wrote:
>> Depends on the environment; in many cases, the admin could, or may even
>> be expected to, raise the quota.
>
> If you're expected to raise the quota in case it's exceeded, don't set
> it in the first place, th
On 12.8.2014 00:42, Andrzej A. Filip wrote:
On 08/10/2014 12:31 AM, Timo Sirainen wrote:
On 10 Aug 2014, at 01:19, Timo Sirainen wrote:
I'd really like to hear Timo's view on having lmtp do a (configurable)
DEFER when the disk is full which is, most likely, a "temporary" error.
My opinion:
On 08/10/2014 12:31 AM, Timo Sirainen wrote:
> On 10 Aug 2014, at 01:19, Timo Sirainen wrote:
>
>>> I'd really like to hear Timo's view on having lmtp do a (configurable)
>>> DEFER when the disk is full which is, most likely, a "temporary" error.
>>
>> My opinion: It shouldn't be configurable - i
> Luuk hat am 10. August 2014 um 18:24 geschrieben:
> Quota should be set according to some rules, and never be raised because
> of a 'quota reached'.
> What is the use of 'quota' if the admin raises your quota when things
> are full?
Guys, you are mixing up user quota and the "disk full" or bett
On 10.8.2014 06:18, Will Yardley wrote:
On Sun, Aug 10, 2014 at 01:31:47AM +0300, Timo Sirainen wrote:
Problems that admins can solve are temporary errors for users and
the'll need an error logged. Problems that are caused by users
themselves (like over quota) are usually not temporary errors a
Am 11.08.2014 um 22:44 schrieb Will Yardley:
> 3) In many cases, users aren't able to delete mail to get under their
> (hard) quota without having the quota raised temporarily. If their mail
> client deletes by copying messages into the trash, then purging, for
> example, I've seen cases where the
On Sun, Aug 10, 2014 at 06:24:47PM +0200, Luuk wrote:
> On 10-8-2014 06:18, Will Yardley wrote:
> > Depends on the environment; in many cases, the admin could, or may even
> > be expected to, raise the quota.
>
> !but should not!
>
> Quota should be set according to some rules, and never be raise
On 10-8-2014 06:18, Will Yardley wrote:
Depends on the environment; in many cases, the admin could, or may even
be expected to, raise the quota.
!but should not!
Quota should be set according to some rules, and never be raised because
of a 'quota reached'.
What is the use of 'quota' if the
On Sun, Aug 10, 2014 at 01:31:47AM +0300, Timo Sirainen wrote:
> Problems that admins can solve are temporary errors for users and
> the'll need an error logged. Problems that are caused by users
> themselves (like over quota) are usually not temporary errors and they
> shouldn't have errors logg
On 10 Aug 2014, at 01:19, Timo Sirainen wrote:
>> I'd really like to hear Timo's view on having lmtp do a (configurable)
>> DEFER when the disk is full which is, most likely, a "temporary" error.
>
> My opinion: It shouldn't be configurable - it should always cause temporary
> error. The only t
On 05 Aug 2014, at 14:45, Christian Rohmann wrote:
> may I PING this subject once again to maybe get Timo's opinion.
>
> On 23.07.2014 11:26, Christian Rohmann wrote:
>> Bounced / rejected messages for something that will be usually be
>> resolved very quickly and the messages can then be delive
Hey Timo and all,
may I PING this subject once again to maybe get Timo's opinion.
On 23.07.2014 11:26, Christian Rohmann wrote:
> Bounced / rejected messages for something that will be usually be
> resolved very quickly and the messages can then be delivered after all
> is just not very nice for
On 22.07.2014 19:00, Moritz Augsburger wrote:
> The message could be already saved to disk by the MTA, so I don't see a
> reason for a hard reject, if it could be fixed within some hours by the
> admin (eg by expanding the volume, moving mailboxes between multiple
> storage systems etc).
>
> Mai
Am 22.07.2014 19:00, schrieb Moritz Augsburger:
> On 2014-07-22 17:31, Reindl Harald wrote:
>> in case of disk full *this is* a permanent error likely not
>> correctable by the user given that after delete a message a
>> different one get a new and the disk is full again
>
> The message could be
On 2014-07-22 17:31, Reindl Harald wrote:
> in case of disk full *this is* a permanent error likely not
> correctable by the user given that after delete a message a
> different one get a new and the disk is full again
The message could be already saved to disk by the MTA, so I don't see a
reason
Quoting Reindl Harald :
Am 22.07.2014 17:11, schrieb Christian Rohmann:
In consequence this means the configuration option quota_full_tempfail
is applied in both cases. But to me there is a major difference between
a full disk (a.k.a "admin fucked up") and over-quota (a.k.a. "user has
simply t
Am 22.07.2014 17:11, schrieb Christian Rohmann:
> In consequence this means the configuration option quota_full_tempfail
> is applied in both cases. But to me there is a major difference between
> a full disk (a.k.a "admin fucked up") and over-quota (a.k.a. "user has
> simply too much stuff in his
Hello dovecot-users,
(This problem was being discussed a little in this thread from 2011:
http://www.dovecot.org/list/dovecot/2011-May/059009.html)
I noticed (using LMTP) that Dovecot handles 'no space left on device'
just like an 'over-quota', if I read this part of method "static int
client_de
19 matches
Mail list logo
