Or maybe... FastMail created JMAP, ergo they are the one with the best implementation.
Now Apple is working on moving iCloud to JMAP, and are working with FastMail as a JMAP production level service within mail.app.
Apple uses a proprietary IMAP extension that, until recently, any developer could use by generating a APNS certificate using a reverse engineered endpoint from macOS Server. They’ve since closed this.
How iOS Mail gets push inbox updates working with third-party IMAP servers is in the public since 2015/2016 if you look hard enough. That has nothing to do with JMAP the protocol inherently.
Does Fastmail really get push? I have a vague recollection that the reason I’m using their app over native ios Mail is because ios Mail was notifying me about emails with a noticeable delay.
It’s more focused on how to get notifications to work with an email server that does not support XAPPLEPUSHSERVICE, but I also delve into how Apple abandoned the only reference implementation of XAPPLEPUSHSERVICE.
iOS Mail app does not support IMAP IDLE like any ordinary email clients.
It only supports a proprietary IMAP extension that uses Apple Push Notification Services (APNS) as a sideband channel for IMAP servers to signal the iOS Mail app.
Last I researched this (like… years ago), most IMAP-based email providers that are listed by the iOS Settings have implemented the extension, except for Gmail and Exchange. Fastmail then got on the train since 2015.
Not sure what is with the tweet targeting Fastmail specifically though.
Yeah I looked at the link and first reaction is there are no receipts and failure to produce receipts registers with me as adequately explained as a "skill issue" (via some sort of corollary to Hanlon's razor). My outrage meter is unmoved.
yohannparis|6 months ago
admdly|6 months ago
Fastmail have had sanctioned access from Apple (via their own APNS topic ID) - https://www.fastmail.com/blog/push-email-now-available-in-io...
whazor|6 months ago
[1] https://github.com/jmapio/jmap/commit/1335683f8b542c71bc41a4...
mpercival531|6 months ago
solarkraft|6 months ago
I can not find any reference to Apple having any involvement with or interest in JMAP (as much as I’d wish so).
jarland|6 months ago
1over137|6 months ago
MrDarcy|6 months ago
frizlab|6 months ago
This and Kagi are my top subscriptions recommendations.
jervant|6 months ago
https://github.com/st3fan/dovecot-xaps-plugin
st3fan|6 months ago
1over137|6 months ago
jbc1|6 months ago
mpercival531|6 months ago
IMAP servers through APNS ping the iOS Mail about updates in certain pre-registered inboxes. Then iOS Mail re-fetches those inboxes.
The change signal is pushed; the data (inboxes/emails) aren’t.
tyleo|6 months ago
What actually happened here?
slau|6 months ago
It’s more focused on how to get notifications to work with an email server that does not support XAPPLEPUSHSERVICE, but I also delve into how Apple abandoned the only reference implementation of XAPPLEPUSHSERVICE.
paul-tharun|6 months ago
FastMail got access to it and it is not clear how, without any public announcement or documentation.
It is as if Apple just picked a favorite and went with it.
mpercival531|6 months ago
It only supports a proprietary IMAP extension that uses Apple Push Notification Services (APNS) as a sideband channel for IMAP servers to signal the iOS Mail app.
Last I researched this (like… years ago), most IMAP-based email providers that are listed by the iOS Settings have implemented the extension, except for Gmail and Exchange. Fastmail then got on the train since 2015.
Not sure what is with the tweet targeting Fastmail specifically though.
fluidcruft|6 months ago
unknown|6 months ago
[deleted]
nerdjon|6 months ago
I just checked my emails, I use Amazon Workmail and even that has push support. The only one for me that doesn't is my lesser used gmail.
To my knowledge I get alerts quickly with that email, I have never had an issue of not.
nunez|6 months ago