Bowie Bailey wrote:
Bookworm wrote:
When I build SpamAssassin using the CPAN method, it installs the
test files (20_anti_ratware.cf and similar) in
/usr/share/spamassassin.
However, sa-update shoves updates into
/var/lib/spamassassin/3.001005/updates_spamassassin_org (with extra
crap in /var/lib/spamassassin/3.001005/ )
I suspect that one or the other behavior is actually wrong. Either
the CPAN method has a bad configuration script, or the sa-update has
never been matched to the configure script.
Either way, can anyone give me a suggestion on the best way to deal
with this issue? (Besides the fact that the CPAN should probably use
the same default site rules directory as sa-update?)
Is this an FAQ yet?
Both are correct.
The default rules are installed in /usr/share/spamassassin these are
created when you install/update spamassassin.
Rules updated by sa-update are placed in
/var/lib/spamassassin/(version)/.
SA will use the updated rules if they exist. Otherwise, it uses the
default rules.
Best suggestion: Don't worry about it. It will work fine.
And that's exactly what I needed to know. Thanks.
I've read all the replies up to this point, and yes, I read the man
files for spamassassin itself and for sa-update. It didn't really
answer the question. However, I now have an answer!
I will admit, I didn't go to the web site and read through it. I wasn't
in a position to bring up lynx and try to bang around on the
SpamAssassin apache web site.
BW
