IETF Logo Mail Archive

Re: [Jmap] Submission

"Adrien de Croy" <adrien@qbik.com> Fri, 21 April 2017 23:09 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 3294F128896 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:09:30 -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 iHXxU3F8T_Qe for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 16:09:28 -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 E6B5612785F for <jmap@ietf.org>; Fri, 21 Apr 2017 16:09:27 -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 <0001026433@smtp.qbik.com>; Sat, 22 Apr 2017 11:09:24 +1200
From: Adrien de Croy <adrien@qbik.com>
To: John R Levine <johnl@taugh.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
Date: Fri, 21 Apr 2017 23:09:25 +0000
Message-Id: <emc8d121a7-bfae-4074-8de0-9716d42f680b@bodybag>
In-Reply-To: <alpine.OSX.2.20.1704211846410.56587@ary.qy>
References: <em470cf3b9-5af0-4eb9-a7d0-1d6273df597a@bodybag> <20170421153246.28229.qmail@ary.lan> <emc7258396-7955-4388-9259-0425e1b49134@bodybag> <alpine.OSX.2.20.1704211846410.56587@ary.qy>
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/_F0_oxkZ4Em3VM6X6chDYAUMsjs>
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:09:30 -0000

I did mean inter-organizational.  E.g. external messaging.


------ Original Message ------
From: "John R Levine" <johnl@taugh.com>
To: "Adrien de Croy" <adrien@qbik.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>
Sent: 22/04/2017 10:54:40 AM
Subject: Re: [Jmap] Submission

>>Also if we don't prevent it, inter-organizational mail could use this 
>>as well.  The key is to not make that impossible or worthless.
>
>Hmmn.  I have written submission servers.  They are not particularly 
>complicated or difficult, particularly if they don't have to handle the 
>crypto goop in STARTTLS and AUTH, both of which JMAP does other ways.
>
>Assuming you mean intra-organizational mail, it would be a big help if 
>you could explain concretely what about the standard submission model 
>would make such mail impossible or worthless.  Please be specific.
>
>R's,
>John
>
>_______________________________________________
>Jmap mailing list
>Jmap@ietf.org
>https://www.ietf.org/mailman/listinfo/jmap

v2.23.0 | Report a Bug | By Email