12 ms·
The relevant issue: https://github.com/foxcpp/maddy/issues/19 https://github.com/foxcpp/maddy/issues/19 > Status update: JMAP is a big complex protocol that is
by faitswulff 6y ago
The relevant issue: https://github.com/foxcpp/maddy/issues/19 https://github.com/foxcpp/maddy/issues/19
> Status update: JMAP is a big complex protocol that is not used by any popular clients and has no server libraries available for Go. IMAP is a big complex but also widespread protocol that is well-known, supported by any email client and has server library available for Go. Some of IMAP disadvantages come from incomplete client implementations, not protocol flaws, as JMAP developers want to convince you. I do not expect wide JMAP adoption in next several years, therefore the decision was made to prioritize improving IMAP implementation.
> If somebody insists on having JMAP, I recommend looking at Cyrus email server, perhaps write a Go library for its SASL delegation protocol so it could be used with maddy just as easy as Dovecot.
- josephg 6y agoI just replied on the linked issue. If anyone wants to get started making a jmap server, about a year ago I pulled out the cyrus jmap email parsing code into a standalone C/wasm library: https://www.npmjs.com/package/mime-to-jmap https://www.npmjs.com/package/mime-to-jmap Its a bit of a mess and it needs a write-up, but it should be a reasonable start to making more jmap servers. (This does not implement the jmap application protocol, but it does generate fantastic json from any email blob, incl attachments, snippets, html and text output. And thats crazy difficult to implement correctly.)