Shelley Waltz wrote:
> I am running spamassassin with amavisd on RHEL5. I have the perl
> script sa-update run daily. There are updates .cf files written into
> /var/lib/spamassassin/3.002004/updates_spamassassin_org/
>
> and there is a
> /var/lib/spamassassin/3.002004/updates_spamassassin_org.c
I am running spamassassin with amavisd on RHEL5. I have the perl script
sa-update run daily. There are updates .cf files written into
/var/lib/spamassassin/3.002004/updates_spamassassin_org/
and there is a
/var/lib/spamassassin/3.002004/updates_spamassassin_org.cf
I have spamassassin-3.2.4-1.el
Logan Shaw wrote:
For what it's worth, I haven't added my own rules (yet), but
I believe those are done in a separate place, so the fact that
one set is substituted for another shouldn't cause problems.
Yes, local rules go in their own directory, usually /etc/mail/spamassassin
--
Kelson Vibber
On Thu, 22 Jun 2006, Greg McCann wrote:
...all of the rule files (10_misc.cf, 20_advance_fee.cf,
etc...) get installed in /usr/local/share/spamassassin/
However when I do sa-update, all of the updated rules go
to /var/lib/spamassassin/3.001003/updates_spamassassin_org/,
giving me two complete se
When I first install SA, with...
cd Mail-SpamAssassin-*
perl Makefile.PL
make
make install
...all of the rule files (10_misc.cf, 20_advance_fee.cf, etc...) get installed
in /usr/local/share/spamassassin/
However when I do sa-update, all of the updated rules go to
/var/lib/spamassassin/3.001003
