Re: [Jmap] Submission

"Adrien de Croy" <adrien@qbik.com> Fri, 21 April 2017 23:30 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 7F9F7129BC8 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:30:52 -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 N2CQ58Nolj9V for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:30:50 -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 D9FF5128B93 for <jmap@ietf.org>; Fri, 21 Apr 2017 16:30:49 -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 <0001026443@smtp.qbik.com>; Sat, 22 Apr 2017 11:30:46 +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 23:30:46 +0000
Message-Id: <emba044018-431d-44cf-af93-4f12e5fecc29@bodybag>
In-Reply-To: <20170421231922.29225.qmail@ary.lan>
References: <emc8d121a7-bfae-4074-8de0-9716d42f680b@bodybag> <20170421231922.29225.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/_mEPMorI1TJ6wVuOtHFiOMwqHGY>
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 23:30:52 -0000


------ Original Message ------
From: "John Levine" <johnl@taugh.com>
To: "jmap@ietf.org" <jmap@ietf.org>
Cc: "adrien@qbik.com" <adrien@qbik.com>
Sent: 22/04/2017 11:19:22 AM
Subject: Re: [Jmap] Submission

>In article <emc8d121a7-bfae-4074-8de0-9716d42f680b@bodybag> you write:
>>
>>I did mean inter-organizational.  E.g. external messaging.
>
>In that case, I don't understand your point at all.  Existing mail
>software uses the IETF submission protocols to send billions of
>inter-organizational messages every day, frequently from rather
>limited clients like a 2G flip phone or the laser printer on my desk
>or the NAS in the server room.
>
>Given the multi-decade track record here, what makes this so daunting
>if you wrap some JSON around it?

because in that case we're not looking to improve anything.

My point is that (wrt submision) if we design a system for MUA->"the 
system" which allows for a rich experience for the MUA, then if we don't 
make it impossible for this protocol to be used to extend the system 
outside of the organisation, then we can get the rich experience for all 
mail, not just mail to your colleagues on the same server.

I'm imagining a system where the JMAP server uses JMAP to send it the 
next hop as well if required, and so on, thereby avoiding the 
limitations of SMTP.

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