Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

draft-ietf-jmap-mail: Need to reuse IMAP Keyword registry #73

Closed
aamelnikov opened this issue May 1, 2017 · 6 comments
Closed

draft-ietf-jmap-mail: Need to reuse IMAP Keyword registry #73

aamelnikov opened this issue May 1, 2017 · 6 comments
Labels

Comments

@aamelnikov
Copy link

See RFC 5788 and https://www.iana.org/assignments/imap-keywords/imap-keywords.xhtml#imap-keywords-1.

@brong
Copy link
Member

brong commented May 2, 2017

Also if we're going to use $Seen, etc to map \Seen from IMAP, we need to register those 4 system keywords in the IANA registry saying "reserved for JMAP, do not use in IMAP" and add "updates 5788" to the spec.

@chibenwa
Copy link
Contributor

chibenwa commented May 3, 2017

Have a look to #61 which was previously discussed on the mailing list.

Moreover I would insist on having a uniformed view of when a messages is read (and co...) between IMAP and JMAP thus using %Seen and register it in IANA would be a bog mistake in my eyes

@brong
Copy link
Member

brong commented May 3, 2017

I think I didn't explain it well enough. \Seen via IMAP would map to $Seen via JMAP, to make the JMAP view simpler (those 4 keywords aren't magically special) and avoid the \ quoting horror show.

@brong
Copy link
Member

brong commented Jul 17, 2017

Chris Newman will help with this (from IETF99)

@neilj neilj added the Mail label Dec 9, 2017
@cjnewman
Copy link
Contributor

cjnewman commented Jun 7, 2018

Here's a pull request: #208

@neilj
Copy link
Member

neilj commented Jun 10, 2018

Closed by #208.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants