Re: [Jmap] Submission

"Adrien de Croy" <adrien@qbik.com> Fri, 21 April 2017 06:25 UTC

Return-Path: <adrien@qbik.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 C710A12941C for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 23:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 AOlGi70huNNA for <jmap@ietfa.amsl.com>; Thu, 20 Apr 2017 23:25:51 -0700 (PDT)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B0E12869B for <jmap@ietf.org>; Thu, 20 Apr 2017 23:25:50 -0700 (PDT)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.5 (Build 5926)) with SMTP id <0001025725@smtp.qbik.com>; Fri, 21 Apr 2017 18:25:48 +1200
From: Adrien de Croy <adrien@qbik.com>
To: John Levine <johnl@taugh.com>, "jmap@ietf.org" <jmap@ietf.org>
Date: Fri, 21 Apr 2017 06:25:48 +0000
Message-Id: <em470cf3b9-5af0-4eb9-a7d0-1d6273df597a@bodybag>
In-Reply-To: <20170421001329.24963.qmail@ary.lan>
References: <emf1bd45c2-f07e-45ca-a51f-46c5107b65c7@bodybag> <20170421001329.24963.qmail@ary.lan>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/9ddH0RI8RxYKAs_iXUcf_FGhOjI>
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 06:25:54 -0000


------ Original Message ------
From: "John Levine" <johnl@taugh.com>
To: "jmap@ietf.org" <jmap@ietf.org>
Cc: "adrien@qbik.com" <adrien@qbik.com>
Sent: 21/04/2017 12:13:29 PM
Subject: Re: [Jmap] Submission

>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.
which server?  The upstream SMTP one?

I think trying to pass through SMTP extensions when there may not even 
be an upstream SMTP server is going to be problematic let alone ugly.

Which extensions do we think are even in scope for this?


>
>
>>  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.
So in 100 years we will still be using the 7-bit limbo pole everyone has 
to go under

We need to move past the 1960s.

When will we abandon 7-bit?

Sounds like DKIM didn't think through the need to transform mail. What 
does a server do right now when an SMTP server needs to send 8bit mail 
to a server that doesn't advertise 8BITMIME?  Bounce it? There should be 
a lossless transform that DKIM could cope with.

I suspect many MTAs will happily accept binary mail, but just don't 
advertise 8BITMIME because all the other requirements were far too 
onerous.

Adrien

>
>
>R's,
>John
>
>_______________________________________________
>Jmap mailing list
>Jmap@ietf.org
>https://www.ietf.org/mailman/listinfo/jmap