IETF Logo Mail Archive

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

"Al Iverson" <aiverson@spamresource.com> Fri, 14 November 2008 19:04 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 BD0B33A6A7E; Fri, 14 Nov 2008 11:04: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 144693A69E0 for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 11:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 GIYpj59wl+lo for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 11:04:01 -0800 (PST)
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by core3.amsl.com (Postfix) with ESMTP id 290A53A635F for <ietf@ietf.org>; Fri, 14 Nov 2008 11:04:01 -0800 (PST)
Received: by ug-out-1314.google.com with SMTP id b39so1823155ugd.15 for <ietf@ietf.org>; Fri, 14 Nov 2008 11:03:59 -0800 (PST)
Received: by 10.86.59.18 with SMTP id h18mr769124fga.77.1226689412556; Fri, 14 Nov 2008 11:03:32 -0800 (PST)
Received: by 10.86.31.12 with HTTP; Fri, 14 Nov 2008 11:03:32 -0800 (PST)
Message-ID: <e0c581530811141103y1b831a2ag396bd06823db08cf@mail.gmail.com>
Date: Fri, 14 Nov 2008 14:03:32 -0500
From: Al Iverson <aiverson@spamresource.com>
To: ietf@ietf.org
Subject: Re: uncooperative DNSBLs, IETF misinformation (was: several messages)
In-Reply-To: <C0F2465B4F386241A58321C884AC7ECC0961B8DB@E03MVZ2-UKDY.domain1.systemhost.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <e0c581530811140931t23f85aa9w9629a8aa2bc9f26@mail.gmail.com> <C0F2465B4F386241A58321C884AC7ECC0961B8DB@E03MVZ2-UKDY.domain1.systemhost.net>
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 Fri, Nov 14, 2008 at 1:59 PM,  <michael.dillon@bt.com> wrote:

Thanks, appreciate the insight.

>> > This still breaks deliverability.
>>
>> How?
>
> 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?

Regards,
Al Iverson

-- 
Al Iverson on Spam and Deliverability, see http://www.spamresource.com
News, stats, info, and commentary on blacklists: http://www.dnsbl.com
My personal website: http://www.aliverson.com   --   Chicago, IL, USA
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email