--On Friday, October 06, 2006 10:37 AM -0500 Bookworm <[EMAIL PROTECTED]>
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/ )
On a well-maintained system, everything under /usr should be read-only
except when you upgrade packages. /var is where you put stuff that changes
between package upgrades. /etc is, of course, where you put site-specific
customization.
So a given version of SA puts rules in /usr/lib/spamassassin. Between
upgrades, dynamic updates using sa-update go under
/var/lib/spamassassin/{version}. (The {version} part lets you back out an
update without having to re-download the interim rules updates.) Your own
rules go in your site rules dir, such as /etc/mail/spamassassin.
