Re: fun with protocols, was IETF Mail List Failure
"John Levine" <johnl@taugh.com> Sat, 19 May 2018 16:08 UTC
Return-Path: <johnl@iecc.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 6B63412D95E for <ietf@ietfa.amsl.com>; Sat, 19 May 2018 09:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level:
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=o1SL634W; dkim=pass (1536-bit key) header.d=taugh.com header.b=nIjYrLbg
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 elk4w7BfPA51 for <ietf@ietfa.amsl.com>; Sat, 19 May 2018 09:08:34 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F8B012D945 for <ietf@ietf.org>; Sat, 19 May 2018 09:08:34 -0700 (PDT)
Received: (qmail 92619 invoked from network); 19 May 2018 16:08:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=169c9.5b004c01.k1805; bh=CVUUB3mL4sJn5NobvjqcPlO13KEvhdH1B9up54niN70=; b=o1SL634W7gurftuKFTxblXJQguNM32LqYQiom/8NlpXLDjdcvcfYzWYTgfrbVmOo+Ic0gNGxAv1NqP6dSLRhyYhCR2CQIVA+bOP6hrj1/6FK7yRwNCZx0su7kglKZFKVcPlAT8DrLUsp6Fldvj8ch13UXboeexQZ628KMG+iKH0jEsqi1nSQjmbd0qlkqT7DfbhQJNNi4z/bQKMniCxR2m0630PwpPtCR0IpLpQXglPUltSD8kkEvIY1LWsd/r6V
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=169c9.5b004c01.k1805; bh=CVUUB3mL4sJn5NobvjqcPlO13KEvhdH1B9up54niN70=; b=nIjYrLbgFEgbcBbDmrHO7LzigXd0uL3boT+QSG7ssGKSJCAlUd6c6b2tJNMZfqe9qVZMpw8rOhD1eGdyelfDhf8mkXYapLMWuSIAdBN1+X48yjFPl5Klu/K9NOuFr6RDah9vsmi17KSLaV8h1S/fHagd3EsZHtuG8t512m6UCOkNflpkX7f8L8VOxHejUR5RK/MVHU9k031UKBFdNofze0BPlyoCb+phx1VKGtgbDfjc1wC04N9b0yT9mPNAZCvD
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 19 May 2018 16:08:33 -0000
Received: by ary.qy (Postfix, from userid 501) id 21AF326D3BA2; Sat, 19 May 2018 12:08:32 -0400 (EDT)
Date: Sat, 19 May 2018 12:08:32 -0400
Message-Id: <20180519160833.21AF326D3BA2@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: mcr+ietf@sandelman.ca
Subject: Re: fun with protocols, was IETF Mail List Failure
In-Reply-To: <8082.1526663634@localhost>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IISjZMhOAiJ30K2TapNem8ST9TA>
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: Sat, 19 May 2018 16:08:35 -0000
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. 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
- IETF Mail List Failure IETF Executive Director
- Re: IETF Mail List Failure Randy Bush
- Re: IETF Mail List Failure Spencer Dawkins at IETF
- Re: IETF Mail List Failure Phillip Hallam-Baker
- Re: IETF Mail List Failure Paul Hoffman
- Re: IETF Mail List Failure Michael Richardson
- Re: IETF Mail List Failure Randy Bush
- Re: IETF Mail List Failure Alexa Morris
- Re: fun with protocols, was IETF Mail List Failure John Levine
- Re: fun with protocols, was IETF Mail List Failure Spencer Dawkins at IETF