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

Raphael OUAZANA <rouazana@linagora.com> Thu, 19 March 2020 10:17 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 4F61F3A2671 for <jmap@ietfa.amsl.com>; Thu, 19 Mar 2020 03:17:57 -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 nsQDX8C3tDpT for <jmap@ietfa.amsl.com>; Thu, 19 Mar 2020 03:17:56 -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 E36E53A108F for <jmap@ietf.org>; Thu, 19 Mar 2020 03:17:55 -0700 (PDT)
Received: from linagora.com (unknown [10.233.69.48]) by outgoing.linagora.com (Postfix) with ESMTP id 5EC1D3B; Thu, 19 Mar 2020 10:17:53 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linagora.com; s=s20181122; t=1584613073; bh=XQvOzEzIVNfbvdscpsxiWzqA6Ba+bJan5LHQRE5uqU0=; h=From:Reply-To:To:Subject:Date:References:In-Reply-To:From; b=laaVXGAiGJnZ4lLPmuXSS/Si6YUytfn2Hqf0/Dyx+WUi1+awZN4gU3pMe8ffjBBxi RJ6+ZKQTXnTYxz2/q8F3XJZqikqdNO76URD5FNh5mM4v4Cdf7AH8Qj3iun9kg14b82 Qg9m0RCdZQKfmiDUuj6suIZhO9zWqh15QlMYVVCT0vfcTN/Pp+9ybKsieVsR63d/E0 J9DHDaOZedUsLAl9T8XB27/lFvNphITllsa0zb6KJtUvYDQGWfg74RlHl+FFnLahHb /JAtyYBxnYWT1SjTbhDRRDY61NEMF/XpavjommShhB0ClmOwTvB9wjhz06t/dg+2SR bkob0OzheEa8A==
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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.56.bf28b98699a28c35.170f24c1a82@linagora.com>
Date: Thu, 19 Mar 2020 10:17:18 +0000
References: <b5eac159-c58e-dd75-f7f8-73a99b67345d@fastmail.com> <c4a7348f-0a09-19f0-14fd-4162479b4cd4@fastmail.com> <Mime4j.45.b5134222dd4c80fb.170eebd92f8@linagora.com> <ed338838-996a-26ad-3ba6-b5c578155e18@fastmail.com>
In-Reply-To: <ed338838-996a-26ad-3ba6-b5c578155e18@fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/9fTuAxlQtpNgKVjwB4s9IRcQy1M>
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: Thu, 19 Mar 2020 10:17:58 -0000


Le 18 mars 2020 19:09, de murch@fastmail.com


On 3/18/20 1:42 PM, Raphael OUAZANA wrote:

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:

> - 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?


If the email was sent to an email alias and eventually delivered to the underlying account, the sender of the MDN might want to have the MDN use the alias so as not to leak the real address of the account.


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


Yes, that is what I was thinking.  If the user doesn't provide a from address, then we can default to the email of the account.


I will add an identity parameter, like in MessageSubmission. I will make it mandatory because for me it's not clear how we can get an email address from an account.

Regards,

Raphaël.