Terry Carmen wrote:
For SA 3.2.5 and earlier, default rules are installed to
/usr/share/spamassassin and are only used if none exist in
/var/lib/spamassassin, typically created by using sa-update.
I'm running 3.2.5.
Since it uses sa-update can all non-customized rules be deleted from
/usr/share/spamassassin?
If your installation is still seeing the old rule, it is likely that
either a copy of the rule exists in /etc/mail/spamassassin,
There are no .cf files except local.cf in /etc/mail/spamassassin
Is it possible that local.cf contains a copy of the rule?
which overrides rules in /var/lib/spamassassin, or that your
spamd/amavisd/whatever hasn't been restarted since the rule was updated.
I just did a "find" and have:
/usr/local/share/spamassassin/72_active.cf
/usr/share/spamassassin/72_active.cf
/var/lib/spamassassin/3.002005/updates_spamassassin_org/72_active.cf
Should I have all three or can I safely delete either or both of the
first two?
File locations differ based on distro and install config, so only you
can tell which ones apply to your install. Running "spamassassin --lint
-D" might tell you where it looks for files. I would expect that only
one of the following is being used:
> /usr/local/share/spamassassin/72_active.cf
> /usr/share/spamassassin/72_active.cf
I do recall posts to this list years ago that contraindicated removal of
the default rules directory, so it may be worth searching the archives
for reasons why. If your current install is truly not seeing the
updated rules in /var/lib/spamassassin, removal of the default rules
directory may leave you with a broken install. Again, "spamassassin
--lint -D" may shed some light on what's really happening.
