IETF Logo Mail Archive

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

John Levine <johnl@iecc.com> Sat, 08 November 2008 22:41 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 C07113A67F3; Sat, 8 Nov 2008 14:41:34 -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 C53C03A6844 for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 14:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.156
X-Spam-Level:
X-Spam-Status: No, score=-10.156 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, 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 n9KRlPyrvxri for <ietf@core3.amsl.com>; Sat, 8 Nov 2008 14:41:31 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 9B5223A67F3 for <ietf@ietf.org>; Sat, 8 Nov 2008 14:41:31 -0800 (PST)
Received: (qmail 76532 invoked from network); 8 Nov 2008 22:41:28 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 8 Nov 2008 22:41:28 -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=PGduEvGQJzsbk5ZVDosfDbLfDueQYm65KlYhy4t1GYM=; b=iBNtzWKWLYuKIYFuiYGioQXvOTziadNJ7VH9JtzCjSWyJzJNcnB+h69ab5Yayv+TTGrPCh93fWTx81SDuZZW+ONORmv0vZMx8wsmaW6cCkO34Rwd0Yfzt7vew7QBDkit
Date: Sat, 08 Nov 2008 22:41:27 -0000
Message-ID: <20081108224127.84191.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: <7C487FD22A014981BC0C127D38E548F7@DGBP7M81>
Organization:
X-Headerized: yes
Mime-Version: 1.0
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

>Several years ago, my employer's e-mail spam filter blocked the Unicode 
>mailing list as a "suspect site."  Earlier this year, GoDaddy (registrar 
>of my domain name) did the same, and it took months to figure out what 
>was going on.

What connection does any of this have to do with DNSBLs?  There are lots
of less than fabulous ways to manage a mail system poorly, most of which
have nothing to do with looking up IP addresses in a DNS list.

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email