From Jose-Marcio.Martins@mines-paristech.fr  Tue Mar  1 00:17:33 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB6363A6A43 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level: 
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 m3sFcfdbmuSR for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:17:31 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id D0A013A6AC9 for <asrg@irtf.org>; Tue,  1 Mar 2011 00:17:29 -0800 (PST)
Received: from localhost.localdomain (bororo [10.3.5.15]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p218IUc4016532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 09:18:30 +0100 (MET)
Message-ID: <4D6CABE3.3010609@mines-paristech.fr>
Date: Tue, 01 Mar 2011 09:18:43 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net> <A.1PuJrA-000L1N-GD@smtp-ext-layer.spamhaus.org>
In-Reply-To: <A.1PuJrA-000L1N-GD@smtp-ext-layer.spamhaus.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at cascavel with ID 4D6CABD6.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6CABD6.000 from bororo/bororo/10.3.5.15/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:17:33 -0000

+1 in favor of 07 draft.

(Sorry for top posting... no need to reed the rest).

Jose-Marcio

Steve Linford wrote:
> On 28 Feb 2011, at 23:49, Richard Welty wrote:
>
>> please list me as being in favor of this draft.
>>
>> richard
>
> I also am in favour of the 07 draft. So if this is a vote, here's mine.
>
>    Steve Linford
>    The Spamhaus Project
>    http://www.spamhaus.org
>
>
>
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg


-- 
  ---------------------------------------------------------------
  Jose Marcio MARTINS DA CRUZ           http://j-chkmail.ensmp.fr
  Ecole des Mines de Paris
  60, bd Saint Michel                      75272 - PARIS CEDEX 06
  mailto:Jose-Marcio.Martins@mines-paristech.fr

From soruk@eridani.co.uk  Tue Mar  1 00:29:21 2011
Return-Path: <soruk@eridani.co.uk>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D4693A69FA for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 3LPyBEFzHbc9 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:29:21 -0800 (PST)
Received: from eridani.co.uk (eridanilinux.demon.co.uk [62.49.18.88]) by core3.amsl.com (Postfix) with ESMTP id 9C0033A69C2 for <asrg@irtf.org>; Tue,  1 Mar 2011 00:29:20 -0800 (PST)
Received: from Kozue.int.eridani.co.uk (Kozue.int.eridani.co.uk [192.168.96.240]) by eridani.co.uk (8.14.4/8.14.4) with ESMTP id p218UJww018278 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 08:30:19 GMT
Date: Tue, 1 Mar 2011 08:30:19 +0000 (GMT)
From: Michael McConnell <soruk@eridani.co.uk>
X-X-Sender: soruk@Kozue.int.eridani.co.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <4D6C6254.3080903@thoroquel.org>
Message-ID: <alpine.LFD.2.00.1103010829560.24437@Kozue.int.eridani.co.uk>
References: <4D6C265E.1060101@averillpark.net> <4D6C3FFA.6050407@jdmc.org> <4D6C4B90.1090300@FahQ2.com> <20110301014303.GA2536@gsp.org> <4D6C6254.3080903@thoroquel.org>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
Organization: Eridani Star System
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:29:21 -0000

On Mon, 28 Feb 2011, Joe Sniderman wrote:

> On 02/28/2011 08:43 PM, Rich Kulawiec wrote:
>>
>> I'm in favor of the BCP with its current wording.  Not that I completely
>> agree with every last bit of it, but I think it's an awfully good first
>> stake-in-the-ground, and that we should plant it, take a deep breath,
>> then start thinking and debating about what the second stake should
>> look like.
>
> +1
>
> While I'm not 100% pleased with the current wording of the conflict of
> interest section, it is close enough IMHO. Count me in favor of the BCP
> (with its current text) as well.

+1.

-- Michael McConnell
    Eridani Star System

From skull@bofhland.org  Tue Mar  1 00:35:30 2011
Return-Path: <skull@bofhland.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E6CA3A69AD for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:35:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.801
X-Spam-Level: 
X-Spam-Status: No, score=-1.801 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_RAND_LETTRS4=0.799]
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 hxDr9LPhZAwW for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:35:29 -0800 (PST)
Received: from mithrandir.bofhland.org (mithrandir.bofhland.org [IPv6:2a02:9a8:94::b]) by core3.amsl.com (Postfix) with ESMTP id BED253A6969 for <asrg@irtf.org>; Tue,  1 Mar 2011 00:35:28 -0800 (PST)
Received: from zarathustra.local (zarathustra.spin.it [IPv6:2a02:9a8:1:100::ff3c]) by mithrandir.bofhland.org (Postfix) with ESMTPSA id 50B2660044 for <asrg@irtf.org>; Tue,  1 Mar 2011 09:36:27 +0100 (CET)
Message-ID: <4D6CB005.8040609@bofhland.org>
Date: Tue, 01 Mar 2011 09:36:21 +0100
From: "Emanuele Balla (aka Skull)" <skull@bofhland.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net> <4D6C3FFA.6050407@jdmc.org>	<4D6C4B90.1090300@FahQ2.com> <20110301014303.GA2536@gsp.org>	<4D6C6254.3080903@thoroquel.org> <alpine.LFD.2.00.1103010829560.24437@Kozue.int.eridani.co.uk>
In-Reply-To: <alpine.LFD.2.00.1103010829560.24437@Kozue.int.eridani.co.uk>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:35:30 -0000

On 3/1/11 9:30 AM, Michael McConnell wrote:
> On Mon, 28 Feb 2011, Joe Sniderman wrote:
> 
>> On 02/28/2011 08:43 PM, Rich Kulawiec wrote:
>>>
>>> I'm in favor of the BCP with its current wording.  Not that I completely
>>> agree with every last bit of it, but I think it's an awfully good first
>>> stake-in-the-ground, and that we should plant it, take a deep breath,
>>> then start thinking and debating about what the second stake should
>>> look like.
>>
>> +1
>>
>> While I'm not 100% pleased with the current wording of the conflict of
>> interest section, it is close enough IMHO. Count me in favor of the BCP
>> (with its current text) as well.
> 
> +1.

Add me too.

-- 
Paranoia is a disease unto itself. And may I add: the person standing
next to you may not be who they appear to be, so take precaution.
-----------------------------------------------------------------------------
http://bofhskull.wordpress.com/

From matthias@leisi.net  Tue Mar  1 00:47:56 2011
Return-Path: <matthias@leisi.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 190A63A6ACD for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level: 
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 q9p6FP2s3Fvv for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 00:47:55 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id 4F57A3A69FA for <asrg@irtf.org>; Tue,  1 Mar 2011 00:47:55 -0800 (PST)
Received: by vws16 with SMTP id 16so4571167vws.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 00:48:57 -0800 (PST)
Received: by 10.52.99.100 with SMTP id ep4mr5588235vdb.145.1298969337308; Tue, 01 Mar 2011 00:48:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.183.66 with HTTP; Tue, 1 Mar 2011 00:48:37 -0800 (PST)
In-Reply-To: <4D6CB005.8040609@bofhland.org>
References: <4D6C265E.1060101@averillpark.net> <4D6C3FFA.6050407@jdmc.org> <4D6C4B90.1090300@FahQ2.com> <20110301014303.GA2536@gsp.org> <4D6C6254.3080903@thoroquel.org> <alpine.LFD.2.00.1103010829560.24437@Kozue.int.eridani.co.uk> <4D6CB005.8040609@bofhland.org>
From: Matthias Leisi <matthias@leisi.net>
Date: Tue, 1 Mar 2011 09:48:37 +0100
Message-ID: <AANLkTim3J55zhTZ-ije0upRKZ2UF43uq8M==0CZeOk8U@mail.gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 08:47:56 -0000

>>> +1
>>>
>>> While I'm not 100% pleased with the current wording of the conflict of
>>> interest section, it is close enough IMHO. Count me in favor of the BCP
>>> (with its current text) as well.
>>
>> +1.
>
> Add me too.

+1, including the above paragraph.

-- Matthias

From graeme@graemef.net  Tue Mar  1 01:15:28 2011
Return-Path: <graeme@graemef.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A0E33A69CF for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 01:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 7ZkE2a4ueLQb for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 01:15:27 -0800 (PST)
Received: from boom.graemef.net (boom.graemef.net [82.113.154.29]) by core3.amsl.com (Postfix) with ESMTP id 6D73D3A692A for <asrg@irtf.org>; Tue,  1 Mar 2011 01:15:27 -0800 (PST)
Received: from squonk.lut.ac.uk ([131.231.87.200]) by boom.graemef.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <graeme@graemef.net>) id 1PuLgy-0001VC-Bi for asrg@irtf.org; Tue, 01 Mar 2011 09:16:29 +0000
From: Graeme Fowler <graeme@graemef.net>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <20110301014303.GA2536@gsp.org>
References: <4D6C265E.1060101@averillpark.net> <4D6C3FFA.6050407@jdmc.org> <4D6C4B90.1090300@FahQ2.com>  <20110301014303.GA2536@gsp.org>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 01 Mar 2011 09:16:25 +0000
Message-ID: <1298970985.5587.0.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 (2.28.3-1.fc12) 
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 09:15:28 -0000

On Mon, 2011-02-28 at 20:43 -0500, Rich Kulawiec wrote:
> I'm in favor of the BCP with its current wording.  Not that I completely
> agree with every last bit of it, but I think it's an awfully good first
> stake-in-the-ground, and that we should plant it, take a deep breath,
> then start thinking and debating about what the second stake should
> look like.

It's not often I have agreed with RSK word for word :) but I agree with
that.

Graeme (representing the vastly smaller end of the scale)


From groups@digital-z.com  Tue Mar  1 02:27:12 2011
Return-Path: <groups@digital-z.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F8793A67A4 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 02:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 amUd2rG0GAoU for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 02:27:11 -0800 (PST)
Received: from onefish.servers.nj.binarymonkey.com (mail.digital-z.com [IPv6:2001:470:1f07:769:1:dead:beef:cafe]) by core3.amsl.com (Postfix) with ESMTP id 213A83A67A2 for <asrg@irtf.org>; Tue,  1 Mar 2011 02:27:10 -0800 (PST)
Received: from onefish.servers.nj.binarymonkey.com (localhost [127.0.0.1]) by onefish.servers.nj.binarymonkey.com (BinaryMonkey-MX) with ESMTP id 2D6E29DAD for <asrg@irtf.org>; Tue,  1 Mar 2011 05:28:10 -0500 (EST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=digital-z.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=diz; b=Q+iFpOx dh0y7bj/4uEsC1p0l13yyiH3bP/rIYLFRQb+/JblmK1qy4rvOD4MBbvvh0BCwc/A NXn+dO47OPcHCfot4YiBlzcjODp0wcLZvGPocQyLaZRH/2D9x8Ov+01QkXu926OA Cdwa8/3bYBDbe68R6T37HGBzP57UaoIM843w=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=digital-z.com; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s=diz; bh=+ R4pIxq9O2wPa1qzB62FkfIFMkVMSMCSPSfkctHVvdQ=; b=SkWb6ckijZs3IUpWx 7aeJjfe3SIA5kEGWPcPpsGplkTlAVXoqvDFpclpaYPw1wSP/RLfsS6ciV22ZEWep NtwYYb85+yd2Y9YxW9obxyQdsZgIV8gqf14fuMZokqUSAslWSXv/Dq7SN4DD2bxD s+ex3nUqfY8f4a7rILAeFwzziE=
Received: from [10.10.253.254] (75-175-183-126.blng.qwest.net [75.175.183.126]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by onefish.servers.nj.binarymonkey.com (BinaryMonkey-MX) with ESMTPSA id BB2019DAB for <asrg@irtf.org>; Tue,  1 Mar 2011 05:28:09 -0500 (EST)
Message-ID: <4D6CCA33.1050401@digital-z.com>
Date: Tue, 01 Mar 2011 03:28:03 -0700
From: Blaine Fleming <groups@digital-z.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<A.1PuJrA-000L1N-GD@smtp-ext-layer.spamhaus.org> <4D6CABE3.3010609@mines-paristech.fr>
In-Reply-To: <4D6CABE3.3010609@mines-paristech.fr>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 10:27:12 -0000

ditto

--Blaine

On 3/1/2011 1:18 AM, Jose-Marcio Martins da Cruz wrote:
> 
> +1 in favor of 07 draft.
> 
> (Sorry for top posting... no need to reed the rest).
> 
> Jose-Marcio
> 
> Steve Linford wrote:
>> On 28 Feb 2011, at 23:49, Richard Welty wrote:
>>
>>> please list me as being in favor of this draft.
>>>
>>> richard
>>
>> I also am in favour of the 07 draft. So if this is a vote, here's mine.
>>
>>    Steve Linford
>>    The Spamhaus Project
>>    http://www.spamhaus.org
>>
>>
>>
>>
>>
>> _______________________________________________
>> Asrg mailing list
>> Asrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/asrg
> 
> 


From vesely@tana.it  Tue Mar  1 03:42:32 2011
Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2969B3A67AF for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 03:42:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.617
X-Spam-Level: 
X-Spam-Status: No, score=-4.617 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 JxEB3wGCpbC7 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 03:42:31 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 03ECD3A67AD for <asrg@irtf.org>; Tue,  1 Mar 2011 03:42:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1298979808; bh=s3DULS1edpGB3Rq06YGnSEBlfvDRoJTkHYOLLbymwJE=; l=993; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=ZeHgTvAbBxdkBDIBjvGF+Dm8sP6kfNENM9BFtX3WpzIeWIA+BTebF8jKn7ytHQ+9y pTQJMbBSmX1KxBINU0wp/hAHYEb2HIxR0InLZvQK4A2TWE4NrnJ+b2vodBCJk7cZUt 5NxXkOcX2jr1tsf/G0Q8d2Tj3xEoXdlNk4O8WOjg=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 01 Mar 2011 12:43:28 +0100 id 00000000005DC039.000000004D6CDBE0.00002225
Message-ID: <4D6CDBE0.1010604@tana.it>
Date: Tue, 01 Mar 2011 12:43:28 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110228012652.21154.qmail@joyce.lan>
In-Reply-To: <20110228012652.21154.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 11:42:32 -0000

On 28/Feb/11 02:26, John Levine wrote:
>> I disagree here and note that legislators may look to this BCP later
>> if they intended to write such legislation.

Agreed, promoting de facto standards seems consistent with common law.

> Having helped some actual legislators write actual legislation, I
> find it utterly implausible that anyone would ever legislate the
> practices of DNSBLs in other than the most general terms.

Is that because of their inability to do otherwise?  (Do they do
better with traffic tickets?)

> Note that in the US they're protected by 47 US 230 which says they can
> do anything they want so long as there's a plausible good faith basis
> for doing so.  Case law confirms that making mistakes does not mean
> you weren't acting in good faith.

BCPs are valid world wide, though.  As unusual as it may be for IETF
documents to inspect business models, I'd cast my vote in favor of
section 2.2.5 just for pioneering such path.

+1, that is.


From geemailenator@gmail.com  Tue Mar  1 07:20:18 2011
Return-Path: <geemailenator@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DEC93A690C for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 07:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 RHq3qSIso51X for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 07:20:17 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id C6A6E3A68DA for <asrg@irtf.org>; Tue,  1 Mar 2011 07:20:16 -0800 (PST)
Received: by mail-vw0-f54.google.com with SMTP id 16so4889350vws.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 07:21:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=9KpGTpmGBXc4wZZvsL+O4T0p3W8dpF+V0IbiiLi0ErM=; b=umM3Yj+svaqWiL8n3JnFk3y+pSk4xWiD3lDGUnk/Nuwj9KBVE84sE93A2i61PeeqKW 8cjywYLfxlamcmG4wNcwssqy1M6Hq+salafBeJ+sGgBhecMZ6uZNr48qWoOVPAC5pM5h JYggEFeMpBFNEI6ZjkUK4OslHmvvkioLM2YrM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=F+tDfGbd9M0X8UEJPcsMajchswLyzwuN2ci9QUHd2zTDXLgl/lMdZgYWvL2Md1NmlB +PPikACqMkEkCwnPFk/jGeIm7KWmj6Z+BUV2jfei1Gsfk9wdH7qVKSffTuVp/lL5SFGa IQ7lS6dpTTRCarWfDVpFVZuHVAH7Tmd+/hWFI=
Received: by 10.220.201.197 with SMTP id fb5mr1787787vcb.53.1298992879147; Tue, 01 Mar 2011 07:21:19 -0800 (PST)
Received: from [172.16.1.2] (modemcable156.249-57-74.mc.videotron.ca [74.57.249.156]) by mx.google.com with ESMTPS id b18sm1119729vcm.40.2011.03.01.07.21.18 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 07:21:18 -0800 (PST)
Sender: Neil Schwartzman <geemailenator@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Neil Schwartzman <neil@cauce.org>
In-Reply-To: <4D6C265E.1060101@averillpark.net>
Date: Tue, 1 Mar 2011 10:21:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
References: <4D6C265E.1060101@averillpark.net>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 15:21:02 -0000

On Feb 28, 2011, at 5:49 PM, Richard Welty wrote:

> please list me as being in favor of this draft.

<aol> +1, and agreed. Heck, I may have even been the person to suggest =
this clause, some years ago at the IRTF meeting when the ASRG was =
resurrected. Charging for delisting is just plain bad business.

Allow me to take a brief moment to draw a significant line between the =
Spamhaus business model, and one based upon delisting. For those too =
drunk, blind, or somehow mentally deficient to spot it for themselves, =
it is simple. One charges the beneficiaries of a given DNSBL (Spamhaus) =
and thus motivates a blacklist operator to run the very best product =
possible. The other, such as previously done by SORBS, or now UCE =
Protect, motivates the DNSBL operator to list as many IPs as possible =
(1) for financial profit.

(Tangentially, were I an employee, particularly senior =
middle-management, like a Director, of a firm where presumably =
non-unionized staff went on 'strike' I would find that reason to rouse =
the CEO from his nightly reveries, not sit back and watch things play =
out. As it stands, the unanimity of the vote is noteworthy, and I doubt =
Messagelabs and Nortel are going to take this lying down. An abnegation =
of professional responsibility, in my mind.)

(1) UCE Protect claims to have listed a significant number of IPs in the =
past week:

Spammer listings within the last 7 days:
Level 1: 1767801 IP's, Level 2: 21354 Allocations, Level 3: 583 ASN's. =
Last Updated: 01.03.2011 13:01 CET
--
Neil Schwartzman
Executive Director
CAUCE
The Coalition Against Unsolicited Commercial Email, North America Inc.

http://cauce.org
http://twitter.com/cauce
IM: caucecanada
Tel.: +1 (303) 800 6345





From geemailenator@gmail.com  Tue Mar  1 07:20:06 2011
Return-Path: <geemailenator@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E55783A68BA for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 07:20:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 j85wF+qlcWD4 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 07:20:05 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id C4D873A68B7 for <asrg@irtf.org>; Tue,  1 Mar 2011 07:20:04 -0800 (PST)
Received: by vws16 with SMTP id 16so4889350vws.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 07:21:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=MXzZYuIXReogsllvL8HU9Wf11hhPU1YxmdAQbV3NjBE=; b=woZA71OVgUdUqmtgVmm9i66kFYUcSQf/JdcaAGIjqgWjgcgVl6ckVOZXRPXbjep7/y beUvQCe/CztMswRtF4s8+fgoifthHY4peH4rtlbDMhYXsdSIj/WS7wZW2nWGu9Wn3nGj dnr11nHSb8zVktaG7LBg3w5mUjMkFw26A++Yk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=Y92F3Efm6ZgzkGEFV9wLom7hlPN3d0SdUDj6cRr/o0koUdpQo3xXIjS8Y4CwTqF2UR a+Z/T5IpT++UH+9qrFPKrNVrnTnZgxT9mt0hXYrsoFh5LcUL5ZohBOlQNU371jfr2zsg l/po8GKKKaZvYbIWj7yhHFCC9h1Kt2mah+SMM=
Received: by 10.220.180.134 with SMTP id bu6mr1751658vcb.44.1298992867350; Tue, 01 Mar 2011 07:21:07 -0800 (PST)
Received: from [172.16.1.2] (modemcable156.249-57-74.mc.videotron.ca [74.57.249.156]) by mx.google.com with ESMTPS id b18sm1119729vcm.40.2011.03.01.07.21.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 07:21:06 -0800 (PST)
Sender: Neil Schwartzman <geemailenator@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Neil Schwartzman <neil@cauce.org>
In-Reply-To: <4D6C297A.10701@fahq2.com>
Date: Tue, 1 Mar 2011 10:21:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <08098715-2DA4-46A3-8AF4-CCB2A73FA848@cauce.org>
References: <AANLkTimHpKzxNLKAabNTQbQNFiAK7EwoeUa9kqF96+ow@mail.gmail.com>	<20110227190039.0FD6B12EC69@ca-mirror-1.uceprotect.net>	<AANLkTimh_=k9=gKmWbDq2Yj_E=4gegNgME9=nZSQvJ+n@mail.gmail.com>	<20110228003938.48F9B12EC69@ca-mirror-1.uceprotect.net>	<4D6B	<A.1PuA1G-000DCv-BL@smtp-ext-layer.spamhaus.org>	<4D6C1456.4030101@nortel.com> <20110228222001.6A4C512EC69@ca-mirror-1.uceprotect.net> <4D6C297A.10701@fahq2.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] UCEPROTECT's comment on draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 15:27:01 -0000

Claus v. Wolfhausen wrote:
> Damned, see what you have done with this BCP, you got my removal crew
> striking.
> Hey I'm at home and I didn't know that they would do this tonight.
> We had a meeting and discussion today in the afternoon and our CEO =
said:
> "Ok, if that becomes an RFC we might stop manual delistings, who =
cares."
>=20
> It looks like that this has scared the removal crew and they try to =
keep
> their jobs.
> I have a deep understanding for them, but I would have done the texts
> very differently.

Interesting. So the CEO basically allows the staff to run rampant, go =
'on strike' (one supposes they will not be paid for this period of =
time), deface the corporate website with ill-advised text, and they =
haven't been fired en masse?

Seems to me any CEO worth his salt would have done that right off the =
bat, and taken down that page. I sure as hell would not have dared pull =
a stunt like this at any place I've worked. I'd go so far as to say I =
deeply distrust the veracity as this has been presented by Claus.

Context: I was a union organizer, and not afraid to stand up for my =
rights.=20

By the way, if anyone is tallying votes - I am very much in favour of =
the Clause (sic) disallowing charges for delistings.

--
Neil Schwartzman
Executive Director
CAUCE
The Coalition Against Unsolicited Commercial Email, North America Inc.

http://cauce.org
http://twitter.com/cauce
IM: caucecanada
Tel.: +1 (303) 800 6345





From aiverson@spamresource.com  Tue Mar  1 08:15:58 2011
Return-Path: <aiverson@spamresource.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1687C3A692E for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level: 
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 cW5kbQa8tgoC for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:15:57 -0800 (PST)
Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by core3.amsl.com (Postfix) with ESMTP id 154C43A6912 for <asrg@irtf.org>; Tue,  1 Mar 2011 08:15:56 -0800 (PST)
Received: by wwb31 with SMTP id 31so6344079wwb.19 for <asrg@irtf.org>; Tue, 01 Mar 2011 08:16:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.71.13 with SMTP id q13mr6251483wed.21.1298996219205; Tue, 01 Mar 2011 08:16:59 -0800 (PST)
Received: by 10.216.183.139 with HTTP; Tue, 1 Mar 2011 08:16:59 -0800 (PST)
In-Reply-To: <08098715-2DA4-46A3-8AF4-CCB2A73FA848@cauce.org>
References: <AANLkTimHpKzxNLKAabNTQbQNFiAK7EwoeUa9kqF96+ow@mail.gmail.com> <20110227190039.0FD6B12EC69@ca-mirror-1.uceprotect.net> <AANLkTimh_=k9=gKmWbDq2Yj_E=4gegNgME9=nZSQvJ+n@mail.gmail.com> <20110228003938.48F9B12EC69@ca-mirror-1.uceprotect.net> <A.1PuA1G-000DCv-BL@smtp-ext-layer.spamhaus.org> <4D6C1456.4030101@nortel.com> <20110228222001.6A4C512EC69@ca-mirror-1.uceprotect.net> <4D6C297A.10701@fahq2.com> <08098715-2DA4-46A3-8AF4-CCB2A73FA848@cauce.org>
Date: Tue, 1 Mar 2011 10:16:59 -0600
Message-ID: <AANLkTi=FNba=i2fcKZVLBWxNC_1dTd1NHcKt2phYx_0V@mail.gmail.com>
From: Al Iverson <aiverson@spamresource.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] UCEPROTECT's comment on draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:15:58 -0000

On Tue, Mar 1, 2011 at 9:21 AM, Neil Schwartzman <neil@cauce.org> wrote:

> Interesting. So the CEO basically allows the staff to run rampant, go 'on=
 strike' (one supposes they will not be paid for this period of time), defa=
ce the corporate website with ill-advised text, and they haven't been fired=
 en masse?
>
> Seems to me any CEO worth his salt would have done that right off the bat=
, and taken down that page. I sure as hell would not have dared pull a stun=
t like this at any place I've worked. I'd go so far as to say I deeply dist=
rust the veracity as this has been presented by Claus.

I have to agree -- I don't think Claus is being honest about this.
Something doesn't smell right and I'm about ready to set up a procmail
filter to address it. I'm really disappointed by UCEPROTECT's churlish
response.

Regards,
Al Iverson

From msergeant@messagelabs.com  Tue Mar  1 08:29:02 2011
Return-Path: <msergeant@messagelabs.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C3883A681D for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level: 
X-Spam-Status: No, score=-5.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 UEJI+2yyh3Uc for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:29:01 -0800 (PST)
Received: from mail33.messagelabs.com (mail33.messagelabs.com [195.245.230.51]) by core3.amsl.com (Postfix) with ESMTP id BF1413A6943 for <asrg@irtf.org>; Tue,  1 Mar 2011 08:29:00 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: msergeant@messagelabs.com
X-Msg-Ref: server-6.tower-33.messagelabs.com!1298996998!35321167!8
X-StarScan-Version: 6.2.9; banners=messagelabs.com,-,-
X-Originating-IP: [95.131.111.138]
Received: (qmail 6002 invoked from network); 1 Mar 2011 16:30:01 -0000
Received: from mlbrn2exc001.messagelabs.com (HELO mlbrn2exc001.messagelabs.com) (95.131.111.138) by server-6.tower-33.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2011 16:30:01 -0000
Received: from smtp-out.devel.messagelabs.com ([10.191.110.53]) by mlbrn2exc001.messagelabs.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 16:29:13 +0000
Received: (qmail 1159 invoked from network); 1 Mar 2011 16:28:56 -0000
Received: from unknown (HELO Valour.local) (10.7.253.21) by matt?dev.int.star.co.uk with SMTP; 1 Mar 2011 16:28:56 -0000
Message-ID: <4D6D1EC7.6080508@messagelabs.com>
Date: Tue, 01 Mar 2011 11:28:55 -0500
From: Matt Sergeant <msergeant@messagelabs.com>
User-Agent: Postbox 1.1.5 (Macintosh/20100613)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
In-Reply-To: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
Content-Type: multipart/alternative; boundary="------------040408090704030005010509"
X-OriginalArrivalTime: 01 Mar 2011 16:29:13.0999 (UTC) FILETIME=[CD5181F0:01CBD82D]
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:29:02 -0000

This is a multi-part message in MIME format.
--------------040408090704030005010509
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Neil Schwartzman wrote:
> <aol>  +1, and agreed. Heck, I may have even been the person to suggest this clause, some years ago at the IRTF meeting when the ASRG was resurrected. Charging for delisting is just plain bad business.
The original wording was designed to cover this, it said (and jeez, this 
was back in 2003!): " If all things listed in your criteria for listing 
are cleared up then there should be no reason to not remove the IP 
address. No /extra/ rules for de-listing.". We simply made it more 
explicit (and better English).

Matt.


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
--------------040408090704030005010509
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Neil Schwartzman wrote:
<blockquote cite="mid:EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org"
 type="cite">
  <pre wrap="">&lt;aol&gt; +1, and agreed. Heck, I may have even been the person to suggest this clause, some years ago at the IRTF meeting when the ASRG was resurrected. Charging for delisting is just plain bad business.</pre>
</blockquote>
The original wording was designed to cover this, it said (and jeez,
this was back in 2003!): "
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
If all things listed in your criteria for listing are cleared up then
there should be no reason to not remove the IP address. No <i>extra</i>
rules for de-listing.". We simply made it more explicit (and better
English).<br>
<br>
Matt.<br>
<BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>
</body>
</html>


--------------040408090704030005010509--

From c.v.wolfhausen@spamkiller.uceprotect.net  Tue Mar  1 08:32:58 2011
Return-Path: <c.v.wolfhausen@spamkiller.uceprotect.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EA323A6997 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.187
X-Spam-Level: 
X-Spam-Status: No, score=-2.187 tagged_above=-999 required=5 tests=[AWL=0.411,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 XKbrPGKlnwaZ for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:32:55 -0800 (PST)
Received: from ca-mirror-1.uceprotect.net (ca-mirror-1.uceprotect.net [208.66.2.20]) by core3.amsl.com (Postfix) with ESMTP id C71BA3A6992 for <asrg@irtf.org>; Tue,  1 Mar 2011 08:32:54 -0800 (PST)
Received: by ca-mirror-1.uceprotect.net (UCEPROTECT, from userid 32767) id B094412EC69; Tue,  1 Mar 2011 17:34:11 +0100 (CET)
MIME-Version: 1.0
Content-Type: Multipart/Alternative; charset="iso-8859-1"; boundary="------------Boundary-00=_WM0E6ZW5BHK000000000"
From: "Claus v. Wolfhausen" <c.v.wolfhausen@spamkiller.uceprotect.net>
To: <asrg@irtf.org>
Date: Tue,  1 Mar 2011 17:34:05 +0100 (CET)
Message-Id: <20110301163411.B094412EC69@ca-mirror-1.uceprotect.net>
Subject: [Asrg] Final statement
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:32:58 -0000

--------------Boundary-00=_WM0E6ZW5BHK000000000
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

This is my last statement to this group before unsubscribing.=0D
=0D
I came here after I have found that BCP 07 to do a serious discussion wit=
h
you, and you would have had the chance to convince me of your positions, =
if
you would have had good arguments. =0D
Unfortunateley, an objectice discussion did not happen, because you (and
that really means as good as anyone here) has prejudices against me, and =
so
I had to hear things as:=0D
"Racket-Protection-Company"  even in the first answer I got from this gro=
up.=0D
=0D
Really nice ... and very professional ....=0D
=0D
I have to admitt that my answer to Mr. Lindford of SPAMHAUS was very iron=
ic
instead of being neutral and objective, but that does not change the fact=
s I
have given the audience about the SPAMHAUS-DNSBLs.=0D
=0D
Unfortunateley I told in a meeting about that BCP and it seems some very
stupid workers got scared to lose their job.=0D
They tried a very stupid action and they reached the opposite of what the=
y
wanted to achieve:  They got fired by the CEO today in the morning.=0D
=0D
Anyway those idiots made me look like an asshole and you were happy to se=
e
me as an asshole instead of turning on the brain and trying to read betwe=
en
the lines.=0D
Chris and Matt do both know the full story what happend and it doesn't
matter to all others here. It doesn't belong to a public lists.=0D
=0D
Since this group is unable to discuss BCP 07 without prejudices against m=
e
and the UCEPROTECT-Network, I would simply waste my time, if I would stay=
 in
this group any longer.=0D
=0D
If there is at least *ONE* here that can think objective and logic, then
think about this:=0D
=0D
Really technical important things got a "SHOULD" OR "RECOMMENDED" while a
the content of a policy (if there is a payment option or not) got a "MUST
NOT" in BCP 07.=0D
=0D
Examples:=0D
2.1 Transparency - It is a joke that there is a SHOULD instead of MUST.=0D
2.1.1 Listing criterias SHOULD be easy available (instead of MUST)=0D
2.2.1 Listings SHOULD be temporary (instead of MUST)=0D
3.3 DNSBLs SHOULD have operational fals  (Instead of MUST)=0D
=0D
That list could be continued. Those examples I have given here are a clea=
r
MUST for every responsible DNSBL-Operator.=0D
=0D
According to your BCP 07 an DNSBL-Operator is not required to publish a
policy at all , but BCP 07 believes it can judge if there is a payment
option in that policy. That is ridiculous. =0D
=0D
That means your BCP 07 is at best a joke and nothing that a professional
person will ever take serious.=0D
=0D
All people that have voted for it have clearly given proof that they are
really blind or incompetent and their only reasoning to vote for this BCP
was to harass the UCEPROTECT-Network.=0D
=0D
That means the UCEPROTECT-Network will gladfully ignore this group and it=
's
decisions or votings from now.=0D
=0D
Claus von Wolfhausen=0D
Technical Director=0D
UCEPROTECT-Network=0D
http://www.uceprotect.net=0D
=0D
=0D
=0D
=0D
=0D
=0D
=20
--------------Boundary-00=_WM0E6ZW5BHK000000000
Content-Type: Text/HTML;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Ty=
pe>
<META name=3DGENERATOR content=3D"IncrediMail 1.0">
<STYLE>=0Av\:* {behavior:url (#default#vml);}=0A</STYLE>

<!--IncrdiXMLRemarkStart>
<IncrdiX-Info>
<X-FID>FLAVOR00-NONE-0000-0000-000000000000</X-FID>
<X-FVER>0,000000</X-FVER>
<X-CNT>;</X-CNT>
</IncrdiX-Info>
<IncrdiXMLRemarkEnd-->
</HEAD>
<BODY style=3D"MARGIN: 5px 10px 0px; FONT-FAMILY: Arial; FONT-SIZE: 12pt"=
 background=3D"" scroll=3Dyes bgColor=3D#ffffff>
<TABLE id=3DINCREDIMAINTABLE border=3D0 cellSpacing=3D0 cellPadding=3D2 w=
idth=3D"100%">
<TBODY>
<TR>
<TD style=3D"POSITION: relative; DIRECTION: ltr; FONT-SIZE: 12pt" id=3DIN=
CREDITEXTREGION width=3D"100%">
<DIV style=3D"PADDING-LEFT: 2px; FONT-FAMILY: Arial; FONT-SIZE: 12pt" id=3D=
INCREDI_TEXT_AREA><FONT size=3D3>
<DIV>This is my last statement to this group before unsubscribing.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I came here after I have found that BCP 07 to do a serious discussio=
n with you, and you would have had the chance to convince me of your posi=
tions, if you would have had good arguments. </DIV>
<DIV>Unfortunateley, an objectice discussion did not happen, because you =
(and that really means as good as anyone here) has prejudices against me,=
 and so I had to hear things as:</DIV>
<DIV>"Racket-Protection-Company"&nbsp; even in the first answer I got fro=
m this group.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Really nice ... and very professional ....</DIV>
<DIV>&nbsp;</DIV>
<DIV>I have to admitt that my answer to Mr. Lindford of SPAMHAUS was very=
 ironic instead of being neutral and objective, but that does not change =
the facts I have given the audience about the SPAMHAUS-DNSBLs.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Unfortunateley I told in a&nbsp;meeting about that BCP and it seems =
some very stupid workers got scared to lose their job.</DIV>
<DIV>They tried a very stupid action and they reached the opposite of wha=
t they wanted to achieve:&nbsp; They got fired by the CEO today in the mo=
rning.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Anyway those idiots made me look like an asshole and you were happy =
to see me as an asshole instead of turning on the brain and trying to rea=
d between the lines.</DIV>
<DIV>Chris and Matt do both know the full story what happend and it doesn=
't matter to all others here. It doesn't belong to a public lists.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Since this group is unable to discuss BCP 07 without&nbsp;prejudices=
 against&nbsp;me and the UCEPROTECT-Network, I would simply waste my time=
, if I would stay in this group any longer.</DIV>
<DIV>&nbsp;</DIV>
<DIV>If there is at least *ONE* here that can think objective and logic, =
then think about this:</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT size=3D3>Really technical important things&nbsp;got a "SHOULD"=
 OR "RECOMMENDED" while a the content of a policy&nbsp;(if there is a pay=
ment option or not)&nbsp;got a "MUST NOT" in BCP 07.</DIV>
<DIV>
<DIV><FONT size=3D3>
<DIV>&nbsp;</DIV>
<DIV>Examples:</DIV>
<DIV>2.1 Transparency - It is a joke that there is a SHOULD instead of MU=
ST.</DIV>
<DIV>2.1.1 Listing criterias SHOULD be easy available (instead of MUST)</=
DIV>
<DIV>2.2.1 Listings SHOULD be temporary (instead of MUST)</DIV>
<DIV>3.3 DNSBLs SHOULD have operational fals&nbsp; (Instead of MUST)</DIV=
>
<DIV>&nbsp;</DIV>
<DIV>That list could be continued. Those examples I have given here are a=
 clear MUST for every responsible DNSBL-Operator.</DIV>
<DIV>&nbsp;</DIV>
<DIV>According to your BCP 07 an DNSBL-Operator is not required to publis=
h a policy at all , but BCP 07 believes it can judge if there is a paymen=
t option in that policy. That is ridiculous.&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>That means your BCP 07 is at best a joke and nothing that a professi=
onal person will ever take serious.</DIV>
<DIV>&nbsp;</DIV>
<DIV>All people that have voted for it have clearly given proof that they=
 are really blind or incompetent and their only reasoning to vote for thi=
s BCP was to harass the UCEPROTECT-Network.</DIV>
<DIV>&nbsp;</DIV>
<DIV>That means the UCEPROTECT-Network will gladfully ignore this group&n=
bsp;and it's decisions or votings from now.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Claus von Wolfhausen</DIV>
<DIV>Technical Director</DIV>
<DIV>UCEPROTECT-Network</DIV>
<DIV><A href=3D"http://www.uceprotect.net">http://www.uceprotect.net</A><=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV></FONT></DIV></FONT></DIV></FONT></DIV></TD></TR>
<TR>
<TD id=3DINCREDIFOOTER width=3D"100%">
<TABLE cellSpacing=3D0 cellPadding=3D0 width=3D"100%">
<TBODY>
<TR>
<TD width=3D"100%"></TD>
<TD id=3DINCREDISOUND vAlign=3Dbottom align=3Dmiddle></TD></TR></TBODY></=
TABLE></TD></TR></TBODY></TABLE></BODY></HTML>
--------------Boundary-00=_WM0E6ZW5BHK000000000--


From matthew@sorbs.net  Tue Mar  1 08:42:13 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BEFB3A692E for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.5
X-Spam-Level: 
X-Spam-Status: No, score=-10.5 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799]
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 vjHsBimPrnwB for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:42:12 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 335803A6838 for <asrg@irtf.org>; Tue,  1 Mar 2011 08:42:09 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id 07E021C940 for <asrg@irtf.org>; Wed,  2 Mar 2011 03:43:09 +1100 (EST)
Received: from nemesis.local (c190-214.i02-8.onvol.net [213.165.190.214]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005)) with ESMTPSA id <0LHE00I0213SB1@nemesis.sorbs.net> for asrg@irtf.org; Wed, 02 Mar 2011 02:43:09 +1000 (EST)
Date: Tue, 01 Mar 2011 17:43:03 +0100
From: Michelle Sullivan <matthew@sorbs.net>
In-reply-to: <AANLkTintXjw_=anj=Z965vTcn0V12JanTx9SB1-ryEuH@mail.gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-id: <4D6D2217.3050001@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
X-Enigmail-Version: 0.96.0
References: <4D6C265E.1060101@averillpark.net> <4D6C3FFA.6050407@jdmc.org> <AANLkTintXjw_=anj=Z965vTcn0V12JanTx9SB1-ryEuH@mail.gmail.com>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:42:13 -0000

Kelly Molloy wrote:
> On Mon, Feb 28, 2011 at 4:38 PM, John Johnson <jjohnson@jdmc.org> wrote:
>   
>> On 02/28/2011 04:49 PM, Richard Welty wrote:
>>     
>>> please list me as being in favor of this draft.
>>>       
>> please count me as also in favor, if not already
>>     
>
> Add me as well.
>
> In fact, Claus, you can add my name and email address to your webpage
> as supporting the BCP. No reason to leave all the work to Chris and
> Matt.
>   

As I had joined the discussion on the payment aspect you can add me as well.

Michelle

From matthew@sorbs.net  Tue Mar  1 08:56:43 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C6C63A69A6 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.5
X-Spam-Level: 
X-Spam-Status: No, score=-10.5 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799]
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 lrA7jdXdnhaI for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 08:56:42 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 80DFB3A6989 for <asrg@irtf.org>; Tue,  1 Mar 2011 08:56:42 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id 6F2A11C548 for <asrg@irtf.org>; Wed,  2 Mar 2011 03:57:42 +1100 (EST)
Received: from nemesis.local (c190-214.i02-8.onvol.net [213.165.190.214]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005)) with ESMTPSA id <0LHE00I051S0B1@nemesis.sorbs.net> for asrg@irtf.org; Wed, 02 Mar 2011 02:57:40 +1000 (EST)
Date: Tue, 01 Mar 2011 17:57:35 +0100
From: Michelle Sullivan <matthew@sorbs.net>
In-reply-to: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-id: <4D6D257F.4060902@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
X-Enigmail-Version: 0.96.0
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 16:56:43 -0000

