Hi Gary and others,
Thanks for the instructions; I will give that a try. My upgrade with
backports.org went successful and I did it before reading Michel's message
about using CPAN to install SA. It's catching 25% of the spam now, instead
of 0%...I've seen a few messages about boosting its accuracy; I'll look
into that next. Thank you all for your help!
Ray
As far as SpamAssassin goes, I don't believe there is a significant
difference in what a .deb package provides and what installing from source
provides (which is essentially what CPAN does, bringing dependencies with
it). I think you would find the program files and rules would be the same
for a given version. The CPAN modules may be available a week or two before
a .deb package is, but that is the only real difference. The .deb package
may also install more dependencies that CPAN would. The .deb package also
installs an initscript, so there are advantages. Mixing both methods is
often a bad thing however.
How does your setup catch spam? At what score is a message considered spam
and what do you do with it? Are you using DCC/Razor2/Pyzor? Are they (along
with other network based tests) working? What rules are hitting when you
get somthing you think should have been marked as spam, but isn't? Are you
hitting rules like ALL_TRUSTED when you should not be? Maybe you should post
examples of local.cf and user_prefs.
To see if anything is going on as far as net tests go, you can break out
debugging info and try stuff like:
spamassassin --lint --debug area=1,dns
Here you would want to see:
dbg: dns: is Net::DNS::Resolver available? yes
spamassassin --lint --debug area=1,uri
spamassassin --lint --debug area=1,razor2
spamassassin --lint --debug area=1,dcc
spamassassin --lint --debug area=1,pyzor
Gary
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
