--- Sam Varshavchik <mrs...@courier-mta.com> wrote:
email builder writes:
Hi everyone,
We are seeing some undesirable behavior with some of our users who are
over
quota... some spam gets in under the radar, and even though it might be
processed with SA or whatever, if it goes to a user who is over quota,
maildrop will bounce it to the "sender", which in the case of spam is
forged.
So... we become a source of backscatter. Not nice. So we are
wondering,
is there a way to avoid this beside blocking all "spam" outright (which
is
not a business we'd like to get involved in for obvious reasons)??
Yes. Use the current version of Courier, whose current version of maildrop
reports an out-of-quota condition as a temporary failure condition,
Oh. Well... we are using Postfix, and I don't think we'll be changing that
any time soon. :(
Anyone done something like this with postfix/maildrop?? Do people just end
up eating this? I'm surprised no one has tried to do something about this
before now (under other MTAs)...?
Thanks
which
works together with Courier's built-in backscatter suppression logic to
eliminate all backscatter by rejecting all subsequent delivery attempts to
the same mailbox with an SMTP temporary failure indication. If the mailbox
goes back under quota reasonably soon, no mail will be lost.
The default configuration settings in the current version of Courier will
never generate any backscatter. It case of locally-originated screwups
Courier will eat the bounce.
5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Quota bounces using m...
