Re: [Jmap] Submission

"John Levine" <johnl@taugh.com> Fri, 21 April 2017 00:13 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 7AECB129B75 for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 17:13:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no 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 ULJDxZN4Tf80 for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 17:13:53 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 644E2120326 for <jmap@ietf.org>; Thu, 20 Apr 2017 17:13:53 -0700 (PDT)
Received: (qmail 70057 invoked from network); 21 Apr 2017 00:13:51 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2017 00:13:51 -0000
Date: Fri, 21 Apr 2017 00:13:29 -0000
Message-ID: <20170421001329.24963.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: jmap@ietf.org
Cc: adrien@qbik.com
In-Reply-To: <emf1bd45c2-f07e-45ca-a51f-46c5107b65c7@bodybag>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Ke0LWDwRmJkCos7CdhoNOlHVbW4>
Subject: Re: [Jmap] Submission
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Apr 2017 00:13:54 -0000

In article <emf1bd45c2-f07e-45ca-a51f-46c5107b65c7@bodybag> you write:
>
>My first impression is that if we considered the entire gamut of ESMTP 
>submission extensions, most would not be relevant for the client, and 
>therefore most would not need to be reflected in JMAP.

I haven't heard anyone demand that JMAP support every SMTP extension.
That would be ridiculous -- no SMTP or submission server supports them
all, either.

But what we do need is an architecture that can pass through whatever
extensions the server wants to support, without needing to revise JMAP
each time there's a new extension.

> Even things like 8BITMIME should be the default, mandatory in the
> client<->JMAP server and if the upstream SMTP system needs to redo
> the message then that's what it needs to do.

Those of us who apply DKIM signatures would be very unhappy with that
misdesign.  Sure, an MUA on a phone isn't likely to do that, but
consider my example of list management software running through JMAP,
they do it all the time.

R's,
John