Neil Schwartzman wrote:
>
> Allow me to take a brief moment to draw a significant line between the Spamhaus business model, and one based upon delisting. For those too drunk, blind, or somehow mentally deficient to spot it for themselves, it is simple. One charges the beneficiaries of a given DNSBL (Spamhaus) and thus motivates a blacklist operator to run the very best product possible. The other, such as previously done by SORBS, or now UCE Protect, motivates the DNSBL operator to list as many IPs as possible (1) for financial profit.
>   

SORBS had no financial gain due to charging.


Michelle


From msergeant@messagelabs.com  Tue Mar  1 09:56:33 2011
Return-Path: <msergeant@messagelabs.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B0CD3A6A2B for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 09:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.399,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 qQySKjOXWjrv for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 09:56:31 -0800 (PST)
Received: from mail208.messagelabs.com (mail208.messagelabs.com [195.245.230.83]) by core3.amsl.com (Postfix) with ESMTP id 9A8613A6957 for <asrg@irtf.org>; Tue,  1 Mar 2011 09:56:30 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: msergeant@messagelabs.com
X-Msg-Ref: server-5.tower-208.messagelabs.com!1299002252!29172235!1
X-StarScan-Version: 6.2.9; banners=messagelabs.com,-,-
X-Originating-IP: [95.131.111.138]
Received: (qmail 29492 invoked from network); 1 Mar 2011 17:57:32 -0000
Received: from mlbrn2exc001.messagelabs.com (HELO mlbrn2exc001.messagelabs.com) (95.131.111.138) by server-5.tower-208.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2011 17:57:32 -0000
Received: from smtp-out.devel.messagelabs.com ([10.191.110.53]) by mlbrn2exc001.messagelabs.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 17:57:49 +0000
Received: (qmail 1482 invoked from network); 1 Mar 2011 17:57:31 -0000
Received: from unknown (HELO Valour.local) (10.7.253.21) by matt?dev.int.star.co.uk with SMTP; 1 Mar 2011 17:57:31 -0000
Message-ID: <4D6D338A.40608@messagelabs.com>
Date: Tue, 01 Mar 2011 12:57:30 -0500
From: Matt Sergeant <msergeant@messagelabs.com>
User-Agent: Postbox 1.1.5 (Macintosh/20100613)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110301163411.B094412EC69@ca-mirror-1.uceprotect.net>
In-Reply-To: <20110301163411.B094412EC69@ca-mirror-1.uceprotect.net>
Content-Type: multipart/alternative; boundary="------------010300000600010506020305"
X-OriginalArrivalTime: 01 Mar 2011 17:57:49.0514 (UTC) FILETIME=[2D9CBAA0:01CBD83A]
Subject: Re: [Asrg] Final statement
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 17:56:33 -0000

This is a multi-part message in MIME format.
--------------010300000600010506020305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Claus v. Wolfhausen wrote:
> Really technical important things got a "SHOULD" OR "RECOMMENDED" 
> while a the content of a policy (if there is a payment option or 
> not) got a "MUST NOT" in BCP 07.
> Examples:
> 2.1 Transparency - It is a joke that there is a SHOULD instead of MUST.
> 2.1.1 Listing criterias SHOULD be easy available (instead of MUST)

These two were a tough call. I'd prefer MUST here too, but if you look 
at the CBL they don't list *exactly* why the listing is there, they 
simply say " lists IPs exhibiting characteristics which are specific to 
open proxies of various sorts (HTTP, socks, AnalogX, wingate etc) and 
dedicated Spam BOTs which have been abused to send spam, worms/viruses 
that do their own direct mail transmission, or some types of 
trojan-horse or "stealth" spamware, dictionary mail harvesters etc." 
which is fair enough but may make them fall foul of the clause if it 
were a MUST.

It's easier for some other DNSBLs where the criteria is simply "the IP 
emailed our spamtrap".

> 2.2.1 Listings SHOULD be temporary (instead of MUST)

I see no reason that has to be a MUST. Some DNSBLs are informational 
only, and as such there's no reason for an expiration. This has been 
discussed here a lot in the archives.

> 3.3 DNSBLs SHOULD have operational fals  (Instead of MUST)

There are reasons for this not being a MUST, again associated with 
informational lists.

> According to your BCP 07 an DNSBL-Operator is not required to publish 
> a policy at all , but BCP 07 believes it can judge if there is a 
> payment option in that policy. That is ridiculous.

It's not entirely ridiculous. I stand by the fact that charging for 
removal is a worse policy than not having listing criteria published in 
certain cases.

> That means your BCP 07 is at best a joke and nothing that a 
> professional person will ever take serious.
> All people that have voted for it have clearly given proof that they 
> are really blind or incompetent and their only reasoning to vote for 
> this BCP was to harass the UCEPROTECT-Network.

You're right, the whole thing was a gag aimed at poking fun at 
UCEPROTECT </sarcasm>.

Seriously, tone down the rhetoric. Perhaps if you had solid arguments 
for needing to charge for removals you would have been taken seriously. 
But when every other blocklist manages to do free removals without any 
problems you need to come up with some pretty damn solid arguments.

Your argument for why the clause shouldn't be there is simply that users 
need a good spanking so that they don't get infected again. In my 
experience this is acheivable through other means, which perhaps you 
haven't considered. The one I used is that sure they can delist if they 
haven't fixed the problem (but only once per TIME_PERIOD), then 
relisting happens again because they hit the trap, and if the sender 
keeps asking to be delisted they get told not until they fix the 
problem. Sort of a 3 strikes and they're out policy [*]. There's nothing 
in the BCP which prohibits that, and it's MUCH more friendly than the 
policy of charging. In my experience the implementation of such a policy 
did not hamper the effectiveness of the blocklist whatsoever.

Matt.

[*] 3 because #1 is done on the web site via CGI, #2 is done via email 
request, then #3 they are out until they fix the problem.



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
--------------010300000600010506020305
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Claus v. Wolfhausen wrote:
<blockquote
 cite="mid:20110301163411.B094412EC69@ca-mirror-1.uceprotect.net"
 type="cite"><font size="3">
  <div><font size="3">Really technical important
things&nbsp;got a "SHOULD" OR "RECOMMENDED" while a the content of a
policy&nbsp;(if there is a payment option or not)&nbsp;got a "MUST NOT" in BCP 07.</font></div>
  <div>
  <div><font size="3"><font size="3">
  <div>&nbsp;</div>
  <div>Examples:</div>
  <div>2.1 Transparency - It is a joke that there is a SHOULD instead
of MUST.</div>
  <div>2.1.1 Listing criterias SHOULD be easy available (instead of
MUST)</div>
  </font></font></div>
  </div>
  </font></blockquote>
<br>
These two were a tough call. I'd prefer MUST here too, but if you look
at the CBL they don't list *exactly* why the listing is there, they
simply say "
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
lists IPs exhibiting characteristics which
are specific to open proxies of various sorts (HTTP, socks, AnalogX,
wingate etc) and dedicated Spam BOTs which
have been abused to send spam, worms/viruses that do their own direct
mail transmission, or some types of trojan-horse or "stealth"
spamware, dictionary mail harvesters etc." which is fair enough but may
make them fall foul of the clause if it were a MUST.<br>
<br>
It's easier for some other DNSBLs where the criteria is simply "the IP
emailed our spamtrap".<br>
<br>
<blockquote
 cite="mid:20110301163411.B094412EC69@ca-mirror-1.uceprotect.net"
 type="cite"><font size="3">
  <div>
  <div><font size="3"><font size="3">
  <div>2.2.1 Listings SHOULD be temporary (instead of MUST)</div>
  </font></font></div>
  </div>
  </font></blockquote>
<br>
I see no reason that has to be a MUST. Some DNSBLs are informational
only, and as such there's no reason for an expiration. This has been
discussed here a lot in the archives.<br>
<br>
<blockquote
 cite="mid:20110301163411.B094412EC69@ca-mirror-1.uceprotect.net"
 type="cite"><font size="3">
  <div>
  <div><font size="3"><font size="3">
  <div>3.3 DNSBLs SHOULD have operational fals&nbsp; (Instead of MUST)</div>
  </font></font></div>
  </div>
  </font></blockquote>
<br>
There are reasons for this not being a MUST, again associated with
informational lists.<br>
<br>
<blockquote
 cite="mid:20110301163411.B094412EC69@ca-mirror-1.uceprotect.net"
 type="cite"><font size="3">
  <div>
  <div>According to your BCP 07 an DNSBL-Operator is not required to
publish a policy at all , but BCP 07 believes it can judge if there is
a payment option in that policy. That is ridiculous. <br>
  </div>
  </div>
  </font></blockquote>
<br>
It's not entirely ridiculous. I stand by the fact that charging for
removal is a worse policy than not having listing criteria published in
certain cases.<br>
<br>
<blockquote
 cite="mid:20110301163411.B094412EC69@ca-mirror-1.uceprotect.net"
 type="cite"><font size="3">
  <div>
  <div><font size="3"><font size="3">
  <div>That means your BCP 07 is at best a joke and nothing that a
professional person will ever take serious.</div>
  <div>&nbsp;</div>
  <div>All people that have voted for it have clearly given proof that
they are really blind or incompetent and their only reasoning to vote
for this BCP was to harass the UCEPROTECT-Network.</div>
  </font></font></div>
  </div>
  </font></blockquote>
<br>
You're right, the whole thing was a gag aimed at poking fun at
UCEPROTECT &lt;/sarcasm&gt;.<br>
<br>
Seriously, tone down the rhetoric. Perhaps if you had solid arguments
for needing to charge for removals you would have been taken seriously.
But when every other blocklist manages to do free removals without any
problems you need to come up with some pretty damn solid arguments.<br>
<br>
Your argument for why the clause shouldn't be there is simply that
users need a good spanking so that they don't get infected again. In my
experience this is acheivable through other means, which perhaps you
haven't considered. The one I used is that sure they can delist if they
haven't fixed the problem (but only once per TIME_PERIOD), then
relisting happens again because they hit the trap, and if the sender
keeps asking to be delisted they get told not until they fix the
problem. Sort of a 3 strikes and they're out policy [*]. There's
nothing in the BCP which prohibits that, and it's MUCH more friendly
than the policy of charging. In my experience the implementation of
such a policy did not hamper the effectiveness of the blocklist
whatsoever.<br>
<br>
Matt.<br>
<br>
[*] 3 because #1 is done on the web site via CGI, #2 is done via email
request, then #3 they are out until they fix the problem.<br>
<br>
<BR>
______________________________________________________________________<BR>
This email has been scanned by the MessageLabs Email Security System.<BR>
For more information please visit http://www.messagelabs.com/email <BR>
______________________________________________________________________<BR>
</body>
</html>


--------------010300000600010506020305--

From joseph.sniderman@thoroquel.org  Tue Mar  1 11:00:34 2011
Return-Path: <joseph.sniderman@thoroquel.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB8AC3A6A76 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6
X-Spam-Level: 
X-Spam-Status: No, score=-6 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 nXGhFBQmC8BK for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:00:33 -0800 (PST)
Received: from mail.thoroquel.org (mail.thoroquel.org [72.14.190.148]) by core3.amsl.com (Postfix) with ESMTP id A43C03A6A65 for <asrg@irtf.org>; Tue,  1 Mar 2011 11:00:33 -0800 (PST)
Received: from [IPv6:2604:8800:101:1::e] (epinephrine.home.thoroquel.com [IPv6:2604:8800:101:1::e]) (authenticated bits=0) by mail.thoroquel.org (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p21J1TEq015208 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Mar 2011 19:01:31 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thoroquel.org; s=thoroquel2a; t=1299006091; bh=V5plWUGa8cj+4dyrjYkE1f0rmIFMj6rHyr/pdid7t38=; h=Message-ID:Date:From:To:Subject:References:In-Reply-To:OpenPGP: Content-Type:Content-Transfer-Encoding:CC:DomainKey-Signature; b=LWz+9bktJW/hC2hDARODUR1baKIfg/zWsgLzkoDTVPx9YM94/zljEDmIrSc98deek 5IbXMOU4NVGbZP9u9Px+rlR3iQ0j6y2TebyS25UdU7+9QxBez6HVUTpu245o6ekhlo i7uUByWGzIs1gUOgW0tGGOIgD74w0rymX5DZh3AgbdQI6CShJTJfy/QBPguIFQg1/s 337jHCWM1G3uM5TSDTz99vtNc0meOmvwTpiYh5jrLnHeaPndqsEvQ65pbvGz7igMAa HQTojh+zLVbRZbKQ3jFdJVwIOVSfvlHnoZTusxuUNU5WaA17g0li2vd8BS7CAKcS5x QlYn4EGBu4Mjg==
Message-ID: <4D6D4284.50102@thoroquel.org>
Date: Tue, 01 Mar 2011 14:01:24 -0500
From: Joe Sniderman <joseph.sniderman@thoroquel.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
In-Reply-To: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
X-Enigmail-Version: 1.1.1
OpenPGP: id=605721CA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:00:35 -0000

On 03/01/2011 10:21 AM, Neil Schwartzman wrote:
> 
> On Feb 28, 2011, at 5:49 PM, Richard Welty wrote:
> 
>> please list me as being in favor of this draft.
> 
> <aol> +1, and agreed. Heck, I may have even been the person to
> suggest this clause, some years ago at the IRTF meeting when the ASRG
> was resurrected. Charging for delisting is just plain bad business.

> Allow me to take a brief moment to draw a significant line between
> the Spamhaus business model, and one based upon delisting. For those
> too drunk, blind, or somehow mentally deficient to spot it for
> themselves, it is simple. One charges the beneficiaries of a given
> DNSBL (Spamhaus) and thus motivates a blacklist operator to run the
> very best product possible.

Yes, and this is a good thing. It encourages the provider of the data
(the DNSxL) to be loyal to the consumer of the data, rather than the
subject of the data.

Spamhaus charges to query its blocklists. Hypothetically, if Spamhaus
were to begin listing IPs (or domains on DBL) that did not meet the
listing criteria, it would risk losing paying customers. This applies to
any DNSxL (positve reputation included) that is funded primarily by its
users rather than its listees.

> The other, such as previously done by
> SORBS, or now UCE Protect, motivates the DNSBL operator to list as
> many IPs as possible (1) for financial profit.

Yes - in theory (the lists mentioned are not prime examples IMHO), and
this applies to whitelists as well.

That said, UCEProtect has previously been very quick to ban listees from
having the option of paying for delisting, and from what I understand
also sells hardware filtering appliances so it would hurt that end of
its business if it listed IPs that didnt meet its listing criteria.

The "fine" SORBS used to charge, IIRC was required to paid to charity,
*not* to SORBS itself, so there would be little or no financial motive
there to list IPs that did not meet its listing criteria.

There are some rare DNSxL's that have managed to be listee-funded and
maintain impartiality. ISIPP is probably a prime example. Listee pays to
be listed, AFAIK list operators determine the category. Some of their
categories make excellent whitelists, while others make excellent
blacklists.

The risk that a blocklist will list IPs solely to collect a delisting
fee, or that a whitelist will list non-qualifying IPs solely to collect
an accreditation fee, is to some extent mitigated by the fact than a
DNSxL doing so will be less widely used, and therefore there will be
less incentive for a listee (or hopeful listee, in the case of a
whitelist) to pay up.

No matter how its sliced up though, its *usually* a really bad idea.

> (Tangentially, were I an employee, particularly senior
> middle-management, like a Director, of a firm where presumably
> non-unionized staff went on 'strike' I would find that reason to
> rouse the CEO from his nightly reveries, not sit back and watch
> things play out. 

Agreed.  Frankly I think it stinks far worse than any delisting fee
possibly could.  I'm highly disappointed to say the least.. I've been a
real "fan" (for lack of a better word) of UCEProtect up until this escapade.

> As it stands, the unanimity of the vote is
> noteworthy, and I doubt Messagelabs and Nortel are going to take this
> lying down. An abnegation of professional responsibility, in my
> mind.)

Quite the contrary, I suspect (and hope) that both Messagelabs and
Nortel will see it for the nastiness and absurdity that is, and take the
high ground by not getting all macho or legalistic about it.

-- 
Joe Sniderman <joseph.sniderman@thoroquel.org>

From esa@winteri.org  Tue Mar  1 11:27:31 2011
Return-Path: <esa@winteri.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1EBC3A6A76 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 XUTk-+4g1lab for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:27:30 -0800 (PST)
Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by core3.amsl.com (Postfix) with ESMTP id A78263A6A74 for <asrg@irtf.org>; Tue,  1 Mar 2011 11:27:30 -0800 (PST)
Received: by gyh4 with SMTP id 4so2398597gyh.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 11:28:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=winteri.org; s=google; h=domainkey-signature:mime-version:sender:x-originating-ip :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=HPjkajbJGw3/KlImhrUBfbbHQP28fXFuj6e2vP81Gh0=; b=YkMYM/x6WPFMJ+UsC62TELnnPDatxhz+IanWD9R5HgUu1zHo8i1oQQqASOddT+ICgZ CLHEvzhZHy+6CuOgFFbvrGc1ltW2Itg2uo6FGkuFIwNeQfD56LZd5R6exZ7A3nC3lCoJ r56jae8Wuulyw/lutPBJhAhtttwCotimPhT1g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=winteri.org; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=NB5UT4WfRVS1aUu+DIzqKqtX/nEPPv0jSr0xuSqm9APhZfeoX+d8Uh+VlfkEJm9VxB 5lVNkfI0YDvKiS5++An0zneU1DTSCoi7CRaCiosDpDoQ6xTWkX2VYeKrhGY1HQzpI2/y J/R7EgWbY2Hnb8YQUtyBMyIl8pQJZMTfvC3/Q=
MIME-Version: 1.0
Received: by 10.151.39.21 with SMTP id r21mr9285799ybj.296.1299007713755; Tue, 01 Mar 2011 11:28:33 -0800 (PST)
Sender: esa@winteri.org
Received: by 10.151.51.5 with HTTP; Tue, 1 Mar 2011 11:28:33 -0800 (PST)
X-Originating-IP: [92.105.66.4]
In-Reply-To: <4D6D4284.50102@thoroquel.org>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org>
Date: Tue, 1 Mar 2011 20:28:33 +0100
X-Google-Sender-Auth: zawkaC6W7SRfRxkrDmn4aQLaWLk
Message-ID: <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
From: Esa Laitinen <esa@laitinen.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: multipart/alternative; boundary=00151750dec656c3b1049d70cd28
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:27:31 -0000

--00151750dec656c3b1049d70cd28
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 1, 2011 at 8:01 PM, Joe Sniderman <
joseph.sniderman@thoroquel.org> wrote:

> Yes, and this is a good thing. It encourages the provider of the data
> (the DNSxL) to be loyal to the consumer of the data, rather than the
> subject of the data.
>
>
There is potential for conflict of interest here, though: what if the
consumer of the data (i.e. paying customer) is also involved in spamming?


-- 
Mr. Esa Laitinen
Tel. +41 76 200 2870
skype/yahoo: reunaesa
Blog: http://happiloppuuahistaa.blogspot.com

--00151750dec656c3b1049d70cd28
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Tue, Mar 1, 2011 at 8:01 PM, Joe Sniderma=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:joseph.sniderman@thoroquel.org">j=
oseph.sniderman@thoroquel.org</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rg=
b(204, 204, 204); padding-left: 1ex;">
Yes, and this is a good thing. It encourages the provider of the data<br>
(the DNSxL) to be loyal to the consumer of the data, rather than the<br>
subject of the data.<br>
<br></blockquote><div>=A0</div><div>There is potential for conflict of inte=
rest here, though: what if the consumer of the data (i.e. paying customer) =
is also involved in spamming? <br><br></div></div><br>-- <br>Mr. Esa Laitin=
en<br>
Tel. +41 76 200 2870<br>skype/yahoo: reunaesa<br>Blog: <a href=3D"http://ha=
ppiloppuuahistaa.blogspot.com" target=3D"_blank">http://happiloppuuahistaa.=
blogspot.com</a><br><br>

--00151750dec656c3b1049d70cd28--

From aiverson@spamresource.com  Tue Mar  1 11:32:28 2011
Return-Path: <aiverson@spamresource.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40983A6A74 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level: 
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 Nzaj-Mjq1HFQ for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:32:28 -0800 (PST)
Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by core3.amsl.com (Postfix) with ESMTP id ED8A93A6A61 for <asrg@irtf.org>; Tue,  1 Mar 2011 11:32:27 -0800 (PST)
Received: by wyb32 with SMTP id 32so5983110wyb.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 11:33:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.162.131 with SMTP id y3mr192720wek.6.1299008010702; Tue, 01 Mar 2011 11:33:30 -0800 (PST)
Received: by 10.216.183.139 with HTTP; Tue, 1 Mar 2011 11:33:30 -0800 (PST)
In-Reply-To: <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
Date: Tue, 1 Mar 2011 13:33:30 -0600
Message-ID: <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com>
From: Al Iverson <aiverson@spamresource.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:32:29 -0000

On Tue, Mar 1, 2011 at 1:28 PM, Esa Laitinen <esa@laitinen.org> wrote:
>
> On Tue, Mar 1, 2011 at 8:01 PM, Joe Sniderman
> <joseph.sniderman@thoroquel.org> wrote:
>>
>> Yes, and this is a good thing. It encourages the provider of the data
>> (the DNSxL) to be loyal to the consumer of the data, rather than the
>> subject of the data.
>>
>
> There is potential for conflict of interest here, though: what if the
> consumer of the data (i.e. paying customer) is also involved in spamming?

I think the conflict is avoiding by not taking money for delistings.
Charging for usage is a wholly separate animal. Either say "who cares,
let the spammers use my data" or have a policy wherein you reserve the
right to stop providing data to anybody at any time, and cut spammers
off.

I'm not seeing an intersection of the two issues here.

Al

From msergeant@messagelabs.com  Tue Mar  1 11:33:33 2011
Return-Path: <msergeant@messagelabs.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C0753A6A86 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:33:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=-0.199, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 Gielbi+mDLya for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:33:32 -0800 (PST)
Received: from mail207.messagelabs.com (mail207.messagelabs.com [85.158.136.67]) by core3.amsl.com (Postfix) with ESMTP id D579B3A6A4A for <asrg@irtf.org>; Tue,  1 Mar 2011 11:33:31 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: msergeant@messagelabs.com
X-Msg-Ref: server-7.tower-207.messagelabs.com!1299008074!13419722!1
X-StarScan-Version: 6.2.9; banners=messagelabs.com,-,-
X-Originating-IP: [95.131.111.138]
Received: (qmail 6050 invoked from network); 1 Mar 2011 19:34:34 -0000
Received: from mlbrn2exc001.messagelabs.com (HELO mlbrn2exc001.messagelabs.com) (95.131.111.138) by server-7.tower-207.messagelabs.com with RC4-SHA encrypted SMTP; 1 Mar 2011 19:34:34 -0000
Received: from smtp-out.devel.messagelabs.com ([10.191.110.53]) by mlbrn2exc001.messagelabs.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 19:34:51 +0000
Received: (qmail 1570 invoked from network); 1 Mar 2011 19:34:33 -0000
Received: from unknown (HELO Valour.local) (10.7.253.21) by matt?dev.int.star.co.uk with SMTP; 1 Mar 2011 19:34:33 -0000
Message-ID: <4D6D4A49.2090107@messagelabs.com>
Date: Tue, 01 Mar 2011 14:34:33 -0500
From: Matt Sergeant <msergeant@messagelabs.com>
User-Agent: Postbox 1.1.5 (Macintosh/20100613)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
In-Reply-To: <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2011 19:34:51.0593 (UTC) FILETIME=[BBD77B90:01CBD847]
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:33:33 -0000

Esa Laitinen wrote:
> There is potential for conflict of interest here, though: what if the 
> consumer of the data (i.e. paying customer) is also involved in spamming?
If they want to pay me to run a blocklist which lists them... go right 
ahead :)

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

