Re: [Jmap] I-D Action: draft-ietf-jmap-mdn-01.txt

Raphael OUAZANA <raphael.ouazana@linagora.com> Fri, 22 March 2019 17:21 UTC

Return-Path: <raphael.ouazana@linagora.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 902A8131339 for <jmap@ietfa.amsl.com>; Fri, 22 Mar 2019 10:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smtpcorp.com header.b=KskVCE4U; dkim=pass (2048-bit key) header.d=linagora.com header.b=b8ekY98o
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 JO9qMaj4QftE for <jmap@ietfa.amsl.com>; Fri, 22 Mar 2019 10:21:20 -0700 (PDT)
Received: from e2i64.smtp2go.com (e2i64.smtp2go.com [103.2.140.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CFB013133B for <jmap@ietf.org>; Fri, 22 Mar 2019 10:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:Message-ID:Subject:To: From:Date:Reply-To:Sender:List-Unsubscribe; bh=7KouriENxzSb5s+Bbyq92uAOKhGjdpth1gs1xEPkRx8=; b=KskVCE4UGHvIFGghQylNeyB8MD c4gmEPCtXNz3FjegcdQAPmQAQjuYzwzjJcz6iHhzjrorGkQnDMevBPongMPPd6qzcxHmsE4FuFDDG 6aA5qcGBYd7emqigQxtKxc8DdmU3x0V8HMmIAVb7hwj2gRkv0Gj/S+GdmFjIYsH5utAoZmwUZq/2r 517kPaQs2lkvrmMgdZhUyX5mhbnDpEN34cbEcw6r2FaU0vvB1WB/lplBi8x1Lv2YGrySwDrIgKE1V DfxYCmY7BERdTMzQU68UQoTkRITIrizxDkCbCNnHCrbv15pso+GSKWgS0V/LpE88DabgoH5oO1KCD jPU4yPzw==;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linagora.com; i=@linagora.com; q=dns/txt; s=s266739; t=1553275280; h=from : subject : to : message-id : date; bh=7KouriENxzSb5s+Bbyq92uAOKhGjdpth1gs1xEPkRx8=; b=b8ekY98oVsdE5ohbMQTqXHxarOc6DKWfBSE9SlxW+ZagMj6lKsWCSVn4N124Bl3zV7FzV3 B5VRzCOugtkhk/tOnAUbz/0NqChVX6imK3j+uzgS5U3gkwYQxkGerLy/vg8O2nA4cZ0XnVIQ N/FQUlNrUqy0EBAAhTKiJ9jv9+mnvHLh/qqbsAyk8yiAgBajl5J3uswNmkiVHzsDOUC0EiXU tZiRUP4+oymPjn1o1de0p9fCz176KGKY/lQ6JfdZtc10pQnbkO7oZQs664teiIcT5/NiN5+m LBbIb8hbAZ/ZkC/w1xhxx03wB/VcQ18q4UI9ltF8ME1Knlx3tI6ILngg==
Received: from [10.45.33.53] (helo=SmtpCorp) by smtpcorp.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from <raphael.ouazana@linagora.com>) id 1h7Nqz-cp4TGJ-CC; Fri, 22 Mar 2019 17:21:13 +0000
Received: from [10.54.36.8] (helo=smtp.linagora.com) by smtpcorp.com with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from <raphael.ouazana@linagora.com>) id 1h7Nqx-rlZFa9-MG; Fri, 22 Mar 2019 17:21:11 +0000
Received: from extranet.linagora.com (obm3-ui.linagora.dc2 [172.24.128.227]) by smtp.linagora.com (Postfix) with ESMTP id 9CA983F161; Fri, 22 Mar 2019 18:21:09 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Fri, 22 Mar 2019 18:21:09 +0100
X-LINAGORA-Copy-Delivery-Done: 1
From: Raphael OUAZANA <raphael.ouazana@linagora.com>
To: Neil Jenkins <neilj@fastmailteam.com>
Cc: IETF JMAP Mailing List <jmap@ietf.org>
In-Reply-To: <879444dd-28a7-4661-a057-e2f4d142eda3@beta.fastmail.com>
References: <155197652116.24727.17736633253141543762@ietfa.amsl.com> <879444dd-28a7-4661-a057-e2f4d142eda3@beta.fastmail.com>
Message-ID: <1ddd3a8f0763f028bae89ace0e33081e@linagora.com>
X-Sender: raphael.ouazana@linagora.com
User-Agent: Roundcube Webmail/1.1.4
X-Smtpcorp-Track: 1h7Nqxr_ZFa9uG._aXFigsqD
Feedback-ID: 266739m:266739aja3LFS:266739sLrdZh-F7H
X-Report-Abuse: Please forward a copy of this message, including all headers, to <abuse-report@smtp2go.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/Xj7GlTvuz-8a8ZWFAhjNhc-C358>
Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-mdn-01.txt
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Mar 2019 17:21:24 -0000

Hi Neil,

Thanks for your comments.

Le 2019-03-21 16:05, Neil Jenkins a écrit :
> A few comments on the new draft:
> 
>> The client SHOULD NOT issue a sendMDN request if the message has
>> the
>> "$MDNSent" keyword set.  In this case, the server MUST reject the
>> submission with a standard "forbiddenToSend" SetError.
> 
> I don't think this should be a forbiddenToSend error; that implies the
> user does not have permission to send. An alreadyExists error might be
> appropriate, or some kind of new "precondition-failed" type error.

I wrote it in the sense of forbidden by the RFC:
        [...]In any case, in the presence of the $MDNSent keyword,
        the client MUST ignore all other flags or keywords for the
        purpose of generating an MDN and MUST NOT send the MDN.

AlreadyExists seems misleading as the user could just not want to send 
the MDN, and in this case it will never exist. Maybe AlreadyProcessed or 
something like that then?

>> o  *created*: "String[EmailSubmission]" A map of creation id
>> (client-
>> specified) to an email sent from the referenced properties.
> 
> The type says this is a map to EmailSubmission objects, but the
> description says it is a map to an Email. Which is it?

I wrote a map to "an email sent [...]". Maybe my English is not good 
enough, but for me an email sent means an EmailSubmission. How could I 
clarify?

>> EMAILSUBMISSION/PARSEMDN
> 
> This method is nothing to do with EmailSubmission really. Probably
> should be called MDN/PARSE.

Probably, I hesitated because like this all the MDN stuff is related to 
EmailSubmission, but I can write a MDN/parse if you think it's better.

>> 4.2 [1].  ASKING FOR MDN WHEN SENDING AN EMAIL
> 
> This example is wrong. You can't set a "headers" property [3] in
> Email/set. You need to set it as a specific header, e.g.
> 
> "header:Disposition-Notification-To": "joe@example.com"

Oops sorry, I guess I took it from an old specification, I will fix.

>> The client issues a parse request:
>> 
>> [[ "EmailSubmission/parseMDN", {
>> "accountId": "ue150411c",
>> "blobIds: "0f9f65ab-dc7b-4146-850f-6e4881093965"
>> }, "0" ]]
> 
> This blobIds argument should be an array, but the example is just
> passing a string.

Right, will fix.

>> 5.2 [2].  REGISTRATION OF JMAP KEYWORD '$MDNSENT'
> 
> This keyword is already registered [4]. There is no need to register
> it again (indeed, this is not allowed).

Oh nice, I was not aware of it. I will remove this part.

Regards,
Raphaël.