Re: [89attendees] spam on old lists - was Fw: new important message

ietf@johnlevine.com Fri, 15 April 2016 18:53 UTC

Return-Path: <ietf@johnlevine.com>
X-Original-To: 89attendees@ietfa.amsl.com
Delivered-To: 89attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4496412DDC4 for <89attendees@ietfa.amsl.com>; Fri, 15 Apr 2016 11:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwBSxjd_06fC for <89attendees@ietfa.amsl.com>; Fri, 15 Apr 2016 11:53:02 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0455512DD57 for <89attendees@ietf.org>; Fri, 15 Apr 2016 11:53:01 -0700 (PDT)
Received: (qmail 10058 invoked from network); 15 Apr 2016 18:53:00 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 15 Apr 2016 18:53:00 -0000
Date: Fri, 15 Apr 2016 18:52:38 -0000
Message-ID: <20160415185238.6233.qmail@ary.lan>
From: ietf@johnlevine.com
To: 89attendees@ietf.org
In-Reply-To: <alpine.LRH.2.01.1604151118350.13335@egate.xpasc.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/89attendees/LOx6vaqg1I6hGTEzeEWK_2iyqoU>
Cc: ietf@ietf.org
Subject: Re: [89attendees] spam on old lists - was Fw: new important message
X-BeenThere: 89attendees@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Mailing list of IETF 89 attendees that have opted in to the list." <89attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/89attendees>, <mailto:89attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/89attendees/>
List-Post: <mailto:89attendees@ietf.org>
List-Help: <mailto:89attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/89attendees>, <mailto:89attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Apr 2016 18:53:04 -0000

>Having fought with DNSBL providers, I think the BLACK part of the name is
>appropriate ... as in BLACK HOLE re. any hope of rational resolution.

There are hundreds of DNSBL providers, most of whom are incompentent,
but nobody uses their lists so it doesn't matter.  There are a few
that are competent and have very low error rates.  They, not
surprisingly, are the ones everyone uses.  When I say everyone, I mean
it -- every mail system of any size uses them as part of their spam
filtering because they have to. They're awful but less awful than the
alternatives.

In this particular case, filtering by From: address on mailing lists
still works well enough, particularly here where the participants tend
to be technically sophisticated and so are somewhat less likely to get
their accounts p3ned than average users.  So I agree that we might as
well turn off useless old meeting lists, but I don't see any need to
twiddle things beyond that.

R's,
John

PS:

>>    We _could_ in principle work up protocols to replace zero-maintenance
>> blacklists as "the solution" to spam. I tried, the last time the topic
>> was hot; but totally failed to get anything that wasn't trivial to bypass.

I don't think that's a failure of imagination, it's in the nature of
systems with malicious participants.  It's not unrelated to the
observation that you wouldn't want to join a club that would have you
as a member.