From Jose-Marcio.Martins@mines-paristech.fr  Tue Mar  1 11:38:34 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E69303A6A61 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.69
X-Spam-Level: 
X-Spam-Status: No, score=-1.69 tagged_above=-999 required=5 tests=[AWL=-0.240,  BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 7puCxvDynZme for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:38:33 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id 0F72A3A6A4A for <asrg@irtf.org>; Tue,  1 Mar 2011 11:38:15 -0800 (PST)
Received: from localhost.localdomain (joe.j-chkmail.org [88.168.143.55]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p21JdHbE028416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 20:39:17 +0100 (MET)
Message-ID: <4D6D4B64.5070304@mines-paristech.fr>
Date: Tue, 01 Mar 2011 20:39:16 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
In-Reply-To: <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at cascavel with ID 4D6D4B65.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6D4B65.000 from joe.j-chkmail.org/joe.j-chkmail.org/88.168.143.55/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:38:35 -0000

Esa Laitinen wrote:

>
>     Yes, and this is a good thing. It encourages the provider of the data
>     (the DNSxL) to be loyal to the consumer of the data, rather than the
>     subject of the data.
>
> There is potential for conflict of interest here, though: what if the
> consumer of the data (i.e. paying customer) is also involved in spamming?

This is probably an exception.

Normal customers will subscribe (let me use the word subscribe instead of pay) in order to use the 
DNSxL to help him fight spam. Spammers will subscribe, probably, to check if him is blacklisted.

This means, the DNSxL list provider shall tell what's the intended good usage of the list.


-- 
  ---------------------------------------------------------------
  Jose Marcio MARTINS DA CRUZ           http://j-chkmail.ensmp.fr
  Ecole des Mines de Paris
  60, bd Saint Michel                      75272 - PARIS CEDEX 06
  mailto:Jose-Marcio.Martins@mines-paristech.fr

From pantpap@otenet.gr  Tue Mar  1 11:48:14 2011
Return-Path: <pantpap@otenet.gr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 459183A6A79 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 i24tmWG3zfpr for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:48:13 -0800 (PST)
Received: from noc.otenet.gr (noc.otenet.gr [195.170.0.29]) by core3.amsl.com (Postfix) with ESMTP id 294A63A6A44 for <asrg@irtf.org>; Tue,  1 Mar 2011 11:48:12 -0800 (PST)
Received: from [192.168.101.7] (wintermute.otenet.gr [212.205.221.141]) by noc.otenet.gr (Postfix) with ESMTP id EBC638B81FB for <asrg@irtf.org>; Tue,  1 Mar 2011 21:49:15 +0200 (EET)
Message-ID: <4D6D4DDB.2000203@otenet.gr>
Date: Tue, 01 Mar 2011 21:49:47 +0200
From: Pandelis Papanikolaou <pantpap@otenet.gr>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Asrg] + 1 vote + 50 cents
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:48:14 -0000

1 + in favor of draft, from a major Greek ISP.

And now that my alibi is in place, I want to share some general remarks
and thoughts on the issue at hand.

On the long run our strategy may be self defeating.

Mail service became heavily impaired because of spam.  Useful mails were
lost in the pile of junk.

Mail service became even more impaired because of some antispam
strategies . In extreme cases many postmasters apply silent discards so
you don't even get a notification that your email was ditched.

Because of the spam frenzy, postmaster mentality has changed. From
"first do no harm" and "zero mail loss" were are mainly targeting high
filtering ratios, low false positives and acceptable collateral damage.

I was quite amazed when I heard from a "corporate" postmaster that he
prefers to filter out 10 legitimate emails than let 1 spam pass...

Block outgoing 25 , the answer to our troubles... Is it really ?

We have a lot of spammers that are using our mail infrastructure using
client credentials. They wont mind using 587 or 465. They even accept
and adapt to very low rate limits (ex. 2 per minute). Let the botnet do
the work...

And since email popularity is diminishing they are moving to messengers,
forums etc etc

Are we going to block those too or maybe even build a great firewall and
sensor everything ?

Is technology alone able to solve this issue?

Using conventional, legal and ethical means , we will never be able to
compete with the guys writing the viruses and running the botnets. The
only sustainable solution is to break the circle of profit.

Deep Throat: Follow the money. True then, also true now.

If "businesses" are able to continue making money by attracting
"clients" through abusive techniques, no matter what we do, profit will
prevail. Profit will always find a way...

Until we are able to do that, we shall, should, must continue to improve
our mitigation techniques having one priority above all else...
To protect and assure our users  ability to communicate.

Thanks for reading

P.





From trelane@trelane.net  Tue Mar  1 11:53:31 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50AFE3A6A4A for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[AWL=-0.299,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 xda7h2lZ9BnZ for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 11:53:30 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by core3.amsl.com (Postfix) with ESMTP id 7FC543A6A16 for <asrg@irtf.org>; Tue,  1 Mar 2011 11:53:30 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 1318A1864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 14:54:34 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRbEp0+so4lZ for <asrg@irtf.org>; Tue,  1 Mar 2011 14:54:31 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id B49391864B8 for <asrg@irtf.org>; Tue,  1 Mar 2011 14:54:31 -0500 (EST)
Received: from [172.16.1.106] (unknown [66.93.203.199]) by mail.trelane.net (Postfix) with ESMTPA id 37B611864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 14:54:31 -0500 (EST)
Message-ID: <4D6D4EF6.8030601@trelane.net>
Date: Tue, 01 Mar 2011 14:54:30 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4B64.5070304@mines-paristech.fr>
In-Reply-To: <4D6D4B64.5070304@mines-paristech.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 19:53:31 -0000

On 3/1/2011 2:39 PM, Jose-Marcio Martins da Cruz wrote:
>
>
> Normal customers will subscribe (let me use the word subscribe instead
> of pay) in order to use the DNSxL to help him fight spam. Spammers
> will subscribe, probably, to check if him is blacklisted.
>
> This means, the DNSxL list provider shall tell what's the intended
> good usage of the list. 

I think that it is clear given the length of this discussion that there
is not a clear consensus among DNSBL operators, and that the text should
be removed from the draft.  Furthermore, I quite honestly don't care if
DNSBL operators extort spammers.  (I am not currently operating a DNSBL,
and am now considering the extort spammers and those who host them
business model).  As long as this is clearly disclosed in the listing
policies, there is no ethical problem.  Spam is theft, and we must
remember that this is the problem.  ISP's typically now have a clean up
charge in their TOS/AUP (the viability of collecting this I will leave
to discuss another day), there is no ethical reason why a DNSBL should
not have the same policy.  Charging end users to avoid spam is
profiteering off of crime.  Better to charge the criminal scum, and
those who host them.

Andrew

From kelly.molloy@gmail.com  Tue Mar  1 12:03:37 2011
Return-Path: <kelly.molloy@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4E863A6AB2 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:03:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[AWL=-0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 m0hUKuWcZhPq for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:03:37 -0800 (PST)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by core3.amsl.com (Postfix) with ESMTP id EFDBA3A68A4 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:03:06 -0800 (PST)
Received: by yxl31 with SMTP id 31so2434158yxl.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 12:04:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=Irae1YQBEcXl7P4Ko065j9Pwfg7PGLtI5vc+K5iiKrg=; b=hi3mSoREHztKRO3D+dZcw5wT8yxCuy/Ubf6WRJF8ZR+7gJB/dvMzwPwROzsh7Q7zJf S/XP/CVwy+qdAYwk+8HCqQbvkbhi51uHLwMzQ5U8fgNoPa3FzKANI1W98bzVy/YynJkF b91srAXjuVgVJiPgcxcKS87kMFeDIfgQrntE0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=VssQrnhfUBAnkZLwWZlIJ/aCHnSvstrY0mY8Ct+144nRx7gbeIwSDfNp/nbowiM2Ia orz4k6de4NOIWzhaZsELwN/wvvMxuYp1lfSJfpk2/+GQOtNqKuEqSHcxTQyliFnvzFPr lpqd3k2n3OEBW19zz+VyxwDZ4oeev9BA7MCws=
MIME-Version: 1.0
Received: by 10.147.167.12 with SMTP id u12mr8823784yao.13.1299009850259; Tue, 01 Mar 2011 12:04:10 -0800 (PST)
Received: by 10.147.167.12 with HTTP; Tue, 1 Mar 2011 12:04:10 -0800 (PST)
In-Reply-To: <4D6D4EF6.8030601@trelane.net>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net>
Date: Tue, 1 Mar 2011 12:04:10 -0800
Message-ID: <AANLkTikdTfYzSXL5ZOCG=18xRnye57YSfv79UVmY5zsZ@mail.gmail.com>
From: Kelly Molloy <kelly.molloy@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:03:37 -0000

On Tue, Mar 1, 2011 at 11:54 AM, Andrew Kirch <trelane@trelane.net> wrote:

> I think that it is clear given the length of this discussion that there
> is not a clear consensus among DNSBL operators, and that the text should
> be removed from the draft. =A0Furthermore, I quite honestly don't care if
> DNSBL operators extort spammers. =A0(I am not currently operating a DNSBL=
,
> and am now considering the extort spammers and those who host them
> business model). =A0As long as this is clearly disclosed in the listing
> policies, there is no ethical problem. =A0Spam is theft, and we must
> remember that this is the problem. =A0ISP's typically now have a clean up
> charge in their TOS/AUP (the viability of collecting this I will leave
> to discuss another day), there is no ethical reason why a DNSBL should
> not have the same policy. =A0Charging end users to avoid spam is
> profiteering off of crime. =A0Better to charge the criminal scum, and
> those who host them.

ISPs have a clean up charge because they incur direct costs when their
customers spam, and it's set forth in the contract between the
customer and the provider and everyone agrees to it. The people who
own the IPs listed in a DNSBL don't have a contract with the operator.
If you want to recover from them, use the courts. A DNSBL operator
doesn't have standing to punish or fine anyone; they're not the
police.

--kelly

From sethb@panix.com  Tue Mar  1 12:04:54 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4067E3A6A16 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:04:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 tpgfgTfizoj5 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:04:53 -0800 (PST)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by core3.amsl.com (Postfix) with ESMTP id 379463A68A4 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:04:53 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail2.panix.com (Postfix) with ESMTP id 9AF9538E41 for <asrg@irtf.org>; Tue,  1 Mar 2011 15:05:56 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 7081D24200; Tue,  1 Mar 2011 15:05:56 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> (message from Neil Schwartzman on Tue, 1 Mar 2011 10:21:17 -0500)
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
Message-Id: <20110301200556.7081D24200@panix5.panix.com>
Date: Tue,  1 Mar 2011 15:05:56 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:04:54 -0000

Neil Schwartzman <neil@cauce.org> wrote:

> Allow me to take a brief moment to draw a significant line between
> the Spamhaus business model, and one based upon delisting. For those
> too drunk, blind, or somehow mentally deficient to spot it for
> themselves, it is simple. One charges the beneficiaries of a given
> DNSBL (Spamhaus) and thus motivates a blacklist operator to run the
> very best product possible.

Why do you believe there is no incentive to run a not-quite-as-good
product if either (1) it's a lot cheaper to do that, or (2) doing that
provides more revenue (e.g. not listing a large customer who would
cease being a customer if listed)?

>  The other, such as previously done by SORBS, or now UCE Protect,
>  motivates the DNSBL operator to list as many IPs as possible (1)
>  for financial profit.

Then why not list 0/0 and maximize revenue?  Obviously, the
willingness of listees to pay for (expedited) removal depends on the
amount of usage the list gets, and false positives tend to decrease
that usage.  There is therefore the same sort of tension between doing
what provides immediate revenue and keeping the list going (and,
presumably, profitable) in the long term.

> (1) UCE Protect claims to have listed a significant number of IPs in the past week:
>
> Spammer listings within the last 7 days:
> Level 1: 1767801 IP's, Level 2: 21354 Allocations, Level 3: 583 ASN's. Last Updated: 01.03.2011 13:01 CET

Given automatic 7-day delisting, at least for Level 1, isn't that
actually the full size of their list?  Their page seems to indicate a
decrease in the size of Level 1, which would argue that way.

Seth

From martijn.grooten@virusbtn.com  Tue Mar  1 12:07:28 2011
Return-Path: <martijn.grooten@virusbtn.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DEBB3A6AAF for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.55
X-Spam-Level: 
X-Spam-Status: No, score=-4.55 tagged_above=-999 required=5 tests=[AWL=1.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 SD0m+qUJ2m6M for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:07:27 -0800 (PST)
Received: from mx4.sophos.com (mx4.sophos.com [74.202.89.161]) by core3.amsl.com (Postfix) with ESMTP id 89FF03A6A9C for <asrg@irtf.org>; Tue,  1 Mar 2011 12:07:27 -0800 (PST)
Received: from mx4.sophos.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 24F9B7017A for <asrg@irtf.org>; Tue,  1 Mar 2011 20:08:31 +0000 (GMT)
Received: from uk-exch1.green.sophos (uk-exch1.green.sophos [10.100.199.16]) by mx4.sophos.com (Postfix) with ESMTP id AD6907014E for <asrg@irtf.org>; Tue,  1 Mar 2011 20:08:30 +0000 (GMT)
Received: from UK-EXCHMBX1.green.sophos ([fe80:0000:0000:0000:e1bd:d3c1:23.222.229.221]) by uk-exch1.green.sophos ([10.100.199.16]) with mapi; Tue, 1 Mar 2011 20:08:29 +0000
From: Martijn Grooten <martijn.grooten@virusbtn.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Tue, 1 Mar 2011 20:08:27 +0000
Thread-Topic: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
Thread-Index: AcvYR7hFMXXZAJ7RTV24JQTGDCW3xQAAxouQ
Message-ID: <18B53BA2A483AD45962AAD1397BE132537AEDC1BA2@UK-EXCHMBX1.green.sophos>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4A49.2090107@messagelabs.com>
In-Reply-To: <4D6D4A49.2090107@messagelabs.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:07:28 -0000

Matt Sergeant wrote:
> Esa Laitinen wrote:
> > There is potential for conflict of interest here, though: what if the
> > consumer of the data (i.e. paying customer) is also involved in
> spamming?
>
> If they want to pay me to run a blocklist which lists them... go right
> ahead :)

ISPs or SaaS-solutions (if they offer both inbound and outbound filtering) =
may well be users (customers) of a blacklist for their inbound filtering an=
d at the same time occasionally find their outbound IP addresses listed on =
the same blacklist.

There is some potential conflict of interest there, albeit not one that wor=
ries me a great deal. I believe that the more honest blacklists, the ones t=
hat list their customers' IP addresses/domains if they think there is a nee=
d for that, will be the better ones and, ultimately, the ones that survive.

I actually find the various possible conflicts of interest not the most imp=
ortant problem with (speedy) delisting fees. I think it is simply wrong for=
 an entity to hand out fines for bad behaviour if they have not been given =
permission to do so, either by the entity that is being fined (which may ha=
ve explicitly or implicitly agreed to T&Cs that include the possibility of =
fines) or by some kind of higher authority (of which there isn't really one=
 on the internet). Even more so if there isn't a way for those being fined =
to contest that decision with an impartial arbiter.

This is all regardless of whether such fines have an effect on the amount o=
f spam being sent, whether they educate their users, whether they are given=
 to those who deserve it and whether those receiving the fines actually ben=
efit from them.

Oh, and for whoever is counting: +1 on the draft from me.

Martijn.

Virus Bulletin Ltd, The Pentagon, Abingdon, OX14 3YP, England.
Company Reg No: 2388295. VAT Reg No: GB 532 5598 33.

From johnl@iecc.com  Tue Mar  1 12:27:01 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 103473A68A4 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.444
X-Spam-Level: 
X-Spam-Status: No, score=-110.444 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 det4X0MzeBVt for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:27:00 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id C32823A6A28 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:26:59 -0800 (PST)
Received: (qmail 80710 invoked from network); 1 Mar 2011 20:28:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=13b45.4d6d56d3.k1103; i=johnl@submit.iecc.com; bh=CoZzHbiFyybHYQzuDUkz6G5oShgfmgkHDhWo5UvzfW8=; b=W7EiQUfgX52eagJUuLQi18zOpXCsn/yeYn+h/zn4Jm2Jic1jsIXIOIQhsnIvkseNpzq3U55if8pKc3IoKDdV+S6vLIDqhU7xecTZrfZqfRzsV6pcAb4Ji4mNuc6JAFrLt3zvD4G5d/DQdjnKq/Q4ralT9aOxPkX7bhdcKwaejUI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Mar 2011 20:27:40 -0000
Date: 1 Mar 2011 15:28:02 -0500
Message-ID: <alpine.BSF.2.00.1103011507460.22961@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:27:01 -0000

Now that the kerfuffle seems to have died down, I'd like to see if we have 
group rough consensus (which does not mean perfect unanimity) on the BL 
best practices overview.  Please read through it and say whether you think 
it's OK, or if not, what specific language to change.

Keep in mind that this is an overview of actual practices of well run BLs 
(that's the C in BCP), so if you think we should change something, it 
would be helpful to identify a well-run BL whose practices support the 
proposed change.  Hence it would be completely unhelpful to say "I don't 
run a BL but if I did I would do X."

It is also not very helpful to say "BL X, which 12 people use, does Y" 
since there are vast numbers of obscure BLs with totally wacky practices.

Here's the current draft:

http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-07

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From Jose-Marcio.Martins@mines-paristech.fr  Tue Mar  1 12:28:24 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B796D3A68A4 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:28:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level: 
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[AWL=-0.200,  BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 9TosmZAaI3n7 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:28:23 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id D943B3A6A28 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:28:06 -0800 (PST)
Received: from localhost.localdomain (joe.j-chkmail.org [88.168.143.55]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p21KT8dr028773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 21:29:09 +0100 (MET)
Message-ID: <4D6D5713.3080205@mines-paristech.fr>
Date: Tue, 01 Mar 2011 21:29:07 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net>
In-Reply-To: <4D6D4EF6.8030601@trelane.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at cascavel with ID 4D6D5714.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6D5714.000 from joe.j-chkmail.org/joe.j-chkmail.org/88.168.143.55/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:28:24 -0000

Andrew Kirch wrote:
> On 3/1/2011 2:39 PM, Jose-Marcio Martins da Cruz wrote:

>> This means, the DNSxL list provider shall tell what's the intended
>> good usage of the list.

Hmmmm.... don't use my arguments this way... ;-)

>
> I think that it is clear given the length of this discussion that there
> is not a clear consensus among DNSBL operators, and that the text should
> be removed from the draft.  Furthermore, I quite honestly don't care if
> DNSBL operators extort spammers.  (I am not currently operating a DNSBL,
> and am now considering the extort spammers and those who host them
> business model).  As long as this is clearly disclosed in the listing
> policies, there is no ethical problem.  Spam is theft, and we must
> remember that this is the problem.  ISP's typically now have a clean up
> charge in their TOS/AUP (the viability of collecting this I will leave
> to discuss another day), there is no ethical reason why a DNSBL should
> not have the same policy.  Charging end users to avoid spam is
> profiteering off of crime.  Better to charge the criminal scum, and
> those who host them.

Well, there are two possibilities :

* charge users to help them to be protected against spam. IMHO, this is the only purpose of DNSBLs.

* charge "criminal scum, and those who host them".

Well, for the second possibility, there are two ways of see this :

* as long as I know, nobody is accredited to act as some sort of "Internet Police". The only 
possibility to apply fines or condamnations are by means of some legal actions imposed by some 
official administration.

* the other possibility, getting money from spammers to delist them and let them continue 
spamming... I'm not a lawyer but I assimilate this as some sort of "money laundry".

Two more cents...

I was a little shocked when looking at uceprotect.org site, by the phrases : "we will stop all 
spammers in this planet" and "WARNING: Do not play around here. You have no idea who we really are, 
and what will happen to you!"...



From hjp-asrg@hjp.at  Tue Mar  1 12:35:27 2011
Return-Path: <hjp-asrg@hjp.at>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A3453A6A8B for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.858
X-Spam-Level: 
X-Spam-Status: No, score=0.858 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, SARE_SUB_RAND_LETTRS4=0.799]
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 eihqCqvW1BW0 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:35:26 -0800 (PST)
Received: from zeno.hjp.at (ns1.hjp.at [212.17.106.132]) by core3.amsl.com (Postfix) with ESMTP id 2A38C3A6A28 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:35:25 -0800 (PST)
Received: by zeno.hjp.at (Postfix, from userid 1000) id 3595B4045; Tue,  1 Mar 2011 21:36:28 +0100 (CET)
Date: Tue, 1 Mar 2011 21:36:28 +0100
From: "Peter J. Holzer" <hjp-asrg@hjp.at>
To: asrg@irtf.org
Message-ID: <20110301203628.GB13178@hjp.at>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net> <4D6D5713.3080205@mines-paristech.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fba/0zbH8Xs+Fj9o"
Content-Disposition: inline
In-Reply-To: <4D6D5713.3080205@mines-paristech.fr>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:35:27 -0000

--Fba/0zbH8Xs+Fj9o
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2011-03-01 21:29:07 +0100, Jose-Marcio Martins da Cruz wrote:
> I was a little shocked when looking at uceprotect.org site, by the=20
> phrases : "we will stop all spammers in this planet" and "WARNING: Do not=
=20
> play around here. You have no idea who we really are, and what will=20
> happen to you!"...

Hmm:

% wget http://uceprotect.org
| 2011-03-01 21:32:47--  http://uceprotect.org/
| Resolving uceprotect.org... 217.23.49.208
| Connecting to uceprotect.org|217.23.49.208|:80... connected.
| HTTP request sent, awaiting response... 302 Found
| Location: http://www.nsa.gov [following]
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| --2011-03-01 21:32:47--  http://www.nsa.gov/
| Resolving www.nsa.gov... 12.120.172.8
| Connecting to www.nsa.gov|12.120.172.8|:80... connected.
| HTTP request sent, awaiting response... 200 OK
| Length: 18099 (18K) [text/html]
| Saving to: =E2=80=9Cindex.html=E2=80=9D

Now we know who they really are ;-).

	hp


--=20
   _  | Peter J. Holzer    | Web 2.0 k=C3=B6nnte man also auch =C3=BCberset=
zen als
|_|_) | Sysadmin WSR       | "Netz der kleinen Geister".
| |   | hjp@hjp.at         |=20
__/   | http://www.hjp.at/ |  -- Oliver Cromm in desd



--Fba/0zbH8Xs+Fj9o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFNbVjMfZ+RkG8quy0RAkRVAKCopEvKG7VKD+qChOZ7W6G3BVj/cQCgpaYo
phNysmbAIQKmlZW9+XWoHjs=
=kTl2
-----END PGP SIGNATURE-----

--Fba/0zbH8Xs+Fj9o--

From sethb@panix.com  Tue Mar  1 12:37:41 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35CD23A6A79 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 Hs0itWI2P9ye for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:37:40 -0800 (PST)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by core3.amsl.com (Postfix) with ESMTP id 53EF33A67B5 for <asrg@irtf.org>; Tue,  1 Mar 2011 12:37:40 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail2.panix.com (Postfix) with ESMTP id 0018F38E44 for <asrg@irtf.org>; Tue,  1 Mar 2011 15:38:43 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id E812124200; Tue,  1 Mar 2011 15:38:43 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com> (message from Al Iverson on Tue, 1 Mar 2011 13:33:30 -0600)
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com>
Message-Id: <20110301203843.E812124200@panix5.panix.com>
Date: Tue,  1 Mar 2011 15:38:43 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:37:41 -0000

Al Iverson <aiverson@spamresource.com> wrote:
> On Tue, Mar 1, 2011 at 1:28 PM, Esa Laitinen <esa@laitinen.org> wrote:
>> On Tue, Mar 1, 2011 at 8:01 PM, Joe Sniderman
>> <joseph.sniderman@thoroquel.org> wrote:
>>>
>>> Yes, and this is a good thing. It encourages the provider of the data
>>> (the DNSxL) to be loyal to the consumer of the data, rather than the
>>> subject of the data.
>>
>> There is potential for conflict of interest here, though: what if the
>> consumer of the data (i.e. paying customer) is also involved in spamming?
>
> I think the conflict is avoiding by not taking money for delistings.

Consider: BigISP is a large user of DNSBL, and pays a lot of money to
DSNBL for that usage.  BigISP gets a high-paying spammer it doesn't
want to remove, and tells DNSBL "If you list us, we'll stop using you
and stop paying you."

How is there no conflict of interest in that case?  There's no charge
for delistings involved.

> Charging for usage is a wholly separate animal. Either say "who cares,
> let the spammers use my data" or have a policy wherein you reserve the
> right to stop providing data to anybody at any time, and cut spammers
> off.

Charging for _anything_ means you have customers who have financial
influence over you.

> I'm not seeing an intersection of the two issues here.

Does this help?

Seth

From sethb@panix.com  Tue Mar  1 12:39:19 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8954A3A6A8C for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[AWL=-0.100,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 FPY0+EWoVFEi for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:39:18 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 8C2043A69CC for <asrg@irtf.org>; Tue,  1 Mar 2011 12:39:18 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id 361D51F092 for <asrg@irtf.org>; Tue,  1 Mar 2011 15:40:22 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 1EAAC24200; Tue,  1 Mar 2011 15:40:22 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <4D6D4A49.2090107@messagelabs.com> (message from Matt Sergeant on Tue, 01 Mar 2011 14:34:33 -0500)
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4A49.2090107@messagelabs.com>
Message-Id: <20110301204022.1EAAC24200@panix5.panix.com>
Date: Tue,  1 Mar 2011 15:40:22 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:39:19 -0000

Matt Sergeant <msergeant@messagelabs.com> wrote:
> Esa Laitinen wrote:
>> There is potential for conflict of interest here, though: what if the 
>> consumer of the data (i.e. paying customer) is also involved in spamming?
> If they want to pay me to run a blocklist which lists them... go right 
> ahead :)

I trust you, personally, to do the right thing; however, I recognize
that a conflict of interest *exists*.

Seth

From Jose-Marcio.Martins@mines-paristech.fr  Tue Mar  1 12:48:53 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E9DC3A6AAE for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level: 
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[AWL=-0.171, BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 C4cmYBoJtQCq for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 12:48:52 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id 685F13A69CC for <asrg@irtf.org>; Tue,  1 Mar 2011 12:48:51 -0800 (PST)
Received: from localhost.localdomain (joe.j-chkmail.org [88.168.143.55]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p21KnrrC028902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 21:49:54 +0100 (MET)
Message-ID: <4D6D5BF0.6000805@mines-paristech.fr>
Date: Tue, 01 Mar 2011 21:49:52 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net>	<4D6D5713.3080205@mines-paristech.fr> <20110301203628.GB13178@hjp.at>
In-Reply-To: <20110301203628.GB13178@hjp.at>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Miltered: at cascavel with ID 4D6D5BF1.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6D5BF1.000 from joe.j-chkmail.org/joe.j-chkmail.org/88.168.143.55/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 20:48:53 -0000

Peter J. Holzer wrote:

>
> % wget http://uceprotect.org
> | 2011-03-01 21:32:47--  http://uceprotect.org/
> | Resolving uceprotect.org... 217.23.49.208
> | Connecting to uceprotect.org|217.23.49.208|:80... connected.
> | HTTP request sent, awaiting response... 302 Found
> | Location: http://www.nsa.gov [following]
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> | --2011-03-01 21:32:47--  http://www.nsa.gov/
> | Resolving www.nsa.gov... 12.120.172.8
> | Connecting to www.nsa.gov|12.120.172.8|:80... connected.
> | HTTP request sent, awaiting response... 200 OK
> | Length: 18099 (18K) [text/html]
> | Saving to: “index.html”
>
> Now we know who they really are ;-).

Not sure. They're cheating.

The result you've got is for http://uceprotect.org. If you try http://www.uceprotect.org, you'll see 
their real web site.

Either way, I don't think this kind of lack of transparency can be part of a BCP.


From linford@spamhaus.org  Tue Mar  1 13:04:24 2011
Return-Path: <linford@spamhaus.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C20DB3A69F9 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.73
X-Spam-Level: 
X-Spam-Status: No, score=-17.73 tagged_above=-999 required=5 tests=[AWL=0.670,  BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3,  RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
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 UioK-7bj+gMg for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:04:23 -0800 (PST)
Received: from smtp-ext-layer.spamhaus.org (ns8.spamhaus.org [82.94.216.239]) by core3.amsl.com (Postfix) with ESMTP id 9968D3A6AC9 for <asrg@irtf.org>; Tue,  1 Mar 2011 13:04:23 -0800 (PST)
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com> <20110301203843.E812124200@panix5.panix.com>
In-Reply-To: <20110301203843.E812124200@panix5.panix.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From: Steve Linford <linford@spamhaus.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Local-MTA-Info: 
X-Mime-Info: text/plain
Message-ID: <A.1PuWl4-000NJL-4x@smtp-ext-layer.spamhaus.org>
Date: Tue, 01 Mar 2011 21:05:26 +0000
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:04:24 -0000

On 1 Mar 2011, at 21:38, Seth wrote:

> Consider: BigISP is a large user of DNSBL, and pays a lot of money to
> DSNBL for that usage.  BigISP gets a high-paying spammer it doesn't
> want to remove, and tells DNSBL "If you list us, we'll stop using you
> and stop paying you."

In your scenario the DNSBL is entering into a pink contract with a =
spam-friendly ISP to facilitate spam to the DNSBL's other paying =
customers.

You could help bolster your scenario by using as example some criminal =
botnet gangs as the DNSBL customers, since they can pay much more to the =
DNSBL to let tons of botnet spam through. If a DNSBL is going to make a =
pink contract with an ISP to let spam through for money, why stop there?

(it's a rhetorical question, no need for an answer)

  Steve Linford
  The Spamhaus Project
  http://www.spamhaus.org
 =20


From hjp-asrg@hjp.at  Tue Mar  1 13:05:43 2011
Return-Path: <hjp-asrg@hjp.at>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68A1E3A69F9 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.113
X-Spam-Level: 
X-Spam-Status: No, score=0.113 tagged_above=-999 required=5 tests=[AWL=0.744,  BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, SARE_SUB_RAND_LETTRS4=0.799]
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 Qp4JuXgDO+BR for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:05:42 -0800 (PST)
Received: from zeno.hjp.at (ns1.hjp.at [212.17.106.132]) by core3.amsl.com (Postfix) with ESMTP id 256143A67B5 for <asrg@irtf.org>; Tue,  1 Mar 2011 13:05:41 -0800 (PST)
Received: by zeno.hjp.at (Postfix, from userid 1000) id 051114045; Tue,  1 Mar 2011 22:06:45 +0100 (CET)
Date: Tue, 1 Mar 2011 22:06:44 +0100
From: "Peter J. Holzer" <hjp-asrg@hjp.at>
To: asrg@irtf.org
Message-ID: <20110301210644.GA2588@hjp.at>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net> <4D6D5713.3080205@mines-paristech.fr> <20110301203628.GB13178@hjp.at> <4D6D5BF0.6000805@mines-paristech.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc"
Content-Disposition: inline
In-Reply-To: <4D6D5BF0.6000805@mines-paristech.fr>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:05:43 -0000

--C7zPtVaVf+AK4Oqc
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2011-03-01 21:49:52 +0100, Jose-Marcio Martins da Cruz wrote:
> Peter J. Holzer wrote:
>> % wget http://uceprotect.org
>> | 2011-03-01 21:32:47--  http://uceprotect.org/
>> | Resolving uceprotect.org... 217.23.49.208
>> | Connecting to uceprotect.org|217.23.49.208|:80... connected.
>> | HTTP request sent, awaiting response... 302 Found
>> | Location: http://www.nsa.gov [following]
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> Now we know who they really are ;-).
>
> Not sure. They're cheating.

I am sure. They are playing silly games, trying to scare the
kids=17spammers. Of course they have nothing to do with the NSA, anybody
can set a redirect.

> The result you've got is for http://uceprotect.org. If you try=20
> http://www.uceprotect.org, you'll see their real web site.

Yup, I know. I just thought it was amusing, and it fit the ominous "You
have no idea who we really are".

	hp


--=20
   _  | Peter J. Holzer    | Web 2.0 k=F6nnte man also auch =FCbersetzen als
|_|_) | Sysadmin WSR       | "Netz der kleinen Geister".
| |   | hjp@hjp.at         |=20
__/   | http://www.hjp.at/ |  -- Oliver Cromm in desd



--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFNbV/kfZ+RkG8quy0RAg2UAJ0bcBtbL5gLGf2G963i1b0U0p624gCfTEHv
zBbvus/xIs+Ai/zQyc+k4y4=
=x1ca
-----END PGP SIGNATURE-----

--C7zPtVaVf+AK4Oqc--

From sethb@panix.com  Tue Mar  1 13:11:30 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 009EB3A69F9 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:11:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[AWL=-0.080,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 5pg-Xm5wiwyz for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:11:28 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 066E43A67B5 for <asrg@irtf.org>; Tue,  1 Mar 2011 13:11:26 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id D3A271F087 for <asrg@irtf.org>; Tue,  1 Mar 2011 16:12:29 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id C5E6324200; Tue,  1 Mar 2011 16:12:29 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <AANLkTikdTfYzSXL5ZOCG=18xRnye57YSfv79UVmY5zsZ@mail.gmail.com> (message from Kelly Molloy on Tue, 1 Mar 2011 12:04:10 -0800)
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net> <AANLkTikdTfYzSXL5ZOCG=18xRnye57YSfv79UVmY5zsZ@mail.gmail.com>
Message-Id: <20110301211229.C5E6324200@panix5.panix.com>
Date: Tue,  1 Mar 2011 16:12:29 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:11:30 -0000

Kelly Molloy <kelly.molloy@gmail.com> wrote:

> The people who own the IPs listed in a DNSBL don't have a contract
> with the operator.  If you want to recover from them, use the
> courts. A DNSBL operator doesn't have standing to punish or fine
> anyone; they're not the police.

Listing in a DNSBL (that's used to the detriment of the listee,
e.g. for blocking email) is itself a punishment, and the DNSBL
operator clearly has standing to list in the DNSBL.

There's no "fine" involved in any case, because nobody is forced to
pay anything.

Seth

From UUkutt@synacor.com  Tue Mar  1 13:16:14 2011
Return-Path: <UUkutt@synacor.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 468A53A6ACA for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_RAND_LETTRS4=0.799]
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 Fmztng4yQxTx for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:16:12 -0800 (PST)
Received: from mail.corp.synacor.com (mail.corp.synacor.com [38.97.88.19]) by core3.amsl.com (Postfix) with ESMTP id C23C03A6ACD for <asrg@irtf.org>; Tue,  1 Mar 2011 13:16:10 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBD856.091AABF3"
Date: Tue, 1 Mar 2011 16:17:13 -0500
Message-ID: <043157728A92A64B935F119F3E3947A9099231DC@syncorpmail.synbuf.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Asrg] draft-irtf-asrg-bcp-blacklists-07
Thread-Index: AcvYVgjHFQDDOMcOR3ynqMaukvWNew==
X-Priority: 1
priority: Urgent
Importance: high
From: "Udeme Ukutt" <UUkutt@synacor.com>
To: <asrg@irtf.org>
Subject: [Asrg]  draft-irtf-asrg-bcp-blacklists-07
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:16:14 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBD856.091AABF3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I took some time to review the BCP 07 draft, and I'm in consensus on the
draft. Please add my vote as well.

=20

Thanks,

=20

Udeme Ukutt

Postmaster, Synacor Inc.

http://www.synacor.com=20

twitter: uukutt


------_=_NextPart_001_01CBD856.091AABF3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:black;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:black'>I took some time to review the BCP 07 draft, and =
I&#8217;m in consensus on the draft. Please add my vote as =
well.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:black'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:black'>Udeme =
Ukutt<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Postmaster, Synacor Inc.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:black'><a =
href=3D"http://www.synacor.com">http://www.synacor.com</a> =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>twitter: =
uukutt<o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CBD856.091AABF3--

From geemailenator@gmail.com  Tue Mar  1 13:18:10 2011
Return-Path: <geemailenator@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6C84B3A6A16 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level: 
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=-0.250,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 4zW9r62A7HBC for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:18:09 -0800 (PST)
Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by core3.amsl.com (Postfix) with ESMTP id 2A58A3A67D6 for <asrg@irtf.org>; Tue,  1 Mar 2011 13:18:09 -0800 (PST)
Received: by vxc34 with SMTP id 34so5322765vxc.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 13:19:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=WDClkaNoFNB2ZdcgO/eh5cpavRZrmqlQ1eOfkkDE/ds=; b=hZz6dMHYX0lsGZaKK0qgqKSlciQSws3r7sOAcRV00aQh65sIrxSrFE1AnXF0vQIEK5 yrFbzYkCg2azr5ZGacbgdw92m4t4YO4MHzbwb3F05N7niT4MNe/+eosvAOMsGpDGwBeY RMfTqrsisGnJbX05XmiejkUVe7JnCanTjEJy8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=ouLeFn0S9ETl5Zx2TIaVYqVhAwTcpv22BP6ivtOfacOK2XgE2tb4CCiMA9n1PFfAxP 8QBnxs5kiXHyA5OHLiIw9M594xQcZw/P5T02gLZDJID+K8U54EMtuDfOjb/wKfs4B4jO O7zgOVwlqZrqWXX3BXjX4c+pYH+VYFlHqXvV0=
Received: by 10.52.167.72 with SMTP id zm8mr11867051vdb.228.1299014102550; Tue, 01 Mar 2011 13:15:02 -0800 (PST)
Received: from [172.16.1.2] (modemcable156.249-57-74.mc.videotron.ca [74.57.249.156]) by mx.google.com with ESMTPS id i14sm2404034vcr.11.2011.03.01.13.15.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 13:15:01 -0800 (PST)
Sender: Neil Schwartzman <geemailenator@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Neil Schwartzman <neil@cauce.org>
In-Reply-To: <A.1PuWl4-000NJL-4x@smtp-ext-layer.spamhaus.org>
Date: Tue, 1 Mar 2011 16:14:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEF93F0E-74A4-4A54-B31A-486B0A5607FD@cauce.org>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com> <20110301203843.E812124200@panix5.panix.com> <A.1PuWl4-000NJL-4x@smtp-ext-layer.spamhaus.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:18:10 -0000

On Mar 1, 2011, at 4:05 PM, Steve Linford wrote:

> On 1 Mar 2011, at 21:38, Seth wrote:
>=20
>> Consider: BigISP is a large user of DNSBL, and pays a lot of money to
>> DSNBL for that usage.  BigISP gets a high-paying spammer it doesn't
>> want to remove, and tells DNSBL "If you list us, we'll stop using you
>> and stop paying you."
>=20
> In your scenario the DNSBL is entering into a pink contract with a =
spam-friendly ISP to facilitate spam to the DNSBL's other paying =
customers.
>=20
> You could help bolster your scenario by using as example some criminal =
botnet gangs as the DNSBL customers, since they can pay much more to the =
DNSBL to let tons of botnet spam through. If a DNSBL is going to make a =
pink contract with an ISP to let spam through for money, why stop there?
>=20
> (it's a rhetorical question, no need for an answer)
>=20


Let's use another example. Spamhaus has, IIRC listed Microsoft IPs. =
(lve.com spam hosting about 18 months ago?). Surely your largest =
customer beat you over the head to have them delisted, no? Paid you =
enough to delist them, and put the rest of your users in jeopardy?=20

(it's a rhetorical question, no need for an answer)

If an DNSBL is respected well enough to be used by a large ISP (and very =
few are, and relatively few do, respectively), one assumes they respect =
the quality of the data well enough not to try to interfere, lest said =
DNSBL go public. Besides which, let's say Spamhaus took a bribe. How =
long until hotmail figures if they can take an indirect bribe, they can =
take one directly. Thus, the credibility goes out the window, and soon =
after, the contract with the DNSBL.

Anyway, this is my last post on this subject; the Chair has called the =
question and we should probably best serve the issue by reviewing the =
document, suggesting changes, and trying to achieve consensus.

--
Neil Schwartzman
Executive Director
CAUCE
The Coalition Against Unsolicited Commercial Email, North America Inc.

http://cauce.org
http://twitter.com/cauce
IM: caucecanada
Tel.: +1 (303) 800 6345





From sethb@panix.com  Tue Mar  1 13:49:46 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 568813A6A16 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:49:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.867
X-Spam-Level: 
X-Spam-Status: No, score=-1.867 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 e5YkveU1XUw7 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 13:49:44 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 77E2E3A67D6 for <asrg@irtf.org>; Tue,  1 Mar 2011 13:49:44 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id CFB4D1F08E; Tue,  1 Mar 2011 16:50:47 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id A6B3624200; Tue,  1 Mar 2011 16:50:47 -0500 (EST)
From: Seth <sethb@panix.com>
To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <4D6D5713.3080205@mines-paristech.fr> (message from Jose-Marcio Martins da Cruz on Tue, 01 Mar 2011 21:29:07 +0100)
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr> <4D6D4EF6.8030601@trelane.net> <4D6D5713.3080205@mines-paristech.fr>
Message-Id: <20110301215047.A6B3624200@panix5.panix.com>
Date: Tue,  1 Mar 2011 16:50:47 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 21:49:46 -0000

Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
wrote:

> Well, there are two possibilities :
>
> * charge users to help them to be protected against spam. IMHO, this is the only purpose of DNSBLs.
>
> * charge "criminal scum, and those who host them".

There are more than those two possibilities.

First, there is no necessity to charge anybody; many lists don't.

Second, there are people who are neither users of the DNSBL nor
criminal scum or those who host them, who might be charged.

> * as long as I know, nobody is accredited to act as some sort of
> "Internet Police". The only possibility to apply fines or
> condamnations are by means of some legal actions imposed by some
> official administration.

That's the only way anybody can be *forced* to pay.  A DNSBL that
charges for (expedited) delisting isn't forcing anybody to do
anything.

> * the other possibility, getting money from spammers to delist them
> and let them continue spamming...

If there were a way to stop them from spamming, we wouldn't be having
this discussion in the first place.

> I'm not a lawyer but I assimilate this as some sort of "money
> laundry".

That has nothing to do with "laundering money".

Any DNSBL that took money not to list spammers would get little usage,
so there would be essentially no benefit to paying it.

A DNSBL that takes money to delist immediately, and is quite willing
to re-list 3 seconds later if the spam continues, isn't particularly
harming its customers for allow spam for 3 seconds.

Seth

From Jose-Marcio.Martins@mines-paristech.fr  Tue Mar  1 14:05:57 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E64823A69FE for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 14:05:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 INKPMFzU8H9d for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 14:05:57 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id 074C53A6AB8 for <asrg@irtf.org>; Tue,  1 Mar 2011 14:05:56 -0800 (PST)
Received: from localhost.localdomain (joe.j-chkmail.org [88.168.143.55]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p21M6weM029436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 23:06:58 +0100 (MET)
Message-ID: <4D6D6E00.4020507@mines-paristech.fr>
Date: Tue, 01 Mar 2011 23:06:56 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net> <4D6D5713.3080205@mines-paristech.fr> <20110301215047.A6B3624200@panix5.panix.com>
In-Reply-To: <20110301215047.A6B3624200@panix5.panix.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at cascavel with ID 4D6D6E02.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6D6E02.000 from joe.j-chkmail.org/joe.j-chkmail.org/88.168.143.55/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 22:05:58 -0000

Seth wrote:
> Jose-Marcio Martins da Cruz<Jose-Marcio.Martins@mines-paristech.fr>
> wrote:

>
>> I'm not a lawyer but I assimilate this as some sort of "money
>> laundry".
>
> That has nothing to do with "laundering money".
>
> Any DNSBL that took money not to list spammers would get little usage,
> so there would be essentially no benefit to paying it.
>
> A DNSBL that takes money to delist immediately, and is quite willing
> to re-list 3 seconds later if the spam continues, isn't particularly
> harming its customers for allow spam for 3 seconds.

If one consider that spammers money is dirty money (criminal activity as one said)... and if part of 
the DNSBL revenue comes from this dirty money, how do you name this ? Probably not "money laundry", 
but surely not something legal.


But well, I'm afraid we are "beating a horse already dead"...

From sethb@panix.com  Tue Mar  1 14:12:02 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EF043A6AF4 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 14:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.857
X-Spam-Level: 
X-Spam-Status: No, score=-1.857 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 PED0-Ba48AWE for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 14:12:01 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 5060E3A6AD2 for <asrg@irtf.org>; Tue,  1 Mar 2011 14:12:01 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id 448F11F082 for <asrg@irtf.org>; Tue,  1 Mar 2011 17:13:05 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 31F0924200; Tue,  1 Mar 2011 17:13:05 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <A.1PuWl4-000NJL-4x@smtp-ext-layer.spamhaus.org> (message from Steve Linford on Tue, 01 Mar 2011 21:05:26 +0000)
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D4284.50102@thoroquel.org> <AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com> <AANLkTimzi+__J8dwVYPZ4td9ZLc_15r-kEgG2jOpg6cJ@mail.gmail.com> <20110301203843.E812124200@panix5.panix.com> <A.1PuWl4-000NJL-4x@smtp-ext-layer.spamhaus.org>
Message-Id: <20110301221305.31F0924200@panix5.panix.com>
Date: Tue,  1 Mar 2011 17:13:05 -0500 (EST)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 22:12:02 -0000

Steve Linford <linford@spamhaus.org> wrote:

> You could help bolster your scenario by using as example some
> criminal botnet gangs as the DNSBL customers,

The key point was later: If you have any customers, for anything, then
you have a potential conflict of interest when a (potential) customer
wants something that conflicts with what you would otherwise do.

If a spammer offers you $1 million to give a concert at Carnegie Hall
if you don't list him, then you have a conflict of interest.  There's
no charge for usage, listing, delisting, or anything else related to
the DNSBL involved.

Seth

From CLEWIS@nortel.com  Tue Mar  1 15:16:51 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A9D33A6B21 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 15:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.8
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 tOynXCgBT+YS for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 15:16:50 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 07FD73A6B2B for <asrg@irtf.org>; Tue,  1 Mar 2011 15:16:49 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p21NHlP19062 for <asrg@irtf.org>; Tue, 1 Mar 2011 23:17:47 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 18:17:45 -0500
Received: from [47.9.28.250] (47.9.28.250) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 1 Mar 2011 18:17:45 -0500
Message-ID: <4D6D7E98.7050307@nortel.com>
Date: Tue, 1 Mar 2011 18:17:44 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
In-Reply-To: <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Mar 2011 23:17:45.0867 (UTC) FILETIME=[DF87BDB0:01CBD866]
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 23:16:51 -0000

On 3/1/2011 10:21 AM, Neil Schwartzman wrote:
>
> On Feb 28, 2011, at 5:49 PM, Richard Welty wrote:
>
>> please list me as being in favor of this draft.
>
> <aol>  +1, and agreed. Heck, I may have even been the person to suggest this clause,

Nope, you can't take credit for that.  It was in the original drafts in 
2003, it and a clause on symmetry in listing/delisting were considered 
highly problemmatic (for much the same political and/or theoretical 
reasons we've seen here) during work on the document at MAAWG in 2004/5 
or thereabouts, but Nick (scribe at the time) managed to save the latter 
clause by rewriting it in its current form.

The reason for its reappearance is manyfold.  First and foremost is that 
I'm continually reminded, through experience/exposure with all portions 
of this industry, that it's _necessary_.  It just kept rearing its ugly 
head.

Secondly, experiences with a couple of documents at MAAWG have 
demonstrated the importance of ignoring the politics and drawing the 
line in the sand clearly and where it needs to be - remembering it's 
still drawn in sand.  If circumstances/events prove it needs to be 
redrawn in a slightly different place, well, that can be fixed.

My grandfather went surprisingly far for someone who had only gotten an 
eighth grade education.  Some of the things he always told me was:

- The only thing worse than making the wrong decision, was not making 
one at all.
- If you can manage to get it right more than 50% of the time, you were 
gold.
- If you were not right, be the first to admit it, fix it, and move on.

Surprisingly applicable even in software development - part of the 
reason I'm able to get away with stuff at $ork nobody else was ;-)
Applicable to BCPs and whitepapers too ;-)

From jason@i6ix.com  Tue Mar  1 15:49:48 2011
Return-Path: <jason@i6ix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43A263A6BF1 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 15:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 wNDvN8xKbavq for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 15:49:47 -0800 (PST)
Received: from zimbra.i6ix.com (zimbra.i6ix.com [216.173.161.100]) by core3.amsl.com (Postfix) with ESMTP id 585783A6B4E for <asrg@irtf.org>; Tue,  1 Mar 2011 15:49:47 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.i6ix.com (Postfix) with ESMTP id 1A6F488601 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:46:50 -0500 (EST)
X-Virus-Scanned: amavisd-new at zimbra.i6ix.com
Received: from zimbra.i6ix.com ([127.0.0.1]) by localhost (zimbra.i6ix.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ryMPIb7szSJ4 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:46:49 -0500 (EST)
Received: from zimbra.i6ix.com (zimbra.i6ix.com [216.173.161.100]) by zimbra.i6ix.com (Postfix) with ESMTP id 7445288600 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:46:49 -0500 (EST)
Date: Tue, 1 Mar 2011 18:46:49 -0500 (EST)
From: Jason Bertoch <jason@i6ix.com>
To: asrg@irtf.org
Message-ID: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>
In-Reply-To: <alpine.BSF.2.00.1103011507460.22961@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [216.173.170.10]
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Linux)/6.0.10_GA_2692)
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 23:49:48 -0000

On 2011/03/01 3:28 PM, John R. Levine wrote:
> Now that the kerfuffle seems to have died down, I'd like to see if we
> have group rough consensus (which does not mean perfect unanimity) on
> the BL best practices overview. Please read through it and say whether
> you think it's OK, or if not, what specific language to change.
>

I still find myself stuck on 2.2.5.  It needs to be removed or changed to not pick on negative-reputation lists.

As this BCP already describes, many (most?) DNSBL's are used as part of an overall scoring system, rather than just at the MTA level.  As such, removal from a negative-reputation list generally has the same net effect as addition to a positive-reputation list.  (Actually, ReturnPath is considered quite favorably in SpamAssassin.)  Any arguments against paid removal from a neg-rep list can be equally applied to paid addition to a pos-rep list.

While I disagree with Claus' particular rhetoric, I somehow feel that everyone who argued against him wouldn't be quite as judgemental against a paid whitelist like ReturnPath.  Not only that, UCEPROTECT is ultimately free...one would only pay for human intervention if the automatic timeframe just isn't soon enough.  Sure, I believe the practice of paying to upgrade your reputation is slimy at best, but why does the BCP pick on neg-rep lists when they, if anyone, SHOULD have evidence of wrong doing?

I'm sorry to pick on ReturnPath...Neil and J.D. have been exceptionally patient on the SA list, and RP's accuracy has improved considerably over the years (though the clarity of reporting issue still needs resolving)...but, in the end, the BCP needs to pick on no-one or pick on everyone that nets the same result.

Finally, with IPv6 staring us in the face, the landscape of DNSBL's will certainly be changing.  The group needs to decide if dictating business/revenue models is even appropriate in a BCP and, if so, needs to elaborate in much more detail to avoid what is ultimately picking on one single DNSBL.

-- 
/Jason

From geemailenator@gmail.com  Tue Mar  1 16:00:26 2011
Return-Path: <geemailenator@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C2A63A6B55 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 ycBUYDdw8XRP for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:00:24 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id 907363A6B54 for <asrg@irtf.org>; Tue,  1 Mar 2011 16:00:24 -0800 (PST)
Received: by vws16 with SMTP id 16so5473133vws.13 for <asrg@irtf.org>; Tue, 01 Mar 2011 16:01:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=ljPWwtmKjb2R72AbJpal0uogBtd8OL+AZfFmuLbQxxo=; b=urT8Vw9gzF0G2SovGOpQhEqp+nb+g191wDd/67X58FZD6pjWTtQcCihjxUvKIo0gZL ACS9iMG+cqd+fr45DpeFTAu4VUMZTv1dp2dQpBvlpKbGvjy/vSF3kMj4qDjHz08XjVCA TjBzCkHLyXD4QBIyMK+HBACJMoCCsVCf+hDas=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=wCnSIwbKPalJyCvFmxVVWpiSiPcLxbxLPK65vG+Q/NgksVzn2RMPsN5CATYA0SgmcK +8VYSv+RBS4qOWgyn3HUNxll7MxRBkTYqL59DD7t0RvqmLBiexkkGcNITIRhAcfnUGnw jKawv7uKlXaiYBHVy9N5IuyH7TZzgjd1N/RrE=
Received: by 10.52.161.67 with SMTP id xq3mr12533462vdb.57.1299024088436; Tue, 01 Mar 2011 16:01:28 -0800 (PST)
Received: from [172.16.1.2] (modemcable156.249-57-74.mc.videotron.ca [74.57.249.156]) by mx.google.com with ESMTPS id y15sm2485962vch.29.2011.03.01.16.01.26 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 01 Mar 2011 16:01:27 -0800 (PST)
Sender: Neil Schwartzman <geemailenator@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Neil Schwartzman <neil@cauce.org>
In-Reply-To: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>
Date: Tue, 1 Mar 2011 19:01:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 00:00:26 -0000

On Mar 1, 2011, at 6:46 PM, Jason Bertoch wrote:

>=20
> While I disagree with Claus' particular rhetoric, I somehow feel that =
everyone who argued against him wouldn't be quite as judgemental against =
a paid whitelist like ReturnPath.  Not only that, UCEPROTECT is =
ultimately free...one would only pay for human intervention if the =
automatic timeframe just isn't soon enough.  Sure, I believe the =
practice of paying to upgrade your reputation is slimy at best, but why =
does the BCP pick on neg-rep lists when they, if anyone, SHOULD have =
evidence of wrong doing?
>=20
> I'm sorry to pick on ReturnPath...Neil and J.D. have been =
exceptionally patient on the SA list, and RP's accuracy has improved =
considerably over the years (though the clarity of reporting issue still =
needs resolving)...but, in the end, the BCP needs to pick on no-one or =
pick on everyone that nets the same result.

Just to clarify a couple of points:

1. I am no longer working for Return Path. Everyone there remains in my =
highest esteem, and
2. I disagree with you. Negative reputation is something no-one wants, =
nor should you be able to buy your way out of it. Conversely, a positive =
bump to differentiate you from the competition is valuable (but no, =
no-one who is a crappy sender could bribe their way onto the list, not =
while I was there, and not since I left), and something those that =
benefit from the service should pay for, just as ISPs should pay for the =
use of a DNSBL.

Just as a DNSBL is expected to block all crappy traffic they know about, =
so too is a whitelist expected to only list the good traffic they know =
about. While we had some heated debates over the years concerning =
sanctions to take against clients (I always voted for firing), delisting =
is just as painful, especially when a client is paying a certification =
company, and isn't certified. ;-)

I will note that other companies also charged for certifying - Goodmail, =
and now Spamhaus, among others. Just as it should be. Whitelisting and =
blacklisting are two different beasts, serving two different masters, =
and thus, two different business models.


cheers,

n

--
Neil Schwartzman
Executive Director
CAUCE
The Coalition Against Unsolicited Commercial Email, North America Inc.

http://cauce.org
http://twitter.com/cauce
IM: caucecanada
Tel.: +1 (303) 800 6345





From asrg3@billmail.scconsult.com  Tue Mar  1 16:11:55 2011
Return-Path: <asrg3@billmail.scconsult.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1ECD93A6AE0 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:11:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 IayPlmn7W8zA for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:11:54 -0800 (PST)
Received: from toaster.scconsult.com (www.scconsult.com [66.73.230.185]) by core3.amsl.com (Postfix) with ESMTP id B98933A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 16:11:52 -0800 (PST)
Received: from [192.168.254.22] (deepfield.scconsult.com [192.168.254.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by toaster.scconsult.com (Postfix) with ESMTP id CCA74CB9ECF for <asrg@irtf.org>; Tue,  1 Mar 2011 19:12:44 -0500 (EST)
From: Bill Cole <asrg3@billmail.scconsult.com>
To: "Anti-Spam Research Group - IRTF" <asrg@irtf.org>
Date: Tue, 01 Mar 2011 19:12:16 -0500
Message-ID: <43DB30BE-7C90-4403-A447-E9FF7B484499@billmail.scconsult.com>
In-Reply-To: <4D6D1EC7.6080508@messagelabs.com>
References: <4D6C265E.1060101@averillpark.net> <EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org> <4D6D1EC7.6080508@messagelabs.com>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate Trial (1.0.1r1928)
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 00:11:55 -0000

On 1 Mar 2011, at 11:28, Matt Sergeant wrote:

> Neil Schwartzman wrote:
>> <aol>  +1, and agreed. Heck, I may have even been the person to 
>> suggest this clause, some years ago at the IRTF meeting when the ASRG 
>> was resurrected. Charging for delisting is just plain bad business.
> The original wording was designed to cover this, it said (and jeez, 
> this was back in 2003!): " If all things listed in your criteria for 
> listing are cleared up then there should be no reason to not remove 
> the IP address. No /extra/ rules for de-listing.". We simply made it 
> more explicit (and better English).

That bit (2.2.4) is properly distinct from the CoI/payment bit (2.2.5) 
because there can be both inherent and prudent forms of 
hysteresis/asymmetry between listing criteria and delisting criteria.

From mike@mtcc.com  Tue Mar  1 16:13:53 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 091903A6AE0 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 fo2INpBMO-Td for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:13:51 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by core3.amsl.com (Postfix) with ESMTP id D65A03A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 16:13:51 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id p220ErpK006960 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 16:14:53 -0800
Message-ID: <4D6D8BFD.6010507@mtcc.com>
Date: Tue, 01 Mar 2011 16:14:53 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com> <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
In-Reply-To: <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1102; t=1299024894; x=1299888894; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20Getting=20group=20consensus=20 on=20draft-irtf-asrg-bcp-blacklists |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=hGlfH4U0ogqrVWi0gWVZe+BrGaL7Nz4jg7JKtTjccR8=; b=qfNvn+kTeczkH0imFRRzlCED9fSiunq9zF7CDgleSkPqZw7jRXW2rpJo/o s25/HrEvjk5FnCczqD7t7HNoSlYFvcFOIhOYfVn5ddpi0FWGi6t8YSe+lPcA fFeOy14BokFJuTJBUPJsxFYLORtOCEAMV1OsbVAjFN8HNJDF5PwOA=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 00:13:53 -0000

On 03/01/2011 04:01 PM, Neil Schwartzman wrote:
>
> 2. I disagree with you. Negative reputation is something no-one wants, nor should you be able to buy your way out of it. Conversely, a positive bump to differentiate you from the competition is valuable (but no, no-one who is a crappy sender could bribe their way onto the list, not while I was there, and not since I left), and something those that benefit from the service should pay for, just as ISPs should pay for the use of a DNSBL.
>    

Er, well that works well when you're dealing with saint.com and
sinner.com, but real world entities are often a blend of each. This
is going to be particularly true of domain based reputation dealing
with $megacorp. In that case, trying to get off blacklists and onto
whitelists with money or threats or combinations of both is going
to produce real life conflicts of interest. For both operators. How
well did the Usenet Death Penalty work against the invading aol, etc
hordes? Not very as I recall, and that was before the Big Bux were
involved that invariably grease the wheels.

Mike

From mike@mtcc.com  Tue Mar  1 16:19:58 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D1D83A6A21 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:19:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 KJdQSoe22Rbf for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 16:19:56 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by core3.amsl.com (Postfix) with ESMTP id 4D2563A6965 for <asrg@irtf.org>; Tue,  1 Mar 2011 16:19:55 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id p220Kwup009259 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 16:20:59 -0800
Message-ID: <4D6D8D6A.3000806@mtcc.com>
Date: Tue, 01 Mar 2011 16:20:58 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: multipart/mixed; boundary="------------010605040603030001040302"
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=6048; t=1299025259; x=1299889259; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20Getting=20group=20consensus=20 on=20draft-irtf-asrg-bcp-blacklists |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20multipart/mixed=3B=0A=20boundary=3D=22---- --------010605040603030001040302=22 |Content-Transfer-Encoding:=20 |MIME-Version:=201.0; bh=gzfEKDZQikRPvJv3C/Yw5FZ6OGlr5uR33aJInPZ9nWU=; b=S+9pziXgWZcAZve8okFZmFkxVVUmOZguM122jLJdtUbxuC8XXwuUv6TXUl E4D/9SZFGfFbRahjZKJpiDYcWcBsAxXfFBK+BJP1+jwebYUANEgiPzmZtRYB 90wQdl6lFT8rEUCpbq6imRw07Q+VjMUIKmfWWVGwFOubwmiwqi4Hs=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 00:19:58 -0000

This is a multi-part message in MIME format.
--------------010605040603030001040302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

and speaking of bad blacklist operators, you get petty assholes
who think that their SMTP is an AI capable of educing meaning
from messages.  I wonder who runs this one? Oh, the working
group chair. Charming.

Mike

-------- Original Message --------
Return-Path: 	<MAILER-DAEMON@mtcc.com>
X-Spam-Checker-Version: 	SpamAssassin 3.3.1 (2010-03-16) on 
takifugu.mtcc.com
X-Spam-Level: 	
X-Spam-Status: 	No, Score=-1.1/4.5, BAYES_00=-1.9,DKIM_ADSP_ALL=0.8, 
NO_RELAYS=-0.001,T_TVD_MIME_NO_HEADERS=0.01,autolearn=no
X-Spam-Bayes-Summ: 	summary=Tokens: new, 41; hammy, 117; neutral, 63; 
spammy, 2.
X-Spam-RBL: 	<dns:mtcc.com?type=MX> [0 mtcc.com.] <dns:mtcc.com> 
[50.0.18.224]
X-Spam-Bayes-Spam: 	0.987-1--Big, 0.987-1--560
X-Spam-Bayes-Ham: 	0.000-+--ISPs, 0.000-+--dnsbl, 0.000-+--DNSBL, 
0.001-+--disagree, 0.001-+--isps
X-Spam-UnTrusted: 	
Received: 	from localhost (localhost) by mtcc.com (8.14.3/8.14.3) id 
p220EupJ006967; Tue, 1 Mar 2011 16:14:56 -0800
Date: 	Tue, 1 Mar 2011 16:14:56 -0800
From: 	Mail Delivery Subsystem <MAILER-DAEMON@mtcc.com>
Message-Id: 	<201103020014.p220EupJ006967@mtcc.com>
To: 	<mike@mtcc.com>
MIME-Version: 	1.0
Content-Type: 	multipart/report; report-type=delivery-status; 
boundary="p220EupJ006967.1299024896/mtcc.com"
Subject: 	Returned mail: see transcript for details
Auto-Submitted: 	auto-generated (failure)



The original message was received at Tue, 1 Mar 2011 16:14:53 -0800
from takifugu.mtcc.com [50.0.18.224]

    ----- The following addresses had permanent fatal errors -----
<neil@cauce.org>
     (reason: 553 Incoherent message (5.1.1))

    ----- Transcript of session follows -----
... while talking to smtp.abuse.net.:
>>>  MAIL From:<mike@mtcc.com>  SIZE=3247
<<<  553 Incoherent message (5.1.1)
501 5.6.0 Data format error



--------------010605040603030001040302
Content-Type: message/delivery-status;
 name="Attached Message Part"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message Part"

Reporting-MTA: dns; mtcc.com
Received-From-MTA: DNS; takifugu.mtcc.com
Arrival-Date: Tue, 1 Mar 2011 16:14:53 -0800

Final-Recipient: RFC822; neil@cauce.org
Action: failed
Status: 5.1.3
Diagnostic-Code: SMTP; 553 Incoherent message (5.1.1)
Last-Attempt-Date: Tue, 1 Mar 2011 16:14:56 -0800

--------------010605040603030001040302
Content-Type: message/rfc822;
 name="ForwardedMessage.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="ForwardedMessage.eml"

Return-Path: <mike@mtcc.com>
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224])
	(authenticated bits=0)
	by mtcc.com (8.14.3/8.14.3) with ESMTP id p220ErpK006960
	(version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO);
	Tue, 1 Mar 2011 16:14:53 -0800
Message-ID: <4D6D8BFD.6010507@mtcc.com>
Date: Tue, 01 Mar 2011 16:14:53 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
CC: Neil Schwartzman <neil@cauce.org>
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com> <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
In-Reply-To: <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	T_RP_MATCHES_RCVD autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on takifugu.mtcc.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1102; t=1299024894; x=1299888894;
	c=relaxed/simple; s=thundersaddle.kirkwood;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=mtcc.com; i=mike@mtcc.com;
	z=From:=20Michael=20Thomas=20<mike@mtcc.com>
	|Subject:=20Re=3A=20[Asrg]=20Getting=20group=20consensus=20
	on=20draft-irtf-asrg-bcp-blacklists
	|Sender:=20
	|To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf
	.org>
	|Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20
	format=3Dflowed
	|Content-Transfer-Encoding:=207bit
	|MIME-Version:=201.0;
	bh=hGlfH4U0ogqrVWi0gWVZe+BrGaL7Nz4jg7JKtTjccR8=;
	b=qfNvn+kTeczkH0imFRRzlCED9fSiunq9zF7CDgleSkPqZw7jRXW2rpJo/o
	s25/HrEvjk5FnCczqD7t7HNoSlYFvcFOIhOYfVn5ddpi0FWGi6t8YSe+lPcA
	fFeOy14BokFJuTJBUPJsxFYLORtOCEAMV1OsbVAjFN8HNJDF5PwOA=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com (
	sig from mtcc.com/thundersaddle.kirkwood verified; ); 
	 dkim-asp=pass header.From=mike@mtcc.com

On 03/01/2011 04:01 PM, Neil Schwartzman wrote:
>
> 2. I disagree with you. Negative reputation is something no-one wants, nor should you be able to buy your way out of it. Conversely, a positive bump to differentiate you from the competition is valuable (but no, no-one who is a crappy sender could bribe their way onto the list, not while I was there, and not since I left), and something those that benefit from the service should pay for, just as ISPs should pay for the use of a DNSBL.
>    

Er, well that works well when you're dealing with saint.com and
sinner.com, but real world entities are often a blend of each. This
is going to be particularly true of domain based reputation dealing
with $megacorp. In that case, trying to get off blacklists and onto
whitelists with money or threats or combinations of both is going
to produce real life conflicts of interest. For both operators. How
well did the Usenet Death Penalty work against the invading aol, etc
hordes? Not very as I recall, and that was before the Big Bux were
involved that invariably grease the wheels.

Mike


--------------010605040603030001040302--

From jason@i6ix.com  Tue Mar  1 17:27:21 2011
Return-Path: <jason@i6ix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B9293A6B15 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 3AeeEvFrvi2m for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:27:20 -0800 (PST)
Received: from zimbra.i6ix.com (zimbra.i6ix.com [216.173.161.100]) by core3.amsl.com (Postfix) with ESMTP id 99D1E3A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 17:27:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.i6ix.com (Postfix) with ESMTP id 54EE888619 for <asrg@irtf.org>; Tue,  1 Mar 2011 20:24:23 -0500 (EST)
X-Virus-Scanned: amavisd-new at zimbra.i6ix.com
Received: from zimbra.i6ix.com ([127.0.0.1]) by localhost (zimbra.i6ix.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxEbu4BLeDv7 for <asrg@irtf.org>; Tue,  1 Mar 2011 20:24:22 -0500 (EST)
Received: from zimbra.i6ix.com (zimbra.i6ix.com [216.173.161.100]) by zimbra.i6ix.com (Postfix) with ESMTP id 07BE988600 for <asrg@irtf.org>; Tue,  1 Mar 2011 20:24:22 -0500 (EST)
Date: Tue, 1 Mar 2011 20:24:21 -0500 (EST)
From: Jason Bertoch <jason@i6ix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <10093249.57.1299029061794.JavaMail.root@zimbra.i6ix.com>
In-Reply-To: <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [216.173.170.10]
X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Linux)/6.0.10_GA_2692)
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 01:27:21 -0000

----- Original Message -----
> From: "Neil Schwartzman" <neil@cauce.org>
> 
> Just to clarify a couple of points:
> 
> 1. I am no longer working for Return Path. Everyone there remains in
> my highest esteem, and

Apologies for not knowing the current state of your career.  I just wanted to give credit where it was due :)

> 2. I disagree with you. Negative reputation is something no-one wants,
> nor should you be able to buy your way out of it. Conversely, a
> positive bump to differentiate you from the competition is valuable
> (but no, no-one who is a crappy sender could bribe their way onto the
> list, not while I was there, and not since I left), and something
> those that benefit from the service should pay for, just as ISPs
> should pay for the use of a DNSBL.

I do see your point, and will vouch that RP has gotten better in recent times but, in reality, senders of quality mail don't really need that positive bump, do they?  Sure, in IPv6, that may be the only thing that gets their mail through, but we're not there yet and neither is this BCP.

> 
> Just as a DNSBL is expected to block all crappy traffic they know
> about, so too is a whitelist expected to only list the good traffic
> they know about. While we had some heated debates over the years
> concerning sanctions to take against clients (I always voted for
> firing), delisting is just as painful, especially when a client is
> paying a certification company, and isn't certified. ;-)
> 

In a score-based system, all of that rhetoric is lost to the final recipient.  A listing on a pos-rep list is just as good as no listing on a neg-rep list.  Paying either one to get there results in the same net effect to the final recipient.  And that's who we all care about, right?

> I will note that other companies also charged for certifying -
> Goodmail, and now Spamhaus, among others. Just as it should be.
> Whitelisting and blacklisting are two different beasts, serving two
> different masters, and thus, two different business models.
> 

While I realize RP isn't alone, I've no experience with Goodmail, and Spamhaus' list is just too new to bother with at the moment.  I also understand your argument that, in theory at least, the models are different.  However, my goal was to point out that their net effect was identical and, therefore, the BCP should either address the models as a whole or not address them at all.

--
/Jason

From johnl@iecc.com  Tue Mar  1 17:53:34 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 924793A6C01 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.075
X-Spam-Level: 
X-Spam-Status: No, score=-111.075 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 EQx5Qr9ip9yM for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:53:33 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 538193A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 17:53:06 -0800 (PST)
Received: (qmail 64543 invoked from network); 2 Mar 2011 01:54:09 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Mar 2011 01:54:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=2809.4d6da341.k1103; i=johnl@user.iecc.com; bh=gNreDct2Ogzzh2jOo3gDrEEabjkPI2pzMDavHZOKVak=; b=QQDn8+W7i459THa4t3mXsm8FteNnAytc2PTMgEyx1x5BkMqXVnNglXpdRoBM57egXgSLv/a/0p4cy77FALkGXT53cwIJ7LWMKYQOjcnZg/Wsm8M9lFM0deHbcqGug/5tzCTKyU/58qtIqBeue4JBF3Lv1aMRCwFTiCDu0AO8RUY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=2809.4d6da341.k1103; olt=johnl@user.iecc.com; bh=gNreDct2Ogzzh2jOo3gDrEEabjkPI2pzMDavHZOKVak=; b=Y9m6GiAklZOq1p/wmlAKH6phB9lGpPjSKv5EB4sgjaD9+VcaHWIzer/0fZRhLrg8Z+xMazS3I6syMbI+/0QnyZ+qILtuhZdbmUw8VLat85hFUd4nrypZpvrTBZrKyVi9unjvPUJphexCd2D1CfSDb8gG9hRSXe6KPHZLcedKlZc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Mar 2011 01:54:09 -0000
Message-ID: <20110302015409.10248.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D6D8D6A.3000806@mtcc.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: [Asrg] RFC 3934 applies to everyone
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 01:53:34 -0000

The IETF has a long standing policy against personal attacks on its
mailing lists.  We are all presumed to be adults here, and part of
that is having the ability to control your own conduct.  For more
information, you might want to read or reread RFC 3934, on Management
of IETF Mailing Lists.

I hope people have the ability to behave themselves, so there's no
need to suspend anyone, but I will if they don't.

R's,
John

>and speaking of bad blacklist operators, you get petty assholes
>who think that their SMTP is an AI capable of educing meaning
>from messages.  I wonder who runs this one? Oh, the working
>group chair. Charming.

From mike@mtcc.com  Tue Mar  1 17:56:35 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B47573A6C04 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.400, 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 p-so6KUaA+E8 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 17:56:34 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by core3.amsl.com (Postfix) with ESMTP id C8E313A6A24 for <asrg@irtf.org>; Tue,  1 Mar 2011 17:56:34 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id p221vcKA013837 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Tue, 1 Mar 2011 17:57:39 -0800
Message-ID: <4D6DA412.2080708@mtcc.com>
Date: Tue, 01 Mar 2011 17:57:38 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110302015409.10248.qmail@joyce.lan>
In-Reply-To: <20110302015409.10248.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1055; t=1299031059; x=1299895059; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20RFC=203934=20applies=20to=20ev eryone |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=Bs/ZzrljbWGyVZnnbmdXGD7jdLc/0691kfZQrj0aBxQ=; b=ouPfnWXYp5aFGRenkylqVqVoT8KObMPYfV7WR6EAa1aqyKmylYUvca2l4/ VIqEjlxoXJYA/4L+EWYA47fyNAmmX4wqhcoZaNWebtXgIgUz9QlPVTiFTJ6l HKrIu2T/X4weK5mhxP4L1X9dbvFo+lsS3JJOAs3AExFVCZ39XOPOI=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] RFC 3934 applies to everyone
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 01:56:35 -0000

Everyone including John Levine:

Diagnostic-Code: SMTP; 553 Incoherent message (5.1.1)

Is a personal attack, and a petty one at that.

Mike



On 03/01/2011 05:54 PM, John Levine wrote:
> The IETF has a long standing policy against personal attacks on its
> mailing lists.  We are all presumed to be adults here, and part of
> that is having the ability to control your own conduct.  For more
> information, you might want to read or reread RFC 3934, on Management
> of IETF Mailing Lists.
>
> I hope people have the ability to behave themselves, so there's no
> need to suspend anyone, but I will if they don't.
>
> R's,
> John
>
>    
>> and speaking of bad blacklist operators, you get petty assholes
>> who think that their SMTP is an AI capable of educing meaning
>>      
> >from messages.  I wonder who runs this one? Oh, the working
>    
>> group chair. Charming.
>>      
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg
>    


From CLEWIS@nortel.com  Tue Mar  1 18:04:21 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 048B33A6C01 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:04:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.871
X-Spam-Level: 
X-Spam-Status: No, score=-4.871 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_00=-2.599, FRT_PROFIT1=3.858, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 7saHjwyrR9ii for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:04:19 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id A158F3A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:04:19 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p2225KY21866 for <asrg@irtf.org>; Wed, 2 Mar 2011 02:05:20 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 21:05:19 -0500
Received: from [47.9.28.250] (47.9.28.250) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 1 Mar 2011 21:05:18 -0500
Message-ID: <4D6DA5DD.1010502@nortel.com>
Date: Tue, 1 Mar 2011 21:05:17 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>
In-Reply-To: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2011 02:05:19.0502 (UTC) FILETIME=[47F6B2E0:01CBD87E]
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 02:04:21 -0000

On 3/1/2011 6:46 PM, Jason Bertoch wrote:
> On 2011/03/01 3:28 PM, John R. Levine wrote:
>> Now that the kerfuffle seems to have died down, I'd like to see if we
>> have group rough consensus (which does not mean perfect unanimity) on
>> the BL best practices overview. Please read through it and say whether
>> you think it's OK, or if not, what specific language to change.
>>
>
> I still find myself stuck on 2.2.5.  It needs to be removed or changed to not pick on negative-reputation lists.
>
> As this BCP already describes, many (most?) DNSBL's are used as part of an overall scoring system, rather than just at the MTA level.  As such, removal from a negative-reputation list generally has the same net effect as addition to a positive-reputation list.  (Actually, ReturnPath is considered quite favorably in SpamAssassin.)  Any arguments against paid removal from a neg-rep list can be equally applied to paid addition to a pos-rep list.

The BCP describes that they _can_ be used in an overall scoring system. 
  Everything I've seen seems to indicate that the majority of use isn't 
scoring.  The very largest environments don't, for example.

One of the crux arguments here is why negative-reputation lists are 
being "picked on".

After all, isn't blacklist removal the same as whitelist addition?

Mathmatically, at least in scoring, of course, they are the same.

But, that's where the similarity ends.  They are worlds apart ethically, 
legally and practically.  Just as Steve Atkins said.

We need to see the big picture here.

I don't want to dwell too long on the ethical/legal issues too much, 
other than to point out that charging a fee for not saying/stop saying 
something bad about someone meets at least a general definition of 
extortion or blackmail.

Whereas charging someone to say something good is just ordinary advertising.

The former is paying to undo the reputational damage someone did without 
invitation (and perhaps without justification), the latter is to improve 
the reputation voluntarily.

Of course, there are many reasons where payment for delisting generally 
won't meet legal definitions of extortion or blackmail, not to mention 
the CDA's protections, but (a) those are largely jurisdictionally 
dependent and (b) it really doesn't matter for practical reasons.  Those 
same practical reasons apply in edge-case.

Practical reasons?  They abound.  Throughout my involvement in many 
portions of the industry, it's clear:

1) Providers of all types & stripes simply won't deal with DNSBLs they 
believe to be unethical.  I see comments like that from very large 
providers almost every day.  Many others on this list frequent the same 
places I do, and see them as well.  Good responsive providers who 
remediate other DNSBL listings quickly and effectively simply refuse to 
have anything to do with the perceived "unethical" ones.  They don't fix 
problems, they don't educate users, they encourage people to ignore them.

2) Many organizations simply won't use DNSBLs they believe to be unethical.

