From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: [9fans] need help with improving my spam filtering
Date: Sun, 15 Oct 2006 16:07:05 +0100 [thread overview]
Message-ID: <2ca63ae02fe6fd23697275bb72c31a7b@tombob.com> (raw)
Hi,
I have set up my Plan 9 box to receive email for myself. It's a very
simple setup with no relaying, just for my own little maildrop.
This year the spam started to arrive in slightly more annoying
quantities, and a few months ago I managed to set up the bayes
filtering for my email. This worked for a while, but now I am getting
more and more spam getting through (mostly because of the anti-bayes
mechanism of hiding the spam in a picture and sending it together with
random but apparently OK text).
So, I'd like to expand my spam stopping capabilities. I have read
smtpd(6), ratfs(4), and scanmail(8) but find myself slightly at sea on
how to combine these to allow me to filter out some of the more
obvious spam.
If I understand correctly, I can start ratfs(4) and since it'll read
the default /mail/lib/blocked file my smtpd(6) will then block some
emails. I can also replace qer(8) with scanmail(8) in my
/mail/lib/qmail and therefore block out even more emails.
The thing I don't yet fully grasp is how I manage the resulting
holding queues and log files and how I properly administer the
/mail/lib/blocked and /mail/lib/patterns files.
Can anyone point me in the right direction for learning more on how to
use ratfs(4) and scanmail(8) for effective spam filtering?
Robby
PS I guess an alternative approach would be for me to use fresh email
addresses for mailing lists every so often. But that feels
shortsighted somehow.
next reply other threads:[~2006-10-15 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 15:07 Robert Raschke [this message]
2006-10-15 15:19 ` andrey mirtchovski
2006-10-15 15:36 ` Russ Cox
2006-10-15 15:41 ` andrey mirtchovski
2006-10-15 15:39 ` Heiko Dudzus
2006-10-15 22:21 ` Steve Simon
2006-10-17 7:19 ` Lyndon Nerenberg
2006-10-17 7:56 ` Steve Simon
2006-10-17 14:55 ` Heiko Dudzus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ca63ae02fe6fd23697275bb72c31a7b@tombob.com \
--to=rrplan9@tombob.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).