On 3/29/2011 3:07 PM, missingshrink wrote:
> Not to hijack this thread - but I am experiencing the same issue.
>
>
> I too - started experiencing tons of spam getting through since a few weeks
> ago.
> In the past hour, 18 messages were not corrected tagged as spam, 3 were. My
> required score is 2.0. I also use 5 DNSBLs. Last week, I uninstalled
> spamassassin, all bayes files I could find, and reinstalled. It did not help
> at all. I regularly run sa-update and sa-learn on my spam folder that I
> manual check to ensure there are no ham messages.
>
> I am almost certain that it is likely to be a configuration issue, but I am
> merely a SA user, not a bayes master. Been using SA for about 7 years
> already though, and it's always worked well.
>
> Here are some sample messages that bypassed SA:
> http://pastebin.com/raw.php?i=0NYi2Ufu
> Here is my SA -D -lint result: http://pastebin.com/raw.php?i=fyJfBQCn
>
> Any help would be much appreciated!
First thing I would do is fix your bayes db. It looks like you are
trying to use a global bayes db, right? If so, you have the bayes_path
set wrong (see the error in 'spamassassin --lint').
You apparently have this:
bayes_path /tmp
While it should look like this:
bayes_path /tmp/bayes
This setting needs to be both the directory path as well as the first
portion of the filename for the bayes files. This will almost always
look like '/path/to/directory/bayes'. Note that 'bayes' is NOT a directory.
Looking at your samples, it appears that the bayes db is your main
problem. BAYES_00 should never fire on spam. This problem may go away
if you define the bayes_path correctly. To prevent the problem from
resurfacing, make sure you run sa-learn on both spam and ham on a
regular basis.
--
Bowie