3) Paying for delist, while it might not make a great deal of difference 
in overall effectiveness if the DNSBL is good enough to redetect and 
relist quickly, many DNSBLs are not, and can massively impair accuracy. 
  Not to mention legal problems if you're not really careful about what 
the payment actually buys the listee.

4) (1) and (2) are very significant factors, and they in turn lead to:
    a) Real spamming problems don't get resolved, and they continue
       unabated.
    b) False positives don't get resolved, and they continue unabated.
    c) Uptake of a DNSBL is reduced, their usefuless declines.
    d) The bad reputation of an individual DNSBL inevitably leaks to the
       mechanism as a whole (just see IETF diatribes for example).
    e) providers don't educate their users what they're doing wrong
    f) DNSBLs get screamed at for unethical behaviour...
    g) DNSBLs scream back...
    h) everybody acts like children...

These are all bad for the receivers of email and the industry as a whole.

5) For the most part, a blacklist hit is more likely to have a negative 
effect on delivery than a whitelist hit having a positive one.

I'm sure you're scratching your head with this one.  The reality is that 
application of whitelisting in an overall receiver-advantageous  way is 
far more difficult than applying blacklisting, and the results of 
getting it wrong can be far more obvious.  huh? (again ;-).  _Few_ 
people apply whitelists (or at least 3rd party ones) as "allow 
everything through", because it's too dangerous - you allow 
viruses/malware or contra-policy material in for example.  Application 
of whitelisting properly is a delicate operation.  In scoring systems, 
they tend to have small positive scores, whereas many individual 
blacklists have large negative ones.  Or they don't score at all, and 
DNSWLs only apply to _parts_ of the filters.  Etc.

