[prev in list] [next in list] [prev in thread] [next in thread]
List: james-dev
Subject: [jira] [Created] (JAMES-4026) Fix inconsistency IMAP - JMAP keyword issue for JMAP RFC-8621
From: René_Cordier_(Jira) <server-dev () james ! apache ! org>
Date: 2024-04-10 6:58:27
Message-ID: JIRA.13575298.1712732442000.2765.1712732460017 () Atlassian ! JIRA
[Download RAW message or body]
Ren=C3=A9 Cordier created JAMES-4026:
-----------------------------------
Summary: Fix inconsistency IMAP - JMAP keyword issue for JMAP =
RFC-8621
Key: JAMES-4026
URL: https://issues.apache.org/jira/browse/JAMES-4026
Project: James Server
Issue Type: Bug
Affects Versions: 3.8.2
Reporter: Ren=C3=A9 Cordier
Fix For: 3.9.0
When migrating some tests from jmap draft to jmap rfc, an issue was identif=
ied regarding conflicts introduced via IMAP on keywords when trying to solv=
e it via jmap email/set method
If we have a message m1 in 2 mailboxes m1 and m2, if we add a flag=C2=A0{{\=
Flagged}}=C2=A0via IMAP on the message in mailbox m2, we create an inconsis=
tency for JMAP. Normally, if we set via email/set the flag to=C2=A0{{$Flagg=
ed}}=C2=A0for m1, it should fix the inconsistency, having the keyword for t=
he message present in both mailboxes.
However, it does not happen right now, as it seems when doing an update on =
email, we do union of keywords regarding the metadata, and if it's the same=
as new flags (which is the case here) then we do nothing, thus not fixing =
the inconsistency.
The fix is a bit tricky, as some simple solution have been attempted while =
creating issues elsewhere.
Need to investigate deeper and fix the issue for JMAP RFC implementation
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic