On 2010-09-22 8:53 PM, Cassidy Larson wrote:
> I haven't tried the quota_full_tempfail yet, because a lot of these
> are just accounts that haven't been used forever and have gotten
> full of spam and I dont know if I'd prefer tempfailing them to just
> bouncing.
Why waste the resources at all
>
> I don't think quota full should be logged as an error.. Without Sieve
> this is logged:
>
> Info: msgid=unspecified: subject=: save failed to INBOX: Quota exceeded
> (mailbox for user is full)
> Info: msgid=unspecified: subject=: rejected: Quota exceeded (mailbox for user
> is full)
>
> Also
On Wed, 2010-09-22 at 12:17 +0200, Stephan Bosch wrote:
> > dovecot: lda(u...@host.com): Error: sieve: script
> > /data/mail/host.com/u...@host.com//.dovecot.sieve failed with
> > unsuccessful implicit keep (user logfile
> > /data/mail/host.com/u...@host.com//.dovecot.sieve.log may reveal
> > addit
sure enough... they did appear back in 1.2.x land. Sorry for the noise.
-c
> I'm wondering how your previous setup handled this. Currently, LDA and
> Pigeonhole don't maintain state information about persistent errors, causing
> a new error message in the logs for each failed delivery.
>
> Regard
Op 22-9-2010 8:45, Cassidy Larson schreef:
Just switched my storage boxes to 2.0.3 with Pigeonhole. Noticing for
those that have quota fulls, my syslog is getting full of errors from
sieve:
dovecot: lda(u...@host.com): Error: sieve: script
/data/mail/host.com/u...@host.com//.dovecot.sieve fail
