Re: [Jmap] the large email (attachment) problem

John R Levine <johnl@taugh.com> Mon, 02 August 2021 21:48 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 130923A1E4B for <jmap@ietfa.amsl.com>; Mon, 2 Aug 2021 14:48:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=yhiRR747; dkim=pass (2048-bit key) header.d=taugh.com header.b=hMvKINyt
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 LpCfY7djjLel for <jmap@ietfa.amsl.com>; Mon, 2 Aug 2021 14:48:28 -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 401DA3A1E0D for <jmap@ietf.org>; Mon, 2 Aug 2021 14:48:27 -0700 (PDT)
Received: (qmail 37712 invoked from network); 2 Aug 2021 21:48:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=934e.61086829.k2108; bh=O66kqayO8FL6xlm3FQhu49cpSquSqVWO3wpTZ5Kl7e0=; b=yhiRR747klRSy6m1zpmsAIAUBJbNSbYma7uopIYb52c3Wl0DUjnVbOCSgTJ5DBczktKQKQr1f4tnSxAQQlHFsOphJWH9korFzETQmSV7HcIcwVaPd7hSK2pUAh+ioc9gPpUaI00e2nMicsq9+NdUlFyc+PT+Tv9h1E4yoHjgS7hi7lf/rHn9rd3a496UV+XXHApwVUineI00zT/4F0Qws1KLPrm81IUCgW7XlWwOSo8BZ1ISf+WvTTJFX5niCPrQEFcwshZTMCtOarAiNZoA4fOgHgbogqgh6St26UOP1s9rSm2DFsnwF45OvBkogViC5criSlFGLaegFej3K3Af3g==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=934e.61086829.k2108; bh=O66kqayO8FL6xlm3FQhu49cpSquSqVWO3wpTZ5Kl7e0=; b=hMvKINytXQ6RoBze8vmBdouwAPL0eHrnK0MOLTmD3Zv1D9aLCUV8I1RPP6H0w3AWClnuagufuNmG4KOUoMjrHk2AvcZrJXT3T6wzK1wGFynv8Jyx7AH75r2Rvt4iahs/KXHDByqOLANmz/KY7MyBIEYbOus8C0W4t8ZioEyh6PizewFk0x+JinY1ne8vGr2qdM2rncpLD1xnlTQaEqDqn3awJwjAED2hSCXoBLU74M4z45UJZi3c+sXVf0uQqZ4q/qEQNl9UwL18tzqV2iyemh5pxbxmxDjRHRQOaIOTlUGNHovjg1FPhg3RV8Dxr220uYgh/6FxCVsAQNxffmJ7HA==
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 ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 02 Aug 2021 21:48:24 -0000
Received: by ary.qy (Postfix, from userid 501) id 48A5C257B626; Mon, 2 Aug 2021 17:48:23 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id E0EC7257B608; Mon, 2 Aug 2021 17:48:23 -0400 (EDT)
Date: 2 Aug 2021 17:48:23 -0400
Message-ID: <761d547b-e184-f039-fd19-7555556fc88@taugh.com>
From: "John R Levine" <johnl@taugh.com>
To: "Neil Jenkins" <neilj@fastmailteam.com>, "IETF JMAP Mailing List" <jmap@ietf.org>
X-X-Sender: johnl@ary.qy
In-Reply-To: <123cd685-5a76-4654-bcce-68c1cf5364bc@dogfood.fastmail.com>
References: <20210802195833.4DAC9257A28E@ary.qy> <123cd685-5a76-4654-bcce-68c1cf5364bc@dogfood.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/qwzgBKFwNtyUNa8NmpMnaH_5pYQ>
Subject: Re: [Jmap] the large email (attachment) problem
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 21:48:41 -0000

>> I suppose, but if the HTML fits in the message, what's the point of the external version other
>> than to debug your MUA?
>
> Sorry, I wasn't clear. The HTML version is a (prettier version) of something like this:
>
> <h2>Attachments</h2>
> <a href="https://example.com/download/large/file">whatididonmyholiday.mp4</a>
>
> So if your client doesn't support the external body, it will instead show the sender-generated links to download the attachment (which is exactly what Google, Microsoft etc. currently do). But if it does support the external body, it can show it like any real attachment and offer the advantages we've discussed (immutability, privacy-preserving caching on delivery etc.). This provides a seamless upgrade path to offer the feature.

Ah.  Of course.


Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly