I added a cron job on my system to handle some of the process of updating
sa rules. It runs every night, looks roughly like this:
sa-update --channel updates.spamassassin.org --channel
sought.rules.yerp.org && /etc/init.d/spamd restart
Additionally I have another cron job for a simple statistics page that
greps mail logs. Output is available on the web:
http://zokum.sysrq.no/spam/ It's in norwegian. The three last statistics
lines are 'spam' 'non-flagged' and outbound mail.
Stats are handy to point to since some users complain that so much spam is
going through. Typically out of 1500 connections to the server, about 30
mails are delivered and not flagged as spam.
I have found that people are much more tolerant of a bit of spam getting
through if they know there is a certain level of filtering, and that they
themselves can see that there are filters and measures in place to reduce
spam and can check for themselves.
In addition to that I have a manual script i run every now and then to
train ham and spam from handfed mailboxes sorted by competent people.
These contain thousands of mails, mostly in norwegian. This step is very
important, and is a good addition to sa-rules updates. I judge these steps
too risky for automation. I tend to run this whenever I have classified a
lot of spam myself.
My biggest problem on this server is norwegian language spam. This isn't
caught by a lot of the rules, and I had to write my own rules.
If I wanted to make things a bit more professional and be stricter about
uptime, I would set up Munin to check the status of SA and alert me in
case of downtime.
PS: I lost the mail address of the guy who wanted a copy of my norwegian
rule set. If you see this post, send me a mail, I think you read this list
:)
--
Kim Roar Foldøy Hauge
Event:Presse - The Gathering 2016
webmas...@samfunnet.no
Root@HC,HX,JH,LZ,OT,P,VH
