[JAMES-3541] Spec compliance: Email/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:11
• Updated: 04/Apr/21 14:11

Description

https://jmap.io/spec-mail.html#emailcopy

This is a standard “/copy” method as described in [@!RFC8620], Section 5.4, 
except only the mailboxIds, keywords, and receivedAt properties may be set 
during the copy. This method cannot modify the message represented by the 
Email.

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