5 ms·
This is great and all, but you're relying on IMAP, an inherently mobile-unfriendly protocol. They should have worked with Fastmail to get this into JMAP.
by amaccuish 8y ago
This is great and all, but you're relying on IMAP, an inherently mobile-unfriendly protocol. They should have worked with Fastmail to get this into JMAP.
- Freak_NL 8y agoI would have pointed you to their issue tracker, but all I can find is a horrible Confluence wiki. Kind of discouraging for potential contributors. There is a mailing list though. At the very least they might add a 'why not (also) JMAP' bullet point to the website if you ask about it: > […] join the COI developer mailing list by sending a mail to dev-join@coi-dev.org. I would guess that they need IMAP to prevent the whole 'nobody uses it' problem.
- enough 8y agoThe specs will soon be available on GitHub soon. If the server supports JMAP, there are no principle obstacles to also support COI over JMAP. But as said, currently the market share of JMAP is neglible.
- disiplus 8y agoi assume for this to work remotely ok the imap idle is a must. also how is it supposed to work on the receiving site ? There has to be some "Folder" where those messages are stored and the imap idle should listen to that folder or else my inbox will be huge mess and mess with my regular mail client. also was there any tests how long does it take for delivery, because the message could hop around and could be scanned, added addotional headers or mess with those there.