4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] when maildir over quota
FromSent OnAttachments
sos...@126.comFeb 24, 2008 11:40 pm 
André MamitzschFeb 25, 2008 1:47 am 
micahFeb 25, 2008 11:43 am 
Sam VarshavchikFeb 25, 2008 4:27 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] when maildir over quotaActions...
From:micah (mic@riseup.net)
Date:Feb 25, 2008 11:43:10 am
List:net.sourceforge.lists.courier-maildrop

André Mamitzsch <and@mamitzsch.de> writes:

you should not reject the mail immediately, it makes sense to retry the delivery when a user is over quota.

This is true in many cases, however if you have a large number of users, which means a certain percentage of those are over quota at all times, then your deferred queue gets quite big and can overload the queuing mechanism and cause a lot of problems.

In this scenario, we found we had to reject on over-quota immediately, but the user gets notificatons via email when they are getting close to over-quota situations, so that they can respond before that happens. This has the added side-benefit that people sending messages dont think that the receiver has received their message for 5 days and then suddenly gets a response, instead bouncing right away you get some sort of status indication.

On a postfix system you can use the following parameter to limit the queue lifetime of a message:

maximal_queue_lifetime (default: 5d) [snip] Specify 0 when mail delivery should be tried only once.

I wouldn't do this as a substitute because then you are going to bounce all mail that gets deferred, no matter if its due to over quota, or because some subsystem is offline temporarily.