Re: uncooperative DNSBLs, was several messages

Rich Kulawiec <rsk@gsp.org> Fri, 14 November 2008 16:32 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 6C43F28C161; Fri, 14 Nov 2008 08:32:22 -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 A1BC83A694D for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 17:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.719
X-Spam-Level:
X-Spam-Status: No, score=-6.719 tagged_above=-999 required=5 tests=[AWL=-0.120, 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 hLr0PXnuKGN5 for <ietf@core3.amsl.com>; Thu, 13 Nov 2008 17:43:37 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 794943A66B4 for <ietf@ietf.org>; Thu, 13 Nov 2008 17:43:37 -0800 (PST)
Received: from squonk.gsp.org (bltmd-207.114.25.46.dsl.charm.net [207.114.25.46]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id mAE1hYGM009481 for <ietf@ietf.org>; Thu, 13 Nov 2008 20:43:37 -0500 (EST)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id mAE1c8Bk027967 for <ietf@ietf.org>; Thu, 13 Nov 2008 20:38:08 -0500 (EST)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.2/8.14.2/Debian-2build1) with ESMTP id mAE1hSHU020745 for <ietf@ietf.org>; Thu, 13 Nov 2008 20:43:28 -0500
Received: (from rsk@localhost) by avatar.gsp.org (8.14.2/8.14.2/Submit) id mAE1hQoS020744 for ietf@ietf.org; Thu, 13 Nov 2008 20:43:26 -0500
Date: Thu, 13 Nov 2008 20:43:26 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: uncooperative DNSBLs, was several messages
Message-ID: <20081114014326.GA20521@gsp.org>
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> <491CB529.5010101@network-heretics.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <491CB529.5010101@network-heretics.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
X-Mailman-Approved-At: Fri, 14 Nov 2008 08:32:18 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Thu, Nov 13, 2008 at 06:15:53PM -0500, Keith Moore wrote:
> 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?

These things are all outside the scope of this document, because they
pertain to how DNSBLs should be used, not how they should be operated.

(They're also not good ideas.  In the former case, backscatter/outscatter
spam will result.  In the latter case, presenting users with a list of
hundreds of messages per day serves no useful purpose.)

---Rsk



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