Re: HTML for email

Keith Moore <> Tue, 02 March 2021 16:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E39C53A2943 for <>; Tue, 2 Mar 2021 08:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=0.001, URIBL_BLOCKED=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 FM--F4JYioTZ for <>; Tue, 2 Mar 2021 08:08:42 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9A4F43A293D for <>; Tue, 2 Mar 2021 08:08:42 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id 82C591636 for <>; Tue, 2 Mar 2021 11:08:41 -0500 (EST)
Received: from mailfrontend1 ([]) by compute5.internal (MEProxy); Tue, 02 Mar 2021 11:08:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=AnPdob9RsbUspTwPlaQUMDjDJM3veu+Od0hQo444l dA=; b=rtX1OfO6Tr6DCDXSz/iZDHq0QiwMfzy5M3/oL/YSKmDiO7HSTbmTgzRxU VPNpqejv2CJwmCEXgnnaEdijnpkyTKk84BPtdnIyEvU+dWjAzhzgIzq0rRLVi6ck Dja+pMdCFvUU7T5vqd/7QRUhPaqvqf72Z8PrTJQ1otrCdAtNmad7isaSy9i3eFgO JjbHIYbGyxJsvqA1coM74IoVygzaC1Tsil3GD4RwS07SqMDX6AEg2mO4Rf3K+MAX gUMpGfn8WcY79z4HsjchpvtV0RBJjBl6reGj0SvY6b+4O8uJo/gZwS40BKyKNB8c ixrPVB8Tj84jjKFLokQsYZFEkTIkA==
X-ME-Sender: <xms:CGM-YPTk0pVgdsze7bOUv02rsVnArYf86abdZZJlPr_lvEN0oCnkig> <xme:CGM-YKHlzN5tIwkOlEDBZpRvnhYUc7zyE0LJlpm8YDEaaJoGAyKWI8OtDragylsN4 pqOY-eJh3ym3A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddttddgkeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeejnecuhfhrohhmpefmvghithhhucfoohhorhgvuceomhhoohhrvgesnhgvthif ohhrkhdqhhgvrhgvthhitghsrdgtohhmqeenucggtffrrghtthgvrhhnpeehhfeutdehfe fgfefghfekhefguefgieduueegjeekfeelleeuieffteefueduueenucfkphepuddtkedr vddvuddrudektddrudehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepmhhoohhrvgesnhgvthifohhrkhdqhhgvrhgvthhitghsrdgtohhm
X-ME-Proxy: <xmx:CGM-YM3UyYt2vZrTIb2qCAfa-C3E4QmSSN3rg8rbSvXAhZXJy53J6g> <xmx:CGM-YIsoKxFePIS4lt3T6wz0flmcqDy0zPxw68I-CEgaXHgs1uCfhA> <xmx:CGM-YDnP4qOL_oYAeAkEm_qFFToSf9KaRMdeTl_tQ1V7JBXLlEFf-A> <xmx:CWM-YJqPVQj1ihFefP0uMwr47TlwvdrXCltUy-UUmeM4ANGlGRkcYQ>
Received: from [] ( []) by (Postfix) with ESMTPA id 2202124005D for <>; Tue, 2 Mar 2021 11:08:39 -0500 (EST)
Subject: Re: HTML for email
References: <20210227190200.06ED46F10439@ary.qy> <4064.1614454347@localhost> <s1f0vo$ejp$> <> <> <> <> <20210301232237.GI30153@localhost> <> <> <>
From: Keith Moore <>
Message-ID: <>
Date: Tue, 2 Mar 2021 11:08:38 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
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 16:08:44 -0000

On 3/2/21 9:08 AM, wrote:

> When dealing with lists in general, do the text only thinkg and you 
> end up with
> delightful stuff like messages that say, "Please see the HTML part for 
> the
> actual content of this message". Or "This message can only be read by 
> a client
> that supports HTML".

My experience echos this.  A few years ago I prototyped a system for 
allowing annotations (among other things) on email list messages.  In 
order to do that I had to parse incoming messages, convert them to HTML 
if necessary, and add links to those messages at appropriate places.   
(think "click here to annotate") What I found for multipart/alternative 
messages was that the HTML quite often didn't reflect the actual 
structure of the message so it was hard to use, and I actually 
experimented with converting the HTML to plain text before doing further 
processing.   But the text portion of the multipart/alternative messages 
were often worse, because of things like Ned cited.