From: Folkert van Heusden <folkert@vanheusden.com>
To: David Schwartz <davids@webmaster.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Time to forbid non-subscribers from posting to the list?
Date: Wed, 9 Aug 2006 16:34:30 +0200 [thread overview]
Message-ID: <20060809143429.GD5815@vanheusden.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKIECNNKAB.davids@webmaster.com>
> > The kernel developers who need to keep the barrier to bug reports low
> > like the current policy.
> > Get a good spam filter, I only get 1-2 pieces a day in my LKML folder.
> How is everyone individually spam filtering better than one central spam
> filter? More likelihood that at least one relevent person will get the bug
> report? Certainly a single central spam filter can get more resources aimed
> at it to make sure it doesn't suppress anything important.
What about just using the spamhaus.org blocklist at vger? Stops quite a
bit of spam over here (http://keetweej.vanheusden.com/nspam_graph.png).
Folkert van Heusden
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next prev parent reply other threads:[~2006-08-09 14:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 11:07 Time to forbid non-subscribers from posting to the list? Alexey Zaytsev
2006-08-08 11:13 ` Jeff Garzik
2006-08-08 19:00 ` David Schwartz
2006-08-08 21:42 ` jdow
2006-08-09 8:51 ` Matthias Andree
2006-08-09 11:22 ` Erik Mouw
2006-08-08 22:00 ` Lee Revell
2006-08-09 14:34 ` Folkert van Heusden [this message]
2006-08-09 15:08 ` Matti Aarnio
2006-08-09 15:35 ` D. Hazelton
2006-08-09 20:38 ` David Lang
2006-08-09 16:28 ` Wakko Warner
2006-08-08 11:15 ` Neil Brown
2006-08-08 11:41 ` Alexey Zaytsev
2006-08-08 19:07 ` Willy Tarreau
2006-08-08 11:23 ` Andi Kleen
2006-08-08 11:47 ` Alexey Zaytsev
2006-08-08 11:55 ` Jes Sorensen
2006-08-08 12:03 ` Alexey Zaytsev
2006-08-08 14:47 ` Matti Aarnio
2006-08-08 21:34 ` jdow
2006-08-08 12:02 ` Andi Kleen
2006-08-08 14:39 ` Alan Cox
2006-08-08 19:16 ` Willy Tarreau
2006-08-08 20:25 ` Lee Revell
2006-08-08 21:23 ` Kyle Moffett
2006-08-09 6:47 ` Jan Engelhardt
2006-08-09 8:04 ` Jes Sorensen
2006-08-09 15:47 ` Geert Uytterhoeven
2006-08-10 14:58 ` Athanasius
2006-08-08 22:16 ` David Miller
2006-08-09 8:45 ` Helge Hafting
[not found] <6HxDe-4Ea-1@gated-at.bofh.it>
[not found] ` <6HxWJ-52E-19@gated-at.bofh.it>
[not found] ` <6HAKV-TE-15@gated-at.bofh.it>
[not found] ` <6HFAX-8dl-31@gated-at.bofh.it>
[not found] ` <6HGni-Y3-19@gated-at.bofh.it>
2006-08-08 22:29 ` Bodo Eggert
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=20060809143429.GD5815@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.