On Tue, 19 Jun 2007, Robert Fitzpatrick wrote:
On Tue, 2007-06-19 at 18:03 +0000, 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 and as of SA 3.2.0,
/var/db/spamassassin/the_version is where rules should show up after
sa-update is ran without the --updatedir parameter. Prior, it placed the
rules in /var/lib/spamassassin/the_version.
Thanks, yes, actually, the first time it happened, it was /var/lib now
that you mention it.
/usr/local/share/spamassassin has the potential for getting overwritten on
future updates. Therefore it would be advisable not to make changes
within.
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.
You shouldn't have to move anything.
The rules in /usr/local/share/spamassassin are not read in if rules exist
in /var/db/spamassassin/the_version.
