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

"Tony Hain" <alh-ietf@tndh.net> Tue, 09 December 2008 23:02 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 7A3183A6999; Tue, 9 Dec 2008 15:02:11 -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 1233F28C141 for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 15:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.513
X-Spam-Level: *
X-Spam-Status: No, score=1.513 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_STATICB=1.372, SARE_MILLIONSOF=0.315]
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 OCUwX1Yy8tcq for <ietf@core3.amsl.com>; Tue, 9 Dec 2008 15:02:09 -0800 (PST)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id 351E23A6999 for <ietf@ietf.org>; Tue, 9 Dec 2008 15:02:09 -0800 (PST)
Received: from eagle (192.168.123.10:1939) by tndh.net with [XMail 1.17 (Win32/Ix86) ESMTP Server] id <S18041AA> for <ietf@ietf.org> from <alh-ietf@tndh.net>; Tue, 9 Dec 2008 15:01:13 -0800
From: Tony Hain <alh-ietf@tndh.net>
To: ned+ietf@mauve.mrochek.com, michael.dillon@bt.com
References: <01N2VWXW3J4M00007A@mauve.mrochek.com> <C0F2465B4F386241A58321C884AC7ECC09EB3C5F@E03MVZ2-UKDY.domain1.systemhost.net> <01N2VZWB0O8800007A@mauve.mrochek.com>
In-Reply-To: <01N2VZWB0O8800007A@mauve.mrochek.com>
Subject: RE: How I deal with (false positive) IP-address blacklists...
Date: Tue, 09 Dec 2008 15:00:50 -0800
Message-ID: <080001c95a51$fb11ac20$f1350460$@net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AclaOl/hyXjQ3kXiSzCrTIS07i0/pwAE+rWQ
Content-Language: en-us
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: alh-ietf@tndh.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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

ned+ietf@mauve.mrochek.com wrote:
> ...
> Maybe it's just me, but I'll take the evidence presented by  someone
> who has access to the operational statistics for a mail system
> that services 10s of millions of end users and handles thousands of  
> outsourced email setups over someone like myself who runs
> a tiny little setup any day.

While large scale is important, small scale setups must not be sacrificed
along the way. We must not create a system where a small cartel of players
hold the keys to 'interoperability' at the deployment level. Current
filtering practice creates way too many false positives already because the
large organizations can't afford to bother with identifying the source. My
lowly server just handles my wife, myself, and my daughter's business, and
way too often I hear complaints about bounces because largeispmailer.com is
refusing to accept mail from an insignificant non-member-of-the-club server.


By no means do I claim enough knowledge about mail services to offer
anything more than the viewpoint of an amateur trying to run a small server.
I would agree with the comments along the way that the current
state-of-the-art is way too hard, and I am sure my configuration is not
correct or complete because I get mail from the process every few hours
stating -- error: gpg required but not found!   yet every time I try to
resolve that I can't figure out what is wrong or if a symbolic link is
missing. Even with help from example configs at jck & psg, it took a fair
amount of time and experimentation to cut over from the previous mta that
was being crushed by the spam load. Life is better now, and as of a few
hours ago mail from the ietf list is flowing over IPv6, but I know the MX
record still needs work because the IPv6 path is being locally redirected.

Tony


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