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

Should we create or register $hasAttachment flag for JMAP/IMAP mapping #212

Open
cjnewman opened this issue Jun 11, 2018 · 1 comment
Open
Labels

Comments

@cjnewman
Copy link
Contributor

JMAP has a boolean hasAttachment property. For JMAP/IMAP mapping, there should be an equivalent in IMAP. The present registry model for JMAP/IMAP keywords allows registering a "reserved" keyword (if we want to define it later) or an "IMAP-only" keyword (if we want to define it in JMAP). I'm willing to supply text either way. I have a slight preference for defining an "IMAP-only" keyword in the JMAP mail spec since the definition of hasAttachment is already in the JMAP spec. For completeness, the third option would be to lose the boolean property and make it a 'both' keyword (with the same definition, but a few caveats for the IMAP case, for backwards compatibility).

@neilj neilj added the Mail label Jun 25, 2018
@neilj
Copy link
Member

neilj commented Jun 27, 2018

Registering $HasAttachment was brought up on the IMAPEXT mailing list 6 months ago: https://www.ietf.org/mail-archive/web/imapext/current/msg05852.html – not sure why Jeff never followed through with this?

I think IMAP-only keyword is fine. I strongly think it should be a property on the Email object rather than a keyword in JMAP because that's immutable and mandates implementation, as explained in https://www.ietf.org/mail-archive/web/jmap/current/msg00488.html

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

2 participants