Im testing spamassassin as a replacement for bogofilter. So far I
have it installed, and am calling it with: /usr/bin/spamd -d -c -m5 -H
-r /var/run/spamd.pid, Im using procmail and have added:
###spamassassin test
:0fw: spamassassin.lock
* < 256000
| spamassassin
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
almost-certainly-spam
# All mail tagged as spam (eg. with a score higher than the set threshold)
# is moved to "probably-spam".
:0:
* ^X-Spam-Status: Yes
/opt/spam/spam
to my procmail script. Looking at the headers on emails coming in I see:
X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on
mail.harrisonburg.k12.va.us
X-Spam-Level:
X-Spam-Status: No, score=-0.1 required=6.0 tests=RCVD_IN_BSP_OTHER
autolearn=ham version=3.1.9
I can also see that there is a spamassassin config file getting
created in each users home directory. The setup was way to easy and I
know that I am missing something in order for it to start grabbing
spam. What am I missing in my config file? I did run the sa-update
and it seems to be working also. My goal is to allow each user to
report as spam emails or report as innocent in horde webmail, and
allow them management of their own spam.
thanks,
ddh
--
Dwayne Hottinger
Network Administrator
Harrisonburg City Public Schools
"Everything should be made as simple as possible, but not simpler."
-- Albert Einstein
"The hottest places in Hell are reserved for those who, in times of moral
crisis, preserved their neutrality."
-- Dante
