I already tried the following:
- turned off push notifications, stopped, ical, contacts and mail and after a reboot turned on push, mail, contacts and ical again via server.app
- renewed the push certificates of my apple id
- tried another apple id with the push certificates
- dropped the profilemanager profiles on my ios devices and added them again after a reboot
the push option now has vanished also for ical on my ios devices
I have the same problem. With my Lion Server worked fine and pushed new mails from my own mail server on the mac mini to my iOS devices. Now I'm using Mountain Lion with the Server App and I can't receive push mails on my devices. I also have new push certificates from apple. I'm not using the Profile Manager (With Lion Server I also didn't use it, and push worked!). So I can't set the Mail Notifications to Push on my devices for the mail account on my ML Server.
When I filter the Console on the Server I can see the following messages:
16.11.12 17:58:49,142 push_notify: Opening connection to apn feedback server feedback.push.apple.com for topic com.apple.mail.XServer.64a87de9-5f35-42d3-9cb0-0631b8942ff8
16.11.12 17:58:54,697 push_notify: Disconnected from apn feedback server feedback.push.apple.com for topic com.apple.mail.XServer.64a87de9-5f35-42d3-9cb0-0631b8942ff8
16.11.12 18:15:12,445 apsd: <APSConnectionNotificationQueue: 0x7fa8d48537d0>: outstanding count -1 for com.apple.apsd-queue-port=com.apple.syncdefaultsd.push-user=501-env=production
The Last message repeats more and more. Is the server trying to push, but has a failure? I don't understand the output.
I'm glad to hear that i am not the only one who has problems with push mail.
My first thought was also that the server has a problem but after reading the thread, i think it could maybe be iOS.
All my devices run 6.01 and all of them are fetching mails from the ML server.
How is ML reciving the mails from the server? Are these mails also pushed or rather fetched?
I have the same Problem with Push Mail but on Lion Server:
I think this is not a Problem on the server but rather in IOS 6.0.1. I cannot swear but i think push is broken since i updated my devices to the new IOS Version.
Hopefully our Problem would be solved soon.
I also would say that this issue does't depent on the used OSX Server. I used a Lion Server for more then one year without having push mail problems. Monday last week I suddenly did not receive any push mail. First I was looking for the problem, but could not find a hint. So I restored a two week old complete time machine backup of my lion server. When the backup was made, push mail worked definetly fine. But also no push. The I decided to install a new blank Mountain Lion Server and did not use any backup. Renewed my push certificates and my signed ssl certificate as well. Everything but push is working propably.
so much time waisted on this and it seems like an iOS error, but I was the opinion that my iPad latest iOS update where still pushing also my iPhone does not...
maybe apple dropped the feature on their side (push certificate) in Germany they had to cancel iCloud push for some patent reason maybe that could be a far reason?
Or some date related bug in the latest iOS update?
Hope apple will have a fix and my server is not in an invalid configuration status after all those repair tryouts :(
Good, but also bad news,
I'm sure now that it is a problem or bug of the actual iOS. I configured my mail account on my old iPhone 3G with iOS 4.2.1 right now fpr testing. Surprise surprise push can by selected and is also working fine.
I hope the will be an update for the actual devices very quick.
There is more than one way to report things to Apple. It really comes down to how much it's worth to you. The most available are…
1) Apple Feedback
2) Apple Developer bug reporter (this works even with the free accounts)
The more detailed you are the better. Bear in mind that there's a lot that can go on with a Push event on Poerts TCP2195-2196 from your server that's out of control of Apple ranging from your server setup (firewalls etc), your network topology (DNS plus your Internet connection and provider proxy servers) through to your ISP and your cellular provider etc, and everything in between… and that's before iOS has a chance to do anything right or wrong.
While I'm definitely not absolving Apple of anything (for all I know it may well be their fault), one needs to appreciate that just saying it doesn't work isn't going to get anyone very far. Apple can't predict every single circumstance that OS X Server may find itself in so as many details as you can give would be useful.