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

John Levine <johnl@taugh.com> Sat, 31 July 2021 17:00 UTC

Return-Path: <johnl@iecc.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 512AA3A0E51 for <jmap@ietfa.amsl.com>; Sat, 31 Jul 2021 10:00:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=uR/HfrE5; dkim=pass (2048-bit key) header.d=taugh.com header.b=EwaFH9TS
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 AfyfeDV-kFYk for <jmap@ietfa.amsl.com>; Sat, 31 Jul 2021 10:00:52 -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 F1A0E3A0E4D for <jmap@ietf.org>; Sat, 31 Jul 2021 10:00:51 -0700 (PDT)
Received: (qmail 82079 invoked from network); 31 Jul 2021 17:00:49 -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:cleverness; s=1409c.610581c1.k2107; bh=exicJksBAVxsa+f0fKOGeMpiyAu3wn2k5HL8eU1Wr3w=; b=uR/HfrE5cSx5eypBLXdZzl3OkYQd9I9YdvXxdGM0Eu+rZdgQf0iO38rO3eisy3wqijLhaXk7M1geZhT1JZPhWZJRlwugtJd/Q2/IvfIPaCVuqRXsXKC1jOpZ7xaDPsRiSYhYFgUtE/OpGyx7De17YiESiF6uWh6qzYuJF44sHwTeeP9pgegKpbWaXi5AtM5/ZhIDdHoKdS4kammOehqxqmvV8mnbtbOZH/bCpVl2eDJHC9y+V3QMUBP5wmGFCS3rFzQ1I11kZdjg5JGQ1AvKC7ATZyphRPS4byjHjQIb9Jwf2AM+efvoB++vodDXxG4cqvrlwNuLYuYk6rz5nRFLyw==
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:cleverness; s=1409c.610581c1.k2107; bh=exicJksBAVxsa+f0fKOGeMpiyAu3wn2k5HL8eU1Wr3w=; b=EwaFH9TSJFz4cvnfWvjFXwG34K4XL8xS+M+xu5YWsxSNPZWhv9tzMNkwVOPXGvvMn1b2Mt2BGUX0SOxIuoxm4U5AJ36iPZqxVCDVw106yUU+CTNqepthmkTFGfkSrWG5oam6azIKjMt718ANrESbHcHGdP4RKvH2DvmRTudLvyMB6eQScM94agi3MobR2LsLLUIvJIfMfWou39TizXyn6tXWp26dA8W/ijq7WKao6xpUPUQGkx+blv3vRW+ahQTYUsf24b1KouZSjFHkxrwBiFDhcpWYS5eMevV9t127U9HlkxtYh16q4EQrObaKqphmSZE3RHtu9j0dAP5nZo7zxA==
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; 31 Jul 2021 17:00:48 -0000
Received: by ary.qy (Postfix, from userid 501) id DE0772563EB0; Sat, 31 Jul 2021 13:00:47 -0400 (EDT)
Date: 31 Jul 2021 13:00:47 -0400
Message-Id: <20210731170047.DE0772563EB0@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: jmap@ietf.org
Cc: jamey@minilop.net
In-Reply-To: <CAJi=jadiwMGvLXG7nK93Ht=TzN-QdmAqyE4Nf7UnGG47f3zSwg@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/fYQNo-xiluI22ctA80mPWtOHMnU>
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: Sat, 31 Jul 2021 17:00:57 -0000

It appears that Jamey Sharp  <jamey@minilop.net> said:
>In the text (plain or HTML) parts of the email, large attachments are 
>still referenced by a URL provided by the sender, as has become common 
>practice today. However, we add new attachment-like parts which serve 
>several purposes: to indicate that a given URL should be treated like an 
>attachment at the recipient, to provide metadata hints, and to provide 
>alternate URLs for retrieving the attachment. ...

Take a look at message/external-body in RFC 2017, 2046 and 2912.  It already has size,
URL, expiration, and content-features parameters.

We could add a few new attributes to external-body like an optional encryption key.

R's,
John