IETF Logo Mail Archive

[JMAP] Re: JMAP for Calendars comments

Ben Bucksch <ben.bucksch@beonex.com> Sun, 05 October 2025 20:47 UTC

Return-Path: <ben.bucksch@beonex.com>
X-Original-To: jmap@mail2.ietf.org
Delivered-To: jmap@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 4DE666DA934A for <jmap@mail2.ietf.org>; Sun, 5 Oct 2025 13:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bpdajv_BxQ58 for <jmap@mail2.ietf.org>; Sun, 5 Oct 2025 13:47:47 -0700 (PDT)
Received: from mail.server.beonex.com (mail.server.beonex.com [144.76.227.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A95E86DA9345 for <jmap@ietf.org>; Sun, 5 Oct 2025 13:47:47 -0700 (PDT)
Received: from mail.beonex.com (fire3.beonex.com [88.99.137.225]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.server.beonex.com (Postfix) with ESMTPS id 95043A00103; Sun, 5 Oct 2025 22:47:36 +0200 (CEST)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by mail.beonex.com (Postfix) with ESMTPA id 05CFFA06F3B2; Sun, 5 Oct 2025 20:47:35 +0000 (UTC)
Date: Sun, 05 Oct 2025 22:47:35 +0200
From: Ben Bucksch <ben.bucksch@beonex.com>
To: jmap@ietf.org
In-Reply-To: <E7E219C3-EC93-4DEA-8945-2643D9FE01E6@stalw.art>
References: <101DEC25-A12F-4063-90FB-446C6E5190BF@stalw.art> <E7E219C3-EC93-4DEA-8945-2643D9FE01E6@stalw.art>
Message-ID: <EA5E45B3-3538-48B2-8F4A-8B6864CF8C23@beonex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Authentication-Results: mail.beonex.com; auth=pass smtp.auth=ben@bucksch.name smtp.mailfrom=ben.bucksch@beonex.com
X-Spamd-Bar: +
Message-ID-Hash: 7MITYV2LNARE6BEQXVJXFLX5BBLAXXLZ
X-Message-ID-Hash: 7MITYV2LNARE6BEQXVJXFLX5BBLAXXLZ
X-MailFrom: ben.bucksch@beonex.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jmap.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [JMAP] Re: JMAP for Calendars comments
List-Id: JSON Meta Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/24AmdbkB7_zO6U-742LYCrirMxE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Owner: <mailto:jmap-owner@ietf.org>
List-Post: <mailto:jmap@ietf.org>
List-Subscribe: <mailto:jmap-join@ietf.org>
List-Unsubscribe: <mailto:jmap-leave@ietf.org>


Am 5. Oktober 2025 17:30:41 MESZ schrieb Mauro De Gennaro <mauro=40stalw.art@dmarc.ietf.org>:
>For example, in Stalwart, calendar addresses are derived from the account’s email address(es) and cannot be modified by users. If we allow users to add other participant identities that are not their email addresses, how should the server validate that they are authorized to use those identities?

1. Doesn't JMAP allow for multiple identities and email addresses that are associated with the same mail account? Presumably, if the account has multiple email addresses, then for a reason. Why would an invitation reply be restricted to only 1 of them?

2. If the invitation is for a particular email address, the user should be allowed to answer the invitation with the same address, even if it's different from the main email address of the account. Otherwise the user has a problem, because the wrong email address leaks. Or the organizer has a problem, because he gets an answer from an email address that he didn't invite. Or both.

v2.34.0 | Report a Bug | By Email | System Status