mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
To: Rik van Riel <riel@redhat.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	Jan De Luyck <lkml@kcore.org>, <linux-kernel@vger.kernel.org>,
	<postmaster@vger.kernel.org>
Subject: Re: vger.kernel.org is listed by spamcop
Date: 22 Apr 2004 10:22:00 +0900	[thread overview]
Message-ID: <buollko4xjb.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.44.0404211034280.1735-100000@chimarrao.boston.redhat.com>

Rik van Riel <riel@redhat.com> writes:
> I'm certain than vger got listed on spamcop due to linux-kernel
> subscribers reporting to spamcop some of the spam that leaked onto
> lkml, through Matti's strict filters.

Does that mean that spamcop does no verification of user reports?

I was under the impression that it's fairly easy to automatically check
whether a particular host is an open-relay or not, so it would seem kind
of irresponsible for spamcop not to do this if some people are relying
on their lists to do blocking (even if there's a disclaimer saying not
to do that, clearly people are ignorant or dumb, so why not play it safe?).

-Miles
-- 
P.S.  All information contained in the above letter is false,
      for reasons of military security.

  reply	other threads:[~2004-04-22  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  5:22 Jan De Luyck
2004-04-21  8:44 ` Matti Aarnio
2004-04-21  8:56   ` Miles Bader
2004-04-21 10:07     ` Erik Mouw
2004-04-21 13:56     ` Graham Murray
2004-04-21 14:17       ` Richard B. Johnson
2004-04-21 14:39     ` Rik van Riel
2004-04-22  1:22       ` Miles Bader [this message]
2004-04-22  1:30         ` Rik van Riel
2004-04-22 16:02           ` Jan Knutar
2004-04-22 14:38         ` Timothy Miller
2004-04-21 15:34     ` H. Peter Anvin
2004-04-21 14:32 ` Rik van Riel

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=buollko4xjb.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=miles@gnu.org \
    --cc=postmaster@vger.kernel.org \
    --cc=riel@redhat.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®