Hmm, perhaps I spoke to soon. It's entirely possible Debian has modified
the source and configuration to look in those directories.
If you're using Debian's version, try SpamAssassin -tD and see what paths
the copy you have REALLY uses.
Even though I disagree with the license of djgbdns, I can
erm, how did you install SpamAssassin?
the numbered configs should have been installed to /usr/share/spamassassin
or /usr/local/share/spamassassin. Not etc.
At 02:49 PM 11/15/2002 -0500, Tom Allison wrote:
Matt Kettler wrote:
try /etc/mail/spammassassin/local.cf
AFAIK /etc/spamassassin/local.cf
Matt Kettler wrote:
try /etc/mail/spammassassin/local.cf
AFAIK /etc/spamassassin/local.cf is the wrong spot and is not checked by
spamassassin.
You can debug what paths SA is using to get your rule files by running
spamsassassin -tD
the first few lines of debug output will tell you what file
Matt Kettler wrote:
try /etc/mail/spammassassin/local.cf
AFAIK /etc/spamassassin/local.cf is the wrong spot and is not checked by
spamassassin.
COOL!
This is either a problem with:
Old Version
or
Debian
Debian sometimes has some weird policies...
--
[It is] best to confuse only one issue a
try /etc/mail/spammassassin/local.cf
AFAIK /etc/spamassassin/local.cf is the wrong spot and is not checked by
spamassassin.
You can debug what paths SA is using to get your rule files by running
spamsassassin -tD
the first few lines of debug output will tell you what files it opened.
At 09:2
Did you restart spamd after you made the changes?
On Fri, 15 Nov 2002, Tom Allison wrote:
> tallison@penguin:~$ cat /etc/spamassassin/local.cf
> # This is the right place to customize your installation of
> SpamAssassin.
> # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
> # t
tallison@penguin:~$ cat /etc/spamassassin/local.cf
# This is the right place to customize your installation of
SpamAssassin.
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
###
#
rewrite_subje
