On Tue, 31 May 2016, Peter Carlson wrote:
I will investigate this (URIBL_BLOCKED) further tomorrow
(https://wiki.apache.org/spamassassin/CachingNameserver),
Note: caching != recursing. You can have a caching forwarding local
nameserver, which won't fix URIBL_BLOCKED.
however I doubt that it is causing the bayesian classifier to report as
ham.
It's not.
https://wiki.apache.org/spamassassin/ImproveAccuracy
I have gone through this wiki (and ones like it) at least a dozen times. My
server is blocking about 50% of the spam, thanks
to some of the other layers of spam protection. It's just bayes that I can't
seem to get right
Why is it marking all messages as ham?
Probably because you're overtraining as ham.
I have tried the following 3 scenarios:
1. Training SPAM only (it's in its own folder)
Won't work, bayes needs both spam and ham to be able to tell the
difference. If that actually *did* get hits on BAYES_00 in this scenario
then you likely are not training the bayes database than SA is actually
using.
What user are you training Bayes as, and what user is SA running under?
2. Training a folder with known HAM
This is the only reliable method.
3. Training with inbox as HAM
See earlier comments.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Justice is justice, whereas "social justice" is code for one set
of rules for the rich, another for the poor; one set for whites,
another set for minorities; one set for straight men, another for
women and gays. In short, it's the opposite of actual justice.
-- Burt Prelutsky
-----------------------------------------------------------------------
6 days until the 72nd anniversary of D-Day
