[KLUG Members] Tuning qmail

[Bruce Smith]

> > getting to the point now that I'm going to give spamassassin (or
> > something else) a try in addition to spamcop.
> 
> I've looked at other things and they are all either slow and shaky perl
> crap, too complicated, or require too much user interaction.  If the
> user actually has to *DO* something, they'll just delete the messages
> and ignore them (well, except for an enlightened *FEW*).  And none of
> these tools really help solve the problem;  the SPAM continues to
> arrive, get miltered, stored - whether or not the user takes the time to
> check/flag/mark/whatever... the message.  So what does the *SYSTEM*
> gain? Absa friggin' lutely nothin'.  So it is a user problem, not one
> for the system to solve (IMHO).

I tend to agree with you, but my boss is getting bugged by users who are
"offended" by their spam, and is telling me to try something else.  So,
I'll try some of that flaky perl crap and see what happens ...

> And we encourage our users to get a SPAMCop submission address and
> forward SPAM messages.  The enlightened *FEW* get their head around this
> pretty easy.

I used to report all my spam, until the guy who runs spamcop told me to
stop it.  :-)

You see, our anti-virus software (RAV, milter), does something weird to
the headers, causing spamcop's reporting system problems.  Hopefully
that'll change sometime soon when I switch to clamav or something else.

 - BS