[jira] [Created] (JAMES-3541) Spec compliance: Email/copy

["Benoit Tellier (Jira)" <se...@james.apache.org>]

Benoit Tellier created JAMES-3541:
-------------------------------------

             Summary: Spec compliance: Email/copy
                 Key: JAMES-3541
                 URL: https://issues.apache.org/jira/browse/JAMES-3541
             Project: James Server
          Issue Type: Sub-task
          Components: JMAP
    Affects Versions: 3.6.0
            Reporter: Benoit Tellier
            Assignee: Antoine Duprat


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

{code:java}
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.
{code}

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

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

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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org