On 5/13/06, Bart Schaefer <[EMAIL PROTECTED]> wrote:
I think there's some kind of conflict between sa-update and
RulesDuJour that has borked my spamassassin installation, but I can't
figure out how.
Apparently the conflict is only that RDJ restarts spamd automatically,
but sa-update does not.
What? The default rules dir is supposed to be
/usr/share/spamassassin/.
I finally grepped "spamassasin" itself and found:
Default configuration data is loaded from the first existing directory
in:
/var/lib/spamassassin/3.001001
/usr/share/spamassassin
/usr/share/spamassassin
/usr/local/share/spamassassin
/usr/share/spamassassin
(Why is /usr/share/spamassassin in that list three times?)
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
notice this at first because spamd didn't restart after sa-update, and
RDJ didn't do anything new until yesterday. (This is a fairly recent
SA reinstall, and an even more recent RDJ install.)
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?
