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

<michael.dillon@bt.com> Tue, 09 December 2008 22:26 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 090E43A6910; Tue, 9 Dec 2008 14:26:28 -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 CD6A23A6910 for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 14:26:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.542
X-Spam-Level:
X-Spam-Status: No, score=-3.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 VdPWDmdz2vTW for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 14:26:26 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id C945A3A68BF for <ietf@ietf.org>; Tue, 9 Dec 2008 14:26:25 -0800 (PST)
Received: from E03MVZ2-UKDY.domain1.systemhost.net ([193.113.30.64]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Dec 2008 22:26:19 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: How I deal with (false positive) IP-address blacklists...
Date: Tue, 09 Dec 2008 22:26:26 -0000
Message-ID: <C0F2465B4F386241A58321C884AC7ECC09EB3CDF@E03MVZ2-UKDY.domain1.systemhost.net>
In-Reply-To: <493EED58.6080403@dcrocker.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: How I deal with (false positive) IP-address blacklists...
Thread-Index: AclaS0O4bfTkRk9MQgCObiWyqmNCywAAX2YQ
From: michael.dillon@bt.com
To: ietf@ietf.org
X-OriginalArrivalTime: 09 Dec 2008 22:26:19.0703 (UTC) FILETIME=[289B7C70:01C95A4D]
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

> >       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.

I agree with all of your points. But I also believe that it should
be possible to encapsulate the neccessary security features into
an Internet email architecture so that people can set up an email
server for a small organization in an afternoon, and it will pretty
much run on its own. The fact that the current Internet email
architecture
does not allow for this, and therefore disenfranchises small 
organizations from running their own email services, does not 
dissuade me from believing that we could fix the problem if we
put some effort into doing so.

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