Tried to update spamassasin with cpan, it failed of course
did:
perl -MCPAN -e shell [as root]
install Mail::SpamAssassin
<http://wiki.apache.org/spamassassin/SpamAssassin>quit
Test Summary Report
-------------------
t/spamc_bug6176.t (Wstat: 0 Tests: 2 Failed: 2)
Failed tests: 1-2
t/spamd_allow_user_rules.t (Wstat: 0 Tests: 5 Failed: 1)
Failed test: 5
Files=163, Tests=1976, 161 wallclock secs ( 1.26 usr 0.24 sys + 49.54
cusr 9.34 csys = 60.38 CPU)
Result: FAIL
Failed 2/163 test programs. 3/1976 subtests failed.
make: *** [test_dynamic] Error 255
JMASON/Mail-SpamAssassin-3.3.1.tar.gz
/usr/bin/make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
reports JMASON/Mail-SpamAssassin-3.3.1.tar.gz
Running make install
make test had returned bad status, won't install without force
On 03/29/2011 02:22 PM, Bowie Bailey wrote:
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.
