Incoming from bogi:
>
> On July 9, 2004 11:46, s. keeling wrote:
> > Incoming from bogi:
> > >
> > > How to get spam-filtering going, i have tryed all i could find, but is
> > > seems to deliver spam unmarked very nicely, please help.
> >
> > # -------------------------------
> > :0fw
> > | /usr/local/bin/spamc
>
> Thank you Stephen. That nailed it. And it is in /usr/bin/spamc,
> just for the reference.
Maybe on your box, it is. :-) You're welcome. You managed to solve
something for me too:
-----------------------------------------
X-Spam-Report:
* -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
* [score: 0.0000]
* 0.6 FAKE_HELO_SHAW_CA Host HELO did not match rDNS: shaw.ca
* 0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
* [68.144.190.28 listed in dnsbl.sorbs.net]
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,FAKE_HELO_SHAW_CA,
RCVD_IN_SORBS autolearn=no version=2.63
X-Spam-Level:
-----------------------------------------
That's what SA said about your mail. I've been fiddling with Spam
reporting rules, and I had added one that looked for "sender is listed
in SORBS" in the headers. Son of a gun, that matches Shaw!
I've since changed it to:
# -----------------------------
# if this is Spam, but sender's already blacklisted, ignore it.
#
:0
* -1^0
* 1^0 ^X-Spam-Status: YES
* 1^0 ()(\
domain appears in spamcop database at sc\.surbl\.org|\
inaccurate or missing WHOIS|\
is blacklisted in|\
listed in dnsbl|\
Received via a relay in|\
Sender is listed in SORBS|\
Sent via a relay in\
)
{
LOG="SA reported - "
:0:
${MAILDIR}/spamreported
}
Now (as it was intended) it will just backup/check SA's work, not
attempt to replace it.
I suspect SORBS is not too quick about removing those it blacklists.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling
- -
_______________________________________________
clug-talk mailing list
[EMAIL PROTECTED]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