Example: in our system, our local DNSWL can get you past any DNSBL 
listings - but not the ancilliary string filters, SpamAssassin or 
ClamAV.  3rd party DNSWLs have _slight_ positive scores in our DNSBL 
engine.  They can get you past one DNSBL listing, but not two.

6) Hankypanky/sloppiness with whitelisting is usually much easier to 
spot - complaints jump, and if they correlate with a whitelist...  Yes, 
receivers watch these things closely and take action.

{RSK: you asked for an example.  I've got a good one.  Email me and I'll 
tell you.  But it's not for public consumption.]

7) "Express" and "charity" - in the end, the distinction doesn't matter 
for (1) or (2).  Proof?  They don't in real life.

Missing the distinction is, of course, probably wrong, but distinction 
or not, the results are the same.

They haven't mattered with UCEProtect or SORBS.  Consider: UCEProtect 
has been around for a while.  Some of their lists are relatively useful. 
  Claus just said they "protect" 2.5M users.  That isn't a lot. In fact, 
it's tiny.  Other DNSBLs without these problems have _individual_ users 
that are 2 orders of magnitude larger.  It's not the only reason of 
course, but it's one of them.  The effect isn't so severe with SORBS, 
but I do think it's fair to suggest that they would have evolved further 
without it.

Personally, I don't think "express delist for a fee" or "donation" are 
all that bad.  But in the end, that subtlety is lost, and all the 
practical harm acrues anyway.

In the end: other DNSBLs have thought long and hard about this for 
years.  Consider, for example, the universal condemnation of this 
practise from every DNSBL (with the obvious exception of UCEProtect) 
that's said something here.  Notice that SORBS agreed with the BCP. 
Consider for example, the lengths to which the CBL distances itself from 
this practice in its FAQ.  Witness what deliverability experts say about 
them.  ISPs.  Etc.

All of my experience indicates that the consequences of this are so 
severe that it's best for _everyone_ to stay as far clear of it as 
possible.  This is one of those cases where an "appearance of 
impropriety" is just as bad as just plain "impropriety".

Perhaps something will come along to change that.  I doubt it.  But it 
ain't all that hard to draft a successor document and change it.  Better 
to get the stake driven in (thanks Rich for the imagery ;-)





From CLEWIS@nortel.com  Tue Mar  1 18:22:36 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAA033A6C04 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.568
X-Spam-Level: 
X-Spam-Status: No, score=-5.568 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 yQS+GreO8byq for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:22:36 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id DF6D93A6A16 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:22:35 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p222Nam25000 for <asrg@irtf.org>; Wed, 2 Mar 2011 02:23:36 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 21:23:33 -0500
Received: from [47.9.28.250] (47.9.28.250) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 1 Mar 2011 21:23:32 -0500
Message-ID: <4D6DAA23.1090503@nortel.com>
Date: Tue, 1 Mar 2011 21:23:31 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>	<28307D97-6889-41FE-836C-356610088E0F@cauce.org> <4D6D8BFD.6010507@mtcc.com>
In-Reply-To: <4D6D8BFD.6010507@mtcc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2011 02:23:33.0476 (UTC) FILETIME=[D405E240:01CBD880]
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 02:22:37 -0000

On 3/1/2011 7:14 PM, Michael Thomas wrote:

> How well did the Usenet Death Penalty work against the invading aol, etc
> hordes? Not very as I recall, and that was before the Big Bux were
> involved that invariably grease the wheels.

_Every_ applied UDP worked and achieved its goals.  Every single one.

I know.  Not only was I there, I was a big part of implementing all of them.

It may not have looked in their press releases that those battles were 
won - they had bigger PR departments than we did.  We only cared about 
results.  And results we got.

Those were the days when ISPs were first introduced to the idea that 
they needed to handle abuse.  Heady days, worked with most of the 
biggies throughout the period and helped them build abuse departments 
where even the need didn't exist previously.  Some of the people on this 
list got their start from those efforts.

AOL was never seriously considered a UDP target.  They were almost the 
very first to see the need for abuse handling, and until recently set 
the gold standard of excellence in it.

Sure, the AOLers were annoying.  But its their spamming we cared about, 
and their spamming got short shrift.

Over the years, some of them backslid.  Some of them improved.  And some 
of them cycled between with horrifying rapidity.  But without those 
days, we'd probably be several years behind where we are in anti-spam.

OTOH, some might blame me for creating email spam.  It was my chasing 
Jef Slaton off Usenet that caused him to become the first significant 
email spammer.  Yup, all my fault.  Oops.  Sorry about that ;-)


From lyndon@gandalf.orthanc.ca  Tue Mar  1 18:29:38 2011
Return-Path: <lyndon@gandalf.orthanc.ca>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 340B53A6A16 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:29:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 d2GH1reHpIpb for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:29:37 -0800 (PST)
Received: from orthanc.ca (ve6bbm-1-pt.tunnel.tserv13.ash1.ipv6.he.net [IPv6:2001:470:7:139::2]) by core3.amsl.com (Postfix) with ESMTP id 247773A6C04 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:29:36 -0800 (PST)
Received: from orthanc.ca (localhost [127.0.0.1]) by orthanc.ca (8.14.4/8.14.4) with ESMTP id p222Uext018849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 18:30:40 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Received: (from uucp@localhost) by orthanc.ca (8.14.4/8.14.4/Submit) with UUCP id p222Ue3U018848; Tue, 1 Mar 2011 18:30:40 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Received: from gandalf.orthanc.ca (frodo.orthanc.ca [172.16.0.3]) by legolas.orthanc.ca (8.14.4/8.14.4) with ESMTP id p222UcxM061438; Tue, 1 Mar 2011 18:30:38 -0800 (PST) (envelope-from lyndon@gandalf.orthanc.ca)
Message-ID: <e36a1f3f286aaa59a246108fddd5ee22@gandalf.orthanc.ca>
To: clewis@nortel.com, asrg@irtf.org
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca>
Date: Tue, 1 Mar 2011 18:30:38 -0800
In-Reply-To: <4D6DAA23.1090503@nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 02:29:38 -0000

> OTOH, some might blame me for creating email spam.  It was my chasing 
> Jef Slaton off Usenet that caused him to become the first significant 
> email spammer.  Yup, all my fault.  Oops.  Sorry about that ;-)

Just proves the point: You were not the Messiah, you were a
very naughty boy! :-)

I wonder how many of the cranks now wish we could resurrect the backbone
cabal ... 

--lyndon


From trelane@trelane.net  Tue Mar  1 18:41:20 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A55333A6A21 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level: 
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[AWL=-0.240,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 8NQx7GKFPfjG for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 18:41:20 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by core3.amsl.com (Postfix) with ESMTP id ECBC83A6A16 for <asrg@irtf.org>; Tue,  1 Mar 2011 18:41:19 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 3820E1864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 21:42:22 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sy7ANTOHfwxS for <asrg@irtf.org>; Tue,  1 Mar 2011 21:42:20 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 87DB81864B8 for <asrg@irtf.org>; Tue,  1 Mar 2011 21:42:20 -0500 (EST)
Received: from [172.16.1.106] (unknown [66.93.203.199]) by mail.trelane.net (Postfix) with ESMTPA id 174181864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 21:42:19 -0500 (EST)
Message-ID: <4D6DAE8B.4060800@trelane.net>
Date: Tue, 01 Mar 2011 21:42:19 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net>	<4D6D5713.3080205@mines-paristech.fr>	<20110301215047.A6B3624200@panix5.panix.com> <4D6D6E00.4020507@mines-paristech.fr>
In-Reply-To: <4D6D6E00.4020507@mines-paristech.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 02:41:20 -0000

On 3/1/2011 5:06 PM, Jose-Marcio Martins da Cruz wrote:
> If one consider that spammers money is dirty money (criminal activity
> as one said)... and if part of the DNSBL revenue comes from this dirty
> money, how do you name this ? Probably not "money laundry", but surely
> not something legal.

Dis-incentivising.

From sethb@panix.com  Tue Mar  1 19:09:51 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6F023A6C10 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:09:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[AWL=-0.050,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 UjsyF7jfiTlm for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:09:51 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 171CA3A6C0A for <asrg@irtf.org>; Tue,  1 Mar 2011 19:09:51 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id 3FDE71F086; Tue,  1 Mar 2011 22:10:55 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 325DC24255; Tue,  1 Mar 2011 22:10:55 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
CC: asrg@irtf.org
In-reply-to: <28307D97-6889-41FE-836C-356610088E0F@cauce.org> (message from Neil Schwartzman on Tue, 1 Mar 2011 19:01:25 -0500)
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com> <28307D97-6889-41FE-836C-356610088E0F@cauce.org>
Message-Id: <20110302031055.325DC24255@panix5.panix.com>
Date: Tue,  1 Mar 2011 22:10:55 -0500 (EST)
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 03:09:51 -0000

Neil Schwartzman <neil@cauce.org> wrote:

> and something those that benefit from the service should pay for,

As a receiver, I benefit from a whitelisting service, otherwise I
wouldn't bother to use it.  For me, the sender benefits less: I'd
accept good mail anyway, the whitelisting just makes it easier.

So should I have to pay to use a whitelisting service?

Suppose there were a perfect reputation service, that provided
information from "ESP outgoing for confirmed opt-in" through
"trojanned PC, emits only spam" and everything in between ("ISP
outgoing, cancels/blocks spamming customers immediately", etc.).

Clearly that's valuable to a recipient.  It's also valuable to the
high-ranked emitters; so, who "should" pay?

Seth

From sethb@panix.com  Tue Mar  1 19:27:39 2011
Return-Path: <sethb@panix.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 304F03A6C0E for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.244
X-Spam-Level: 
X-Spam-Status: No, score=-2.244 tagged_above=-999 required=5 tests=[AWL=0.355,  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 eTBTcYJk7Ndc for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:27:38 -0800 (PST)
Received: from mail1.panix.com (mail1.panix.com [166.84.1.72]) by core3.amsl.com (Postfix) with ESMTP id 598D73A6C0A for <asrg@irtf.org>; Tue,  1 Mar 2011 19:27:38 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail1.panix.com (Postfix) with ESMTP id BFB6A1F084 for <asrg@irtf.org>; Tue,  1 Mar 2011 22:28:42 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id B0E1924255; Tue,  1 Mar 2011 22:28:42 -0500 (EST)
From: Seth <sethb@panix.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-reply-to: <4D6DA412.2080708@mtcc.com> (message from Michael Thomas on Tue,  01 Mar 2011 17:57:38 -0800)
References: <20110302015409.10248.qmail@joyce.lan> <4D6DA412.2080708@mtcc.com>
Message-Id: <20110302032842.B0E1924255@panix5.panix.com>
Date: Tue,  1 Mar 2011 22:28:42 -0500 (EST)
Subject: Re: [Asrg] RFC 3934 applies to everyone
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 03:27:39 -0000

> Diagnostic-Code: SMTP; 553 Incoherent message (5.1.1)
>
> Is a personal attack, and a petty one at that.

It's an attack against whatever software produced the headers that the
receiving software is unable to parse.  I don't consider that
personal.

Seth

From CLEWIS@nortel.com  Tue Mar  1 19:30:24 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A1793A6A21 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.614
X-Spam-Level: 
X-Spam-Status: No, score=-5.614 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 tJU080d2SXZY for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:30:23 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id C5C1F3A6A16 for <asrg@irtf.org>; Tue,  1 Mar 2011 19:30:22 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p223VMm07725 for <asrg@irtf.org>; Wed, 2 Mar 2011 03:31:23 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 1 Mar 2011 22:31:22 -0500
Received: from [47.9.28.250] (47.9.28.250) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 1 Mar 2011 22:31:22 -0500
Message-ID: <4D6DBA08.1070607@nortel.com>
Date: Tue, 1 Mar 2011 22:31:20 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net>	<4D6D5713.3080205@mines-paristech.fr>	<20110301215047.A6B3624200@panix5.panix.com> <4D6D6E00.4020507@mines-paristech.fr>
In-Reply-To: <4D6D6E00.4020507@mines-paristech.fr>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2011 03:31:22.0820 (UTC) FILETIME=[4D8A8040:01CBD88A]
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 03:30:24 -0000

On 3/1/2011 5:06 PM, Jose-Marcio Martins da Cruz wrote:

> If one consider that spammers money is dirty money (criminal activity as one said)... and if part of
> the DNSBL revenue comes from this dirty money, how do you name this ? Probably not "money laundry",
> but surely not something legal.

While this particular horse isn't particularly relevant (if not dead), 
there are a variety of illegal things it could be, depending on the 
circumstances.  The key is whether the DNSBL operator can be shown to 
have _known_ that the delist request corresponded to ongoing illegal 
activity.  If it can, it could be accessory, conspiracy, racketeering or 
other things.

From mike@mtcc.com  Tue Mar  1 19:30:36 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7C69C3A6C12 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level: 
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[AWL=0.266,  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 rKw1gqWBdxBM for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 19:30:35 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by core3.amsl.com (Postfix) with ESMTP id 5CBDA3A67ED for <asrg@irtf.org>; Tue,  1 Mar 2011 19:30:35 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id p223Vdbw015883 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 19:31:39 -0800
Message-ID: <4D6DBA1B.2070003@mtcc.com>
Date: Tue, 01 Mar 2011 19:31:39 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110302015409.10248.qmail@joyce.lan> <4D6DA412.2080708@mtcc.com> <20110302032842.B0E1924255@panix5.panix.com>
In-Reply-To: <20110302032842.B0E1924255@panix5.panix.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=509; t=1299036700; x=1299900700; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20RFC=203934=20applies=20to=20ev eryone |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=7h4UAAvt90t+gTa34vX8Hcu9h4wz1N6iFhSfT5BYiC0=; b=WXc3RWsYizKvt9rfx3x01OlxOzZajqSHdiY639amswzz0gS12jM5m39Y0l 41066SQzFT7wl77Nt1aKI9PRr+FR406QNvnM2jyBWhe6LZfuCwhG3r+rkomB Tcqh5RKD4Xg781ZiJRKzWNbf2ZOtOQhjrryxnIbPV45oheUWMu/5s=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Cc: Seth <sethb@panix.com>
Subject: Re: [Asrg] RFC 3934 applies to everyone
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 03:30:36 -0000

On 03/01/2011 07:28 PM, Seth wrote:
>> Diagnostic-Code: SMTP; 553 Incoherent message (5.1.1)
>>
>> Is a personal attack, and a petty one at that.
>>      
> It's an attack against whatever software produced the headers that the
> receiving software is unable to parse.  I don't consider that
> personal.
>    

No, this is John's mail server blacklisting me in his own petty way.
There is nothing wrong with my message headers. Look for yourself,
and if there's a problem blame sendmail.

Mike

From mike@mtcc.com  Tue Mar  1 20:07:18 2011
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82B9B3A6A6B for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 M6+sDdC006HU for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:07:17 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) by core3.amsl.com (Postfix) with ESMTP id 988633A6C10 for <asrg@irtf.org>; Tue,  1 Mar 2011 20:07:17 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id p2248LYS029303 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 20:08:21 -0800
Message-ID: <4D6DC2B5.7080407@mtcc.com>
Date: Tue, 01 Mar 2011 20:08:21 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <2971038.39.1299023209305.JavaMail.root@zimbra.i6ix.com>	<28307D97-6889-41FE-836C-356610088E0F@cauce.org>	<4D6D8BFD.6010507@mtcc.com> <4D6DAA23.1090503@nortel.com>
In-Reply-To: <4D6DAA23.1090503@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=619; t=1299038902; x=1299902902; c=relaxed/simple; s=thundersaddle.kirkwood; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com; i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com> |Subject:=20Re=3A=20[Asrg]=20Getting=20group=20consensus=20 on=20draft-irtf-asrg-bcp-blacklists |Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org> |Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed |Content-Transfer-Encoding:=207bit |MIME-Version:=201.0; bh=lP/q9xQ7wkSRQyC8ynS3XJqzqRxNC1h3LNZ72R3ZTAg=; b=O53zsWEZFXDoHKLLlDWYRTIK0C2tAJYeUZXm8oq9Ny/Co9U/sEqlnle7U0 tyqLoo9UQ5k1rfhXeQxEMElTtT8MD/vSLhb5pYjpwE9w8IrbFpduEMPdFZgR 5VMqzkwI2bzga0mpnyYZWHsfxXW4xfocOJEqfXXBR/S+brM+EtRTA=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from mtcc.com/thundersaddle.kirkwood verified; );  dkim-asp=pass header.From=mike@mtcc.com
Cc: Chris Lewis <clewis@nortel.com>
Subject: Re: [Asrg] Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 04:07:18 -0000

On 03/01/2011 06:23 PM, Chris Lewis wrote:
> On 3/1/2011 7:14 PM, Michael Thomas wrote:
>
> AOL was never seriously considered a UDP target.  They were almost the 
> very first to see the need for abuse handling, and until recently set 
> the gold standard of excellence in it.

Those were the cries I remember hearing back then though. Aol
and all the rest of the commercial ISP's coming onto the net back
then was what laid bare that the UDP wasn't scalable. And it's
still not in the context of reputation. What does a good or bad
reputation mean in the context of a Yahoo! or hotmail? Not much.

Mike

From johnl@iecc.com  Tue Mar  1 20:13:40 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 819F43A67ED for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.084
X-Spam-Level: 
X-Spam-Status: No, score=-111.084 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 9r6k1ARAYf1I for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:13:39 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 42B2A3A6A21 for <asrg@irtf.org>; Tue,  1 Mar 2011 20:13:39 -0800 (PST)
Received: (qmail 2035 invoked from network); 2 Mar 2011 04:14:43 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Mar 2011 04:14:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=b1e1.4d6dc433.k1103; i=johnl@user.iecc.com; bh=WLS8PXg/HyUEZxoboMXnAMZNRlt5JBa3sl2mOk/6jYw=; b=h9azO8HMxHUBhYCWSYOiwkipZvr5RaRW3zJaL5ouLS+O+Y5yK7M/BylB797ZiB9it6zgBTGI90eP1fn/+P91clx6zES9XIut3M7021SZFWjHbs3IPSbGidhgjW+lXi+p9b5n73qo4Daz+zq+/uFc1JTrIcGRiOTr/uhKPBDoKK0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=b1e1.4d6dc433.k1103; olt=johnl@user.iecc.com; bh=WLS8PXg/HyUEZxoboMXnAMZNRlt5JBa3sl2mOk/6jYw=; b=XXUSiqEscnKKshSqd4iX+vQZrB027kS4gk622W2IfW32nPLYcPzKVmjd7Esus+4LIe1THdxd4RdoYUiKTy5QZ9qWkJB34PEB+YC6aTPS2Ytkknxnr1JYGlR5DFI938TM3P9p1nD5RxIUfTRzpHKGqPPRaHy2fhVwiWRNZjdfvJw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Mar 2011 04:14:43 -0000
Message-ID: <20110302041443.45536.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D6DA412.2080708@mtcc.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] RFC 3934 applies to everyone
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 04:13:40 -0000

In article <4D6DA412.2080708@mtcc.com> you write:
>Everyone including John Levine:
>
>Diagnostic-Code: SMTP; 553 Incoherent message (5.1.1)
>
>Is a personal attack, and a petty one at that.

Sigh.  Mike is complaining about an SMTP return code that is produced
by my own personal mail server, which has no relation to this or any
other IETF mailing list, and is not returned in response to any IETF
mailing list mail.  I cannot imagine why he thinks it is relevant to
the ASRG, and I don't want to know.

In any event, personal attacks on IETF lists are inappropriate and
disruptive.  If they continue, I'll invoke the usual 3934 30-day
suspension.

R's,
John


From trelane@trelane.net  Tue Mar  1 20:56:27 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FC4E3A6C13 for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 NdkwztohOsYM for <asrg@core3.amsl.com>; Tue,  1 Mar 2011 20:56:26 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by core3.amsl.com (Postfix) with ESMTP id C50E43A6B5D for <asrg@irtf.org>; Tue,  1 Mar 2011 20:56:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 8B08F1864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 23:57:29 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxfKOG6OHIW5 for <asrg@irtf.org>; Tue,  1 Mar 2011 23:57:27 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id D790A1864B8 for <asrg@irtf.org>; Tue,  1 Mar 2011 23:57:26 -0500 (EST)
Received: from [172.16.1.106] (unknown [66.93.203.199]) by mail.trelane.net (Postfix) with ESMTPA id 6D2D41864B4 for <asrg@irtf.org>; Tue,  1 Mar 2011 23:57:26 -0500 (EST)
Message-ID: <4D6DCE35.4070106@trelane.net>
Date: Tue, 01 Mar 2011 23:57:25 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net>	<4D6D5713.3080205@mines-paristech.fr>	<20110301215047.A6B3624200@panix5.panix.com>	<4D6D6E00.4020507@mines-paristech.fr> <4D6DBA08.1070607@nortel.com>
In-Reply-To: <4D6DBA08.1070607@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 04:56:27 -0000

On 3/1/2011 10:31 PM, Chris Lewis wrote:
> On 3/1/2011 5:06 PM, Jose-Marcio Martins da Cruz wrote:
>
>> If one consider that spammers money is dirty money (criminal activity
>> as one said)... and if part of
>> the DNSBL revenue comes from this dirty money, how do you name this ?
>> Probably not "money laundry",
>> but surely not something legal.
>
> While this particular horse isn't particularly relevant (if not dead),
> there are a variety of illegal things it could be, depending on the
> circumstances.  The key is whether the DNSBL operator can be shown to
> have _known_ that the delist request corresponded to ongoing illegal
> activity.  If it can, it could be accessory, conspiracy, racketeering
> or other things.
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg
Those who are not lawyers should not practice law.  In fact, this is
another failing of this section of the draft.

Andrew

From Jose-Marcio.Martins@mines-paristech.fr  Wed Mar  2 00:33:40 2011
Return-Path: <Jose-Marcio.Martins@mines-paristech.fr>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE9473A6AA4 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 00:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.45
X-Spam-Level: 
X-Spam-Status: No, score=-1.45 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_SUB_RAND_LETTRS4=0.799]
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 px5uRkL6jyc1 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 00:33:40 -0800 (PST)
Received: from smtp-3.ensmp.fr (smtp-3.ensmp.fr [194.214.158.227]) by core3.amsl.com (Postfix) with ESMTP id 0CEF03A6A89 for <asrg@irtf.org>; Wed,  2 Mar 2011 00:33:39 -0800 (PST)
Received: from localhost.localdomain (bororo [10.3.5.15]) (authenticated bits=0) by smtp-3.ensmp.fr (8.14.3/8.14.3/JMMC-11/Mar/2010) with ESMTP id p228YfRE002473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <asrg@irtf.org>; Wed, 2 Mar 2011 09:34:41 +0100 (MET)
Message-ID: <4D6E0120.60404@mines-paristech.fr>
Date: Wed, 02 Mar 2011 09:34:40 +0100
From: Jose-Marcio Martins da Cruz <Jose-Marcio.Martins@mines-paristech.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20110104 Fedora/2.0.11-2.fc14 SeaMonkey/2.0.11
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <4D6C265E.1060101@averillpark.net>	<EE315DEA-7486-4673-9875-DEC91352BC55@cauce.org>	<4D6D4284.50102@thoroquel.org>	<AANLkTinxGLpeWmxGWR7hiLoZabYhhmfQdAh=JagCg2yk@mail.gmail.com>	<4D6D4B64.5070304@mines-paristech.fr>	<4D6D4EF6.8030601@trelane.net>	<4D6D5713.3080205@mines-paristech.fr>	<20110301215047.A6B3624200@panix5.panix.com>	<4D6D6E00.4020507@mines-paristech.fr> <4D6DBA08.1070607@nortel.com>
In-Reply-To: <4D6DBA08.1070607@nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Miltered: at cascavel with ID 4D6E0121.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 4D6E0121.000 from bororo/bororo/10.3.5.15/localhost.localdomain/<Jose-Marcio.Martins@mines-paristech.fr>
Subject: Re: [Asrg] draft-irtf-asrg-bcp-blacklists-07 [re-send]
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Jose-Marcio.Martins@mines-paristech.fr, Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 08:33:41 -0000

Chris Lewis wrote:
> On 3/1/2011 5:06 PM, Jose-Marcio Martins da Cruz wrote:

> While this particular horse isn't particularly relevant (if not dead),
> there are a variety of illegal things it could be, depending on the
> circumstances. The key is whether the DNSBL operator can be shown to
> have _known_ that the delist request corresponded to ongoing illegal
> activity. If it can, it could be accessory, conspiracy, racketeering or
> other things.

Right ! And finally, IMHO, the less there will be "money transactions"
in the DNSBL management the better will be. Surely, charging the user
for a service perfectly defined isn't a problem.

From matthew@sorbs.net  Wed Mar  2 08:28:46 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D300E3A6831 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 08:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.899
X-Spam-Level: 
X-Spam-Status: No, score=-10.899 tagged_above=-999 required=5 tests=[AWL=0.399, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3]
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 S43SJaRlmO2g for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 08:28:42 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 8E8433A67A5 for <asrg@irtf.org>; Wed,  2 Mar 2011 08:28:35 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id 6947C19D25 for <asrg@irtf.org>; Thu,  3 Mar 2011 03:29:36 +1100 (EST)
Received: from nemesis.local (c190-214.i02-8.onvol.net [213.165.190.214]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005)) with ESMTPSA id <0LHF00505V56PI@nemesis.sorbs.net> for asrg@irtf.org; Thu, 03 Mar 2011 02:29:34 +1000 (EST)
Date: Wed, 02 Mar 2011 17:29:29 +0100
From: Michelle Sullivan <matthew@sorbs.net>
In-reply-to: <4D6AC45C.3080506@trelane.net>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-id: <4D6E7069.2080803@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
X-Enigmail-Version: 0.96.0
References: <20110227210118.44390.qmail@joyce.lan> <4D6AC316.20702@thoroquel.org> <4D6AC45C.3080506@trelane.net>
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 16:28:46 -0000

Andrew Kirch wrote:
> On 2/27/2011 4:33 PM, Joe Sniderman wrote:
>   
>> On 02/27/2011 04:01 PM, John Levine wrote:
>>     
>>> I'm seeing no support at all for "Claus'" contention that we should
>>> change the language about pay to delist in DNSBL practices draft.
>>>
>>> If anyone else agrees that we should change it, please say so now,
>>> otherwise I think we will consider the discussion over.
>>>       
>> I agree that it should be changed but not removed entirely. Change it
>> from a "MUST NOT" to a "SHOULD NOT" perhaps.
>>
>>
>>     
> Concur here.  I think Claus makes a valid point in that expedited
> service might require expedited cost.  I am also concerned that this is
> in direct contradiction of existing DNSBL practices, such as SORBS.  


Umm it does?
 (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
on the website has been updated to indicate there is no such thing as
the SORBS fine any more)

Michelle

