IETF Logo Mail Archive

Re: [Jmap] Submission

"Adrien de Croy" <adrien@qbik.com> Sat, 22 April 2017 02:34 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 B6466128B90 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 19:34:11 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-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 3MKEEKTk0usb for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 19:34:09 -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 587BC127286 for <jmap@ietf.org>; Fri, 21 Apr 2017 19:34:08 -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 <0001026525@smtp.qbik.com>; Sat, 22 Apr 2017 14:34:06 +1200
From: Adrien de Croy <adrien@qbik.com>
To: Ted Lemon <mellon@fugue.com>, Chris Newman <chris.newman@oracle.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Sat, 22 Apr 2017 02:34:06 +0000
Message-Id: <em7c623b25-3c13-47c8-8e66-94d2804bfcd0@bodybag>
In-Reply-To: <2409CB86-1C1B-417B-9934-B969180C714F@fugue.com>
References: <20170419163429.8556.qmail@ary.lan> <87d1c873cf.fsf@fifthhorseman.net> <alpine.OSX.2.20.1704191353500.43511@ary.qy> <01QDEV2QM6XC00005O@mauve.mrochek.com> <BC098A22-2837-4316-822A-27232A896EF1@fugue.com> <4471fa93-2321-4a7e-87b0-fbb00927d584@gulbrandsen.priv.no> <77D58FD6-0D09-424E-8EEF-5C6738BAD6A4@oracle.com> <2409CB86-1C1B-417B-9934-B969180C714F@fugue.com>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/7.0.27943.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBD88CE545-D595-4FA7-B6CD-AB9C6BFBAEDF"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/MzvX3pz1dHg0R9RUzjdZbP24UGo>
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: Sat, 22 Apr 2017 02:34:11 -0000

yes, also curious about this.  Real world experience is always good to 
learn.


------ Original Message ------
From: "Ted Lemon" <mellon@fugue.com>
To: "Chris Newman" <chris.newman@oracle.com>
Cc: "jmap@ietf.org" <jmap@ietf.org>; "Arnt Gulbrandsen" 
<arnt@gulbrandsen.priv.no>
Sent: 22/04/2017 2:16:49 PM
Subject: Re: [Jmap] Submission

>On Apr 21, 2017, at 9:48 PM, Chris Newman <chris.newman@oracle.com> 
>wrote:
>>My product's existing JMAP-like proxy is a JSON/HTTP to 
>>submission/IMAP proxy. One of the design errors that was made (back in 
>>the 1990s) was to not support submission extensions. This is one of 
>>the largest remaining design errors in our proxy and has caused 
>>significant problems. I do not want the JMAP standard to repeat the 
>>mistake we made.
>
>Can you give an example of a failure mode that resulted from this 
>omission?  (Not doubting you, just curious what the specific problem 
>was).
>

v2.23.0 | Report a Bug | By Email