Sorry if the question sounds stupid, but I have hard time to understand
the benefits of maintaining standard flags inside m2dir (the IMAP system
flags + IANA-defined IMAP keywords).
> This will help to preserve semantics, even if mail were to be> replicated to yet another remote store that potentially uses different> flags.
If I understand well, it is for the case where I sync remote IMAP A to
local m2dir B, then decide to sync this same local m2dir B to another
remote IMAP A' that may contain different standard flags? Does this case
really happen?
I could agree for custom flags, but knowing that standard flags should
be the same between IMAP servers, why adding the burden of maintaining
such mapping versus storing flags verbatim?
--
Regards
Clément DOUIN
https://soywod.me
Hey,
On 4/17/24 10:05 PM, Clément DOUIN wrote:
> Sorry if the question sounds stupid, but I have hard time to understand> the benefits of maintaining standard flags inside m2dir (the IMAP system> flags + IANA-defined IMAP keywords).> >> This will help to preserve semantics, even if mail were to be>> replicated to yet another remote store that potentially uses different>> flags.> > If I understand well, it is for the case where I sync remote IMAP A to> local m2dir B, then decide to sync this same local m2dir B to another> remote IMAP A' that may contain different standard flags? Does this case> really happen?
No that cannot happen. But if you want to migrate from IMAP to JMAP (via
a local m2dir) for example, the mapping will be very helpful. And who
knows, maybe there is KMAP soon, and it uses different standard flags ;)
Cheers,
Conrad
> But if you want to migrate from IMAP to JMAP (via a local m2dir) for> example, the mapping will be very helpful. And who knows, maybe there> is KMAP soon, and it uses different standard flags ;)
It feels "wrong" to me, but I cannot explain properly why. Let's take
another example:
IMAP has a default keyword $Junk. m2dir maps it to \Junk. But KMAP does
not have any equivalent. How do you sync m2dir and KMAP flags/keywords?
From m2dir → KMAP, you can use a custom user-defined flag, but from KMAP
→ m2dir? I guess the only way is to walk through user-defined flags and
see if one does match the \Junk flag.
In the actual spec, users need to manage both standard flags AND custom
flags. What I try to dig is if managing only custom flags could not make
the spec simpler. And let the application level do the mapping.
That said, m2dir can be seen as another backend, so it also makes sense
for it to have its own flag system. But in this case I would detach more
from any existing, or I would lighten it.
---
I just read back the spec and seems to have changed since yesterday :D
so basically you have few common standard keywords between IMAP and JMAP
(starting by $), the rest is user-defined, right? Looks less complicated
to me. So I guess you can discard this email.
--
Regards
Clément DOUIN
https://soywod.me