These days all spam uses forged return addresses, so the
only thing that bouncing spam will accomplish is that it'll clog your mail
queue, and/or annoy some innocent victim out there.
True. But. The setup I have in mind is:
1)removing most spam messages (/^X-Spam-Status: Yes/).
2)bouncing any that scored 2+ (or some such)
The latter may include false positives. The purpose of the bounce is to
alert valid email authors that I did not get their message. The purpose
of the setup is to implement an aggressive spam policy without the fear
of losing important mail.
Also, I intended to use a null mailbox to ensure that i ignore any
bounces that bounce back. Good point about innocent victims -- I'll
have to think about that some.
By the time the mail filter runs, the message has already been
accepted by
the mail server.
Good point. One option is to use courierfilter -- not maildrop -- to do
the bouncing. Of course I would then have to run SpamAssassin as a
courierfilter. Has that been done?
Any other ideas? Or does the whole thing still seem like a bad way to
go about it?
Kate Porter writes:
I have recently installed a complete courier system with maildrop +
SpamAssassin. I've been working on maildrop filters, and would like
some pointers to sample maildroprc code (assuming that this is
maildrop's responsibility) that generates a custom bounce.
Essentially, I'd like to bounce the message with some stern statement
about how it has been marked as spam, and if it really really isn't spam
the author should do something about it.
9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Sample bounce
