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

"Al Iverson" <aiverson@spamresource.com> Fri, 14 November 2008 17:31 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 F200E3A69E9; Fri, 14 Nov 2008 09:31:25 -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 1E8503A69E9 for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 09:31:25 -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 nQcnvk8AU3S5 for <ietf@core3.amsl.com>; Fri, 14 Nov 2008 09:31:24 -0800 (PST)
Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.186]) by core3.amsl.com (Postfix) with ESMTP id B08E13A6906 for <ietf@ietf.org>; Fri, 14 Nov 2008 09:31:23 -0800 (PST)
Received: by gv-out-0910.google.com with SMTP id e6so309887gvc.15 for <ietf@ietf.org>; Fri, 14 Nov 2008 09:31:22 -0800 (PST)
Received: by 10.86.84.5 with SMTP id h5mr748055fgb.12.1226683881629; Fri, 14 Nov 2008 09:31:21 -0800 (PST)
Received: by 10.86.31.12 with HTTP; Fri, 14 Nov 2008 09:31:21 -0800 (PST)
Message-ID: <e0c581530811140931t23f85aa9w9629a8aa2bc9f26@mail.gmail.com>
Date: Fri, 14 Nov 2008 12:31:21 -0500
From: Al Iverson <aiverson@spamresource.com>
To: ietf@ietf.org
Subject: Re: uncooperative DNSBLs, IETF misinformation (was: several messages)
In-Reply-To: <C0F2465B4F386241A58321C884AC7ECC09597929@E03MVZ2-UKDY.domain1.systemhost.net>
MIME-Version: 1.0
Content-Disposition: inline
References: <A.1L0jlO-000MSh-Ku@smtp-ext-layer.spamhaus.org> <C0F2465B4F386241A58321C884AC7ECC09597929@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 3:19 AM,  <michael.dillon@bt.com> wrote:

>> - DNSBLs break email deliverability.
>>    (DNSBL technology in fact ensures that the email sender is notified
>>    if an email is rejected, unlike Bayesian filters/content filters
>>    which place spam in the user's trash without notifying the senders)
>
> This still breaks deliverability.

How?

>> - DNSBLs "sit in the middle of an end-to-end email transaction"
>>    (see: http://www.spamhaus.org/dnsbl_function.html for
>> enlightenment)
>
> There is a diagram under Rights of a Sender vs Rights of a Receiver
> which shows that the DNSBL modifies the behavior of the Receiving
> mail server. This is what I mean by "sitting in the middle of an
> end-to-end (sender to recipient) email transaction.

At the desire of the receiving mail site's administrator.

And is not unique to DNSBLs. Any sort of spam filtering modifies the
behavior of the receiving mail server.

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