From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "David Miller" <davem@davemloft.net>
Cc: jeff@garzik.org, matti.aarnio@zmailer.org, rlrevell@joe-job.com,
folkert@vanheusden.com, linux-kernel@vger.kernel.org
Subject: Re: VGER does gradual SPF activation (FAQ matter)
Date: Tue, 13 Jun 2006 00:29:46 +0200 [thread overview]
Message-ID: <9a8748490606121529v4fe3c261jd73ebcb6a06f8386@mail.gmail.com> (raw)
In-Reply-To: <20060612.130058.78495098.davem@davemloft.net>
On 12/06/06, David Miller <davem@davemloft.net> wrote:
> From: Jeff Garzik <jeff@garzik.org>
> Date: Mon, 12 Jun 2006 10:52:32 -0400
>
> > Create two simple web pages, one that shows the last 24 hours' worth of
> > LKML posts, and another one that shows the last 24 hours' worth of spam.
> > Allow any user on the Internet to report an LKML post as spam, or
> > alternately, highlight a false positive as not-spam. (perhaps generate
> > one of those wavy-text verify-you-are-a-human graphics)
> >
> > Then you, as admin, only have to click a button that accepts or rejects
> > the submission(s). If you want to scan it yourself for false positives,
> > you just hit the same webpage as everybody else.
> >
> > That feedback is then fed into the bayesian system, to train it using
> > well-known methods.
>
> I like this idea a lot.
It's a lot more sane than SPF, that's for sure.
I'd suggest taking a look at DSPAM (http://dspam.nuclearelephant.com/)
for something like that.
But, there are also other, and even simpler, options.
I've personally found that using some of the build-in anti-spam
features in postfix can be used to stop a lot of spam with almost zero
impact on ham. While some of the features do affect some ham, there
are a few that almost never do, yet they stop quite a bit of spam :
smtpd_client_restrictions =
reject_unauth_pipelining
Reject the mail if the sending server tries to send SMTP commands
ahead of time without first checking if the server supports
pipelining.
I've only ever seen obvious spam sources being rejected by this.
smtpd_helo_required = yes
Mail servers that can't be bothered to send any HELO/EHLO at all are
in my experience only spam sources.
smtpd_helo_restrictions =
reject_invalid_hostname,
This will reject mail from servers that send a hostname in HELO/EHLO
that has bad syntax or invalid characters. I've never seen this one
reject valid senders, but I have seen it reject a lot of spam sources.
Postfix also has other more strict checks you can enable on helo, but
those tend to reject too much valid mail.
strict_rfc821_envelopes = yes
This rejects some spam from spambots that don't know how to generate a
proper mail. I've on occasion seen it hit valid senders, but very
rarely.
smtpd_sender_restrictions =
reject_non_fqdn_sender,
reject_unknown_sender_domain
This will reject mail with senders without a fully qualified name as
well as sender addresses where the sender domain does not have an A or
MX record.
This stops a lot of spam on my servers and I've never had any problems
with it since what's the point of accepting a mail from somewhere that
you can't reply back to...
smtpd_recipient_restrictions =
reject_non_fqdn_recipient,
reject_unknown_recipient_domain
Same as for senders, reject the mail if the recipient domain i not
fully qualified or the recipient domain has no A or MX record.
Implementing these things should have a minimum of impact on ham on
vger, but should stop a fair amount of spam - at least they do for me,
and my servers at work pass hundreds of thousands of messages daily
without users complaining about these settings and I can see in the
logs that they stop quite a lot of junk.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-06-12 22:29 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 22:27 Matti Aarnio
2006-06-10 23:06 ` David Woodhouse
2006-06-11 0:16 ` Rik van Riel
2006-06-11 0:44 ` David Woodhouse
2006-06-11 13:02 ` Theodore Tso
2006-06-11 13:55 ` Rik van Riel
2006-06-11 14:03 ` Avi Kivity
2006-06-12 8:47 ` Matthias Andree
2006-06-12 10:17 ` Neil Brown
2006-06-12 10:35 ` David Woodhouse
2006-06-12 11:07 ` Matthias Andree
2006-06-11 2:24 ` marty fouts
2006-06-11 2:41 ` jdow
2006-06-11 2:58 ` David Schwartz
2006-06-11 5:17 ` jdow
2006-06-12 8:18 ` Bernd Petrovitsch
2006-06-12 8:23 ` jdow
2006-06-12 8:31 ` Bernd Petrovitsch
2006-06-12 9:47 ` Neil Brown
2006-06-12 10:30 ` Alan Cox
2006-06-12 10:33 ` Neil Brown
2006-06-12 17:37 ` Gerhard Mack
2006-06-12 18:14 ` Krzysztof Halasa
2006-06-12 18:46 ` jdow
2006-06-12 19:16 ` Krzysztof Halasa
2006-06-12 21:51 ` Bernd Petrovitsch
2006-06-13 21:12 ` David Woodhouse
2006-06-12 9:53 ` Alan Cox
2006-06-12 10:01 ` Bernd Petrovitsch
2006-06-12 11:14 ` Matthias Andree
2006-06-12 10:58 ` Neil Brown
2006-06-12 11:22 ` Matthias Andree
2006-06-12 11:42 ` Kyle Moffett
2006-06-13 23:32 ` Scott Lockwood
2006-06-13 23:42 ` Kyle Moffett
2006-06-14 0:02 ` Neil Brown
2006-06-14 10:20 ` Matthias Andree
2006-06-16 3:53 ` Kyle Moffett
2006-06-12 8:27 ` Bernd Petrovitsch
2006-06-12 20:25 ` Horst von Brand
2006-06-12 21:10 ` Nick Warne
2006-06-12 22:06 ` Jesper Juhl
2006-06-12 22:12 ` Randy.Dunlap
2006-06-12 23:03 ` jdow
2006-06-13 3:00 ` Horst von Brand
2006-06-13 5:54 ` jdow
2006-06-13 8:36 ` Bernd Petrovitsch
2006-06-13 9:58 ` Marc Perkel
2006-06-13 13:28 ` Horst von Brand
2006-06-13 14:34 ` David Woodhouse
2006-06-13 9:05 ` David Woodhouse
2006-06-13 10:45 ` Matthias Andree
2006-06-13 12:24 ` David Woodhouse
2006-06-13 12:49 ` Matthias Andree
2006-06-13 13:10 ` David Woodhouse
2006-06-13 15:19 ` Marc Perkel
2006-06-13 15:57 ` Auke Kok
2006-06-13 19:54 ` David Woodhouse
2006-06-13 20:31 ` Lennart Sorensen
2006-06-13 20:48 ` David Woodhouse
2006-06-15 17:05 ` Keith Owens
2006-06-15 23:14 ` Wakko Warner
2006-06-13 0:11 ` Phil Oester
2006-06-13 0:26 ` David Miller
2006-06-13 4:18 ` Willy Tarreau
2006-06-13 15:17 ` Joel Jaeggli
2006-06-12 21:43 ` Bernd Petrovitsch
2006-06-13 3:05 ` Horst von Brand
2006-06-13 8:31 ` Bernd Petrovitsch
2006-06-13 10:50 ` Matthias Andree
2006-06-13 13:15 ` Justin Piszcz
2006-06-11 5:09 ` Neil Brown
2006-06-11 5:26 ` jdow
2006-06-11 6:12 ` Willy Tarreau
2006-06-11 16:02 ` Folkert van Heusden
2006-06-11 17:54 ` Lee Revell
2006-06-11 18:54 ` David Miller
2006-06-12 9:09 ` Matthias Andree
2006-06-12 11:32 ` Nikita Danilov
2006-06-12 14:52 ` Jeff Garzik
2006-06-12 20:00 ` David Miller
2006-06-12 22:29 ` Jesper Juhl [this message]
2006-06-12 22:48 ` David Miller
2006-06-12 22:57 ` Jesper Juhl
2006-06-13 3:54 ` VGER does gradual SPF activation (FAQ matter) - Alternative Marc Perkel
2006-06-13 4:51 ` David Miller
2006-06-13 13:41 ` VGER does gradual SPF activation (FAQ matter) Athanasius
2006-06-11 17:31 ` Marc Perkel
2006-06-11 18:50 ` Florian Weimer
[not found] ` <20060611072223.GA16150@flint.arm.linux.org.uk>
2006-06-12 8:32 ` Matti Aarnio
2006-06-12 8:40 ` Russell King
2006-06-12 9:57 ` Neil Brown
2006-06-12 15:55 ` Russell King
2006-06-12 20:06 ` Zwane Mwaikambo
2006-06-12 11:22 ` David Woodhouse
2006-06-12 15:41 ` Simon Oosthoek
2006-06-12 22:55 ` Matthias Andree
2006-06-13 17:41 ` Matti Aarnio
2006-06-12 9:05 ` Matthias Andree
2006-06-12 17:28 ` Matthew Frost
2006-06-13 0:12 ` David Woodhouse
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=9a8748490606121529v4fe3c261jd73ebcb6a06f8386@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=davem@davemloft.net \
--cc=folkert@vanheusden.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®