IETF Logo Mail Archive

Re: IESG Statement on Spam Control on IETF Mailing Lists

Henrik Levkowetz <henrik@levkowetz.com> Mon, 14 April 2008 23:31 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED7FE3A6A39; Mon, 14 Apr 2008 16:31:46 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28B2D3A69DD for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 16:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level:
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[AWL=0.229, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AMsxmP+yJw9 for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 16:31:44 -0700 (PDT)
Received: from merlot.tools.ietf.org (unknown [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 206BB3A69C6 for <ietf@ietf.org>; Mon, 14 Apr 2008 16:31:44 -0700 (PDT)
Received: from localhost ([127.0.0.1]:45332 helo=chardonnay.local) by merlot.tools.ietf.org with esmtp (Exim 4.69) (envelope-from <henrik@levkowetz.com>) id 1JlY9f-0005n3-8T; Tue, 15 Apr 2008 01:32:08 +0200
Message-ID: <4803E977.8080302@levkowetz.com>
Date: Tue, 15 Apr 2008 01:32:07 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
References: <20080414153938.0A5153A6D4D@core3.amsl.com> <4803BDB1.4030005@levkowetz.com> <4803C5D7.7020900@gmail.com> <01MTM8WCXSZK00007A@mauve.mrochek.com> <4803DA2D.9090602@levkowetz.com> <01MTMBYCI1TI00007A@mauve.mrochek.com>
In-Reply-To: <01MTMBYCI1TI00007A@mauve.mrochek.com>
X-Enigmail-Version: 0.95.6
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: ned.freed@mrochek.com, brian.e.carpenter@gmail.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on merlot.tools.ietf.org); SAEximRunCond expanded to false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 2008-04-15 00:35 Ned Freed said the following:
>> On 2008-04-14 23:11 Ned Freed said the following:

> I guess I should be flattered, but really, I fail to see why. Guaranteed bypass
> of moderation is simply an allowed-poster whitelist. 

So it seems to me that you've failed to see the problem.

Anybody who considers themselves a valid poster is supposed to be able to
bypass moderation, challenge-response and spam-filtering.  This would also
include a spammer who considers himself a valid poster.  At the same time,
the IETF lists MUST provide spam control.  I see this as a contradiction in
the announced text.

In other words, if one is not already on a whitelist, how does one get on
to it, automatically, without moderation and challenge-response, while
spam-filtering is still provided?

	Henrik
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email