IETF Logo Mail Archive

Re: HTML for email

Benjamin Kaduk <kaduk@mit.edu> Mon, 01 March 2021 23:52 UTC

Return-Path: <kaduk@mit.edu>
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 7E68D3A254A for <ietf@ietfa.amsl.com>; Mon, 1 Mar 2021 15:52:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 5aYcR23Vp7PR for <ietf@ietfa.amsl.com>; Mon, 1 Mar 2021 15:52:52 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 CABD63A2548 for <ietf@ietf.org>; Mon, 1 Mar 2021 15:52:51 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 121Nqjs6015301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 1 Mar 2021 18:52:50 -0500
Date: Mon, 01 Mar 2021 15:52:44 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
Subject: Re: HTML for email
Message-ID: <20210301235244.GN21@kduck.mit.edu>
References: <20210227190200.06ED46F10439@ary.qy> <4064.1614454347@localhost> <s1f0vo$ejp$1@gal.iecc.com> <59240886-320d-fae3-6b98-7b83dacaf5e7@network-heretics.com> <CAMm+LwhWCsG68GOws-Zm9TDcEZ4trGBhq7Dm-_0Ci8Ri7kDK=Q@mail.gmail.com> <603D2360.1070406@btconnect.com> <20210301183401.GI21@kduck.mit.edu> <20210301232237.GI30153@localhost> <20210301233255.GM21@kduck.mit.edu> <2cd24bef-ab9a-a772-a671-15dd143d0f58@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2cd24bef-ab9a-a772-a671-15dd143d0f58@network-heretics.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BvlglIURjzSCPwd38JWifKKk03M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Mar 2021 23:52:53 -0000

On Mon, Mar 01, 2021 at 06:47:20PM -0500, Keith Moore wrote:
> On 3/1/21 6:32 PM, Benjamin Kaduk wrote:
> 
> > (FWIW, I myself perennially find myself reminding people that the official
> > IETF mail archive (web) service only displays the text/plain component, so
> > things like color and <div>s for quoting/indentation are lost.)
> 
> To me it seems like an "official" archive needs to preserve messages in 
> the formats in which they were submitted, or as close to that as possible.
> 
> I can certainly understand if the web interface to such an archive 
> doesn't support every aspect of MIME, or if it is careful about what 
> HTML (or JS, or...) it presents to the reader.   But losing color and 
> indentation seems very sub-optimal.
> 
> It's just a simple matter of (yet more) programming I suppose. And the 
> devil is in the details.

I put the "web" qualifier in because there is also an official IMAP
archive, that does preserve the message as submitted.  But it's not very
discoverable and requires quite a bit more effort to set up and use.

-Ben

v2.23.0 | Report a Bug | By Email