Custom spamassassin rules files

[Stephen Swaney]

Chris,

Try:

spamassassin -D -p /etc/MailScanner/spam.assassin.prefs.conf  --lint

where -P <[dir]/spam.assassin.prefs.conf> is correct path to
spam.assassin.prefs.conf on your system. You should see some lines like:

debug: using "/usr/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: using "/root/.spamassassin" for user state dir

If the .cf files are in one rules dir listed by your system, check the
permissions on the files.

Steve

Stephen Swaney
President
Fortress Systems Ltd.
Steve.Swaney at FSL.com


> -----Original Message-----
> From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
> Behalf Of Chris Kissinger
> Sent: Wednesday, January 14, 2004 3:52 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Custom spamassassin rules files
>
> Okay... I give up. I can not trace why whese rules aren't kicking in.
>
> I've tried to add the popcorn, chickenpox, and weeds rules that are out
> there. I've thrown the cf files in both /etc/mail/spamassassin/ and
> /usr/share/spamassassin/ trying to make this work. There have been plenty
> of
> spams that should have triggered these but it just isn't working.
>
> Setup has MailScanner running on a gateway sendmail server so nothing is a
> true "local" address. Mail is definately being scanned, just not picking
> up
> the custom rules.
>
> I'm just at a loss why this isn't working, trying to stay away from
> needing
> to add these to spam.assassin.prefs.conf but I have no other solutions.
>
> Any ideas would be helpful.
>
> Thanks,
> Chris
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> Fortress Systems Ltd.
> www.fsl.com
>