From CLEWIS@nortel.com  Wed Mar  2 09:21:48 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43BB73A6838 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 09:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.045
X-Spam-Level: 
X-Spam-Status: No, score=-6.045 tagged_above=-999 required=5 tests=[AWL=0.554,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bLF4ez3h5erq for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 09:21:47 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 34EE73A6840 for <asrg@irtf.org>; Wed,  2 Mar 2011 09:21:46 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p22HMmm05883 for <asrg@irtf.org>; Wed, 2 Mar 2011 17:22:48 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 12:22:47 -0500
Received: from [47.9.28.35] (47.9.28.35) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 2 Mar 2011 12:22:46 -0500
Message-ID: <4D6E7CE3.8060404@nortel.com>
Date: Wed, 2 Mar 2011 12:22:43 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org> <4D6AC45C.3080506@trelane.net> <4D6E7069.2080803@sorbs.net>
In-Reply-To: <4D6E7069.2080803@sorbs.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2011 17:22:47.0184 (UTC) FILETIME=[72F06100:01CBD8FE]
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 17:21:48 -0000

On 3/2/2011 11:29 AM, Michelle Sullivan wrote:
> Andrew Kirch wrote:

>> Concur here.  I think Claus makes a valid point in that expedited
>> service might require expedited cost.  I am also concerned that this is
>> in direct contradiction of existing DNSBL practices, such as SORBS.

> Umm it does?
>   (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
> on the website has been updated to indicate there is no such thing as
> the SORBS fine any more)

Indeed, I think that this an important point.  Even though a DNSBL has 
ceased using the practise, it's still used as an argument as if it was 
still being used, and in many places still used as a reason to 
avoid/disparage the DNSBL.

Even after being mentioned numerous times _here_ this meme still 
continues to influence the discourse long after it become invalid - and 
remember, SORBS is in support of 2.2.5.

Further, why shouldn't a "Best Current Practises" document point out 
that a particular existing practise isn't "best"?  Isn't that what BCPs 
are supposed to do if necessary?

From joseph.sniderman@thoroquel.org  Wed Mar  2 11:01:02 2011
Return-Path: <joseph.sniderman@thoroquel.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 303643A684A for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.371
X-Spam-Level: 
X-Spam-Status: No, score=-6.371 tagged_above=-999 required=5 tests=[AWL=0.228,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tw2MrhNJ1ufC for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:01:00 -0800 (PST)
Received: from mail.thoroquel.org (mail.thoroquel.org [72.14.190.148]) by core3.amsl.com (Postfix) with ESMTP id 71DCB3A6844 for <asrg@irtf.org>; Wed,  2 Mar 2011 11:01:00 -0800 (PST)
Received: from [IPv6:2604:8800:101:1::e] (epinephrine.home.thoroquel.com [IPv6:2604:8800:101:1::e]) (authenticated bits=0) by mail.thoroquel.org (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p22J1vBt017539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 19:01:59 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thoroquel.org; s=thoroquel2a; t=1299092520; bh=Y1UdGXCz7W8uWlUnnvD33jhZ/GLkXoy+yu39/aryZg0=; h=Message-ID:Date:From:To:Subject:References:In-Reply-To:OpenPGP: Content-Type:Content-Transfer-Encoding:CC:DomainKey-Signature; b=D7njXPOo7V1m0teSOJSOERcke3ol1Ibv86g6ueRaLopizbOhI5CWxNrNY1G2bpuOc aF7GLKqty/R2tWnEV8q6hMoyjq8baSNoIKY1iTRQvisNBlzidPCT/Npmh90JfANzDu /yQbPIK2LJWqrMGFFPBxyy4FS5K6XxaP8jzQTthJSFSJE7Uk/IoPCCjbrXuaFBbp6x YAMXOj0+XIt4kTGDdByANvRIX5oxaLy/zFguKO3PRdNHrtFOp9c+fiJnvxvstaKywa QXBtldES0Vag5umIYt8rcLwjPU9JD+Z79snQigkGU3yJHiX4U1Xq1IYZCOawYhjrLN Tg1Naq6Chdo+w==
Message-ID: <4D6E9420.5030309@thoroquel.org>
Date: Wed, 02 Mar 2011 14:01:52 -0500
From: Joe Sniderman <joseph.sniderman@thoroquel.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org>	<4D6AC45C.3080506@trelane.net> <4D6E7069.2080803@sorbs.net> <4D6E7CE3.8060404@nortel.com>
In-Reply-To: <4D6E7CE3.8060404@nortel.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=605721CA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:01:02 -0000

On 03/02/2011 12:22 PM, Chris Lewis wrote:
> On 3/2/2011 11:29 AM, Michelle Sullivan wrote:
>> Andrew Kirch wrote:
> 
>>> Concur here.  I think Claus makes a valid point in that expedited
>>> service might require expedited cost.  I am also concerned that this is
>>> in direct contradiction of existing DNSBL practices, such as SORBS.
> 
>> Umm it does?
>>   (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
>> on the website has been updated to indicate there is no such thing as
>> the SORBS fine any more)
> 
> Indeed, I think that this an important point.  Even though a DNSBL has
> ceased using the practise, it's still used as an argument as if it was
> still being used, and in many places still used as a reason to
> avoid/disparage the DNSBL.

True, unfortunately.  On that one hand, that shows how once adopted, its
hard to ever make the "bad smell" go away, but on the other hand, the
prevalence of using outright false information to disparage DNSBLs, and
how event those with no axe to grind can so often fall for the
misinformation.

> Even after being mentioned numerous times _here_ this meme still
> continues to influence the discourse long after it become invalid - and
> remember, SORBS is in support of 2.2.5.

> Further, why shouldn't a "Best Current Practises" document point out
> that a particular existing practise isn't "best"?  Isn't that what BCPs
> are supposed to do if necessary?

It still is not "in direct contradiction of existing DNSBL practices,
such as SORBS" since that is not SORBS's current DNSBL practice.

-- 
Joe Sniderman <joseph.sniderman@thoroquel.org>

From trelane@trelane.net  Wed Mar  2 11:46:17 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 913843A6882 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[AWL=0.228,  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 yOjSE1nOH-RU for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:46:16 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by core3.amsl.com (Postfix) with ESMTP id 973133A6863 for <asrg@irtf.org>; Wed,  2 Mar 2011 11:46:16 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id DF807186500 for <asrg@irtf.org>; Wed,  2 Mar 2011 14:47:21 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anb+4Bo0iXIz for <asrg@irtf.org>; Wed,  2 Mar 2011 14:47:19 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 60CCA1864FF for <asrg@irtf.org>; Wed,  2 Mar 2011 14:47:19 -0500 (EST)
Received: from [172.16.1.106] (Andrew-Dell.system.lan [172.16.1.106]) by mail.trelane.net (Postfix) with ESMTPA id E3CE61864DA for <asrg@irtf.org>; Wed,  2 Mar 2011 14:47:18 -0500 (EST)
Message-ID: <4D6E9EBD.8040605@trelane.net>
Date: Wed, 02 Mar 2011 14:47:09 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org>	<4D6AC45C.3080506@trelane.net>	<4D6E7069.2080803@sorbs.net> <4D6E7CE3.8060404@nortel.com> <4D6E9420.5030309@thoroquel.org>
In-Reply-To: <4D6E9420.5030309@thoroquel.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:46:17 -0000

On 3/2/2011 2:01 PM, Joe Sniderman wrote:
> On 03/02/2011 12:22 PM, Chris Lewis wrote:
>> On 3/2/2011 11:29 AM, Michelle Sullivan wrote:
>>> Andrew Kirch wrote:
>>>> Concur here.  I think Claus makes a valid point in that expedited
>>>> service might require expedited cost.  I am also concerned that this is
>>>> in direct contradiction of existing DNSBL practices, such as SORBS.
>>> Umm it does?
>>>   (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
>>> on the website has been updated to indicate there is no such thing as
>>> the SORBS fine any more)
>> Indeed, I think that this an important point.  Even though a DNSBL has
>> ceased using the practise, it's still used as an argument as if it was
>> still being used, and in many places still used as a reason to
>> avoid/disparage the DNSBL.
> True, unfortunately.  On that one hand, that shows how once adopted, its
> hard to ever make the "bad smell" go away, but on the other hand, the
> prevalence of using outright false information to disparage DNSBLs, and
> how event those with no axe to grind can so often fall for the
> misinformation.
>
Err, are you accusing me of some sort of personal attack against
Michelle or SORBS?  I don't believe that there's a bad smell there at
all.  After being harassed and sued by a spammer, that legal defense
fund SORBS was running came to my aid big time.  I for one support these
measures.  DNSBL operators open themselves to huge legal liability, even
when protected by 47 USC 230 (at least in the United States).  Denying
them _ANY_ method of revenue generation is quite frankly wrong, and THAT
leaves a bad taste in my mouth.  Quite frankly I believe the entire
section is far outside of the scope of a BCP document.

Andrew

From johnl@iecc.com  Wed Mar  2 11:50:52 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DC423A688C for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:50:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.692
X-Spam-Level: 
X-Spam-Status: No, score=-110.692 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 nKFh7pbqUJOm for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:50:51 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id CBD773A687D for <asrg@irtf.org>; Wed,  2 Mar 2011 11:50:50 -0800 (PST)
Received: (qmail 11224 invoked from network); 2 Mar 2011 19:51:56 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Mar 2011 19:51:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=140e9.4d6e9fdc.k1103; i=johnl@user.iecc.com; bh=BESJiyBZyVki7+xkLyGeqZAzanuYNfIZ4Z1FZBZveRQ=; b=rEBQtO5C3XMHXie0c8m4NrhXBkmN16tfPibi0uhhtrbSFPp4xaGumuQFnXrtL2e6b69RPRY00Snetg5G/acl64NfA5b1ZBCb2EzB+lepoZxcXqDKxn7p/AlCq6CdJYG0lrVe8WXC2VtTOJR6uvGzKcsxzGrt15MXzuw2apnVmWE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=140e9.4d6e9fdc.k1103; olt=johnl@user.iecc.com; bh=BESJiyBZyVki7+xkLyGeqZAzanuYNfIZ4Z1FZBZveRQ=; b=Yy5oju9+AEa+TiTRyZScd511Cv7NiFNokpsjFFfRf7Zbm1TzagHZ1Jh2dPapi9fVyI8gctN/X2L+bdkK/i5fs+jsf4/6lTxuTSsV6NY5yOzp/O9uxO9ZRBiEhs7FqIEmrAh7yE2CEKNk8o1YrAbQIDTW6cmOtnBImee8/7y4Krg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Mar 2011 19:51:56 -0000
Message-ID: <20110302195156.82152.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <alpine.BSF.2.00.1103011507460.22961@joyce.lan>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:50:52 -0000

Going through recent messages, I see 25 people saying they support
the draft in its current form, and two that don't. (Three if you
count "Claus".)

I see that a few people have subscribed recently and I hope they
are going through the archives, to bring themselves up to date
on the discussion, so I'll give it another couple of days.

I think that Chris and Matt have a few minor wording improvements, but
nothing large that they want to adjust.  Keeping in mind that the
highly competent copy editors at the RFC Editor will make a pass and
fix any grammar issues, this is your last change to suggest
clarifications.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

PS: The archives are here, by the way.

http://www.ietf.org/mail-archive/web/asrg/current/maillist.html 

From laura@carrotcafe.com  Wed Mar  2 11:54:31 2011
Return-Path: <laura@carrotcafe.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7422F3A6862 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 ApDOH6hAkoYZ for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:54:30 -0800 (PST)
Received: from m.wordtothewise.com (b.wordtothewise.com [208.187.80.136]) by core3.amsl.com (Postfix) with ESMTP id D06E23A6831 for <asrg@irtf.org>; Wed,  2 Mar 2011 11:54:30 -0800 (PST)
Received: from valeria.wordtothewise.com (184.wordtothewise.com [208.187.80.184]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: wttwlaura) by m.wordtothewise.com (Postfix) with ESMTPSA id 397582DED5 for <asrg@irtf.org>; Wed,  2 Mar 2011 11:55:37 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Laura Atkins <laura@carrotcafe.com>
In-Reply-To: <20110302195156.82152.qmail@joyce.lan>
Date: Wed, 2 Mar 2011 11:55:36 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <652B6D28-ABCC-48E1-B675-C9D6BE45E0E2@carrotcafe.com>
References: <20110302195156.82152.qmail@joyce.lan>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:55:56 -0000

On Mar 2, 2011, at 11:51 AM, John Levine wrote:

> I think that Chris and Matt have a few minor wording improvements, but
> nothing large that they want to adjust.  Keeping in mind that the
> highly competent copy editors at the RFC Editor will make a pass and
> fix any grammar issues, this is your last change to suggest
> clarifications.

I support the draft as written. 

laura

-- 
Laura Atkins   laura@carrotcafe.com

   "If you do not choose to lead, you will forever be led by others.
   Find what  scares you and do it. And you *can* make a difference,
   if you choose to do so." JMS


From trelane@trelane.net  Wed Mar  2 11:56:17 2011
Return-Path: <trelane@trelane.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56B543A687D for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  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 Se+pBjV6RifH for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 11:56:16 -0800 (PST)
Received: from mail.trelane.net (mail.trelane.net [66.93.203.104]) by core3.amsl.com (Postfix) with ESMTP id 5B6163A686D for <asrg@irtf.org>; Wed,  2 Mar 2011 11:56:16 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id 8125A1864F5 for <asrg@irtf.org>; Wed,  2 Mar 2011 14:57:22 -0500 (EST)
X-Virus-Scanned: amavisd-new at trelane.net
Received: from mail.trelane.net ([127.0.0.1]) by localhost (master.trelane.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9y3m96DmDGBq for <asrg@irtf.org>; Wed,  2 Mar 2011 14:57:20 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.trelane.net (Postfix) with ESMTP id D16A61864FF for <asrg@irtf.org>; Wed,  2 Mar 2011 14:57:19 -0500 (EST)
Received: from [172.16.1.106] (Andrew-Dell.system.lan [172.16.1.106]) by mail.trelane.net (Postfix) with ESMTPA id 6F5C61864F5 for <asrg@irtf.org>; Wed,  2 Mar 2011 14:57:19 -0500 (EST)
Message-ID: <4D6EA11F.1050505@trelane.net>
Date: Wed, 02 Mar 2011 14:57:19 -0500
From: Andrew Kirch <trelane@trelane.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org>	<4D6AC45C.3080506@trelane.net>	<4D6E7069.2080803@sorbs.net>	<4D6E7CE3.8060404@nortel.com> <4D6E9420.5030309@thoroquel.org> <4D6E9EBD.8040605@trelane.net>
In-Reply-To: <4D6E9EBD.8040605@trelane.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 19:56:17 -0000

On 3/2/2011 2:47 PM, Andrew Kirch wrote:
> On 3/2/2011 2:01 PM, Joe Sniderman wrote:
>> On 03/02/2011 12:22 PM, Chris Lewis wrote:
>>> On 3/2/2011 11:29 AM, Michelle Sullivan wrote:
>>>> Andrew Kirch wrote:
>>>>> Concur here.  I think Claus makes a valid point in that expedited
>>>>> service might require expedited cost.  I am also concerned that this is
>>>>> in direct contradiction of existing DNSBL practices, such as SORBS.
>>>> Umm it does?
>>>>   (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
>>>> on the website has been updated to indicate there is no such thing as
>>>> the SORBS fine any more)
>>> Indeed, I think that this an important point.  Even though a DNSBL has
>>> ceased using the practise, it's still used as an argument as if it was
>>> still being used, and in many places still used as a reason to
>>> avoid/disparage the DNSBL.
>> True, unfortunately.  On that one hand, that shows how once adopted, its
>> hard to ever make the "bad smell" go away, but on the other hand, the
>> prevalence of using outright false information to disparage DNSBLs, and
>> how event those with no axe to grind can so often fall for the
>> misinformation.
>>
> Err, are you accusing me of some sort of personal attack against
> Michelle or SORBS?  I don't believe that there's a bad smell there at
> all.  After being harassed and sued by a spammer, that legal defense
> fund SORBS was running came to my aid big time.  I for one support these
> measures.  DNSBL operators open themselves to huge legal liability, even
> when protected by 47 USC 230 (at least in the United States).  Denying
> them _ANY_ method of revenue generation is quite frankly wrong, and THAT
> leaves a bad taste in my mouth.  Quite frankly I believe the entire
> section is far outside of the scope of a BCP document.
>
> Andrew
In the interests of attempting to reach consensus I would propose
language which specifies that DNSBL maintainers MUST disclose their
listing, de-listing, and any associated fees prominently in their terms
of service.  At that point it is up to the end-user to decide what is,
and what isn't ethical.  I don't care what you call it, I will sleep
better charging perpetrators of a crime (spam) than its victims.

Andrew

From hanov3r@gmail.com  Wed Mar  2 12:06:22 2011
Return-Path: <hanov3r@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 778743A6881 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level: 
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 0IU6dLD3oqme for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:06:21 -0800 (PST)
Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by core3.amsl.com (Postfix) with ESMTP id 7B8293A686D for <asrg@irtf.org>; Wed,  2 Mar 2011 12:06:21 -0800 (PST)
Received: by pvg11 with SMTP id 11so53922pvg.13 for <asrg@irtf.org>; Wed, 02 Mar 2011 12:07:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Dmd4H0pxslFidHw/tfNto1HnxmlE/QD+JDRAf2r0rm0=; b=lW1g5NwluF18Tn5Pr+J9wHtUbeeubEyYBdXbATb7XnKjvl3WqQOcG1orSbjrH/rWJY P/frToAkJe40K0p6z+kOBySthSRoI4T9gk1VcutZLOS3cuizEFKDpeafYRor/Z8kYLeX 8f3Ky7pEzN4a9+t71/BCOuvkw9R8SANUuXW6Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=N9ph0C6Md3d/YxYQsDRaIOdY2l4NYlsvBAdds+pTq0P2BTqZE3dNFjAK3MlEZ6Ius2 olB+BLQoSlfErSiVeAdzPdejRejhrYGi76ay9WJg/oykbjOelKkm9hC6MSbq1/mbD1mG /apxqzYkJYcpgrGOSzm7RR2RIg02ukq6LeiMQ=
Received: by 10.142.192.16 with SMTP id p16mr79999wff.357.1299096447890; Wed, 02 Mar 2011 12:07:27 -0800 (PST)
Received: from [172.22.5.30] (nat.cloudmark.com [72.5.239.5]) by mx.google.com with ESMTPS id w27sm366461wfd.16.2011.03.02.12.07.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 12:07:26 -0800 (PST)
Message-ID: <4D6EA37A.2060807@gmail.com>
Date: Wed, 02 Mar 2011 12:07:22 -0800
From: David Romerstein <hanov3r@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.16) Gecko/20101125 Thunderbird/3.0.11
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110302195156.82152.qmail@joyce.lan>
In-Reply-To: <20110302195156.82152.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:06:22 -0000

On 3/2/2011 11:51 AM, John Levine wrote:
> I think that Chris and Matt have a few minor wording improvements, but
> nothing large that they want to adjust.

I support the draft as written.

> Keeping in mind that the
> highly competent copy editors at the RFC Editor will make a pass and
> fix any grammar issues

I am *so* very glad you said this. I was going to offer to red-pen it. :)

-- D

From CLEWIS@nortel.com  Wed Mar  2 12:32:54 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1337E3A684E for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:32:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.724
X-Spam-Level: 
X-Spam-Status: No, score=-5.724 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 a-SG-UVH2WWZ for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:32:53 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 77AA63A686E for <asrg@irtf.org>; Wed,  2 Mar 2011 12:32:52 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p22KXsm06225 for <asrg@irtf.org>; Wed, 2 Mar 2011 20:33:54 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 2 Mar 2011 15:27:31 -0500
Received: from [47.9.28.35] (47.9.28.35) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Wed, 2 Mar 2011 15:27:30 -0500
Message-ID: <4D6EA831.3040201@nortel.com>
Date: Wed, 2 Mar 2011 15:27:29 -0500
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <20110302195156.82152.qmail@joyce.lan>
In-Reply-To: <20110302195156.82152.qmail@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2011 20:27:31.0049 (UTC) FILETIME=[416FF590:01CBD918]
Subject: Re: [Asrg] Last chance: Getting group consensus on	draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:32:54 -0000

On 3/2/2011 2:51 PM, John Levine wrote:

> I think that Chris and Matt have a few minor wording improvements, but
> nothing large that they want to adjust.  Keeping in mind that the
> highly competent copy editors at the RFC Editor will make a pass and
> fix any grammar issues, this is your last change to suggest
> clarifications.

As a FYI: the pending "bits" are:

- two grammatical blunders that someone spotted recently.
- After the previous round (just after 07 was released), John and I 
thought that there were two minor wording revisions that would be worth 
making - in the introduction as I recall.  I think one of them was 
finessing some wording about non-DNS distribution.  Nothing to do with 
dos or don'ts (capitalized or not ;-).  Do you remember that John? 
Haven't found it in a quick scan of my mailbox.

Do you think it worth re-issuing with those nits fixed as an 08, or 
leave that to the copy editors?


From geemailenator@gmail.com  Wed Mar  2 12:34:56 2011
Return-Path: <geemailenator@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 030B13A6816 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:34:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 sAP1umS-4l+n for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:34:54 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id A31353A6850 for <asrg@irtf.org>; Wed,  2 Mar 2011 12:34:54 -0800 (PST)
Received: by vws16 with SMTP id 16so391553vws.13 for <asrg@irtf.org>; Wed, 02 Mar 2011 12:36:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=TLyFzZZJ87PucHmaTJBB7CZjWJ6PTZO7aeJtPIucWH8=; b=oR85FX6kzC5eoJ1GVsxbx4WT2zYpgdvOmlzcEg/TZ2dN+5x2ON+Kvm9jPrgqyq8kYe F+0TNArmfDH5xRXqi3LtpFc0ge/k3VTbdlN8v4LGDYlw30pulCLU2XI5vfLUTRKOFrps DlPiCcTGDR40hXvbvTaT1zk9GQtI8Vkn00Z7I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=EOcS56v3dEaII1VYJtb+xMTLx/IFXW/BSVEMe5BBlt5GaO1nyets/jAKZzl7NPKAgn TWQZcSpfBepNpZGgoWBG6iO45Q0YwhJT3wt/F/Sb/QE7Utq4sYvsID50a673j7UK69rr 4uHrFTtIayd+81qvucGSE1xVAvIJUoZFdXVEM=
Received: by 10.52.169.39 with SMTP id ab7mr432881vdc.88.1299098160892; Wed, 02 Mar 2011 12:36:00 -0800 (PST)
Received: from [172.16.1.2] (modemcable156.249-57-74.mc.videotron.ca [74.57.249.156]) by mx.google.com with ESMTPS id dd19sm88216vdb.30.2011.03.02.12.35.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Mar 2011 12:35:59 -0800 (PST)
Sender: Neil Schwartzman <geemailenator@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
From: Neil Schwartzman <neil@cauce.org>
In-Reply-To: <20110302195156.82152.qmail@joyce.lan>
Date: Wed, 2 Mar 2011 15:35:58 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <D5863EFD-E32D-4251-AA02-0373C9821F3C@cauce.org>
References: <20110302195156.82152.qmail@joyce.lan>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Mailer: Apple Mail (2.1082)
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:34:56 -0000

On Mar 2, 2011, at 2:51 PM, John Levine wrote:

> I think that Chris and Matt have a few minor wording improvements, but
> nothing large that they want to adjust.  Keeping in mind that the
> highly competent copy editors at the RFC Editor will make a pass and
> fix any grammar issues, this is your last change to suggest
> clarifications.

I support the draft as written.

--
Neil Schwartzman
Executive Director
CAUCE
The Coalition Against Unsolicited Commercial Email, North America Inc.

http://cauce.org
http://twitter.com/cauce
IM: caucecanada
Tel.: +1 (303) 800 6345





From kelly.molloy@gmail.com  Wed Mar  2 12:50:25 2011
Return-Path: <kelly.molloy@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 21C5D3A6840 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.88
X-Spam-Level: 
X-Spam-Status: No, score=-2.88 tagged_above=-999 required=5 tests=[AWL=-0.080,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 dDCMt2zHrx3l for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:50:24 -0800 (PST)
Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by core3.amsl.com (Postfix) with ESMTP id 48A543A6835 for <asrg@irtf.org>; Wed,  2 Mar 2011 12:50:24 -0800 (PST)
Received: by yie12 with SMTP id 12so129652yie.13 for <asrg@irtf.org>; Wed, 02 Mar 2011 12:51:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=z/OAGBoge080NwbVdGTpmj52xf/T/zS0CsU5Ysu97QI=; b=ZZzP7a96kyiCaKq1ygs/mi0Vw2kx5D9ueCGdMdOgAJbPl0om6LhxqI1ShkfwzOH52+ XHBKR1Yj7qSrsIXazpcC+X1io36us6GaHGfgvvIx+/aenZFXgHFLKoWK+fETAcVoPC3E OuTaQ8hEMgGxGwu4AaYxi9w100//jpRAsMHNI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ErkOkD2c4whqPBL6NmggfWI+l57nxKQ6DwwNMtX063Xi/If4zfoe96i5+yQxKxm0KR 9n1j1ueBGFlOWmsKpYyPe+xa1bQAXsJAx1VthbPByEjhZ3ObMo1DEVFlJ2gFSZ10K179 3mMjekadC+5UC0A2dLIHW98vHuFEpA9pAUBFU=
MIME-Version: 1.0
Received: by 10.236.109.194 with SMTP id s42mr250990yhg.79.1299099089876; Wed, 02 Mar 2011 12:51:29 -0800 (PST)
Received: by 10.147.167.12 with HTTP; Wed, 2 Mar 2011 12:51:29 -0800 (PST)
In-Reply-To: <D5863EFD-E32D-4251-AA02-0373C9821F3C@cauce.org>
References: <20110302195156.82152.qmail@joyce.lan> <D5863EFD-E32D-4251-AA02-0373C9821F3C@cauce.org>
Date: Wed, 2 Mar 2011 12:51:29 -0800
Message-ID: <AANLkTin=kU0AaCxATODGAXAP4i=09rWQW9zQ61xe-9Uk@mail.gmail.com>
From: Kelly Molloy <kelly.molloy@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:50:25 -0000

On Wed, Mar 2, 2011 at 12:35 PM, Neil Schwartzman <neil@cauce.org> wrote:
>
> On Mar 2, 2011, at 2:51 PM, John Levine wrote:
>
>> I think that Chris and Matt have a few minor wording improvements, but
>> nothing large that they want to adjust. =A0Keeping in mind that the
>> highly competent copy editors at the RFC Editor will make a pass and
>> fix any grammar issues, this is your last change to suggest
>> clarifications.
>
> I support the draft as written.

I think I said this before, but +1:

I support the draft as written.

From johnl@iecc.com  Wed Mar  2 12:56:08 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC7BB3A6864 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.674
X-Spam-Level: 
X-Spam-Status: No, score=-110.674 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 rvpTQSRAFHKN for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:56:07 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id ED0743A6835 for <asrg@irtf.org>; Wed,  2 Mar 2011 12:56:06 -0800 (PST)
Received: (qmail 29746 invoked from network); 2 Mar 2011 20:57:12 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Mar 2011 20:57:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=3caf.4d6eaf27.k1103; i=johnl@user.iecc.com; bh=94u+iZ+E0coPuJQKc7K111itHaOv7muPWvQt+q3NWZU=; b=XV9yUx3wJWlRdHAuLS1h7xeUCO9d5DnsfDGOaNOT1y8ZVDqX5Rm++vdyNH01+QotCdz6DcIMNdxfyAyWBCxwZOFtJOcdy4Cob2R4fSpjF267N1SZp8rcyS38o96M7QiAUrFipi6LIc50H8nm8x6IT4rtqoEWnWbxx2ucaWfy2AM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=3caf.4d6eaf27.k1103; olt=johnl@user.iecc.com; bh=94u+iZ+E0coPuJQKc7K111itHaOv7muPWvQt+q3NWZU=; b=bzx2ZJFXORCWSy7xhjZ5hqfLIDdx/cYrLyCjIhdDxYc/PJzZy1uuz4DaryMGic36fXR+4cDyBUpZQy1tZ526q+ACeOVshykuLsWcH69qFkvX1wLStaRgIGNEMzNQ8X3vifuuPE8A03G1j7hnzJI0HfcIsYlxh5uHFla7gjmGMdw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Mar 2011 20:57:11 -0000
Message-ID: <20110302205711.15534.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D6EA831.3040201@nortel.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Last chance: Getting group consensus on	draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:56:08 -0000

>- two grammatical blunders that someone spotted recently.
>- After the previous round (just after 07 was released), John and I 
>thought that there were two minor wording revisions that would be worth 
>making - in the introduction as I recall.  I think one of them was 
>finessing some wording about non-DNS distribution.  Nothing to do with 
>dos or don'ts (capitalized or not ;-).  Do you remember that John? 

Nope.  I'll see if I can find it.

>Do you think it worth re-issuing with those nits fixed as an 08, or 
>leave that to the copy editors?

It's OK to send a note to the editor suggesting things to fix.  People
do it all the time.

R's,
John

From joseph.sniderman@thoroquel.org  Wed Mar  2 12:57:22 2011
Return-Path: <joseph.sniderman@thoroquel.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A04153A68AC for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HVJsQfTmhU1U for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 12:57:21 -0800 (PST)
Received: from mail.thoroquel.org (mail.thoroquel.org [72.14.190.148]) by core3.amsl.com (Postfix) with ESMTP id DB3043A68A9 for <asrg@irtf.org>; Wed,  2 Mar 2011 12:57:20 -0800 (PST)
Received: from [IPv6:2604:8800:101:1::e] (epinephrine.home.thoroquel.com [IPv6:2604:8800:101:1::e]) (authenticated bits=0) by mail.thoroquel.org (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p22KwJcL017681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 20:58:21 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=thoroquel.org; s=thoroquel2a; t=1299099502; bh=kHyMlHbXGtdV+jpHLf5v4GKy8o8KskizoQaoiLYrl/E=; h=Message-ID:Date:From:To:Subject:References:In-Reply-To:OpenPGP: Content-Type:Content-Transfer-Encoding:CC:DomainKey-Signature; b=K8pLj38nQE+gZO8inTuVHZOUgT0jwkfvyZDYZYWnN0mKv1tioft0pkPhsefqmYPXc /yLlGWTRPZC2OMlGuda2t2B2rmCtwyKJ004emWl6jaUzlvVizOJg8cQcnnDAT04O+X Nrt9UvU8wLFZ8F+7D7sesH7OPJhwBH3EZuVTaczfvW8U5r6LcCIO0j3i7lwVwoWGc3 pQ1Cz4AB9EVM3KAn19FZE5ndN5SjE5bgbnNDP5AFPN63t/8pD1olAqNKQbFDVj8EYE RQwA3egpQsaED6+wN8M8CtxFj8O+efc0uOwCJ34jIiI3TsWnHHN9/4b8cRuH2rfDQ4 VxS6qvCI853mw==
Message-ID: <4D6EAF67.7020400@thoroquel.org>
Date: Wed, 02 Mar 2011 15:58:15 -0500
From: Joe Sniderman <joseph.sniderman@thoroquel.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org>	<4D6AC45C.3080506@trelane.net>	<4D6E7069.2080803@sorbs.net>	<4D6E7CE3.8060404@nortel.com> <4D6E9420.5030309@thoroquel.org> <4D6E9EBD.8040605@trelane.net>
In-Reply-To: <4D6E9EBD.8040605@trelane.net>
X-Enigmail-Version: 1.1.1
OpenPGP: id=605721CA
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 20:57:22 -0000

On 03/02/2011 02:47 PM, Andrew Kirch wrote:
> On 3/2/2011 2:01 PM, Joe Sniderman wrote:
>> On 03/02/2011 12:22 PM, Chris Lewis wrote:
>>> On 3/2/2011 11:29 AM, Michelle Sullivan wrote:
>>>> Andrew Kirch wrote:
>>>>> Concur here.  I think Claus makes a valid point in that expedited
>>>>> service might require expedited cost.  I am also concerned that this is
>>>>> in direct contradiction of existing DNSBL practices, such as SORBS.
>>>> Umm it does?
>>>>   (FYI SORBS has not imposed any fines since Oct 12, 2010 and the policy
>>>> on the website has been updated to indicate there is no such thing as
>>>> the SORBS fine any more)
>>> Indeed, I think that this an important point.  Even though a DNSBL has
>>> ceased using the practise, it's still used as an argument as if it was
>>> still being used, and in many places still used as a reason to
>>> avoid/disparage the DNSBL.
>> True, unfortunately.  On that one hand, that shows how once adopted, its
>> hard to ever make the "bad smell" go away, but on the other hand, the
>> prevalence of using outright false information to disparage DNSBLs, and
>> how event those with no axe to grind can so often fall for the
>> misinformation.
>>
> Err, are you accusing me of some sort of personal attack against
> Michelle or SORBS?  

Quite the contrary!

> I don't believe that there's a bad smell there at all.

> After being harassed and sued by a spammer, that legal defense
> fund SORBS was running came to my aid big time.  I for one support these
> measures.

Yes, I am somewhat (probably lots more to it than I know about) familiar
with that chain of events.  My point is that despite the fact that you
clearly have no axe to grind, no hostility or personal issue against
SORBS, that the FUD (namely that SORBS still charges a fine) spread by
those who do seems to have rubbed off on you as well. (unless I am just
misreading you)

Despite the fact that SORBS stopped charging a fine, its common
knowledge that they do charge a fine. Ie, common knowledge in this
regard is wrong.

*That* is the bad smell that doesnt go away. If a DNSBL is willing to
live with that bad smell, I dont think its anyones place to try to stop
them from doing so.

> DNSBL operators open themselves to huge legal liability, even
> when protected by 47 USC 230 (at least in the United States).  Denying
> them _ANY_ method of revenue generation is quite frankly wrong, and THAT
> leaves a bad taste in my mouth.

Agreed absolutely.  That said, there is a lot of area between best
practice and worst practice.  As a *general* rule, paid delisting is
probably somewhere in the middle of the road on that broad range.

> Quite frankly I believe the entire
> section is far outside of the scope of a BCP document.

I would tend to agree, but not because of any of the specifics of paid
delisting. Business model in general doesnt make sense to cover in a
BCP. That said, even with it included, i think the current text is good
enough.

-- 
Joe Sniderman <joseph.sniderman@thoroquel.org>

From johnl@iecc.com  Wed Mar  2 13:27:58 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5BAB3A68A9 for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 13:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.658
X-Spam-Level: 
X-Spam-Status: No, score=-110.658 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 SYt09y110KJu for <asrg@core3.amsl.com>; Wed,  2 Mar 2011 13:27:57 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 39B4D3A6816 for <asrg@irtf.org>; Wed,  2 Mar 2011 13:27:57 -0800 (PST)
Received: (qmail 40259 invoked from network); 2 Mar 2011 21:29:02 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Mar 2011 21:29:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=ee0a.4d6eb69e.k1103; i=johnl@user.iecc.com; bh=Q0y05aE0X0EF4v9YcHtn7cATi8/XgwnUxlRn6ICpxt4=; b=VpeBOCI6sZW336XpX3msL5ijRZPFObX6OpaMNRZ/6amQ/RJcGb460cwZibAECUATVuySk2t05dl6YdxL89dGp4CeoayaTeD3z/PQuZEzLH43xkNXrKTEuGv8c/bHuq4aZ3JdCMJsMMuWgy+2lAi+hgp0HyHAFUZMWh/Pi/BPkbA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=ee0a.4d6eb69e.k1103; olt=johnl@user.iecc.com; bh=Q0y05aE0X0EF4v9YcHtn7cATi8/XgwnUxlRn6ICpxt4=; b=wdLqPu/jM8o0oGjrfwUmzYWG1ThiVAFGkQRg5B7DGAwlY3p7kpkOTIteNgbXPjDQvfY+4lId9jdpf+bnwMS56ftnydDS0t3hm9kJ9JPNIirfQPgAi51/xOLyOr5w9ywlivJF04t2ssSDC92g95lem0OphRigvPp/EtJBoZjOHNM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Mar 2011 21:29:02 -0000
Message-ID: <20110302212902.60937.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D6EA831.3040201@nortel.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Last chance: Getting group consensus on	draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Mar 2011 21:27:59 -0000

>- After the previous round (just after 07 was released), John and I 
>thought that there were two minor wording revisions that would be worth 
>making - in the introduction as I recall.  I think one of them was 
>finessing some wording about non-DNS distribution.  Nothing to do with 
>dos or don'ts (capitalized or not ;-).  Do you remember that John? 
>Haven't found it in a quick scan of my mailbox.

After greppage (accent on the last syllable) I found a few things:

* At the end of 1.1, say something about why DNS and note that there
  are other distrubution methods than DNS, notably rsync

* Add a forward reference from 2.2.2 (about response contact blocking) to 
> advanced planning in the face of DDoS (3.2).  Either that, or a simple 
> sentence about being able to change contact process in case of need.

For the former, perhaps add:

 The DNS has been the most popular distrubution method for DNSBLs due
 to its ubiquity and its good scaling and performance characteristics.
 It is also common to make private arrangements to distribute DNSBL
 data in bulk to high volume users, typically by rsync [ref].  The data
 is the same in either case, the the recommendations in this document
 apply regardless of distribution method, other than the ones in
 Sections 3.1-3.2 that specifically refer to DNS distribution.

R's,
John

From msk@cloudmark.com  Thu Mar  3 23:56:04 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD1EA3A6892 for <asrg@core3.amsl.com>; Thu,  3 Mar 2011 23:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.294
X-Spam-Level: 
X-Spam-Status: No, score=-104.294 tagged_above=-999 required=5 tests=[AWL=-1.494, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 TGSFO7V+kg5t for <asrg@core3.amsl.com>; Thu,  3 Mar 2011 23:56:04 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by core3.amsl.com (Postfix) with ESMTP id 2C5233A692D for <asrg@irtf.org>; Thu,  3 Mar 2011 23:56:04 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 3 Mar 2011 23:57:12 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Thu, 3 Mar 2011 23:57:10 -0800
Thread-Topic: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
Thread-Index: AcvZFXkNKjHFC6GcSNSvQFqSHDtVkQBLCzyA
Message-ID: <F5833273385BB34F99288B3648C4F06F1341E74595@EXCH-C2.corp.cloudmark.com>
References: <20110302195156.82152.qmail@joyce.lan> <4D6EA37A.2060807@gmail.com>
In-Reply-To: <4D6EA37A.2060807@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-asrg-bcp-blacklists
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 07:56:05 -0000

> -----Original Message-----
> From: asrg-bounces@irtf.org [mailto:asrg-bounces@irtf.org] On Behalf Of D=
avid Romerstein
> Sent: Wednesday, March 02, 2011 12:07 PM
> To: asrg@irtf.org
> Subject: Re: [Asrg] Last chance: Getting group consensus on draft-irtf-as=
rg-bcp-blacklists
>=20
> I am *so* very glad you said this. I was going to offer to red-pen it.
> :)

I'm a huge fan of making the RFC Editor do as little work as possible, so i=
f you have the time, energy and willingness, please do bust out the red pen=
.

From matthew@sorbs.net  Fri Mar  4 00:27:48 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 854AA3A6908 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 00:27:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.299
X-Spam-Level: 
X-Spam-Status: No, score=-11.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3]
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 FjwD9T9Boxrd for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 00:27:47 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 613B23A6842 for <asrg@ietf.org>; Fri,  4 Mar 2011 00:27:45 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id 0CA4B1BB60 for <asrg@ietf.org>; Fri,  4 Mar 2011 19:28:50 +1100 (EST)
Received: from users-Mac-mini.local ([192.168.255.4]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar 3 2005)) with ESMTPSA id <0LHI00L06Y7XHF@nemesis.sorbs.net> for asrg@ietf.org; Fri, 04 Mar 2011 18:28:50 +1000 (EST)
Date: Fri, 04 Mar 2011 09:28:43 +0100
From: Michelle Sullivan <matthew@sorbs.net>
To: Anti-Spam Research Group - IRTF <asrg@ietf.org>
Message-id: <4D70A2BB.2090802@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.16) Gecko/20101123 SeaMonkey/2.0.11
Subject: [Asrg] BCP and payments.
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 08:27:48 -0000

I think this may have been already put to bed, but I haven't seen a post 
like this so far..

BCP = Best Current Practices

UCEPROTECT are the only larger (umm 'known') DNSBl with a pay model.

Other well known (and arguably larger in usage - SORBS userbase is way 
over (multiply by way over) the 2.5m that Claus has presented for 
UCEPROTECT) DNSBls are:

CBL (mostly through Spamhaus)
Spamcop
Spamhaus
SORBS

None of which charge, and there is a general consensus on this list that 
charging is wrong (I have said it for years, since 2003 when I 
implemented the charity donation I said it was wrong.  I said that 
collecting the money yourself for yourself is a VERY wrong practice.  
Chris (and others) should remember i said, "I don't like it, in fact I 
hate it, but I can't see an effective alternative")  Therefore would it 
not follow that the list which includes a lot of DNSBl operators 
(representitives from all the large ones and lots of smaller ones) 
suggesting that the Best Current Practice of not charging is actually 
the Best Current Practice...?

That said I can see why there is the argument with "MUST NOT" vs "SHOULD 
NOT" because I argued some years ago (version 5?) that it should be 
"SHOULD NOT" because there are those (here even) that will point at any 
DNSBl and the clause where that DNSBl fails to meet the BCP and use it 
as a reason for stopping using the DNSBl at a management level in a 
company rather than clearing up listings and stopping spam.  That 
practice IMHO is against the purpose of the BCP which is a guide to how 
one should operate (rather than give so called rules/law/policy on how 
it should be run.)

Does that make sense?

Regards,

Michelle

From msk@cloudmark.com  Fri Mar  4 08:26:32 2011
Return-Path: <msk@cloudmark.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B164A3A6802 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 08:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.044
X-Spam-Level: 
X-Spam-Status: No, score=-104.044 tagged_above=-999 required=5 tests=[AWL=-1.445, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Y4HynP6hU-ng for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 08:26:32 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.36]) by core3.amsl.com (Postfix) with ESMTP id F0EE33A67A1 for <asrg@irtf.org>; Fri,  4 Mar 2011 08:26:31 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by spite.corp.cloudmark.com ([172.22.10.72]) with mapi; Fri, 4 Mar 2011 08:27:41 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Date: Fri, 4 Mar 2011 08:27:40 -0800
Thread-Topic: [Asrg] Rough consensus on pay to delist
Thread-Index: AcvW5peQ3XIAaBSzRcWS0fZO53AV2wDomCjw
Message-ID: <F5833273385BB34F99288B3648C4F06F1341E74598@EXCH-C2.corp.cloudmark.com>
References: <4D6AC8C8.3010008@trelane.net> <20110228012652.21154.qmail@joyce.lan>
In-Reply-To: <20110228012652.21154.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 16:26:32 -0000

> -----Original Message-----
> From: asrg-bounces@irtf.org [mailto:asrg-bounces@irtf.org] On Behalf Of J=
ohn Levine
> Sent: Sunday, February 27, 2011 5:27 PM
> To: asrg@irtf.org
> Subject: Re: [Asrg] Rough consensus on pay to delist
>=20
> >I disagree here and note that legislators may look to this BCP later
> >if they intended to write such legislation.
>=20
> Having helped some actual legislators write actual legislation, I
> find it utterly implausible that anyone would ever legislate the
> practices of DNSBLs in other than the most general terms.
>=20
> Note that in the US they're protected by 47 US 230 which says they can
> do anything they want so long as there's a plausible good faith basis
> for doing so.  Case law confirms that making mistakes does not mean
> you weren't acting in good faith.

Feel free to point me at some reading materials to answer this question, bu=
t:

Isn't that statement contradictory to what happened to MAPS?

From andrew.barrett@gmail.com  Fri Mar  4 09:35:57 2011
Return-Path: <andrew.barrett@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7F6E3A6818 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 09:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Sa4jpY-bgq9R for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 09:35:57 -0800 (PST)
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by core3.amsl.com (Postfix) with ESMTP id 07B033A68AB for <asrg@irtf.org>; Fri,  4 Mar 2011 09:35:56 -0800 (PST)
Received: by yxl31 with SMTP id 31so957542yxl.13 for <asrg@irtf.org>; Fri, 04 Mar 2011 09:37:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PgetGcsjS7Wcg8zHRv+uDvPuxP3z9HCVOZFBABosS4M=; b=mEDjP5UcLQJqNmMEssVFQQqGRMs6b7M6Zj/iFVVnhU9TwEhDTCEyJ7W/bsDV4z25M1 PzB8AQursOcoOTLPEpCTWexTO5QQLQzkmwaavn8X9AtK6ZeFnsbb7PZ9EoCI+P56ihZp etNWCN0BNtZzK0X9t1kRBT2IqmbybMW7Fzi8E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=dV1Xh8vojvW8vFx/9B+qk997b0qymHZb6IjUiMZhBnmEHuFfXiSfBd7ZwpMsZqXAch 39uES6hwdx0Lnc0SY9zcgVU8bybD5oaXVnujv0PlV6vnol8BCfFrd/jwVepmx4WbLAk3 mut7pgTAWSZW+QD4064et+/1W27SmWEQT+9DA=
MIME-Version: 1.0
Received: by 10.150.164.11 with SMTP id m11mr930118ybe.263.1299260226024; Fri, 04 Mar 2011 09:37:06 -0800 (PST)
Received: by 10.147.83.19 with HTTP; Fri, 4 Mar 2011 09:37:05 -0800 (PST)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F1341E74598@EXCH-C2.corp.cloudmark.com>
References: <4D6AC8C8.3010008@trelane.net> <20110228012652.21154.qmail@joyce.lan> <F5833273385BB34F99288B3648C4F06F1341E74598@EXCH-C2.corp.cloudmark.com>
Date: Fri, 4 Mar 2011 12:37:05 -0500
Message-ID: <AANLkTim0MskGP5jAiQK7e2D_eSvnm0PNwsymG9aqkbpH@mail.gmail.com>
From: Andrew Barrett <andrew.barrett@gmail.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 17:35:58 -0000

On Fri, Mar 4, 2011 at 11:27 AM, Murray S. Kucherawy <msk@cloudmark.com> wr=
ote:

>> Note that in the US they're protected by 47 US 230 which says they can
>> do anything they want so long as there's a plausible good faith basis
>> for doing so. =A0Case law confirms that making mistakes does not mean
>> you weren't acting in good faith.
>
> Feel free to point me at some reading materials to answer this question, =
but:
>
> Isn't that statement contradictory to what happened to MAPS?

I don't recall that 47 US 230 was the basis of any action against
MAPS; plaintiffs tended to cite violations of various anti-trust or
anti-competitive statutes. In any event, I don't recall an instance in
which plaintiff ultimately prevailed on the merits. Prevailed, yes; on
the merits, no.

All the best,
Andrew. (ex-MAPSter)

From johnl@iecc.com  Fri Mar  4 09:39:16 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CB493A68B9 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 09:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.072
X-Spam-Level: 
X-Spam-Status: No, score=-111.072 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 FCZhQ4R1GMJ1 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 09:39:14 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 829BF3A69C8 for <asrg@irtf.org>; Fri,  4 Mar 2011 09:39:14 -0800 (PST)
Received: (qmail 60438 invoked from network); 4 Mar 2011 17:40:23 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 4 Mar 2011 17:40:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=809.4d712407.k1103; i=johnl@user.iecc.com; bh=1LusPoulFF1/0hh5f64YMCrig6JhxEt97yyBLZiPk/Y=; b=DztMibgLdYapcysyZ/ifqAXQpgakTYFcJhYiLNjZgc10cfvZMFlXejm4Ddi6gt8Uti2yi5MrOXj7mFKevcl+DNR8YPnB6em2/CNj1+uu8n2AU7hsUUGNhmpvjzRgqeqdMI9Tj3arIq0M9wSYAYSHMtUIE+KD9XpqnGwt5Z9+Z5A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=809.4d712407.k1103; olt=johnl@user.iecc.com; bh=1LusPoulFF1/0hh5f64YMCrig6JhxEt97yyBLZiPk/Y=; b=ab/cQWcT+GDXFYKJ65SJhaMMHBFEd2I1SDU2VKUII8ctC9QVyPyCCVBssHSJNuLdmeYH9LOdq0B/PdUEqPdgbEyT0TYASHOeWiO1mdyfnJpY9nfppNI3YTdF6NJTlIQbncjWFv0NxbsVXueu3xPKo4SsYhwfLQUu/mNffnatYno=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Mar 2011 17:40:22 -0000
Message-ID: <20110304174022.2056.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <F5833273385BB34F99288B3648C4F06F1341E74598@EXCH-C2.corp.cloudmark.com>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] legal issues, was Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 17:39:16 -0000

