Thanks Rainer,
> > Well that certainly forced the use of /etc/mail/spamassassin/local.cf,
> > however now I get no mail filtering what so ever. Its like it
> doesn't know
> > about the rules files.
>
> You may run "spamassassin -D --siteconfigpath=/etc/mail/spamassassin <
> /dev/null 2>&1 | grep
On Sun, Jan 09, 2005 at 12:13:12PM +1100, Paul Grenda wrote:
> > use the "--siteconfigpath=/etc/mail/spamassassin" parameter.
> Well that certainly forced the use of /etc/mail/spamassassin/local.cf,
> however now I get no mail filtering what so ever. Its like it doesn't know
> about the rules fi
> -Original Message-
> From: Rainer Sokoll [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 8 January 2005 8:18 PM
> To: users@spamassassin.apache.org
> Subject: Re: SpamAssassin 3.0.2 Path Problems
>
>
> On Sat, Jan 08, 2005 at 12:18:48PM +1100, Paul Grenda wrote:
>
On Sat, Jan 08, 2005 at 12:18:48PM +1100, Paul Grenda wrote:
> After trying to install Spamassasasin 3.0.2 using the rpmbuild withour
> success, I have managed to install it using perl Makefile.PL, make, make
> install and it seems to have been largely sucessful except it no longer
> seems to be a
> no longer seems to be able to find my local.cf (see another thread on this
> forum).
local.cf seems to have moved around in various installs on various platforms.
Search around and see if there is a default local.cf in some other directory,
perhaps
/etc/mail/spamassassin.
Your problem with t
After trying to install Spamassasasin 3.0.2 using the rpmbuild withour
success, I have managed to install it using perl Makefile.PL, make, make
install and it seems to have been largely sucessful except it no longer
seems to be able to find my local.cf (see another thread on this forum).
Now I thi
