Yes , I guess I need to update the site to include this info , as this question emerges too often.
Some extra features like push notification will require subscription (probably a few $ a year).
Right now it works (only in a dev environment) with MSGraph and Gmail.
Just waiting for JMAP push notifications to be enabled by Fastmail , to release support for the tree protocols.
Would that require giving up the access credentials to app-supporting servers or there’s a way to avoid this and make two servers meet “in the middle” with client orchestrating the initial setup (at least with JMAP)?
I self-host and don’t like how way too many client apps deal with credentials in the name of convenience, many without even announcing that they do send them somewhere outside the device. I don’t currently have JMAP but I’m interested in replacing IMAPv4 as soon as something better is ready aka has all the features I use and mobile and desktop clients (I don’t really care about the webapps).
The only credentials which will flow is OAuth/API token.
Mailtemi (future)server would not store it, only ephemeral (http + cert check) connection to advice for push notification.JMAP and MSGraph protocols are fine by design.
Gmail needs a bit of tweaking to hash email addresses , because in their API the key is email.
There are edge cases like non ascii email addresses.
For IMAP there is no push protocol without a password knowledge.
No plan/wish to deal/know/store it.
But still I think of small open source AWS golang/nodejs code(+markeplace bridge).
Just the password possession should be only of the owner.
IMAP IDLE needs an open connection.
When the phone is locked all apps are suspended(connection closed) except if they are VOIP.
So this makes IDLE unusable. Moreover an open connection takes more energy.
So here comes push notification and from open protocols only JMAP has it.
