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
ds on what you mean by core rules. Assuming the ones that came with
SpamAssassin, you don't do anything with those. SA just picks them up
automatically from the update directory. If you're talking about rules
you added, then those should be in /etc/mail/spamassassin.
Bret
On Tue, 19 Jun 2007, Robert Fitzpatrick wrote:
On Tue, 2007-06-19 at 18:03 +, Duane Hill wrote:
On Tue, 19 Jun 2007, Robert Fitzpatrick wrote:
Can someone tell me for sure which way this needs to be and how to get
sa-update to look at /usr/local/share/spamassassin again if that is what
I n
So, I should move my core rules to /var/db/spamassassin/the_version
after setting up SA from the ports system? The issue is debug does not
seem to find my core rules under /usr/share, there is no mention of them
in the debug output.
--
Robert
No. Once sa-update has updated /var/db/spamassassin
On Tue, 2007-06-19 at 18:03 +, Duane Hill wrote:
> On Tue, 19 Jun 2007, Robert Fitzpatrick wrote:
> > Can someone tell me for sure which way this needs to be and how to get
> > sa-update to look at /usr/local/share/spamassassin again if that is what
> > I need to do?
>
> I'm using FreeBSD here
On Tue, 19 Jun 2007, Robert Fitzpatrick wrote:
From the beginning I have used /usr/local/share/spamassassin for the .cf
files as this is how the ports system sets up SA on our FreeBSD system.
Sometime ago, someone posted a response to an issue I had at the time
with rules firing that I should b
>From the beginning I have used /usr/local/share/spamassassin for the .cf
files as this is how the ports system sets up SA on our FreeBSD system.
Sometime ago, someone posted a response to an issue I had at the time
with rules firing that I should be using the
default /var/db/spamassassin/ and I wa
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
11 matches
Mail list logo
