public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Miles Bader <miles@gnu.org>
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: Wed, 21 Apr 2004 12:07:38 +0200	[thread overview]
Message-ID: <20040421100738.GC4270@harddisk-recovery.com> (raw)
In-Reply-To: <buoad15hfp2.fsf@mcspd15.ucom.lsi.nec.co.jp>

On Wed, Apr 21, 2004 at 05:56:41PM +0900, Miles Bader wrote:
> Matti Aarnio <matti.aarnio@zmailer.org> writes:
> > The only way to handle this is to have smarter people, who are always
> > vigilant enough to look deeply into the message headers and do realize
> > that some spam has leaked thru VGER's lists.
> 
> I'm confused -- the spamcopy info page you listed implies that hosts are
> listed if they are an _open relay_, which is a completely different
> thing from `spam leaking though VGER's lists.'

Vger is not an open relay:

% telnet vger.kernel.org smtp
Connected to vger.kernel.org.
Escape character is '^]'.
220 vger.kernel.org ZMailer Server 2.99.57-pre1 #11 ESMTP ready at Wed, 21 Apr 2004 05:56:30 -0400
EHLO harddisk-recovery.com
250-vger.kernel.org expected "EHLO xxx.xxx.xxx"
250-SIZE 0
250-8BITMIME
250-PIPELINING
250-CHUNKING
250-ENHANCEDSTATUSCODES
250-DSN
250-X-RCPTLIMIT 10000
250-ETRN
250 HELP
MAIL FROM: <>
250 2.0.0 Ok (sourcechannel 'error' accepted) Ok
RCPT TO: <erik@harddisk-recovery.com>
550 5.7.1 Your IP address [xx.xx.xx.xx] is not allowed to relay to email address <erik@harddisk-recovery.com> via our server; MX rule

Spamcop is wrong. Some spammer targeted one of the lists on vger. That
doesn't make vger an open relay.

> If VGER actually is an open relay, that's very bad, but presumably
> something easily solved by the machine's maintainers.  Some spam getting
> through to VGER list recipients, on the other hand, is just annoying
> (and certainly shouldn't be the cause of any blacklisting).
> 
> The spamcop report page seems to say that the listings are due to user
> reports; could the real problem be clueless users who don't understand
> the difference above?

Yes.


Erik

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

  reply	other threads:[~2004-04-21 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  5:22 vger.kernel.org is listed by spamcop Jan De Luyck
2004-04-21  8:44 ` Matti Aarnio
2004-04-21  8:56   ` Miles Bader
2004-04-21 10:07     ` Erik Mouw [this message]
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
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=20040421100738.GC4270@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kcore.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=miles@gnu.org \
    --cc=postmaster@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