9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] need help with improving my spam filtering
Date: Sun, 15 Oct 2006 17:39:47 +0200	[thread overview]
Message-ID: <d3ed6a6d8e51b4c70e543a2d324f9621@voidness.de> (raw)
In-Reply-To: <2ca63ae02fe6fd23697275bb72c31a7b@tombob.com>

> 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).

Same here.  I made a hold rule for this in /mail/lib/patterns, allowing
only some people and lists to send GIFs. Works for the moment but
could be too restrictive.

> 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.  

Based on the connecting IP address and originating account, yes.

> I can also replace qer(8) with scanmail(8) in my
> /mail/lib/qmail and therefore block out even more emails.

Based on the content of the mail.  Because you said, it's just for
your own little maildrop, be aware that incoming mail can only be
filtered with scanmail(8) when it gets resent (and queued) to your own
system with the little trick discussed in this thread:

http://9fans.net/archive/2002/03/257

> 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.

Greylisting is another option.  (When I saw in the source, that
greylist.c can deal with entire whitelisted subnets, it was an option
for me again)

Heiko



  parent reply	other threads:[~2006-10-15 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-15 15:07 Robert Raschke
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 [this message]
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=d3ed6a6d8e51b4c70e543a2d324f9621@voidness.de \
    --to=heiko.dudzus@gmx.de \
    --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).