Re: [Jmap] draft-ietf-jmap-mdn-06

Raphael OUAZANA <rouazana@linagora.com> Wed, 18 March 2020 17:42 UTC

Return-Path: <rouazana@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 821653A1992 for <jmap@ietfa.amsl.com>; Wed, 18 Mar 2020 10:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.621
X-Spam-Level:
X-Spam-Status: No, score=-1.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=linagora.com
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 wJEG2M7xfXJo for <jmap@ietfa.amsl.com>; Wed, 18 Mar 2020 10:42:54 -0700 (PDT)
Received: from outgoing.linagora.com (outgoing.linagora.com [51.75.198.246]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 216B53A195F for <jmap@ietf.org>; Wed, 18 Mar 2020 10:42:53 -0700 (PDT)
Received: from linagora.com (unknown [10.233.69.48]) by outgoing.linagora.com (Postfix) with ESMTP id 16F443B; Wed, 18 Mar 2020 17:42:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1584553372; bh=J+xtD/QgjRJLNw0q1aKFyIgTQaBV0ZNmA/TYi5SMjF8=; h=From:Reply-To:To:Subject:Date:References:In-Reply-To:From; b=GBpclY9ifv+U4zsfZaJCzzWx0BS9ZY+iYhz2Zbnl3kES12yOQf1Pa1awbM46/ES94 1nDGYrmqMgyV6o5OL+Ab5AeCn6UTeCrjChCnzqhzMaysO/Xt7k4EeEyz6QanbXpxhK tmbnUM6GC0IqPxxzO4m9EqmXw6ekBTDt/wTGBDDqEpHqgY19d7o8wlC8GR230wlzyv NyhdNYW241MGbt6ITbie9MNFKQJnpzmZHK1O6QYTl5MnLPJ6zjl/Ywlnen3pxUo3J/ WnbcqUHLqofDOZ/8MAUFRvXV2u67Qlkd3mDuxYNNyNJbpNbCpMYCgQlKseFcTW8D6a oNb+0axCHXXVg==
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: Raphael OUAZANA <rouazana@linagora.com>
Sender: Raphael OUAZANA <rouazana@linagora.com>
Reply-To: rouazana@linagora.com
To: "jmap@ietf.org" <jmap@ietf.org>, Ken Murchison <murch@fastmail.com>
Message-ID: <Mime4j.45.b5134222dd4c80fb.170eebd92f8@linagora.com>
Date: Wed, 18 Mar 2020 17:42:46 +0000
References: <b5eac159-c58e-dd75-f7f8-73a99b67345d@fastmail.com> <c4a7348f-0a09-19f0-14fd-4162479b4cd4@fastmail.com>
In-Reply-To: <c4a7348f-0a09-19f0-14fd-4162479b4cd4@fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/6XhkGZFBep9EjhZ8xN58jvh22gQ>
Subject: Re: [Jmap] draft-ietf-jmap-mdn-06
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: Wed, 18 Mar 2020 17:43:02 -0000

Hello,

Le 6 mars 2020 20:35, de murch@fastmail.com

On 3/5/20 7:40 PM, Ken Murchison wrote:
> A few questions as I implement this in Cyrus:
>
> - forEmailId is allowed to be null, presumably just for MDN/parse
> responses.  Should we mandate that it be non-null for MDN/send,
> because otherwise, what's the point?


Exactly. I'm adding a word about this.


> - subject and textBody are both allowed to be null.  Should we
> recommend default text for both?


I think it asks more questions than it solves an issue. How the server can choose the good language to send the notification?


> - The JMAP server may not be able to determine the Final-Recipient of
> the original message was Bcc'd or sent to an alias.  Should the MDN
> object include a 'from' property?


It should match the email of the account, no?

Or maybe we should ask for an identity when sending an MDN, so that the user can choose which email appears in this field?



Also, do we need a specific error type if the email corresponding to
fromEmailId does NOT have a Disposition-Notification-To header?  Or do
we use invalidProperties, forbidden, invalidEmail, noRecipients?



It seems I missed the notFound error, I'm adding it.


Regards,

Raphaël Ouazana.