public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Folkert van Heusden <folkert@vanheusden.com>,
	David Schwartz <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: Wed, 9 Aug 2006 12:28:48 -0400	[thread overview]
Message-ID: <20060809162848.GA12306@animx.eu.org> (raw)
In-Reply-To: <20060809150851.GH3021@mea-ext.zmailer.org>

Matti Aarnio wrote:
> 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.

Be nice if those that get listed and have real spammer problems actually
clean up.  Some don't care.

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

Personally, I use several RBLs, spamhaus and spamcop being 2 of those.

If it's possible, one suggesting I have is to filter out some HELO strings.
I have 3 of those in my suggestion:
1) strings consisting of either the IP or the hostname of the receiving
server (vger.kernel.org I assume)
2) any helo that does not contain a dot.  I do not know the impact on the
list if that were used
3) tom.com and 163.com.  I have noticed that these are very common in some
of the spam on the list and others that I am on.

These are only suggestions and I do not expect anyone to blindly use them. 
I do use these methods and others, however, I am the only user of the mail
server in which I'm sending this email.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???

  parent reply	other threads:[~2006-08-09 16:32 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
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 [this message]
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=20060809162848.GA12306@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=davids@webmaster.com \
    --cc=folkert@vanheusden.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.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