Re: Redundant email floods

John C Klensin <john-ietf@jck.com> Thu, 18 December 2014 16:28 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B1F1A1B73 for <ietf@ietfa.amsl.com>; Thu, 18 Dec 2014 08:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zYEx4eMFYWbi for <ietf@ietfa.amsl.com>; Thu, 18 Dec 2014 08:28:50 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EB161A9102 for <ietf@ietf.org>; Thu, 18 Dec 2014 08:27:07 -0800 (PST)
Received: from h8.int.jck.com ([198.252.137.35] helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Y1dus-0003BY-DQ; Thu, 18 Dec 2014 11:27:06 -0500
Date: Thu, 18 Dec 2014 11:27:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Redundant email floods
Message-ID: <B311981B15E022DE14BA63F3@JcK-HP8200.jck.com>
In-Reply-To: <49A9FD1B-92DF-4079-B20A-ADE9131C25F1@vpnc.org>
References: <5C9D9BE3E2E657BAD5F7C6C4@JcK-HP8200.jck.com> <49A9FD1B-92DF-4079-B20A-ADE9131C25F1@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EBXA21CXkLpk6OU9FSqS8uhWTlc
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
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>
X-List-Received-Date: Thu, 18 Dec 2014 16:28:54 -0000


--On Thursday, December 18, 2014 08:10 -0800 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> On Dec 18, 2014, at 7:48 AM, John C Klensin
> <john-ietf@jck.com> wrote:
>> Is this bothering anyone else?
> 
> Not me.
> 
>>  Can something be done about it?
> 
> Yes, but please don't. The heuristics of whom *not* to send
> the messages to should be handled by your MUA, not by the
> Secretariat.

Paul,

If you are not bothered, than that is probably the end of it for
you.  As to what should be done, if this is bothering and/or
interfering with others getting work done, the most I'd consider
asking for is capability for more selective opt-outs on lists
that are used for multiple purposes.  Not more lists and
certainly not less distribution of information.

On the other hand, Carsten's suggestion seems generally useful
to me.   We already include the abstracts in the announcement;
including a sentence or two of change summary would help, IMO.
Independent of whether it helped with the issue I identified or
not, it would save needing to retrieve a draft just to figure
out that it was updated to correct a few obvious typos.  I'd
find that a big advantage.  Don't know if others would too.

    john