Re: fun with protocols, was IETF Mail List Failure

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 21 May 2018 13:38 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFFF61270A3 for <ietf@ietfa.amsl.com>; Mon, 21 May 2018 06:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2J4nOoKBpCkq for <ietf@ietfa.amsl.com>; Mon, 21 May 2018 06:38:33 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D0DA127076 for <ietf@ietf.org>; Mon, 21 May 2018 06:38:33 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id v68-v6so3921816ywd.3 for <ietf@ietf.org>; Mon, 21 May 2018 06:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3X9UhTibDXFdUEFDbNyMXA6qkOsN5B1IpRTRGZY1RWo=; b=liBjUBc/ktDsanco+5Eg3NRiSs0IEql/EBldnjZsfvW0zAh4T4z7CE7IdgaSV1pJUh CmmFjCAjFD7cmG39YP4hxNu7nnVsJ6xvzu6kg2v3UiZyJVJ2TR6BbABvVssufkOqsFWB 6o5oqvhsJHoVT631pantrJmgzENRQLAHFstLPi2iGFLm/VW6MH+gjx2MbghgC9zM7XBN mgrl2ECzW5G7YzoQu/oKF2EGGBvfI8DbpKwGkhsO8l6m3+F8H47uBEyF9awE8JGiDML/ PzaikjQF0MUijOBiF27ZWekxJN4i0ZRbS9PpqOl585I84TmWMTEAfrnZOvOEuFTffNXA z4HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3X9UhTibDXFdUEFDbNyMXA6qkOsN5B1IpRTRGZY1RWo=; b=Ww1Bb/JJB6VHl4k55UnMQouwrsqHkfx3GKnAmBtaduGVcvFle74bTgFyb6mlsoUXza gZJGc0UUhvJSt///VrjjZ0g3L9QeqTTj2RnTXBsct5ySA4cHZdvPnO+3UZABKIqgvudP 2+AGhTZWqTaoIE7Ozss31sxvnXMvQC1qjZ/rSgv1EY0GSz7zgs2qc86O4cbwUQQQSHi2 F4TsSSEGq8WuyVV1zwEKCu8mu1ZJUpXSZMs96I0pChNz9hdhxNE2SE0E5+/LQfN20rT6 YeOOJb/F7RmL9rdAUihOmlodJi3tPFHUKDPSfgH7w9CrPoodlXwuAdYFvyHWYgcyszEs xzkw==
X-Gm-Message-State: ALKqPwd6Rc1M9csyNwDosA15Hj+YLDAF+xtNjAH+fo0mdvH+cbJpHiw+ wmSMz9+ykG4LB4bG96yoANKhZNVFsbHvMFqeH1Ni+A==
X-Google-Smtp-Source: AB8JxZqyM2hUZSa10xwbe54+6dzqAJUBlUwZ78Ru5NmwZVgMvJo/jCWz67Tr2o6ocBKZAAr0+y+fwbwfomgdcLbmY7M=
X-Received: by 2002:a0d:e8c2:: with SMTP id r185-v6mr10120471ywe.27.1526909912351; Mon, 21 May 2018 06:38:32 -0700 (PDT)
MIME-Version: 1.0
References: <8082.1526663634@localhost> <20180519160833.21AF326D3BA2@ary.qy>
In-Reply-To: <20180519160833.21AF326D3BA2@ary.qy>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 21 May 2018 08:38:19 -0500
Message-ID: <CAKKJt-dzQH9cw+=oyuAjEA5X6VnsJuwVFx_6DDoLUY3aJ3T5pg@mail.gmail.com>
Subject: Re: fun with protocols, was IETF Mail List Failure
To: John Levine <johnl@taugh.com>
Cc: IETF list <ietf@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary="000000000000ee0a62056cb76a16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_S89aLr5y2BmV1YImgpcyiAgNFM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 21 May 2018 13:38:36 -0000

So, keeping in mind that as a TSV AD, I've been sitting through the IESG's
discussions about what to do with DMARC and IETF mailing lists, but e-mail
in general and DMARC in particular is not remotely my area of expertise
(all e-mail looks like a bytestream to transport types, as does almost
everything else) ...

On Sat, May 19, 2018 at 11:09 AM John Levine <johnl@taugh.com> wrote:

> In article <8082.1526663634@localhost> you write:
> >> NNTP is actually two separate protocols. ...
>
> >We do have the common IMAP server, ...
>
> >I would probably prefer to use NNTP to access that system, as the good old
> >news reader tools still beat most mail readers (for me, who still lives in
> >emacs), but they also don't handle HTML email. (Maybe that's a good thing,
> >given efail)
>
> Funny you should mention that.  I have a little script that copies
> messages on the lists I read from the IETF IMAP server to local
> newsgroups to my local NNTP server, which I then read with my
> newsreader.  The groups are marked as moderated which means that
> "posted" articles are mailed instead, and it sends them to the
> appropriate list.  Works great.
>

I am intrigued by this thought, but find myself wondering whether there is
any remaining problem with DMARC from e-mailed responses.

I also wonder what threading looks like if an exchange is bouncing back and
forth between someone who's using e-mail and someone who's using a
newsreader and e-mailing responses (from the point of view of the e-mail
user, the newsreader user, and third-party observers).

But I don't think the IESG believes we've come up with the Final Ultimate
Solution to the DMARC Mailing List Problem (with apologies to
http://www.dmuth.org/fussp.html), so I'm still willing to wonder about
stuff like this ...

Spencer, who is 1/16th of the IESG on his best days, and is not the IESG
liaison to the tools team (according to https://trac.ietf.org/trac/iesg/wiki,
that's now EKR)


> Re HTML messages, newsreaders have evolved since you used trn twenty
> years ago.  Take a look.  Thunderbird's not bad.
>
> Setting up an IETF NNTP server with all of the lists as newsgroups
> wouldn't be very hard, give or take the usual hassles of setting
> up a new service and being sure it's someone's job to oversee it.
>
> R's,
> John
>
>