IETF Logo Mail Archive

RE: uncooperative DNSBLs, IETF misinformation (was: several messages)

<michael.dillon@bt.com> Fri, 14 November 2008 19:12 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 D5DE83A69C9; Fri, 14 Nov 2008 11:12:03 -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 794783A69C9 for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 11:12:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.542
X-Spam-Level:
X-Spam-Status: No, score=-3.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 oN2BRRGcxmwx for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 11:12:02 -0800 (PST)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id 87D393A68D5 for <ietf@ietf.org>; Fri, 14 Nov 2008 11:12:02 -0800 (PST)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.61]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Nov 2008 19:12:01 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: uncooperative DNSBLs, IETF misinformation (was: several messages)
Date: Fri, 14 Nov 2008 19:11:55 -0000
Message-ID: <C0F2465B4F386241A58321C884AC7ECC0961B8E7@E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <e0c581530811141103y1b831a2ag396bd06823db08cf@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
thread-topic: uncooperative DNSBLs, IETF misinformation (was: several messages)
Thread-Index: AclGi8+q/qxWLLo/RPeU77pTdWs1DQAANGoA
From: michael.dillon@bt.com
To: ietf@ietf.org
X-OriginalArrivalTime: 14 Nov 2008 19:12:01.0777 (UTC) FILETIME=[DF9D6610:01C9468C]
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

> > A user writes an email and sends it to another user. The other user 
> > does not receive the email. This means that deliverability 
> is broken. 
> > The DNSBL is an agent in preventing that delivery.
> 
> Is this unique to DNSBLs? If not, then why does it merit 
> deeper consideration in the context of DNSBLs?

Because the draft
<http://www.ietf.org/internet-drafts/draft-irtf-asrg-dnsbl-07.txt>
that started this discussion has set the context of DNSBLs.
You are right that it also merits deeper consideration in other
contexts.

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

v2.23.0 | Report a Bug | By Email