Re: Spamassassin from CPAN and sa-update location.
Hi Bookworm, There isn't a problem. This is exactly how it is designed to work. SA has an inbuilt order of checking for files, RTFM: http://spamassassin.apache.org/full/3.1.x/dist/doc/spamassassin.html#configuration 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?) Bookworm -- Anthony Peacock CHIME, Royal Free University College Medical School WWW:http://www.chime.ucl.ac.uk/~rmhiajp/ If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas. -- George Bernard Shaw
RE: Spamassassin from CPAN and sa-update location.
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. -- Bowie
Re: Spamassassin from CPAN and sa-update location.
On Fri, Oct 06, 2006 at 11:44:51AM -0400, Bowie Bailey wrote: 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. Is this an FAQ yet? Yes, actually. http://wiki.apache.org/spamassassin/RuleUpdates :) -- Randomly Selected Tagline: We all know engineers are way better than doctors because doctors can only kill people one at a time while engineers can send 600 to a 1000 people screaming into Mt. Rushmore at 300 to 400 knots. - Unknown pgpT6XDP9ndSi.pgp Description: PGP signature
RE: Spamassassin from CPAN and sa-update location.
Theo Van Dinter wrote: On Fri, Oct 06, 2006 at 11:44:51AM -0400, Bowie Bailey wrote: 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. Is this an FAQ yet? Yes, actually. http://wiki.apache.org/spamassassin/RuleUpdates Lots of good stuff there, but nothing that specifically references the /usr/share/spamassassin vs /var/lib/spamassassin question. -- Bowie
Re: Spamassassin from CPAN and sa-update location.
On Fri, Oct 06, 2006 at 12:11:24PM -0400, Bowie Bailey wrote: Lots of good stuff there, but nothing that specifically references the /usr/share/spamassassin vs /var/lib/spamassassin question. Well, there is, though not directly as a why local state dir instead of default rules dir type question. Usually, this issue comes up when people ask about moving files from one location to the other, which is covered in the FAQ area: After sa-update completes, do I have to move the files somewhere for them to be used? However, about one versus the other ... The location used is specified quite a few times in the Using sa-update and Installed Updates sections, and I think it's pretty clear that it's designed that way. The FAQ question: Should I use --updatedir to put updates in the default rules directory (ie: /usr/share/spamassassin), or the site rules directory (ie: /etc/mail/spamassassin)? also talks about how there are two directories and they do different things. I think it makes sense, but then again I'm a bit biased about the whole thing. If someone feels they want to explain things in more detail, please feel free to update the wiki page (that is, after all, why it's a wiki page... ;)) -- Randomly Selected Tagline: Having a firewall that allows NFS to the Internet is like having a seat belt that lets your head touch the dashboard. - Marcus Ranum pgp20ZjRVQd06.pgp Description: PGP signature
Re: Spamassassin from CPAN and sa-update location.
--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.
Re: Spamassassin from CPAN and sa-update location.
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
