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.
FastMail is using JMAP, a protocol designed to support push notifications. MXRoute is stuck with SMTP/IMAP which don't support those. There might be a different reason, but I think this is probably the core issue here
I think saying they are stuck with standard email protocols is a bit of a stretch. JMAP is not widely implemented outside of Fastmail and certainly isn’t used by Apple Mail, which actually uses a proprietary IMAP extension (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.
Fastmail have been singled out as they appear to have been given special treatment in the form of an APNS topic ID. Other hosts have been using a reverse engineered endpoint to generate certificates, which has recently been closed.
There’s some discussion on the Apple developer forums - https://developer.apple.com/forums/thread/778671. The solution for the OP there seems to have been they also will get special treatment, but there remains no route for others to use to get the same.
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.
There isn’t a skill issue at play here - it’s that Apple have closed the previously unofficial route others have been using (including MXRoute), which has brought the issue to a head. There’s some discussion on the Apple developer forums - https://developer.apple.com/forums/thread/778671.
That linked topic says Apple is working with the developer to handle it. I don't see any evidence of favoritism.
Fastmail clearly reached out to Apple eons ago, which is evidence of skill on fastmail's part and not favortism on Apple's part. Admittedly, fastmail very likely has lots of contacts in Apple (Jeremy Howard isn't nobody), but that's also a skill issue.
Having friends inside of Apple that provide you with something no one else can obtain is a fairly decent definition of favoritism.
You cannot send Push notifications to the stock iOS Mail app no matter how hard you try. They can. There are functions inside of iOS that are made better because of this (auto copied 2FA codes, for example).
Of the many email hosts out there, only a handful receiving special treatment with no route for others to even request the same is special treatment. In the case of Fastmail, they’ve had this access since 2015.
It’s also very interesting that Apple reached out to the user in the developer forum thread after they raised it as an EU DMA issue.
Fastmail have had sanctioned access from Apple (via their own APNS topic ID) - https://www.fastmail.com/blog/push-email-now-available-in-io...
[1] https://github.com/jmapio/jmap/commit/1335683f8b542c71bc41a4...
I can not find any reference to Apple having any involvement with or interest in JMAP (as much as I’d wish so).
I love every answer my comment received!
This and Kagi are my top subscriptions recommendations.
https://github.com/st3fan/dovecot-xaps-plugin
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.
What actually happened here?
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.
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.
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.
There’s some discussion on the Apple developer forums - https://developer.apple.com/forums/thread/778671. The solution for the OP there seems to have been they also will get special treatment, but there remains no route for others to use to get the same.
Fastmail clearly reached out to Apple eons ago, which is evidence of skill on fastmail's part and not favortism on Apple's part. Admittedly, fastmail very likely has lots of contacts in Apple (Jeremy Howard isn't nobody), but that's also a skill issue.
You cannot send Push notifications to the stock iOS Mail app no matter how hard you try. They can. There are functions inside of iOS that are made better because of this (auto copied 2FA codes, for example).
It’s also very interesting that Apple reached out to the user in the developer forum thread after they raised it as an EU DMA issue.
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.