Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?
Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services).
The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew)
Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right?
G
I have no idea about that Mac proprietary stuff ... however, https://doc.dovecot.org/configuration_manual/push_notification/ might be a solution/workaround for you.
regards,
infoomatic
Am 08.01.20 um 22:33 schrieb Gerben Wierda:
Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services).
The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew)
Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right?
G
https://github.com/st3fan/dovecot-xaps-daemon
Works PERFECTLY. I use it on CentOS 6 and 7.
Thanks, Steffan Cline steffan@hldns.com 602-793-0014
On Jan 8, 2020, at 2:39 PM, infoomatic infoomatic@gmx.at wrote:
I have no idea about that Mac proprietary stuff ... however, https://doc.dovecot.org/configuration_manual/push_notification/ might be a solution/workaround for you.
regards,
infoomatic
Am 08.01.20 um 22:33 schrieb Gerben Wierda: Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services).
The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew)
Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right?
G
This requires the ongoing use of macOS Server (as does the patch that is part of the MacPorts port of dovecot2). The issue then is: how do you keep getting certificates for push mail if mail services have been removed from macOS Server? I can configure this today but on Oct 20, my apns certificate expires. Then what?
Gerben Wierda Chess and the Art of Enterprise Architecture Mastering ArchiMate Architecture for Real Enterprises at InfoWorld On Slippery Ice at EAPJ
On 9 Jan 2020, at 00:19, Steffan Cline steffan@hldns.com wrote:
https://github.com/st3fan/dovecot-xaps-daemon
Works PERFECTLY. I use it on CentOS 6 and 7.
Thanks, Steffan Cline steffan@hldns.com 602-793-0014
On Jan 8, 2020, at 2:39 PM, infoomatic infoomatic@gmx.at wrote:
I have no idea about that Mac proprietary stuff ... however, https://doc.dovecot.org/configuration_manual/push_notification/ might be a solution/workaround for you.
regards,
infoomatic
Am 08.01.20 um 22:33 schrieb Gerben Wierda: Now that Apple has abandoned mail server capabilities in macOS Server.app we have to move to an open source solution. I have done this using Macports and it works well (no thanks to Apple as it never published the in 2018 promised migration info for mail services).
The MacPorts Apple Push Notification variant based on a patch written a few years ago for dovecot supports APNS but it requires you to export a certificate form your old High Sierra Server.app. With the patch and that certificate, dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes Apple mail clients think they are talking to macOS Server and they switch to push notifications for updates. Now, that certificate needs to be renewed yearly by Server.app and imported by hand etc. At some point this will stop working (apart from that you need to keep an old macOS Server around to renew)
Is there another way to get this working with an open source dovecot, outside of using Apple’s push notification service? Some other standard? Some other service? Probably not, right?
G
Another concern is that Apple is planning to discontinue the binary notification-submission endpoint late this year --- it's been replaced by a (significantly nicer, IMHO) http2-based endpoint, but a quick look at the xaps daemon looks like it's using the old protocol.
participants (5)
-
Aki Tuomi
-
Gerben Wierda
-
infoomatic
-
Steffan Cline
-
Wim Lewis