On 5/13/06, Theo Van Dinter <[EMAIL PROTECTED]> wrote:
On Sat, May 13, 2006 at 10:57:11AM -0700, Bart Schaefer wrote:
> Well, guess what. "sa-update" creates the
> /var/lib/spamassassin/3.001001 directory if it does not exist, rather
> than finding the directory that does exist and using that. I didn't
Of course. sa-update *only* uses the /var/lib area. It doesn't care
about what other rules you already have installed or where they are.
But surely there's some kind of disconnect here. sa-update creates an
empty directory that spamassassin (and spamd) then uses preferentially
to the one that really has the rules in it.
> Yet the CPAN install of spamassassin uses /usr/share/spamassassin for
> the installation. Surely the install ought to use the same directory
> that sa-update is going to create, or vice-versa?
No. sa-update is optional and writes stuff to its own area separate
from the installation of SA.
In that case I would argue that either (a) running sa-update should
not create a directory when there are no updates to populate it, or
(b) running sa-update should copy the existing set of rules into the
update directory.
You may want to check out http://wiki.apache.org/spamassassin/RuleUpdates
which talks about sa-update, how it works, etc.
I did, before the first time I ran it. That page explains about
setting up channels, gives an example of running sa-update (I didn't
bother to restart spamassassin after I ran it, because it reported
there were no updates available) and goes on to say:
* Currently, for 3.1.1 and 3.2.0, to use any channel for updates
requires that updates.spamassassin.org also be used. This is because
once the update directory exists, the SpamAssassin modules expect to
find all rules in that directory.
Nowhere does it say that it creates this directory and leaves it empty
when there are no updated rules. Nowhere in "man sa-update" does it
say that either. How was I supposed to realize that running sa-update
would leave me with a crippled installation?
