Re: HTML for email

Brian E Carpenter <> Tue, 02 March 2021 01:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 25DA03A0A1C for <>; Mon, 1 Mar 2021 17:35:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Vpqn--_GZBtU for <>; Mon, 1 Mar 2021 17:35:50 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DC57A3A0A2B for <>; Mon, 1 Mar 2021 17:35:46 -0800 (PST)
Received: by with SMTP id c19so815560pjq.3 for <>; Mon, 01 Mar 2021 17:35:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=XntCA8s+EtUhq41KCFYo1ugMOXRSmDzpHTfQYkdmmDk=; b=ZXItrJDvyBKJxgeBB6O1xhkNQPqADIF2n0IQyIzHg8TdQ3WtAcabJnWkjkkQEIRVSX 9w67zKcuUnp/w9xRSIiuTaxIeJcb3JEipd1zHEWPxs4qp1tdV4u7df2qrQV+ECbBA05Y KfIFnd4tRgmyahPG9vC2mB++L5MWLTG7Dp2w+UzhcQIRsaSZtTpd7+Y1Zm/XwkMgWpxU UPpWCusPaBcxdA83Z5tYWMKHPXYjPRDE/9eT7uUN83MS4iyQ8gRSk12oIe7BgGFQ2Apv nr+1M43GMijOoT3wuna9dl6TamCnycFzLAZNYZfB5NCpbDoab8np4khUx390GCdh6/JW +Skw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XntCA8s+EtUhq41KCFYo1ugMOXRSmDzpHTfQYkdmmDk=; b=U28whDPoIb8OFsi+0aphIcVeRKmM4UpoaskMUeuIi4dYG501H3ISKpisSZx6l6LC+R ent4eImic2oIJNZ576yHouV7Dz2HNJIvjPUXi/tMELJ+Ite9Z4OU/CaLLlqwIi8U7Vg1 wMPlqKBSLGlyCyQwpmBuUwzHH9tkI7vmyt+eyzlPxPivwfXkDYu6Tqbrq5RRy9dawX8u vTT1lfipxO34PlVzfMAs+qmCLFpsspkS6X7PLJdStJWIx3BzqFRgqtX2BM3cTPyeyDdf 35cPYS1MWkZwvIypOdpJ4f9MwOIWY14qsfs/5PnEZQeHH+rH5hFdhstV0QKhPqDIEmQ6 +DwA==
X-Gm-Message-State: AOAM5316s/dr98d6YhEYifZkuCsTRlPOkCV/iVuifOztPHpCvBo7ESxf tJkyGotYtMOClY3gK+WRwMmGu9DS4Mvwng==
X-Google-Smtp-Source: ABdhPJy32+C6r1PFiUpmWhs7jBN4PQj+0GdcptLMUqi6EXHI3meUbSHqSKwEB3+Qs7qZw2iEywJOxA==
X-Received: by 2002:a17:902:e8cb:b029:e2:9906:45a6 with SMTP id v11-20020a170902e8cbb02900e2990645a6mr1237415plg.41.1614648943734; Mon, 01 Mar 2021 17:35:43 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id mp19sm1424381pjb.2.2021. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Mar 2021 17:35:43 -0800 (PST)
Subject: Re: HTML for email
To: John Levine <>,
References: <20210302004213.764C56F50A2D@ary.qy>
From: Brian E Carpenter <>
Message-ID: <>
Date: Tue, 2 Mar 2021 14:35:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20210302004213.764C56F50A2D@ary.qy>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Mar 2021 01:35:51 -0000

On 02-Mar-21 13:42, John Levine wrote:
...> On the other hand, perhaps we could make up our mind first whether formatted e-mail is a
> part of the way the world works now, or it's a scourge to be stomped out.  Like, you know, NAT.

What we actually do with NAT, although it's undoubtedly the worst invention since white bread, is invent ways of living with it. For the purposes of IETF-style debate via email, we haven't really invented a good way of living with Content-Type: text/html, which is why some discussion threads rapidly become incomprehensible.

That is a technical problem of the kind that the IETF ought to be good at solving, if we tackle it systematically. How to maked threaded commenting work properly when some senders prefer Content-Type: text/html and others prefer Content-Type: text/plain?

(Incidentally, I have been amused to see several messages in my spam bucket recently with the subject "Telefax is the new email".)