IETF Logo Mail Archive

Re: How I deal with (false positive) IP-address blacklists...

Dave CROCKER <dhc2@dcrocker.net> Tue, 09 December 2008 22:12 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 0E27628C187; Tue, 9 Dec 2008 14:12:56 -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 608F928C187 for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 14:12:54 -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=[AWL=0.000, 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 3i2aUytUQi-6 for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 14:12:53 -0800 (PST)
Received: from sbh17.songbird.com (mail.mipassoc.org [IPv6:2001:470:1:76:0:ffff:4834:7146]) by core3.amsl.com (Postfix) with ESMTP id D56E23A688F for <ietf@ietf.org>; Tue, 9 Dec 2008 14:12:52 -0800 (PST)
Received: from [192.168.0.6] (adsl-67-124-149-191.dsl.pltn13.pacbell.net [67.124.149.191]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id mB9MCf3g030004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Dec 2008 14:12:42 -0800
Message-ID: <493EED58.6080403@dcrocker.net>
Date: Tue, 09 Dec 2008 14:12:40 -0800
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 2.0.0.18 (Windows/20081105)
MIME-Version: 1.0
To: michael.dillon@bt.com
Subject: Re: How I deal with (false positive) IP-address blacklists...
References: <C0F2465B4F386241A58321C884AC7ECC09EB3C5F@E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <C0F2465B4F386241A58321C884AC7ECC09EB3C5F@E03MVZ2-UKDY.domain1.systemhost.net>
X-Virus-Scanned: ClamAV 0.92/8738/Tue Dec 9 11:31:40 2008 on sbh17.songbird.com
X-Virus-Status: Clean
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 09 Dec 2008 14:12:42 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


michael.dillon@bt.com wrote:
>       Why should
> it not be as simple to set up an IETF standard email
> system for a small organization as it was 10 years ago?


If you go back far enough, New York City was small and friendly.  Not much 
required to build a satisfactory home there.

Things have changed.  No matter the size of the home, things have changed.

Environmental pressures are ignored only at one's serious risk.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email