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.

Ironically, Google does use APNS to support its own Gmail app on iOS, and for many other reasons. Just not for IMAP.

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.

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.

Why can't MXroute do exactly the same thing? Did they open a ticket?

No, I went straight to trying to shame them on Twitter. The part where I said "We’ve tried to talk. @Apple just stops responding once they realize what we’re asking" was just a joke, you got me.

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).

There's no evidence "nobody else can obtain" it. The parent's link to the Apple developer forum shows somebody else obtaining it. There's no evidence that MXroute couldn't do the same.

MXroute doesn't go around threatening US companies with EU law from Texas. As for your requirement for evidence, this situation does not require your approval unless you work for Apple and can offer some help in the matter. The tweet you are critiquing is me (owner of MXroute) attempting to gain Apple's attention to get what Fastmail and that EU user have obtained. I'll continue doing what I'm doing, if that's alright with you.

Why would you expect a defined process? It's proprietary software on a closed platform.

I'll just take your word for it that there's no ways for Texans to get the same treatment as these other companies. Oh well. Take it up with your legislature, I guess.

This is a pretty unfortunate context for this, but I just wanted to say that I've been using your service for years, and me and my handful of customers are 100% satisfied.

It sucks that Apple won't just embrace interop with host mail services in some formal way, I'm not sure what the benefit of this specific flavor of gatekeeping achieves. It also sucks that HN contrarians are reflexively dumping on this, instead of supporting entrepreneurs like one might hope in such a community. Anyway, keep up the great work, I'm with you long term.

I kind of wrote about this: https://sebastian.lauwe.rs/blog/ios-migadu-notifications/

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.

MXRoute has been trying from ages to get push notifications on the IOS mail app but were getting ignored.

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.

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

The stock iOS Mail app does not support JMAP and therefore it has no relation to Push notifications for the stock iOS Mail app.

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).

For example a relatively modern email protocol: https://www.rfc-editor.org/rfc/rfc8621.html

I am a bit confused here as well, is there a difference between "Push" and the notifications on iOS?

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.