>> Note that in the US they're protected by 47 US 230 which says they can
>> do anything they want so long as there's a plausible good faith basis
>> for doing so.  Case law confirms that making mistakes does not mean
>> you weren't acting in good faith.
>
>Feel free to point me at some reading materials to answer this question, but:
>
>Isn't that statement contradictory to what happened to MAPS?

I believe that all the cases were settled or dismissed.  (Not 100%
sure, they're so old that PACER doesn't have documents for most of
them.)  MAPS severely underestimated the costs of discovery and such,
even if one wins a case, and I'm not sure how good their overall legal
strategy was.  As far as I know, they didn't make a 230 defense; Anne
Mitchell could fill in the gaps if there aren't confidentiality
issues.

More recently, in e360insight vs. Comcast, E360 claimed that Comcast
was unfairly blocking his CAN SPAM compliant mail. Comcast crushed
E360 with a 230 defense.

In Zango vs. Kaspersky, Zango objected to Kaspersky's listing them as
spyware. The court granted summary judgement to Kaspersky noting that
it didn't matter whether their listing was correct, so long as it was
made in good faith.

A silly little company called Holomaxx is currently suing Yahoo and
Hotmail in separate suits for blocking their spam, and we all expect
230 wins there, too.

As far as what to read, CAUCE and the Cornell Legal Information
Institute are working on an online spam law archive as part of
the LII's online legal resources.  I expect that will start coming
online in a month or two.

R's,
John

From dotis@mail-abuse.org  Fri Mar  4 11:46:06 2011
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE66328C0DC for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 11:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 7rh82P9wQun8 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 11:46:06 -0800 (PST)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 1403F28C0D9 for <asrg@irtf.org>; Fri,  4 Mar 2011 11:46:06 -0800 (PST)
Received: from us-dougo-mac.us.trendnet.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 8996AA94452 for <asrg@irtf.org>; Fri,  4 Mar 2011 19:48:09 +0000 (UTC)
Message-ID: <4D7141BE.7010208@mail-abuse.org>
Date: Fri, 04 Mar 2011 11:47:10 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110227210118.44390.qmail@joyce.lan>	<4D6AC316.20702@thoroquel.org>	<4D6AC45C.3080506@trelane.net>	<4D6E7069.2080803@sorbs.net>	<4D6E7CE3.8060404@nortel.com> <4D6E9420.5030309@thoroquel.org> <4D6E9EBD.8040605@trelane.net>
In-Reply-To: <4D6E9EBD.8040605@trelane.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 19:46:06 -0000

On 3/2/11 11:47 AM, Andrew Kirch wrote:
>  ... After being harassed and sued by a spammer, that legal defense
>  fund SORBS was running came to my aid big time. I for one support
>  these measures. DNSBL operators open themselves to huge legal
>  liability, even when protected by 47 USC 230 (at least in the United
>  States). Denying them _ANY_ method of revenue generation is quite
>  frankly wrong, and THAT leaves a bad taste in my mouth. Quite
>  frankly I believe the entire section is far outside of the scope of a
>  BCP document.

Agreed.

There might also be two-factor authentication techniques, that could 
rely upon SMS  for example) which might be seen as a charge.  How one 
supports a service should be stated, but not dictated as MUSTs by this BCP.

Unfortunately, the basis upon much of the practices advocated are likely 
to prove unworkable in the near future.  As such, there are far too many 
MUSTs.

Also RFC330 should be updated to RFC5735.

-Doug

From johnl@iecc.com  Fri Mar  4 12:33:57 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A3693A6830 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 12:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.077
X-Spam-Level: 
X-Spam-Status: No, score=-111.077 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 EKZnyEabBHKp for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 12:33:56 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id DE4A73A69BE for <asrg@irtf.org>; Fri,  4 Mar 2011 12:33:55 -0800 (PST)
Received: (qmail 4310 invoked from network); 4 Mar 2011 20:35:04 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 4 Mar 2011 20:35:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=ea0a.4d714cf8.k1103; i=johnl@user.iecc.com; bh=OkzyOCNhfCu9KmdYQai3yAGRSg4USWvzyIujOucpcuc=; b=EiErYqbRv8KmsPrIdDpPBfHKJrvM1r1XN3G9Sd17nXdE8P6LLiQQw03rQR+LbAAgBzPaf3qsuV2WWidNKk11ZLfNUqxqKUTYj3mlGnG/sYduPeY7lR9UPCd8kF253kir0jZrYyksKvpOfsRnlXr21a1On6Z0OrtsjEh+UHej6lI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=ea0a.4d714cf8.k1103; olt=johnl@user.iecc.com; bh=OkzyOCNhfCu9KmdYQai3yAGRSg4USWvzyIujOucpcuc=; b=n4QQwnlrS6tEQwPWnCSF7lU571helIbfT1/Z9iYPvwxk0NptmUXrO5lY7dmWtTC6JLYbuVB0vAPZcPwYWV5EBp0sdKD70XuUu9bwfRYCOcYCViRiAk9cpItLMz/Mr7lwSkdWys0rlJSZKtoJ0+SvH3jZz1SDyTMo7eWsVip/2Ek=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 4 Mar 2011 20:35:04 -0000
Message-ID: <20110304203504.59913.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D6E9EBD.8040605@trelane.net>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 20:33:57 -0000

> Denying them _ANY_ method of revenue generation ...

Since nobody's proposing that, can we stop now?

R's,
John

PS: Spamhaus says that they're quite adequately funded, presumably
from the large mail systems that pay for bulk access to their lists.


From dotis@mail-abuse.org  Fri Mar  4 14:16:20 2011
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A27F03A68AC for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 14:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 TrtS63+WCpDw for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 14:16:20 -0800 (PST)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 552143A6869 for <asrg@irtf.org>; Fri,  4 Mar 2011 14:16:19 -0800 (PST)
Received: from us-dougo-mac.us.trendnet.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 5E4E7A94452 for <asrg@irtf.org>; Fri,  4 Mar 2011 22:18:25 +0000 (UTC)
Message-ID: <4D7164F6.2060805@mail-abuse.org>
Date: Fri, 04 Mar 2011 14:17:26 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110304203504.59913.qmail@joyce.lan>
In-Reply-To: <20110304203504.59913.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 22:16:20 -0000

On 3/4/11 12:35 PM, John Levine wrote:
>> Denying them _ANY_ method of revenue generation ...
> Since nobody's proposing that, can we stop now?
You really mean ANY and ALL.

Exclusion methods for those seeking faster service might be facilitated 
through additional forms of authentication, which might then require 
nominal fees.

2.2.5.  Conflict of Interest

.---
Therefore, negative-connotation DNSBLs MUST not charge fees or require 
donations for delisting or "faster handling", and it is RECOMMENDED that 
such DNSBLs that do charge fees or require donations not be used.
'---

Fees may result as nominal charges related to authentication methods.  
Such authentication might be needed to support services highly prone to 
abuse.  Practical methods MUST BE allowed when mitigating flooding aimed 
a inflicting greater expense or the degradation of services.   
Responding to SMS might prove practical, but would be in conflict with 
the premise stated in 2.2.4 of MUST NOT charge fees in responding to a 
request.   Also, requiring a donation to independent third-parties 
explicitly avoids this being a conflict of interest.

This section is wrong and poorly considered, especially since most spam 
is carried over bot-nets where DoS issues are a greater concern.  None 
of this should be a problem as long as listing is made in good faith, 
and is normally corrected without requests being made.  Why expose these 
services litigation on the basis of nominal fees commonly used elsewhere.

-Doug



From johnl@iecc.com  Fri Mar  4 16:10:27 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 352D13A6A17 for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 16:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.082
X-Spam-Level: 
X-Spam-Status: No, score=-111.082 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 nvEN1LSvx7vM for <asrg@core3.amsl.com>; Fri,  4 Mar 2011 16:10:26 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id DAA7A3A692D for <asrg@irtf.org>; Fri,  4 Mar 2011 16:10:25 -0800 (PST)
Received: (qmail 41172 invoked from network); 5 Mar 2011 00:11:34 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 5 Mar 2011 00:11:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=d80.4d717fb6.k1103; i=johnl@user.iecc.com; bh=bmyNgZLijZeq9Ojp5BfibYeeI+mJ8F9KZcxCLIAUBlw=; b=Swh3ejWSfS9+6v/DEfn2xbMY64eA8MQSyeLuUaScKS6VDckmw0PBcpA6WGLknVfzgfYg6LhWuh691c+HDjjYpM57VQdi5xBhozGshoatx4GPdKuwUFHM5QcEh5MfwThwdqnjYAxYe3LWseEqPTrdF5tGq7bEUy/7ABT0r8EFqHc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=d80.4d717fb6.k1103; olt=johnl@user.iecc.com; bh=bmyNgZLijZeq9Ojp5BfibYeeI+mJ8F9KZcxCLIAUBlw=; b=kwemNuOMCaR3vTAynajIOCrKJikr/KcoQ832D/6ceVlZJT495CCP9hO3KC4uEXWYiRV/w+KdW2XznfjeWiMCiqBTSnTIybKBOQUkOBm4z5PFMaN0cDJJm8VwBcFC1hRfD8j++cP/XEFALSimowdi5dpS3lN9binnq2osr8NGd84=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Mar 2011 00:11:33 -0000
Message-ID: <20110305001133.3455.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D7164F6.2060805@mail-abuse.org>
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2011 00:10:27 -0000

>Fees may result as nominal charges related to authentication methods.  
>Such authentication might be needed to support ...

Something like that is hypothetically possible, but we're documenting
existing practice.  If anyone is aware of a BL that people actually
use that's using authentication so complex that they have to charge
for it, let us know.

R's,
John

From fw@deneb.enyo.de  Sat Mar  5 11:25:54 2011
Return-Path: <fw@deneb.enyo.de>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D62E3A69C7 for <asrg@core3.amsl.com>; Sat,  5 Mar 2011 11:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 AvHcbbXkAdre for <asrg@core3.amsl.com>; Sat,  5 Mar 2011 11:25:53 -0800 (PST)
Received: from ka.mail.enyo.de (ka.mail.enyo.de [87.106.162.201]) by core3.amsl.com (Postfix) with ESMTP id 5FE193A687E for <asrg@ietf.org>; Sat,  5 Mar 2011 11:25:53 -0800 (PST)
Received: from [172.17.135.4] (helo=deneb.enyo.de) by ka.mail.enyo.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1Pvx83-0000QJ-Dm for asrg@ietf.org; Sat, 05 Mar 2011 20:27:03 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.72) (envelope-from <fw@deneb.enyo.de>) id 1Pvx83-0004eU-6s for asrg@ietf.org; Sat, 05 Mar 2011 20:27:03 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: asrg@ietf.org
References: <4D70A2BB.2090802@sorbs.net>
Date: Sat, 05 Mar 2011 20:27:03 +0100
In-Reply-To: <4D70A2BB.2090802@sorbs.net> (Michelle Sullivan's message of "Fri, 04 Mar 2011 09:28:43 +0100")
Message-ID: <87d3m5z7ug.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [Asrg] BCP and payments.
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Mar 2011 19:25:54 -0000

* Michelle Sullivan:

> None of which charge, and there is a general consensus on this list
> that charging is wrong (I have said it for years, since 2003 when I
> implemented the charity donation I said it was wrong.

Are you referring to charges for removal, or just charging for access
to the DNSBL?

From dotis@mail-abuse.org  Sun Mar  6 22:21:28 2011
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEDCB3A6914 for <asrg@core3.amsl.com>; Sun,  6 Mar 2011 22:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 ev-JSkCcoeDi for <asrg@core3.amsl.com>; Sun,  6 Mar 2011 22:21:27 -0800 (PST)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id B5C3E3A6909 for <asrg@irtf.org>; Sun,  6 Mar 2011 22:21:27 -0800 (PST)
Received: from US-DOUGO-MAC.local (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 108EAA9447B for <asrg@irtf.org>; Mon,  7 Mar 2011 06:23:35 +0000 (UTC)
Message-ID: <4D7479AC.6080607@mail-abuse.org>
Date: Sun, 06 Mar 2011 22:22:36 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110305001133.3455.qmail@joyce.lan>
In-Reply-To: <20110305001133.3455.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 06:21:28 -0000

On 3/4/11 4:11 PM, John Levine wrote:
>> Fees may result as nominal charges related to authentication methods.
>> Such authentication might be needed to support ...
> Something like that is hypothetically possible, but we're documenting
> existing practice.  If anyone is aware of a BL that people actually
> use that's using authentication so complex that they have to charge
> for it, let us know.
The BCP makes blanket statements that clearly overreach, as it logically 
fails in its justification. Nominal charges by third-parties as part of 
some type of authentication do not represent a CONFLICT OF INTEREST, as 
implied by the overreaching section making these requirements.  It seems 
unlikely ISP support desks would be receptive to such restrictions.  For 
example, tunneling services requests may impose such requirements.  When 
a service is flooded with spoofed requests, it is not unreasonable to 
require at least non-free email accounts or SMS messages as a method to 
elevate requests.  The way this section has been written, such methods 
would be excluded without any valid justification.  Again, these methods 
do not represent a CONFLICT OF INTEREST nor represent unreasonable or 
unused practices.

-Doug



From linford@spamhaus.org  Sun Mar  6 23:50:39 2011
Return-Path: <linford@spamhaus.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABB4B3A6923 for <asrg@core3.amsl.com>; Sun,  6 Mar 2011 23:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.297
X-Spam-Level: 
X-Spam-Status: No, score=-18.297 tagged_above=-999 required=5 tests=[AWL=0.902, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
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 US3yt1cCzXPz for <asrg@core3.amsl.com>; Sun,  6 Mar 2011 23:50:38 -0800 (PST)
Received: from smtp-ext-layer.spamhaus.org (ns8.spamhaus.org [82.94.216.239]) by core3.amsl.com (Postfix) with ESMTP id 74F883A68F2 for <asrg@irtf.org>; Sun,  6 Mar 2011 23:50:38 -0800 (PST)
References: <20110305001133.3455.qmail@joyce.lan> <4D7479AC.6080607@mail-abuse.org>
In-Reply-To: <4D7479AC.6080607@mail-abuse.org>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From: Steve Linford <linford@spamhaus.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
X-Local-MTA-Info: 
X-Mime-Info: text/plain
Message-ID: <A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org>
Date: Mon, 07 Mar 2011 07:51:50 +0000
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 07:50:39 -0000

On 7 Mar 2011, at 07:22, Douglas Otis wrote:

> The BCP makes blanket statements that clearly overreach, as it =
logically fails in its justification.

In most people's view, "Pay me to remove you from the blacklist I just =
put you on" is a significant conflict of interest.

I'm sure it will interest you to know that two separate European =
consumer protection agencies, OPTA (NL) and OFT (UK), have asked serious =
questions in law enforcement circles (London Action Plan, etc) about the =
particular European blacklist that uses this business model, having had =
many complaints of extortion/racketeering from European Internet users =
who claim their mail server IPs were held to ransom. With "Pay me to =
remove you from the blacklist I just put you on" there is a very strong =
incentive to blacklist wide IP ranges as miscellaneous escalations =
simply to collect larger amounts of removal fees. The conflict of =
interest is substantial and should be flagged as extremely poor =
practice.

  Steve Linford
  The Spamhaus Project
  http://www.spamhaus.org
 =20


From esa@winteri.org  Mon Mar  7 00:12:36 2011
Return-Path: <esa@winteri.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C97923A689F for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 00:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 mIMsT2PQJGpe for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 00:12:34 -0800 (PST)
Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by core3.amsl.com (Postfix) with ESMTP id 51D2A3A6827 for <asrg@irtf.org>; Mon,  7 Mar 2011 00:12:33 -0800 (PST)
Received: by yie12 with SMTP id 12so1742485yie.13 for <asrg@irtf.org>; Mon, 07 Mar 2011 00:13:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=winteri.org; s=google; h=domainkey-signature:mime-version:sender:x-originating-ip :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=LFDalpHQzCd0ABCfAgnaJAMZ3THaBpfV0mAWFYm7hnY=; b=RwCPUE2wvWg5h9ij9kCO8ftv1T7o2UohC5E+OWR/rxp4vo3Kcnw0d2v7ylsOXFTpYy 33GgTta2RdsKbNwZKQLsiFnSXiftwFpjjk+cww9ikkfz6XdOY3zik2Cchq3u+C1C0lkp OZ22pjszI3CZRgSvcbhC2MLJF8Zx58thBs8Wk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=winteri.org; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=PhsjbUKxANfOeHQaH8KQaSDqWPQ306CuseYcrc0BRPnbtA1WRGR57SjCi+KKEE1wr9 HWiFuRdctebkX39TXc5/KhmgYmtDNSlRGD7E9IQTuSBGJYNb5k6kirb5Zxy9dwpBo4sx 9M3suuwr3scUdrP2MgDVepDYmRLpmSYbpVs/k=
MIME-Version: 1.0
Received: by 10.151.76.13 with SMTP id d13mr3939274ybl.444.1299485626653; Mon, 07 Mar 2011 00:13:46 -0800 (PST)
Sender: esa@winteri.org
Received: by 10.151.51.5 with HTTP; Mon, 7 Mar 2011 00:13:46 -0800 (PST)
X-Originating-IP: [91.199.43.40]
In-Reply-To: <A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org>
References: <20110305001133.3455.qmail@joyce.lan> <4D7479AC.6080607@mail-abuse.org> <A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org>
Date: Mon, 7 Mar 2011 09:13:46 +0100
X-Google-Sender-Auth: k3jMc218ua0xJg4IQA_nag9Y4Ig
Message-ID: <AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com>
From: Esa Laitinen <esa@laitinen.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Content-Type: multipart/alternative; boundary=000e0cd70d7c2add98049de013a6
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 08:12:36 -0000

--000e0cd70d7c2add98049de013a6
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 7, 2011 at 8:51 AM, Steve Linford <linford@spamhaus.org> wrote:

> In most people's view, "Pay me to remove you from the blacklist I just put
> you on" is a significant conflict of interest.
>

There is also a significant difference in  "Pay me to remove you from the
blacklist I just put you on"  and "you'll be automatically removed in 7
days, but if you cannot wait, you can also pay to get processed faster",
don't you think?


> I'm sure it will interest you to know that two separate European consumer
> protection agencies, OPTA (NL) and OFT (UK), have asked serious questions in
> law enforcement circles (London Action Plan, etc) about the particular
> European blacklist that uses this business model, having had many complaints
> of extortion/racketeering from European Internet users who claim their mail
> server IPs were held to ransom.
>
>
I actually fail to see what consumer protection agencies have with the issue
to do: normally mailservers are run by companies.

But anyway, blacklists have always drawn heat. Did that stop Spamhaus, for
example?


We're beating a dead horse here: majority of the messages have indicated
that charging for expedited delisting causes a conflict of interest, but
charging for using the list doesn't. I disagree, but can live with it (isn't
the first time I disagree with the majority, won't be the last I guess ;-)


-- 
Mr. Esa Laitinen
Tel. +41 76 200 2870
skype/yahoo: reunaesa
Blog: http://happiloppuuahistaa.blogspot.com

--000e0cd70d7c2add98049de013a6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Mar 7, 2011 at 8:51 AM, Steve Li=
nford <span dir=3D"ltr">&lt;<a href=3D"mailto:linford@spamhaus.org">linford=
@spamhaus.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204)=
; padding-left: 1ex;">
In most people&#39;s view, &quot;Pay me to remove you from the blacklist I =
just put you on&quot; is a significant conflict of interest.<br></blockquot=
e><div><br>There is also a significant difference in=A0 &quot;Pay me to rem=
ove you from the blacklist I just put you on&quot;=A0 and &quot;you&#39;ll =
be automatically removed in 7 days, but if you cannot wait, you can also pa=
y to get processed faster&quot;, don&#39;t you think?<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I&#39;m sure it will interest you to know that two separate European consum=
er protection agencies, OPTA (NL) and OFT (UK), have asked serious question=
s in law enforcement circles (London Action Plan, etc) about the particular=
 European blacklist that uses this business model, having had many complain=
ts of extortion/racketeering from European Internet users who claim their m=
ail server IPs were held to ransom. <br>

<br></blockquote></div><br>I actually fail to see what consumer protection =
agencies have with the issue to do: normally mailservers are run by compani=
es. <br><br>But anyway, blacklists have always drawn heat. Did that stop Sp=
amhaus, for example?<br>
<br><br>We&#39;re beating a dead horse here: majority of the messages have =
indicated that charging for expedited delisting causes a conflict of intere=
st, but charging for using the list doesn&#39;t. I disagree, but can live w=
ith it (isn&#39;t the first time I disagree with the majority, won&#39;t be=
 the last I guess ;-)<br>
<br><br>-- <br>Mr. Esa Laitinen<br>Tel. +41 76 200 2870<br>skype/yahoo: reu=
naesa<br>Blog: <a href=3D"http://happiloppuuahistaa.blogspot.com" target=3D=
"_blank">http://happiloppuuahistaa.blogspot.com</a><br><br>

--000e0cd70d7c2add98049de013a6--

From brendan@swiftspirit.co.za  Mon Mar  7 02:52:44 2011
Return-Path: <brendan@swiftspirit.co.za>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D11BA3A6944 for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 02:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HS_INDEX_PARAM=0.001]
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 RokkKS+y3XAu for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 02:52:43 -0800 (PST)
Received: from fw2a.glodns.net (fw2a.glodns.net [196.220.48.60]) by core3.amsl.com (Postfix) with ESMTP id 7AA7F3A67AE for <asrg@irtf.org>; Mon,  7 Mar 2011 02:52:43 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by fw2a.glodns.net (Postfix) with ESMTP id DD5CE28C028 for <asrg@irtf.org>; Mon,  7 Mar 2011 10:51:14 +0000 (UTC)
X-Virus-Scanned: amavisd-new at fw2a.glodns.net
Received: from fw2a.glodns.net ([196.220.48.60]) by localhost (fw2a.glodns.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IiQ6kg8nZfbP for <asrg@irtf.org>; Mon,  7 Mar 2011 05:51:09 -0500 (EST)
Received: from control.glodns.net (smtp1w.glodns.net [75.126.138.3]) by fw2a.glodns.net (Postfix) with ESMTP id 603BA28C061 for <asrg@irtf.org>; Mon,  7 Mar 2011 05:51:09 -0500 (EST)
Received: (qmail 3291 invoked from network); 7 Mar 2011 12:53:50 +0200
Received: from dsl-185-163-220.dynamic.wa.co.za (HELO ?41.185.163.220?) (41.185.163.220) by smtp1b.plesk.glodns.net with (AES256-SHA encrypted) SMTP; 7 Mar 2011 12:53:49 +0200
Message-ID: <4D74B93B.5060203@swiftspirit.co.za>
Date: Mon, 07 Mar 2011 12:53:47 +0200
From: Brendan Hide <brendan@swiftspirit.co.za>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20110305001133.3455.qmail@joyce.lan>	<4D7479AC.6080607@mail-abuse.org>	<A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org> <AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com>
In-Reply-To: <AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 10:52:44 -0000

I'm joining the bandwagon late it seems. Please note my opinions do not 
in any way reflect the opinions of my Employer.

The ISP I work for went through major expansion of our network in the 
last 2 years. We got our own address space, issued many of these to our 
ADSL customers and had to also, of course, self-manage the network. Very 
quickly UCEPROTECT had us listed because we blundered. We didn't pay. We 
saw how fruitless this would be, so we fixed the issue by installing 
spam filtering on port 25. This worked and now only the spam filter 
server gets listed every now and again, which we're happy to leave for 7 
days. We tell our customers to use port 587 with Authentication. As a 
result the majority of the mail reaching our filter system is blocked as 
spam and only a small amount of actual spam leaves the network.

Despite being on the "receiving end" of UCEPROTECT I feel no ill towards 
them, except as a reminder of how easy it is for poor technical 
implementation to result in spam being sent out. It was our fault.

While I don't like the idea that UCEPROTECT makes money from express 
delistings, I feel this is outside the scope of RFC and technical BCP 
documents. Yes, when a company makes money by "extortion" (and I use 
this term VERY loosely here) its a damned good idea to make their 
listing criteria publically available. However I don't see this being 
relevant except for the case of legal proceeding, again, IMHO outside 
the scope of the document being discussed.

-- 
__________
Brendan Hide
Mobile: +27 83 448 3867
Mobile: brendan.cell@swiftspirit.co.za (plain text only please)
Web Africa - Internet Business Solutions - http://www.webafrica.co.za/?AFF1E97


From graeme@graemef.net  Mon Mar  7 03:01:01 2011
Return-Path: <graeme@graemef.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 14ACA28C108 for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 03:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[AWL=0.400, 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 Qe2-bAeASK3A for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 03:00:59 -0800 (PST)
Received: from boom.graemef.net (graemef-2-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:1362::2]) by core3.amsl.com (Postfix) with ESMTP id AD12A3A6961 for <asrg@irtf.org>; Mon,  7 Mar 2011 03:00:46 -0800 (PST)
Received: from cpc13-shep11-2-0-cust235.8-3.cable.virginmedia.com ([86.24.149.236] helo=[192.168.7.241]) by boom.graemef.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <graeme@graemef.net>) id 1PwYCM-0000Yi-2b for asrg@irtf.org; Mon, 07 Mar 2011 11:01:59 +0000
From: Graeme Fowler <graeme@graemef.net>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com>
References: <20110305001133.3455.qmail@joyce.lan> <4D7479AC.6080607@mail-abuse.org> <A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org> <AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 07 Mar 2011 11:02:10 +0000
Message-ID: <1299495730.2943.33.camel@supergrover.internal.graemef.net>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 11:01:01 -0000

On Mon, 2011-03-07 at 09:13 +0100, Esa Laitinen wrote:
> We're beating a dead horse here

Quite - too much effort seems to be concentrating on one piece of
detail.

That said, if we all take a breath and step back a moment, the crux of
the matter appears to me (neither an ISP nor a DNSBL operator, but an
interested observer) to be this:

This discussion is based on a proposed BCP document. That's important:
Best Current Practice.

BCP documents do not preclude operating in a way which is contradictory,
they merely flag those ways as either not being current, or being
acknowledged as not the best way to operate.

Some time ago in this thread a question was asked if anyone knew of any
other currently operating DNSBLs which charge for delisting, or to
expedite delisting. I do not recall an answer being forthcoming.

>From a completely apolitical standpoint (acknowledging that there may be
some smaller DNSBL operators who aren't engaged here operating DNSBLs
which have a very local user base and therefore aren't represented here)
that indicates that payment for delisting or expedited delisting is
*not* a widely held current practice. Ergo, it is not "best" or
"current".

I would like to propose the following change to 2.2.5, which I hope
covers the controversy in words which are slightly less controversial:

------------------------------------------------------------------------
2.2.5 Payment to DNSBL operators

        It is widely considered appropriate for a DNSBL to charge for
        access to it by its users - the definition of a commercial
        DNSBL.
        
        However, the practise of requiring a listee to pay for delisting
        from a negative connotation DNSBL (used by subscribers, paid or
        otherwise, for blocking purposes) is widely considered not to be
        appropriate. This also applies to charges made for expedited
        delisting from a negative connotation DNSBL, for example after a
        malware infection or other temporary condition is cleared.
        
        Negative-connotation DNSBLs MUST NOT charge fees or require
        donations for delisting or expedited delisting. Such a practise
        is controversial and likely to damage the reputation of the
        DNSBL or the DNSBL operator and may render the DNSBL less useful
        than intended.
------------------------------------------------------------------------

I've stuck with MUST NOT there, because the actual best and current
practice is exactly that. Feel free to throw it out with the bathwater.

Graeme


From matthew@sorbs.net  Mon Mar  7 07:40:59 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EF9728C0D9 for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 07:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.033
X-Spam-Level: 
X-Spam-Status: No, score=-11.033 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3]
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 BwO+udga1A5q for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 07:40:58 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 22A3B3A68AD for <asrg@irtf.org>; Mon,  7 Mar 2011 07:40:53 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id DBF8960C9 for <asrg@irtf.org>; Tue,  8 Mar 2011 02:42:00 +1100 (EST)
Received: from nemesis.local (c190-214.i02-8.onvol.net [213.165.190.214]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005)) with ESMTPSA id <0LHP00D0229RSC@nemesis.sorbs.net> for asrg@irtf.org; Tue, 08 Mar 2011 01:41:58 +1000 (EST)
Date: Mon, 07 Mar 2011 16:41:50 +0100
From: Michelle Sullivan <matthew@sorbs.net>
In-reply-to: <87d3m5z7ug.fsf@mid.deneb.enyo.de>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-id: <4D74FCBE.4070309@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
X-Enigmail-Version: 0.96.0
References: <4D70A2BB.2090802@sorbs.net> <87d3m5z7ug.fsf@mid.deneb.enyo.de>
Cc: asrg@ietf.org
Subject: Re: [Asrg] BCP and payments.
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 15:40:59 -0000

Florian Weimer wrote:
> * Michelle Sullivan:
>
>   
>> None of which charge, and there is a general consensus on this list
>> that charging is wrong (I have said it for years, since 2003 when I
>> implemented the charity donation I said it was wrong.
>>     
>
> Are you referring to charges for removal, or just charging for access
> to the DNSBL?
> _________


Removal.

Shells


From matthew@sorbs.net  Mon Mar  7 07:41:03 2011
Return-Path: <matthew@sorbs.net>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60DD83A686E for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 07:41:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.355
X-Spam-Level: 
X-Spam-Status: No, score=-10.355 tagged_above=-999 required=5 tests=[AWL=-0.545, BAYES_05=-1.11, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_OTHER=-0.1, RCVD_IN_BSP_TRUSTED=-4.3]
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 IhshAxgOe5Jt for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 07:40:58 -0800 (PST)
Received: from anaconda.sorbs.net (anaconda.sorbs.net [113.52.8.152]) by core3.amsl.com (Postfix) with ESMTP id 22B703A68CF for <asrg@ietf.org>; Mon,  7 Mar 2011 07:40:53 -0800 (PST)
Received: from mail.sorbs.net (mail.sorbs.net [113.52.8.200]) by anaconda.sorbs.net (Postfix) with ESMTP id C4B3760C2 for <asrg@ietf.org>; Tue,  8 Mar 2011 02:42:00 +1100 (EST)
Received: from nemesis.local (c190-214.i02-8.onvol.net [213.165.190.214]) by nemesis.sorbs.net (iPlanet Messaging Server 5.2 HotFix 2.05 (built Mar  3 2005)) with ESMTPSA id <0LHP00D0229RSC@nemesis.sorbs.net> for asrg@ietf.org; Tue, 08 Mar 2011 01:41:58 +1000 (EST)
Date: Mon, 07 Mar 2011 16:41:50 +0100
From: Michelle Sullivan <matthew@sorbs.net>
In-reply-to: <87d3m5z7ug.fsf@mid.deneb.enyo.de>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-id: <4D74FCBE.4070309@sorbs.net>
Organization: Spam and Open Relay Blocking System
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.23) Gecko/20090823 SeaMonkey/1.1.18
X-Enigmail-Version: 0.96.0
References: <4D70A2BB.2090802@sorbs.net> <87d3m5z7ug.fsf@mid.deneb.enyo.de>
Cc: asrg@ietf.org
Subject: Re: [Asrg] BCP and payments.
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 15:41:03 -0000

Florian Weimer wrote:
> * Michelle Sullivan:
>
>   
>> None of which charge, and there is a general consensus on this list
>> that charging is wrong (I have said it for years, since 2003 when I
>> implemented the charity donation I said it was wrong.
>>     
>
> Are you referring to charges for removal, or just charging for access
> to the DNSBL?
> _________


Removal.

Shells


From johnl@iecc.com  Mon Mar  7 09:47:22 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AC5E3A67FD for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 09:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.095
X-Spam-Level: 
X-Spam-Status: No, score=-111.095 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 V5foA0JJcYP6 for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 09:47:20 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id C9FBC3A67DA for <asrg@irtf.org>; Mon,  7 Mar 2011 09:47:16 -0800 (PST)
Received: (qmail 55370 invoked from network); 7 Mar 2011 17:48:29 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 7 Mar 2011 17:48:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=14163.4d751a6d.k1103; i=johnl@user.iecc.com; bh=XnjUnLhuyT7JVTcK0fZOx25dLy2WBv+YeY+7MEkNjzw=; b=Z+bkHHjNfcrsd+pPIt4OisKdoU+TBgbhsiSHJn4i1gpmIZ6Ka+KXVg3UwceL20+U+8IbGrXdhCTv+25sfNLvieL8rtRhfuW7jbW3SAh0oTcKVWXbwUAPh6+ysn7Ui3M3kF2FlVxeYcH1ue386vsSrD9yEFJacjOHbtcL/ajszFU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=14163.4d751a6d.k1103; olt=johnl@user.iecc.com; bh=XnjUnLhuyT7JVTcK0fZOx25dLy2WBv+YeY+7MEkNjzw=; b=EHlVK3yLqhpDLzD/AW0uQPAeCuaQlnHxNC37mfaxDweYUGfKl5spkYpnen/1Q+9c0FQpPL3pnE/1fHGpO+QFNjWw1/H71YJvLD4+IsDgPU15UF3QhgfYQsfKmSqr8U5qRPsjqX8Gg5wboJ3P+9iNH9lzQjFszBfFC/KP8C0gyAc=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 7 Mar 2011 17:48:27 -0000
Message-ID: <20110307174827.82274.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: asrg@irtf.org
Organization: 
Cc: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: [Asrg] BCP draft next steps
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 17:47:22 -0000

It's abundantly clear that the vast majority of people agree with
the BCP's language about pay to remove, so we're done there.

I've seen a few editorial changes that shouldn't affect the sense of
the document, and I gather that a few people are going through it for
a copy edit.

Assuming they don't change the sense, I'd encourage everyone to get
their proposed changes to Chris and Matt so they can do one final
editing pass and we can declare victory.

By longstanding IETF policy, there's no draft submission between
March 14th and about March 30th due to the in-person meeting in
Prague.  So it'd be nice if we could get it done by the 14th.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From dotis@mail-abuse.org  Mon Mar  7 10:29:03 2011
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A02FD3A680D for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 10:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 64uVcZaLHIqG for <asrg@core3.amsl.com>; Mon,  7 Mar 2011 10:29:02 -0800 (PST)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id 5B0793A6821 for <asrg@irtf.org>; Mon,  7 Mar 2011 10:29:02 -0800 (PST)
Received: from us-dougo-mac.us.trendnet.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id 65091A94452 for <asrg@irtf.org>; Mon,  7 Mar 2011 18:30:37 +0000 (UTC)
Message-ID: <4D75241B.3030405@mail-abuse.org>
Date: Mon, 07 Mar 2011 10:29:47 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: asrg@irtf.org
References: <20110305001133.3455.qmail@joyce.lan>	<4D7479AC.6080607@mail-abuse.org>	<A.1PwVEM-0007e0-54@smtp-ext-layer.spamhaus.org>	<AANLkTimS3PZcjb9fFqP9myHze=1uvtK=Ag5N4sy_QXeq@mail.gmail.com> <1299495730.2943.33.camel@supergrover.internal.graemef.net>
In-Reply-To: <1299495730.2943.33.camel@supergrover.internal.graemef.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Rough consensus on pay to delist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Mar 2011 18:29:03 -0000

On 3/7/11 3:02 AM, Graeme Fowler wrote:
> Negative-connotation DNSBLs MUST NOT charge fees _or require
> donations_ for delisting or expedited delisting. Such a practise
> is controversial and likely to damage the reputation of the
> DNSBL or the DNSBL operator and may render the DNSBL less useful
> than intended.
Graeme,

"or require donations"  is overreaching.  How about  "require 
substantial donations" or "require donations as punishment".

To be clear, this is NOT about any direct payment to the listing 
service.  The term "donation" is vague and might be construed to mean 
ALL sources of request be treated alike.  Clearly, requests from "free" 
email services containing thousands of compromised accounts CAN NOT 
receive the same priority as those from cleaner email services.   
Blanket statements of this nature suggests requests originating from 
"fee" versus "free" email not be balanced against limited resources.  It 
seems prudent to advise those making a request, how various sources of 
requests might be handled.  In doing so, one might see this as then 
requiring donations to those email services with good reputations.    
Reviewing requests requires expensive wetware where the quality of the 
service also demands prompt responses to correct obvious errors.

-Doug




From fu@cs.uni-goettingen.de  Fri Mar 11 02:57:20 2011
Return-Path: <fu@cs.uni-goettingen.de>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2E203A689A for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 02:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.172
X-Spam-Level: 
X-Spam-Status: No, score=-0.172 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, SUBJ_ALL_CAPS=2.077]
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 e9yb9ky8lXHu for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 02:57:20 -0800 (PST)
Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by core3.amsl.com (Postfix) with ESMTP id 3467C3A6893 for <asrg@irtf.org>; Fri, 11 Mar 2011 02:57:20 -0800 (PST)
Received: from s5.ifi.informatik.uni-goettingen.de ([134.76.81.25] helo=[172.23.0.20]) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <fu@cs.uni-goettingen.de>) id 1Py03K-00011T-UO for asrg@irtf.org; Fri, 11 Mar 2011 11:58:39 +0100
Message-ID: <4D7A00AA.8060905@cs.uni-goettingen.de>
Date: Fri, 11 Mar 2011 11:59:54 +0100
From: Xiaoming Fu <fu@cs.uni-goettingen.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: asrg@irtf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated: Id:xfu
X-Virus-Scanned: (clean) by exiscan+sophie
Subject: [Asrg] CFP: IEEE ICNP 2011
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 10:57:20 -0000

