John Heim wrote:
----- Original Message ----- From: "Noel Jones" <[EMAIL PROTECTED]>
In setting up the pre-queue spam filter, I followed the instructions
here:
http://www.postfix.org/SMTPD_PROXY_README.html
What are you using as your smtpd_proxy_filter? Seems it could do
better...
Spampd and spamassassin. I have spent a lot of time tweaking the
spamassassin settings but I'm afraid of false positives and of
increasing the load on my mta too much. I didn't really intend to ask
spamassassin questions here. When I asked my original question, I
thought we were doing pretty well wrt catching spam before it even
entered the system. I thought there was something else misconfigured in
my postfix config.
I agree that false positives are bad... but hopefully you're
rejecting mail and not discarding it. When (legit) mail is
rejected, the sender is notified and you'll hear about it...
Note that if you use some of the suggested RBLs and other
postfix restrictions, load on your server will go way down
compared to running spamassassin on everything.
I also strongly suggest clamav if you're not using it. And I
also strongly recommend the Sanesecurity add-on signatures for
clamav; they catch lots of phish and scam mail that
spamassassin seems to have trouble with. The clamav-milter
(part of clamav) works well with postfix, or there is a
plug-in for SpamAssassin if you don't want to set it up
separately.
>
> What? There's no "DO_NOT_FORWARD_SPAM" flag I can set to
'yes'? Bummer.
>
I'm waiting on the NO_SPAM_HERE flag.
--
Noel Jones
