Feature Request: JMAP support with native iOS push notifications (Fastmail)

Mobile apps
1

Dear eM Client Team,

I am a longtime eM Client user with a lifetime license, using eM Client across macOS, iOS, and iPadOS with Fastmail as my primary email provider.

My biggest ongoing pain point is the lack of reliable push notifications on iOS. I understand this is a complex problem - iOS does not support IMAP IDLE in the background, and the current Firebase-based push mechanism has significant limitations: the app does not refresh in the background, badge counts are inconsistent, and the inbox state is often stale when opening the app.

I have done some research and I believe the solution already exists: JMAP push via webhooks.

Fastmail - one of the primary developers of the JMAP standard - already supports JMAP push webhooks for third-party clients. I have also seen that a new Swift-native JMAP email client called Plume has successfully implemented native iOS push notifications using this exact mechanism, proving that it is technically feasible.

I am aware that JMAP support is already on eM Client’s 2026 roadmap for the desktop and Android versions. I would like to specifically request that iOS is also included in the JMAP roadmap, as this would finally solve the push notification problem in a standards-compliant, reliable way - without relying on a Firebase proxy.

The ideal outcome would be:

  1. eM Client iOS connects to Fastmail via JMAP instead of IMAP
  2. eM Client registers a JMAP push webhook with Fastmail
  3. Fastmail notifies eM Client’s server instantly on new mail
  4. Native iOS push notification arrives immediately, with the inbox already up to date when the app is opened

I would be happy to participate in any beta testing if this feature is developed. Thank you for considering this request.

2

Where does it show JMAP is already on the roadmap for the desktop & android in 2026 ?

There is only a current Sleekplan suggestion “open status” at this stage for JMAP support which you can vote for below, but that doesn’t mean it will be implemented this year.

Also as @lancealot posted in the below thread on JMAP support

https://forum.emclient.com/t/jmap-support-wanted/78419/17

Quote:-

“Which reputable email service providers beside Fastmail (who developed the spec) have mature support for JMAP? Thunderbird’s implementation is far from being mature, in the same way Thunderbirds EWS implementation is”.

“So, unless more reputable email providers support JMAP, I don’t see lots of people really wanting it. At least Google, Microsoft, and just about every other email provider out their support IMAP, regardless of whatever API scheme they put on top of the HTTP(s) protocol for additional access methods. I do like how JMAP includes Calendar and Contact support, but even CalDAV and CardDAV is more widely supported (GMail for example), especially in iOS/MacOS mail, contact, and calendar apps”.

“The problem is not eM Client not supporting JMAP, it is that most email service providers not finding it worth the effort to support JMAP. When that changes then it will make more sense for eM Client to support JMAP. Wake me up when Google and Office365 support JMAP in the same way they support IMAP or their native APIs”.