Apple Support Communities > Servers and Enterprise Software > Mac OS X Server v10.6 Snow Leopard > Discussions
This discussion is archived
14213 Views 27 Replies Latest reply: Aug 20, 2010 9:08 AM by Tim Bloom1
Currently Being ModeratedDec 11, 2009 8:35 AM (in response to Tim Harris)Actually the host is mail.mycompany.com. Push Notification is showing mycompany.com.
This is mismatched, but it doesn't seem that the Push Notification log is throwing up any errors about it.Aluminum iMac - 24", Mac OS X (10.6.2), 4GB RAM
Currently Being ModeratedDec 11, 2009 9:03 AM (in response to B. Kennedy)
notification:domain = "mail.mycompany.com"
it seems to me that the problem is with Server Admin and not the server itself as push has the correct settings.
what does *sudo serveradmin settings mail:imap:notificationserveraddress*Mainly xserve's and mac mini's, Mac OS X (10.4.11)
Currently Being ModeratedDec 11, 2009 9:11 AM (in response to Tim Harris)The notification server responded "mail.mycompany.com".Aluminum iMac - 24", Mac OS X (10.6.2), 4GB RAM
Currently Being ModeratedDec 11, 2009 9:22 AM (in response to B. Kennedy)Then it seems the problem is with server admin and not the server. Which I guess is good newsMainly xserve's and mac mini's, Mac OS X (10.4.11)
Currently Being ModeratedDec 11, 2009 9:23 AM (in response to Tim Harris)Will this be submitted as a bug?Aluminum iMac - 24", Mac OS X (10.6.2), 4GB RAM
Currently Being ModeratedDec 11, 2009 10:54 AM (in response to B. Kennedy)No by me, I'm an end user like yourself, but you can submit feedback http://www.apple.com/feedback/macosx.htmlMainly xserve's and mac mini's, Mac OS X (10.4.11)
Currently Being ModeratedDec 16, 2009 5:35 PM (in response to B. Kennedy)Hi,
please check http://support.apple.com/kb/TS2987 which should solve the problem described.
Currently Being ModeratedJan 15, 2010 12:35 AM (in response to accckkk)The solution provided here works great to solve the push notification server for the iCal server, however it doesn't help resolve the mail push notification. Nor does it help resolve the issue of setting a server going forward. Each time you try to set the server, it just defaults to the domain name, instead of a host name.MacBook Pro 15" 1.83 Ghz, Mac OS X (10.6.2)
Currently Being ModeratedApr 13, 2010 5:18 PM (in response to Chris Byrd)is there really no way around this? I have the same or a similar issue, where the push service hostname and domain do not match. not matter what i try the push service will continue to show domain as: systemhostname.local instead of my FQDN - anytime i try and add a push server to services that want to use push they end up defaulting to the .local hostname when i add them.
I tried the procedure outlined in the KB article but this didn't work..
here is my serveradmin settings dump for the service:
notification:hide-nodes = 1
notification:backend = "sqlite"
notification:dbuser = ""
notification:rhost = "127.0.0.1"
notification:secret = "=I*"IVEDSoS4TIy"
notification:sslKeyFile = "/etc/certificates/server.thewcateam.net.C68343A438DA835B1B69D4FADE3BA6DB3C10AA BF.concat.pem"
notification:jid = "pubsub"
notification:clusterHostname = ""
notification:clusterNodes = emptyarray
notification:domain = "WCA-Server.local"
notification:verbose = 0
notification:sslCAFile = "/etc/certificates/server.thewcateam.net.C68343A438DA835B1B69D4FADE3BA6DB3C10AA BF.chain.pem"
notification:connectAsClient = no
notification:dbname = "/var/db/idavoll"
notification:rport = "5347"
notification:privilegedUsers:arrayindex:0 = "notificationuser"
notification:privilegedUsers:arrayindex:1 = "com.apple.notificationuser"
notification:dbpass = ""
notification:connectToCluster = noOther OS
Currently Being ModeratedApr 13, 2010 8:08 PM (in response to MustardParty)This is crazy - there is NOTHING out there on how to change the notification:domain = "" value. Does that really mean that once a server is deployed somewhere and push is configured there is literally NO WAY other than a reinstall to deploy it to another domain later on?? I refuse to accept that.
What if I used sudo changeip 10.0.1.11 10.0.1.11 server.thewcateam.net server.thewcateam.net to force the system to 'refresh' the domain that it is currently already set to? would that be enough to force the propagation of the host name through all the services; would that end up updating the notification:domain value?Other OS
Currently Being ModeratedMay 2, 2010 5:10 AM (in response to MustardParty)Hey MustardParty,
First a caveat. I have just installed my first OS X server and are by no means an expert on anything here. So whatever I suggest do so with extreme caution and if it doesn't work for you I can't help you further.
For whatever reason I decided to change the name of my server half way through installation. While it probably would have been easier to wipe everything out and start from scratch I have learnt a lot more about the inner workings (and shortcomings).
Most of the changes I was able to make inside Server Admin with the exception of a pesky keychain key that caused me problems for a while and had to be deleted through Keychain Access.
This iCal push notification server really had me stumped as I couldn't change it and having got rid of the old server name meant I couldn't log on to it either. Eventually I used the command line of BBEdit (a fantastic tool if you don't like or know the old Unix editors) to edit the following file /etc/caldavd.plist
There are a few places that you will need to change it starting around line 130 and then again around line 198. Just look through the file and thoughtfully change the names where you see the old one.
I think this has fixed if for me but I'm also happy for someone to point out the errors of my ways. Good luck.iMac 24", MacBook Air and Mac min (all Intel), Mac OS X (10.6.3)
Currently Being ModeratedJun 10, 2010 10:20 AM (in response to MustardParty)I have been working three days now to get the domain name changed within the "Push Notification" Service. Changing DNS, removing iCal files, updating com.apple.NotificationServer.plist and other com.apple.servermgr_notification.plist files did not help (following the instructions from the KB.
Finally I found that in the "iChat" Service I had not changed the domain name. After removing the old domain name there and adding the new one, suddenly also the "Push Notification" domain changed.Mac Server, Mac OS X (10.6.3)
Currently Being ModeratedAug 20, 2010 9:08 AM (in response to Kraxnax)
I have been working three days now to get the domain name changed within the "Push Notification" Service. Changing DNS, removing iCal files, updating com.apple.NotificationServer.plist and other com.apple.servermgr_notification.plist files did not help (following the instructions from the KB.
Finally I found that in the "iChat" Service I had not changed the domain name. After removing the old domain name there and adding the new one, suddenly also the "Push Notification" domain changed.
This is it. I've been digging around for hours and finally found that this is exactly where this information is held. Thanks.