David Baron wrote:
On Sunday 14 May 2006 21:24, Andrew wrote:
I have this working fine. However, once that ....03000100001 directory
exists, all my custom rules (i.e. bayes, regex tests, etc) are no longer
working and most all spams get through!
Took it off once again. Something needs be modified before this can be
used.
I just set up sa-update myself. I've downloaded the latest ruleset from
updates.spamassassin.org and restarted spamd. I don't seem to be having
the problem you describe, though. I have the Baysian filter on and some
SARE rulesets in /usr/local/etc/mail/spamassassin and I'm still seeing
hits with them. Here are the options I use when I start spamd.
spamd --siteconfigpath=/usr/local/etc/mail/spamassassin
--pidfile=/var/run/spamd.pid
OK. There is no siteconfigpath in /etc/init.d/spamassassin nor
in /etc/default/spamassassin which gives this is $OPTIONS. It would be easy
enough to try. Put this in which of these files?
Browsing through the Mail::SpamAssassin::Conf man page, I couldn't find
a configuration file parameter equivalent to the --siteconfigpath
command line option for spamd. I'd put it in your
/etc/init.d/spamassassin startup script.
Before I set up sa-update, I also had the --configpath option set to
/usr/local/share/spamassassin. I had to take this out otherwise spamd
wouldn't find the rulesets in /var/lib/spamassassin/3.001001/
This is probably the default. Now it looks first in the version
set /var/lib ..... 3.001001/, Does the siteconfigpath override or add to this
(most probably adds or should) ? Should there be a multiple siteconfigpath?
Symlinks to various directories from the ...3.001001?
Here is what appears to be happening on my system.
1. Because I don't have configpath set, spamd is looking in
/var/lib/spamassassin for rulesets.
2. Because it finds the /var/lib/spamassassin directory, it doesn't
check /usr/local/share/spamassassin where the rulesets distributed with
SpamAssassin reside.
3. Because I have set siteconfigpath, spamd loads extra rulesets and
configuration info from /usr/local/etc/mail/spamassassin.
In my case, what spamd finds in siteconfigpath is definitely used in
addition to what it finds in /var/lib/spamassassin.
I've never tried specifying more than one siteconfigpath. My gut feeling
is that it won't work. I can't think of a reason why I would need more
than one.
Andrew
