Awesome thanks.
the output showed
[3887] dbg: config: using "/etc/mail/spamassassin" for site rules pre files
[3887] dbg: config: read file /etc/mail/spamassassin/init.pre
[3887] dbg: config: read file /etc/mail/spamassassin/v310.pre
[3887] dbg: config: read file /etc/mail/spamassassin/v312.pre
[3887] dbg: config: read file /etc/mail/spamassassin/v320.pre
[3887] dbg: config: using "/var/lib/spamassassin/3.002002" for sys rules
pre files
[3887] dbg: config: read file
/var/lib/spamassassin/3.002002/saupdates_openprotect_com.pre
[3887] dbg: config: using "/var/lib/spamassassin/3.002002" for default
rules dir
[3887] dbg: config: read file
/var/lib/spamassassin/3.002002/saupdates_openprotect_com.cf
[3887] dbg: config: read file
/var/lib/spamassassin/3.002002/sought_rules_yerp_org.cf
[3887] dbg: config: read file
/var/lib/spamassassin/3.002002/updates_spamassassin_org.cf
which seems to me that it is actually loading up the correct files - yet
when i do a test on a piece of mail which should hit heaps of rules
especially the sought_rules it is not hitting at all.
Are there any other tests I can do?
Kate
Matt Kettler wrote:
Kathryn Kleinschafer wrote:
Hi all,
My installation of spamassassin seems to have stopped using all the
rules I have added when checking email. They now reside in
/var/lib/spamassassin/3.002002
I'm trying to run spamassassin -D --lint and output it to say
test.txt so that I can see it all later and try and trouble shoot why
its not using the rules.
Can anyone tell me how I can do this or if there is a better way to
check why they are not working.
The debug output goes to stderr. you need to redirect it with 2>
instead of >
ie: spamassassin -D --lint 2> output.txt
