public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jdow" <jdow@earthlink.net>
To: <davids@webmaster.com>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Time to forbid non-subscribers from posting to the list?
Date: Tue, 8 Aug 2006 14:42:29 -0700	[thread overview]
Message-ID: <04b101c6bb33$9131bd00$0225a8c0@Wednesday> (raw)
In-Reply-To: MDEHLPKNGKAHNMBLJOLKIECNNKAB.davids@webmaster.com

From: "David Schwartz" <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.
>>
>> Jeff
> 
> 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.

If you have the luxury of the ability to write personalized rules and
whitelist entries for SpamAssassin it can become a startlingly good
filtering system. And you can tailor the filtering for individual 
sources with meta rules. Processing large numbers of messages through
BAYES and large numbers of rules gets quite time consuming, perhaps
more than vger might want to handle. Processing only a small number
of email accounts for trustworthy people allows one the luxury of
custom rules and individual BAYES filtering. Since a lot of what
one person might consider to be spam is another person's ham this is
a good thing. (And SURBL is a good thing, too. It is remarkably
reliable as long as you're not one of the first receiving a particular
piece of junk. The SpamAssassin "RulesEmporium" has some very nice
anti-spam rule sets, too.)

{^_^}   Joanne

  reply	other threads:[~2006-08-08 21:42 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 [this message]
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
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='04b101c6bb33$9131bd00$0225a8c0@Wednesday' \
    --to=jdow@earthlink.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox