Hi Gary,
On Thu, 17 Aug 2006, Gary V wrote:
I would suggest installing a newer version from backports.org.
Thanks for the suggestion! I was not aware of backports.org at all.
I could also go up to testing or *gasp* unstable, but I really don't want
to. I'm not a very good system admin and don't really know how to fix some
things when they break. Also would rather have a working system than a
up-to-the-minute system.
read this, it may validate your choice to stay stable:
http://www200.pair.com/mecham/spam/kernel.html
I was wondering whether it is possible to update the rules and not the
software. I guess not? spamassassin in Debian is one package? But
anyway, I'll do your backports.org suggestion -- thanks!
Yes, once you are using 3.1.1 or greater, run 'sa-update' - you will get a
complete set of up-to-date rules.
You may need to install gnupg and import the signing key, this is how I did
it:
apt-get install gnupg
cd /etc/spamassassin
wget http://spamassassin.apache.org/released/GPG-SIGNING-KEY
gpg --import GPG-SIGNING-KEY
You might consider a cron job for sa-update:
28 15 * * * /usr/bin/sa-update && /usr/bin/spamassassin --lint &&
/etc/init.d/spamd restart
Also, once you upgrade to 3.1.x, edit v310.pre to enable DCC Plugin (if you
use it and you agree to the license terms) and Razor2 Plugin.
How are you integrating spamassassin?
It is running as a daemon as the spamc/spamd combination. I use fetchmail
to get mail from the server, and then procmail processes it. I call spamc
from within procmail according to the sample .procmailrc that accompanys
the package.
Ray
Gary V
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
