Re: uncooperative DNSBLs, was several messages

Keith Moore <moore@network-heretics.com> Thu, 13 November 2008 23:15 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 906013A6A0D; Thu, 13 Nov 2008 15:15:57 -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 A680128C0F8 for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 15:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 zehXTGm3fGLz for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 15:15:56 -0800 (PST)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id 04CE13A68A6 for <ietf@ietf.org>; Thu, 13 Nov 2008 15:15:56 -0800 (PST)
Received: from lust.indecency.org (adsl-150-225-81.tys.bellsouth.net [72.150.225.81]) by m1.imap-partners.net (MOS 3.10.3-GA) with ESMTP id BEJ55324 (AUTH admin@network-heretics.com) for ietf@ietf.org; Thu, 13 Nov 2008 15:15:55 -0800 (PST)
Message-ID: <491CB529.5010101@network-heretics.com>
Date: Thu, 13 Nov 2008 18:15:53 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: uncooperative DNSBLs, was several messages
References: <Pine.LNX.4.33.0811121942450.12067-100000@egate.xpasc.com> <20081113112302.38928.qmail@simone.iecc.com> <e0c581530811130740g1db5cbfehbcdad361660bf48b@mail.gmail.com> <491C5339.8090801@dcrocker.net>
In-Reply-To: <491C5339.8090801@dcrocker.net>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Dave CROCKER wrote:

> The difficulty is that the current line of argument is that because some
> DNSBLs are operated badly, DNSBLs are bad.

I have a strong suspicion that poor design of the DNSBL protocol (and/or
its interface to SMTP and NDNs) encourages more badness than is needed.

For instance, what would happen if mail servers provided feedback to
both senders (on a per message basis in the form of NDNs) and recipients
(say, via a web page that listed messages blocked due to DNSBLs)...in
both cases describing which DNSBL blocked the message and what the
blocking criteria were?

What if recipients could disable blocking on a per-DNSBL basis?

Assuming that we're going to have reputation services, I'm looking for
ways to make them more accountable/responsible.

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