[CalendarServer-users] calendar server or radicale?
raj at mischievous.us
Mon Jul 30 12:28:08 PDT 2018
Thanks! I really appreciate all of the good, detailed, information you're sharing here! I was, at one point, thinking that maybe I could update my current Server.app originated APN cert and then use it with the open source calendarserver. It sounds as if you're telling me that even if this could be made to work, it wouldn't last much longer anyway, so it's probably not worth the work. Apple's push notifications for email will be the thing I miss the most. It's been really nice to get immediate notification without having to poll all of the time.
I now have my own server running with calendarserver, apache2, xwiki, postfix, and named. Most of these were easy to setup, since I've done it many times before. The most challenging was getting xwiki to work with SSL, since it's best done by putting it under apache, but following instructions online, I got that working yesterday. I'm now all set with what looks to be a complete replacement for everything I currently have under Server.app, which is good. I was worried about this impending transition!
I just miss not having APNS! I guess I could always forward my personal email to my icloud email account and get notifications from there! :)
Again, thanks a lot for all of the great information! Time moves forward and we all have to keep up!
> On Jul 27, 2018, at 7:55 PM, Andre LaBranche <dre at apple.com> wrote:
>> On Jul 27, 2018, at 2:47 PM, Richard Johnson <raj at mischievous.us> wrote:
>> I guess it's a non-issue, once I get APNS going as well.
> Unfortunately, APNS push can’t really be used with the opensource distribution of CalendarServer if you want to push Apple’s Calendar app on macOS or iOS. This is because the push certs needed for the CalendarServer server have an identifier that includes a reference to the name of the entity to whom the cert is issued. Calendar.app only recognizes certs provisioned through a restricted portal used exclusively by macOS Server, which has historically been the primary release vehicle for CalendarServer. The next version of macOS Server will retain the profile manager service and drop all other services. That has been announced and is reflected in the developer seeds of the Mojave-aligned macOS Server release. In the current GM macOS Server release, these services are still available but hidden in portions of the UI as an additional indicator that they are going away. Since APNS certs have to be renewed annually, I would expect the exclusive macOS Server cert portal to remain operational for existing installations, at least for a while, but probably not indefinitely (I honestly can’t predict how long that might be).
> Other calendar clients might support APNS, and if so, CalendarServer should support them, with the caveat that CalendarServer implements what is now considered the legacy and deprecated APNS server auth mechanism that uses x509 certs. The new mechanism (token based) is quite a bit better, and the public developer push portal will probably stop issuing APNS certs at some point, and (the open source distribution of) CalendarServer’s APNS support would be effectively gone at most 365 days later due to inability to renew those certs - unless somebody implements the new APNS server auth mechanism as an open source contribution. Whether or not CalendarServer is what Apple uses internally, the commit history of this repo is an accurate if slow-moving indicator of the maintenance and activity level of the CalendarServer distribution available to you. With my Apple hat on, I can’t share with you what I or anyone else at Apple is doing, but as a matter of public record, you can see the frequency, scope, and percentage of all commits to the open source repo over time from people with Apple addresses.
More information about the calendarserver-users