[JAMES-3540] Spec compliance: Blob/copy

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.0
• Component/s: JMAP
• Assignee: Antoine Duprat
• Reporter: Benoit Tellier
• Created: 04/Apr/21 14:09
• Updated: 04/Apr/21 14:09

Description

https://jmap.io/spec-core.html#blobcopy

Binary data may be copied between two different accounts using the Blob/copy method rather than having to download and then reupload on the client.

Our JMAP implementation (and the underlying right system backing it) do not support multi-account. Making this methods globally useless.

However, in the sake of spec compliance, we might consider expose a naive version of it:

Quoting https://jmap.io/spec-core.html#copy

accountId: Id The id of the account to copy records to. This MUST be different to 
the fromAccountId.

As we currently enforce accountId to match the user account, we can:

• Reject with invalidArguments if accountId is the user one and fromAccountId also the user one.
• Reject with accountNotFound if accountId do not match the user one
• Reject with fromAccountNotFound if fromAccountId is different from the user accountId.

Not really useful, but it would technically be specification compliant...