Eduardo Júnior wrote:
Hi,
I have just done an update in the rules of my spamassassin with sa-update
He dropped everything to /var/lib/spamassassin/version
He created the directory with several updates_spamassassin_org. Cf
And a updates_spamassassin_org.cf <http://updates_spamassassin_org.cf>
and updates_spamassassin_org.pre.
Peguei of the includes updates_spamassassin_org.cf
<http://updates_spamassassin_org.cf> and put in
/etc/spamassassin/local.cf <http://local.cf> and I made a copy of my
*. cf / etc / spamassassin to maintain consistently referenced in the
path includes.
No. DO NOT copy the files from where sa-update put them. Just run it,
and leave them where they are. SA will find them where sa-update put them.
The *ONLY* files that should be in /etc/spamassassin are the ones you
put there (ie: local.cf, or any add-on rules that aren't a part of the
standard set).
Executei a /init.d/spamassassin restart to restart.
The question is:
I am making an accurate?
How to test if these new rules are working properly?
If you want to make sure your SA is detecting the new rule directory
sa-update created:
Look near the top of the output of "spamassassin --lint -D", it should
mention the new directory about a half page down or so.
I´m using:
# spamassassin --version
SpamAssassin version 3.1.7
running on Perl version 5.8.8
You really should consider upgrading versions. sa-update only updates
rules, and there have been no new rules for the 3.1.x family since late
2007. We're on 3.2.5 now.
