IETF Logo Mail Archive

Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)

John Levine <johnl@iecc.com> Sun, 09 November 2008 01:24 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E5D93A6807; Sat, 8 Nov 2008 17:24:14 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 058253A6807 for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 17:24:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.431
X-Spam-Level:
X-Spam-Status: No, score=-9.431 tagged_above=-999 required=5 tests=[AWL=-0.751, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4, SARE_ADULT2=1.42, 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 yFuXgc9Jm38t for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 17:24:12 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id E00593A6403 for <ietf@ietf.org>; Sat, 8 Nov 2008 17:24:11 -0800 (PST)
Received: (qmail 76808 invoked from network); 9 Nov 2008 01:24:07 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 9 Nov 2008 01:24:07 -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; s=t1108; i=johnl@user.iecc.com; bh=X+a4N6QxMXAECg1wwJRRkiF/xK5+tbnoROSNzXxRvVk=; b=PQUct/cWDSN8BwlSqCPZr1ggKGOpvI43ClNmHiJHDs7gJzPH/pmABJl7MQoD45DDZ9HYgKcFOxffmkvLBRBzlU/Y/fgUFr1KSB2N+dl5UGnu1bM4ddsBhoi3igjCd/8k
Date: Sun, 09 Nov 2008 01:24:07 -0000
Message-ID: <20081109012407.24163.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: draft-irtf-asrg-dnsbl (DNS Blacklists and Whitelists)
In-Reply-To: <A2A3269922C450550C530905@[172.16.0.38]>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> I've got two separate and unrelated incidents in the last 10 days in
> which RBL lists have decided to block some (but not all) of
> Comcast's outbound mail servers. ...

I remain baffled by this line of argument.  

If anecdotes about DNSBLs not run the way you like disqualify even
describing the technology in a standards track document, how could you
in good concience allow the publication of RFC 5321, which describes
the technology used to send several billion phishes, 419 scams, and
penis pill ads every day?  The vast majority of SMTP usage, over 95%
of all transactions, is for mail that is unwanted, fraudulent, and
probably illegal.  I dare say that considerably less than 95% (heck,
less than 1%) of DNSBL lookups produce a problematic result.

R's,
John

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

v2.23.0 | Report a Bug | By Email