Re: Time to forbid non-subscribers from posting to the list?

From: Matti Aarnio
Date: Wed Aug 09 2006 - 11:06:49 EST

On Wed, Aug 09, 2006 at 04:34:30PM +0200, Folkert van Heusden wrote:
> > > 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 blocklist at vger? Stops quite a
> bit of spam over here (

I have seen these lists classify major ISP relays as spam sources(*),
even classify VGER as one. Their maintenance standards are varying,
some demand ridiculous things out of DNS zone SOA timers, some are
otherwise retarded in their "we are the world police, beware or be
sorry".. and then they simply evaporate into the bit heaven.

(*) ISP user's main relays are spam fan-out sources way more often
than system keepers would like, but very few MTAs provide rate-limits
for anonymous ( = "non autenticated" ) users to keep a high-jacked
Windows machine from being effective spam-sources and utterly killing
the ISP relay.. (See "ASTA Recommendation".)
(Limiting spam-sending to 60 messages per hour of 240 rcpt per hour
can still get the relay to spam lists, but it won't flood internal
queues as badly as completely unlimited feed rates.)

Spamhouse and Spamcop have long(er) existence compared to most
DNS BLs, but still I am utterly worried...
("Many times burned, forever distrustful..")

> Folkert van Heusden
> - multitail is tail on steroids. multiple
> windows, filtering, coloring, anything you can think of

/Matti Aarnio
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at