We apologize if you receive multiple copies of this message.

===================================================================
19th IEEE International Conference on Network Protocols (ICNP 2011)
Vancouver, BC Canada, October 17-20, 2011
http://www.cs.utah.edu/~mprobst/ICNP2011/
===================================================================


IMPORTANT DATES:
Title/Abstract submission:	April 15, 2011 11:59 PM PDT
Full paper submission:	        April 22, 2011 11:59 PM PDT
Notification of acceptance:	July 28, 2011
Camera ready version:	        August 26, 2011 11:59 PM PDT
The advance (discounted) registration deadline:	TBD
Conference:	                October 17-20, 2011

CALL FOR PAPERS:
http://www.cs.utah.edu/~mprobst/ICNP2011/ICNP-2011-CFP.pdf

ICNP, the IEEE International Conference on Network Protocols, is the 
premier conference covering all aspects of network protocols, including 
design, analysis, specification, verification, implementation, and 
performance. ICNP 2011, the 19th ICNP, sponsored by IEEE and IEEE 
Computer Society Technical Committee on Distributed Processing, will be 
held in Vancouver, Canada, October 17-20, 2011. Papers with significant 
research contributions to the held of network protocols are solicited 
for submission. Papers cannot be previously published nor under review 
by another conference or journal. Papers containing plagiarized material 
will be subject to the IEEE plagiarism policy and will be rejected 
without review.

Topics of interest include, but are not limited to:

* Protocol design, implementation, testing, and analysis
* Measurement of protocol performance
* Protocols for specific functions, such as routing, congestion control, 
security, survivability, and network management
* Protocols for wireless, mobile, sensor, mesh networks, cognitive 
communication, and white spaces.
* Protocols for cloud computing, peer-to-peer systems, emerging 
distributed systems, and disruption tolerant networks.

Papers must deal specifically with protocols. Papers on general 
networking where protocols are only a secondary focus will be considered 
only if they are of exceptional quality. ICNP will select an accepted 
full paper for the best paper award.

ICNP 2011 will use a double-blind review process. The identity of 
authors and referees will not be revealed to each other. To ensure blind 
reviewing, author names and affiliations should not appear in the paper; 
bibliographic references should be made in such a way as to preserve 
author anonymity. Papers should adhere to the IEEE Computer conference 
paper format (IEEEtran.cls) and should not exceed 10 pages. The font 
size should be no smaller than 10 pt. At lease one author of an accepted 
paper is expected to register for the conference and to present the 
paper at the conference, in order for the paper to appear in the 
conference proceedings and the IEEE digital library.


ORGANIZING COMMITTEE

General Chairs:
Funda Ergun, Simon Fraser University, Canada
Thomas La Porta, Penn State University, USA

Program Chairs:
Sneha Kasera, University of Utah, USA
Baochun Li, University of Toronto, Canada

Advisory Board:
Simon Lam, University of Texas at Austin, USA
Mike T. Liu, Ohio State University, USA
Raymond Miller, University of Maryland, USA

Steering Committee:
Ken Calvert, University of Kentucky, USA (Chair)
Kevin Almeroth, UC Santa Barbara, USA
Sonia Fahmy, Purdue University, USA
Mohamed Gouda, University of Texas, USA
Teruo Higashino, Osaka University, Japan
David Lee, Ohio State University, USA
K. K. Ramakrishnan, AT&T Labs Research, USA
Krishan Sabnani, Bell Labs, USA



Besides the main conference, ICNP 2011 will include workshops, posters 
and a PhD forum as well. Further details will be given in a later date.

Best regards,
Xiaoming Fu

From johnl@iecc.com  Fri Mar 11 10:36:30 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ACFCC3A6C67 for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 10:36:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.292
X-Spam-Level: 
X-Spam-Status: No, score=-110.292 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 Tsrz-tLhWSMw for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 10:36:29 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 8BC453A6992 for <asrg@irtf.org>; Fri, 11 Mar 2011 10:36:28 -0800 (PST)
Received: (qmail 78794 invoked from network); 11 Mar 2011 18:37:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:vbr-info:user-agent:cleverness; s=133c9.4d7a6bfa.k1103; i=johnl@submit.iecc.com; bh=Pp3lJBabstK7BLi4lUo7dxP/xm9w23tv62g+Go1CHbM=; b=dunAWGZ3Ox5yWM8mRPLbp0+p4oT3RhuxSPgJpBL8iRuXqdvLzB5iP5t9x6DRaX9JFIgcn3nIU0MmXUlPMhORasyHvWodbrBR/p4l/I95QxDGLkbQV3BaxsPZ+2bDICRnEfLfUXxpASW5Ehjlozy9vi6i6TCx76qPPiHfz8mE2tg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd johnl@64.57.183.62) with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Mar 2011 18:37:24 -0000
Date: 11 Mar 2011 13:37:46 -0500
Message-ID: <alpine.BSF.2.00.1103111335190.12085@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Subject: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 18:36:31 -0000

Chris just sent in a minor update, which you can find here:

http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-08

For people who read -07, the Diff1 button at the top of the page will 
produce a redlined diff against -07 and Diff2 will produce side by side 
diffs.

The differences are minor and are intended to be editorial.  Let us know 
if we screwed something up.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From franck@avonsys.com  Fri Mar 11 15:29:35 2011
Return-Path: <franck@avonsys.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C98C3A6A33 for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 15:29:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 3jzk+y4YcwCZ for <asrg@core3.amsl.com>; Fri, 11 Mar 2011 15:29:33 -0800 (PST)
Received: from seine.avonsys.com (unknown [IPv6:2001:df0:67::129]) by core3.amsl.com (Postfix) with ESMTP id 07F823A672E for <asrg@irtf.org>; Fri, 11 Mar 2011 15:29:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by seine.avonsys.com (Postfix) with ESMTP id 460B8DFC002 for <asrg@irtf.org>; Sat, 12 Mar 2011 11:27:11 +1200 (FJT)
X-Virus-Scanned: amavisd-new at avonsys.com
Received: from seine.avonsys.com ([127.0.0.1]) by localhost (seine.avonsys.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhwcB7ALQavD for <asrg@irtf.org>; Sat, 12 Mar 2011 11:27:06 +1200 (FJT)
Received: from seine.avonsys.com (seine.avonsys.com [192.168.69.129]) by seine.avonsys.com (Postfix) with ESMTP id 2E06CDFC001 for <asrg@irtf.org>; Sat, 12 Mar 2011 11:27:06 +1200 (FJT)
Date: Sat, 12 Mar 2011 11:27:06 +1200 (FJT)
From: Franck Martin <franck@avonsys.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <22301783.1161.1299886229334.JavaMail.franck@Macintosh.local>
In-Reply-To: <alpine.BSF.2.00.1103111335190.12085@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [64.244.66.2]
X-Mailer: Zimbra 6.0.5_GA_2213.UBUNTU6 (Zimbra Desktop/2.0.1_10659_Mac)
Subject: Re: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2011 23:29:35 -0000

in 1.1 can you spell DNSWL, RHSBL and URIBL ? And ASN and DNS while you are at it. I don't like unexpanded TLAs or FLAs.

Thanks


Franck Martin 
http://www.avonsys.com/ 
http://www.facebook.com/Avonsys 
http://www.linkedin.com/company/avonsys 
twitter: FranckMartin Avonsys 

Check your domain reputation: http://gurl.im/b69d4o 
Application Monitoring: http://gurl.im/4d39Gu 


----- Original Message -----
From: "John R. Levine" <johnl@iecc.com>
To: "Anti Spam Research Group" <asrg@irtf.org>
Sent: Friday, 11 March, 2011 10:37:46 AM
Subject: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08

Chris just sent in a minor update, which you can find here:

http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-08

For people who read -07, the Diff1 button at the top of the page will 
produce a redlined diff against -07 and Diff2 will produce side by side 
diffs.

The differences are minor and are intended to be editorial.  Let us know 
if we screwed something up.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly
_______________________________________________
Asrg mailing list
Asrg@irtf.org
http://www.irtf.org/mailman/listinfo/asrg

From dotis@mail-abuse.org  Mon Mar 14 15:32:08 2011
Return-Path: <dotis@mail-abuse.org>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 928C33A6FC2 for <asrg@core3.amsl.com>; Mon, 14 Mar 2011 15:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.157
X-Spam-Level: 
X-Spam-Status: No, score=-106.157 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
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 t0bQtZf5Vq-m for <asrg@core3.amsl.com>; Mon, 14 Mar 2011 15:32:07 -0700 (PDT)
Received: from harry.mail-abuse.org (harry.mail-abuse.org [168.61.5.27]) by core3.amsl.com (Postfix) with ESMTP id C105E3A6944 for <asrg@irtf.org>; Mon, 14 Mar 2011 15:32:00 -0700 (PDT)
Received: from us-dougo-mac.us.trendnet.org (gateway1.sjc.mail-abuse.org [168.61.5.81]) by harry.mail-abuse.org (Postfix) with ESMTP id AE781A9445B for <asrg@irtf.org>; Mon, 14 Mar 2011 22:34:21 +0000 (UTC)
Message-ID: <4D7E97B3.8020600@mail-abuse.org>
Date: Mon, 14 Mar 2011 15:33:23 -0700
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: asrg@irtf.org
References: <alpine.BSF.2.00.1103111335190.12085@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1103111335190.12085@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 22:32:08 -0000

On 3/11/11 10:37 AM, John R. Levine wrote:
>  Chris just sent in a minor update, which you can find here:
>
>  http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-08
>
>  For people who read -07, the Diff1 button at the top of the page will
>  produce a redlined diff against -07 and Diff2 will produce side by
>  side diffs.
>
>  The differences are minor and are intended to be editorial. Let us
>  know if we screwed something up.

John,

In general, this is a well written document, although some of the 
guidance reduces the role played by ISPs.  In section 2.2.3, there is 
too much emphasis on the use of temporary listings, since this will 
expose trap locations and eventually make detection less effectual for 
anyone other than ISPs monitoring for abuse remediation.  A topic fully 
overlooked by the draft.  This becomes a greater concern when dealing 
with a future where bad actors are able to employ unique IP addresses 
for every message ever sent.

As indicated in a prior message, the reference for RFC3330 should have 
been updated to RFC5735.

It is also technically and conceptually incorrect to place prohibitions 
of (third-party) donations within Section 2.2.5 Conflict of Interest.  
This prohibition should be moved to a different section.  What is meant 
by donations should have been better defined, since almost any 
requirement imposed by a listing service that incurs an additional cost 
could be incorrectly included within this category.  Lists must be 
allowed to be flexible, since many have been driven out-of-business when 
dealing with bot-net related attacks.

-Doug



From johnl@iecc.com  Mon Mar 14 22:19:20 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 832C43A6978 for <asrg@core3.amsl.com>; Mon, 14 Mar 2011 22:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.726
X-Spam-Level: 
X-Spam-Status: No, score=-110.726 tagged_above=-999 required=5 tests=[AWL=0.473, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 tPhnq+tEEkP2 for <asrg@core3.amsl.com>; Mon, 14 Mar 2011 22:19:14 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 0A1C73A6980 for <asrg@irtf.org>; Mon, 14 Mar 2011 22:19:12 -0700 (PDT)
Received: (qmail 47619 invoked from network); 15 Mar 2011 05:08:48 -0000
Received: from gal.iecc.com (64.57.183.53) by mail1.iecc.com with QMQP; 15 Mar 2011 05:08:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:cc:mime-version:vbr-info; s=adb0.4d7ef723.k1103; i=johnl@user.iecc.com; bh=rsD8A7SK9DxHP0aM6oBNyXSTeWVMYYcP1A7/h/SJUiQ=; b=IvJpZQRoGN7l663ufJMUcNtHoNIRc4dmbImZmCXsFuWTC3ghaNdDtDEgOcSaDqkFXSI5Z7vHBh4ySgV7+HxbdU4I4wdlmiGLPYm1dTOeVUxARK3mF3eCockqTm6XPu9Y/AwBXR0h4jaN94nIt8dm7veg+eq6eTvMuegzrpMxLxI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 15 Mar 2011 05:20:35 -0000
Message-ID: <20110315052035.44463.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: Anti Spam Research Group <asrg@irtf.org>
Organization: 
Cc: 
Mime-Version: 1.0
Subject: [Asrg] I-D Action: draft-levine-iprangepub-02.txt
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 05:19:20 -0000

I've updated my draft describing a b-tree approach to publishing DNSxLs.

I rewrote a lot of it to make it easier to follow, and added some
stuff to handle multiple overlapping ranges with exception entries,
like rbndnsd handles.  I reran some experiments yesterday using
a snapshot of the Spamhaus Zen BL and a day's stream of connections,
about 100K of them, and got a 78% hit rate using small (512 byte) records.
I'll try it with bigger EDNS0 records and see if it makes much difference.

It's a little rough toward the end, since I had to rush it in to beat
the pre-Prague submission deadline.

R's,
John

--- snip ---

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : An efficient method to publish ranges of IP addresses in the DNS
	Author(s)       : J. Levine
	Filename        : draft-levine-iprangepub-02.txt
	Pages           : 14
	Date            : 2011-03-14

The DNS has long been used to publish lists of IPv4 address ranges in
blacklists and whitelists.  The size of the IPv6 address space makes
the entry-per-IP approach used for IPv4 lists impractical.  A new
technique for publishing IP address ranges is described.  It is
intended to permit efficient publishing and querying, and to have
good DNS cache behavior.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-levine-iprangepub-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

From UUkutt@synacor.com  Tue Mar 15 09:09:49 2011
Return-Path: <UUkutt@synacor.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D20D3A6D66 for <asrg@core3.amsl.com>; Tue, 15 Mar 2011 09:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.841
X-Spam-Level: 
X-Spam-Status: No, score=-0.841 tagged_above=-999 required=5 tests=[AWL=0.959,  BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799]
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 IdMsuObQPU2C for <asrg@core3.amsl.com>; Tue, 15 Mar 2011 09:09:48 -0700 (PDT)
Received: from mail.corp.synacor.com (mail.corp.synacor.com [38.97.88.19]) by core3.amsl.com (Postfix) with ESMTP id 5DBE13A6D0B for <asrg@irtf.org>; Tue, 15 Mar 2011 09:09:47 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Mar 2011 12:11:10 -0400
Message-ID: <043157728A92A64B935F119F3E3947A909B5849B@syncorpmail.synbuf.local>
In-Reply-To: <mailman.1.1299873604.10785.asrg@irtf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
Thread-Index: AcvgJzontvRRMBy4SuyP9xPqDHblrQDBABLw
References: <mailman.1.1299873604.10785.asrg@irtf.org>
From: "Udeme Ukutt" <UUkutt@synacor.com>
To: <asrg@irtf.org>
Subject: Re: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 16:09:49 -0000

John,

>> Chris just sent in a minor update, which you can find here:

>> http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-08

>> For people who read -07, the Diff1 button at the top of the page will
produce a redlined diff against -07 and Diff2 will produce side by=20
>> side diffs. The differences are minor and are intended to be
editorial.  Let us know if we screwed something up.

I'll review the 08 version, but is there much of a difference between
versions BCP07 & BCP08?


Udeme Ukutt
Postmaster, Synacor Inc. =20


From CLEWIS@nortel.com  Tue Mar 15 09:14:28 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61E8C3A6E04 for <asrg@core3.amsl.com>; Tue, 15 Mar 2011 09:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.734
X-Spam-Level: 
X-Spam-Status: No, score=-5.734 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 MdM9sZXsLg6y for <asrg@core3.amsl.com>; Tue, 15 Mar 2011 09:14:27 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 6516F3A6D1F for <asrg@irtf.org>; Tue, 15 Mar 2011 09:14:27 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p2FGFjS17334 for <asrg@irtf.org>; Tue, 15 Mar 2011 16:15:46 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Mar 2011 12:15:44 -0400
Received: from [47.9.28.28] (47.9.28.28) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 15 Mar 2011 12:15:44 -0400
Message-ID: <4D7F90AF.6010904@nortel.com>
Date: Tue, 15 Mar 2011 12:15:43 -0400
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: <asrg@irtf.org>
References: <mailman.1.1299873604.10785.asrg@irtf.org> <043157728A92A64B935F119F3E3947A909B5849B@syncorpmail.synbuf.local>
In-Reply-To: <043157728A92A64B935F119F3E3947A909B5849B@syncorpmail.synbuf.local>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Mar 2011 16:15:44.0691 (UTC) FILETIME=[3CB76830:01CBE32C]
Subject: Re: [Asrg] Last final final draft-irtf-asrg-bcp-blacklists-08
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 16:14:28 -0000

On 3/15/2011 12:11 PM, Udeme Ukutt wrote:
> John,
>
>>> Chris just sent in a minor update, which you can find here:
>
>>> http://tools.ietf.org/html/draft-irtf-asrg-bcp-blacklists-08
>
>>> For people who read -07, the Diff1 button at the top of the page will
> produce a redlined diff against -07 and Diff2 will produce side by
>>> side diffs. The differences are minor and are intended to be
> editorial.  Let us know if we screwed something up.
>
> I'll review the 08 version, but is there much of a difference between
> versions BCP07&  BCP08?

Very little.  Use the diff button John mentioned.

From andydawson76@gmail.com  Fri Mar 25 07:39:40 2011
Return-Path: <andydawson76@gmail.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 543FC28C0EF for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 07:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 vKrrLagCV+ZS for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 07:39:39 -0700 (PDT)
Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by core3.amsl.com (Postfix) with ESMTP id 4BF0028C0EE for <asrg@irtf.org>; Fri, 25 Mar 2011 07:39:39 -0700 (PDT)
Received: by iwn33 with SMTP id 33so1400733iwn.13 for <asrg@irtf.org>; Fri, 25 Mar 2011 07:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=fbFZNha3Dd6zAow6RxkgB0o/NAFxD81u1LwqajMH3Iw=; b=OMCHDbnDeluAiv5O85ygDkTz9zy4aXB2fl+NvnlsMi/yhP1Zpw9PPdf8T7RtFQImuk NbrkSU8gD+OChg7fdchC1wpy03JAcKlW4Rq8lNNX0SHxKp7r7eTJSYf4G7QUi4IpdZ2/ c2L+mZrOlb8Rc/fU9lDr+Wua8LqbjsJ0T16Yo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=lHvDdzaT0AUBSckiq3RbqPfriH1HUklD3EqSGWCNGT40z7lFgRN6BljN+fngK1uHGD BDZYgQ9r3saTwZkYnbthxpCoQ9UWlamKK7TSFsHSRUFUrAMi9Hx+Jr9Dhn6VF/fZX7ym H2IRoYtB5Qm+pHACIcr2dKzGHXSUqCqgDNR4g=
MIME-Version: 1.0
Received: by 10.231.202.132 with SMTP id fe4mr866275ibb.79.1301064074347; Fri, 25 Mar 2011 07:41:14 -0700 (PDT)
Received: by 10.231.197.21 with HTTP; Fri, 25 Mar 2011 07:41:14 -0700 (PDT)
Received: by 10.231.197.21 with HTTP; Fri, 25 Mar 2011 07:41:14 -0700 (PDT)
Date: Fri, 25 Mar 2011 15:41:14 +0100
Message-ID: <AANLkTinfGN=nvwME6AQb5QVUc9zVM4w66ynrhnF2dp4y@mail.gmail.com>
From: Andy Dawson <andydawson76@gmail.com>
To: asrg@irtf.org
Content-Type: multipart/alternative; boundary=00504502eb91fb45ce049f4f95b9
Subject: [Asrg] rfc honeypot-in-addressbook technique
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2011 14:41:25 -0000

--00504502eb91fb45ce049f4f95b9
Content-Type: text/plain; charset=UTF-8

Hi,

l don't know if this is an appropriate list, or if I'm about to present an
old/un-viable idea. for both of these points i apologize in advance.

As a gmail user, i am almost imune to spam/phishing mails. however,
everytime someone in my addressbook infects their computer with malware, i
receive spam, as it comes from an authorized account which i 'trust', and
are obviously sent to all contacts available to the compromised account.
Most of the mails i receive in this way come from unsavvy relatives -
contacts i dont want to simply delete.

Thinking about the process used to succesfully send these mails, i arrived
at the following what if:

What if, before the sender's email account had been compromised, they had
added "any alias" help@emailcompromised.foo to their contact list. had they
done so as soon as their account was abused, the following could
automatically be determined :

- an email accout which has been compromise
- the content and headers of a spam message
- a spam/phishing site
- the ip of a malware-infected machine.

For each of these points, action could be taken, in addition to updating
spam detection mechanisms, stopping scam-sites before they afect many users,
or even auto-blocking affected email accounts.

Before wasting effort where others have gone before, is there any milage in
this idea?

Regards,

Andy Dawson
(Web Developer)

--00504502eb91fb45ce049f4f95b9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>Hi,</p>
<p>l don&#39;t know if this is an appropriate list, or if I&#39;m about to =
present an old/un-viable idea. for both of these points i apologize in adva=
nce.</p>
<p>As a gmail user, i am almost imune to spam/phishing mails. however, ever=
ytime someone in my addressbook infects their computer with malware, i rece=
ive spam, as it comes from an authorized account which i &#39;trust&#39;, a=
nd are obviously sent to all contacts available to the compromised account.=
 Most of the mails i receive in this way come from unsavvy relatives - cont=
acts i dont want to simply delete.</p>

<p>Thinking about the process used to succesfully send these mails, i arriv=
ed at the following what if:</p>
<p>What if, before the sender&#39;s email account had been compromised, the=
y had added &quot;any alias&quot; help@emailcompromised.foo to their contac=
t list. had they done so as soon as their account was abused, the following=
 could automatically be determined :</p>

<p>- an email accout which has been compromise<br>
- the content and headers of a spam message<br>
- a spam/phishing site<br>
- the ip of a malware-infected machine.</p>
<p>For each of these points, action could be taken, in addition to updating=
 spam detection mechanisms, stopping scam-sites before they afect many user=
s, or even auto-blocking affected email accounts.</p>
<p>Before wasting effort where others have gone before, is there any milage=
 in this idea?</p>
<p>Regards,</p>
<p>Andy Dawson<br>
(Web Developer)</p>

--00504502eb91fb45ce049f4f95b9--

From CLEWIS@nortel.com  Fri Mar 25 08:35:56 2011
Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 673B63A6403 for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 08:35:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
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 I1gtbsGul2+3 for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 08:35:55 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 59CB13A63EC for <asrg@irtf.org>; Fri, 25 Mar 2011 08:35:55 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id p2PFbOL28951 for <asrg@irtf.org>; Fri, 25 Mar 2011 15:37:25 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 25 Mar 2011 11:37:24 -0400
Received: from [47.130.64.244] (47.130.64.244) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 25 Mar 2011 11:37:24 -0400
Message-ID: <4D8CB6B2.5080805@nortel.com>
Date: Fri, 25 Mar 2011 11:37:22 -0400
From: "Chris Lewis" <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <AANLkTinfGN=nvwME6AQb5QVUc9zVM4w66ynrhnF2dp4y@mail.gmail.com>
In-Reply-To: <AANLkTinfGN=nvwME6AQb5QVUc9zVM4w66ynrhnF2dp4y@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Mar 2011 15:37:24.0668 (UTC) FILETIME=[89ED3FC0:01CBEB02]
Subject: Re: [Asrg] rfc honeypot-in-addressbook technique
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2011 15:35:57 -0000

On 3/25/2011 10:41 AM, Andy Dawson wrote:

> Before wasting effort where others have gone before, is there any milage
> in this idea?

There may be some work you could do in this area, but I think you have 
to develop the idea a bit better in terms of achievable goals and 
practicality before expending too much effort on it.

Years ago we implemented something like this in our global address list, 
so that we could detect if someone in the company got infected and 
started spewing.  Many other organizations undoubtedly did the same.

But the days of those types of viruses is _long_ past (predates even 
Netsky/Bagel etc).  I think those addresses are still there, but I don't 
think they've raised an alarm in the better part of a decade.  Viruses 
just don't do that no more.

You could consider the "compromise of gmail/yahoo/aol... accounts" as a 
new type of something that behaves the same way.  It can be a technque 
for sites to find out when someone has leaked their address books 
counter to policy.  But...

Consider - not necessarily as parts of a technique, but helping you 
steer it:

- traction - how likely are people to voluntarily put such addresses in 
their address books?  Not enough to matter.  Broader solutions are needed
- noise - how are you going to distinguish infestations versus users 
deliberately blasting their entire address book?
- results - what are you going to do when you find one?
- identifiability - you need to be able to figure out _who_ got 
infected, even if you don't have tracing information or even a useable 
From:.
- survivability - how do you prevent the malicious from evading it?  The 
honeypot addresses can't be too obvious.


From johnl@iecc.com  Fri Mar 25 08:42:47 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 835AE3A6774 for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 08:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.003
X-Spam-Level: 
X-Spam-Status: No, score=-111.003 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 MsoxXtJeZrgy for <asrg@core3.amsl.com>; Fri, 25 Mar 2011 08:42:46 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 6C87B3A672F for <asrg@irtf.org>; Fri, 25 Mar 2011 08:42:46 -0700 (PDT)
Received: (qmail 68307 invoked from network); 25 Mar 2011 15:44:20 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 25 Mar 2011 15:44:20 -0000
Date: 25 Mar 2011 15:43:58 -0000
Message-ID: <20110325154358.5889.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: asrg@irtf.org
In-Reply-To: <4D8CB6B2.5080805@nortel.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [Asrg] rfc honeypot-in-addressbook technique
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2011 15:42:47 -0000

>- traction - how likely are people to voluntarily put such addresses in 
>their address books?  Not enough to matter.  Broader solutions are needed
>- noise - how are you going to distinguish infestations versus users 
>deliberately blasting their entire address book?

I'd be particularly worried about noise, since so many people seem
willing to let the social network du jour scrape their address book
and blast out invites to everyone.  That seems pretty spammy to me,
but I suspect many of the people who do it would disagree.

R's,
John

From darxus@chaosreigns.com  Thu Mar 31 19:42:17 2011
Return-Path: <darxus@chaosreigns.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 709423A6B15 for <asrg@core3.amsl.com>; Thu, 31 Mar 2011 19:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_23=0.6, NO_RELAYS=-0.001]
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 a2NS5zhYvd64 for <asrg@core3.amsl.com>; Thu, 31 Mar 2011 19:42:16 -0700 (PDT)
Received: from panic.chaosreigns.com (Darxus-1-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:1b8a::2]) by core3.amsl.com (Postfix) with ESMTP id 07A8B3A6ADE for <asrg@irtf.org>; Thu, 31 Mar 2011 19:42:15 -0700 (PDT)
Received: by panic.chaosreigns.com (Postfix, from userid 1000) id 124DB225F15; Thu, 31 Mar 2011 22:43:55 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=chaosreigns.com; s=mail; t=1301625835; bh=5Px+zAjjj1S9sORqbAjqilbt/8n2YH3qKaEt8as7grk=; h=Date:From:To:Subject:Message-ID:MIME-Version:Content-Type; b=xGZIDAR/+zZSKuSTOUwsDpii7G73xWTSmm7cbCMysnYthhewHHOOjzMP3jLf6vTN1 l7n9cj1N+xvdiW31AZIGmeiRFUYP0edjIMdoMUVfPAmhMhcBp2zDIgcblCUS94mN0b 1w8K5cLVeWBGxQp/8uhdl5p6oPFfVT45xQ6W+ctU=
Date: Thu, 31 Mar 2011 22:43:55 -0400
From: darxus@chaosreigns.com
To: asrg@irtf.org
Message-ID: <20110401024355.GA26967@chaosreigns.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [Asrg] Automated public whitelist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 02:42:17 -0000

Since 2006 I have been involved with dnswl.org, and frustrated with its
lack of automation.  It's fine for Matthias Leisi to run his project as
he sees fit.  I'm finally trying to resolve my frustration by creating a
fully automated public, free whitelist.  And including some blacklisting
data as a side-effect.

It works, it's fully automated.  The results are looking great for the two
people providing data.  Now I just need data from more people to improve
its usefulness to others.

http://www.chaosreigns.com/iprep/

There are SpamAssassin rules which pull data via DNS, in the usual
fashion.  I think, long term, I'd prefer to provide the data only via
rsync, because I think it would require less bandwidth (especially for
IPv6).  There's also a text file with the full set of aggregated data:
For each IP address, the percentage of email which has been ham, and a
count of the total emails seen.  Oversimplified a little.  The percentage
is normalized like SpamAssassin's S/O score, data is weighted by
recentness, and the count is a logarithm.

The data:
http://www.chaosreigns.com/iprep/iprep.txt

Of the 85,002 IPs I have data for, 99.966% of them are 100% ham or 100%
spam.  So I have excellent information on what the next email from them
will be.

To contribute data, create a mail folder containing only ham, and another
containing only spam, say ~/mail/ham/ and ~/mail/spam/ and, assuming
you're using maildir, run (from cron):

iprep.pl ham:dir:~/mail/ham/ spam:dir:~/mail/spam/

If using mbox, replace "dir" with "mbox".  These are SpamAssassin
mass-check style "targets" - more info on the web page.

There's also an option to pipe an email to its STDIN, queuing data for
later upload.

For both methods, the data is uploaded via rsync, which you'll need to
email me to get an account for.  I strongly prefer that you not email me
from a freemail account (gmail, yahoo, hotmail, etc.), just to try to make
it a little harder for spammers to feed me bad data.

I'm mostly interested in getting more ham.  I'd also appreciate hand
classified spam that was sent to real email addresses.  I'm not terribly
interested in extremely high volume spam traps - while I recognize they are
very useful for blacklisting, I'm happy to leave that to others.

My plan for IPv6 is to aggregate to some size net blocks.  I just set up
IPv6 on my server, so there are a couple of its IPs in the data, but
I haven't done the aggregation yet.  This is a huge case where I think
providing the data via rsync, for cidr blocks instead of individual IPs,
is a good idea.

-- 
"The most elementary and valuable statement in science, the beginning
of wisdom is: 'I do not know'." - Data, ST:TNG 2x2 Where Silence Has Lease
http://www.ChaosReigns.com

From johnl@iecc.com  Thu Mar 31 22:20:14 2011
Return-Path: <johnl@iecc.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85FE73A67F1 for <asrg@core3.amsl.com>; Thu, 31 Mar 2011 22:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.547
X-Spam-Level: 
X-Spam-Status: No, score=-110.547 tagged_above=-999 required=5 tests=[AWL=0.652, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
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 9iZ90tIaTd-h for <asrg@core3.amsl.com>; Thu, 31 Mar 2011 22:20:10 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 977C53A67E1 for <asrg@irtf.org>; Thu, 31 Mar 2011 22:20:10 -0700 (PDT)
Received: (qmail 93392 invoked from network); 1 Apr 2011 05:21:50 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 1 Apr 2011 05:21:50 -0000
Date: 1 Apr 2011 05:21:28 -0000
Message-ID: <20110401052128.45238.qmail@joyce.lan>
From: johnl@iecc.com
To: asrg@irtf.org
X-Newsgroups: iecc.lists.asrg
In-Reply-To: <20110401024355.GA26967@chaosreigns.com>
Organization: 
Subject: Re: [Asrg] Automated public whitelist
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 05:20:15 -0000

>It works, it's fully automated.  The results are looking great for the two
>people providing data.  Now I just need data from more people to improve
>its usefulness to others.

Sounds swell, but how do you plan to qualify the people sending in
data?  What's to keep a spammer from sending in a file full of his
junk marked ham?

R's,
John

PS: This is a very familiar scaling problem.
