Configuring Calendar Server in Mountain Lion Server

Configuring Calendar Server in Mountain Lion Server is a fairly simple and straight forward process. The Calendar Server is a CalDAV Server, leveraging HTTP and HTTPS, running on ports 8008 and 8443 respectively. To enable the Calendar service in Mountain Lion Server, open the Server application and click on Calendar in the SERVICES section of the sidebar.

Enabling the Calendar Server in Mountain Lion Server

Enabling the Calendar Server in Mountain Lion Server

Once open, click on Edit to enable email notifications of invitations in the Calendar Server. Provide the email address and then click on the Next button.

Mountain Lion Server :: Configuring Email Notifications in Calendar Server

Mountain Lion Server :: Configuring Email Notifications in Calendar Server

At the Configure Server Email Address screen, provide the type of incoming mail service in use, provide the address of the mail server and then the port number used, if not a standard port for HTTPS-based IMAP (or POP if you’d prefer), the user name and the valid password for the account. Then click on the Next button.

Mountain Lion Calendar Server :: Configuring IMAP

Mountain Lion Calendar Server :: Configuring IMAP

At the outgoing mail server screen, provide the Outgoing Mail Server address, the port, whether or not SSL is in use (it should be if possible), the password protocol, the user name and the password. Then click on the Next button.

Mountain Lion Calendar Server :: Verify Settings

Mountain Lion Calendar Server :: Verify Settings

At the Mail Account Summary screen, review the settings and if correct, click Finish. Back at the service configuration screen, click on the plus sign (“+”) and provide a type of location, a name for the location, whether or not invitations to the resource are accepted and then enter the account name for any accounts that can manage the location’s calendar (they will auto-complete, so there’s no need to remember users and groups exactly). Click Done to complete the setup. Use the Resource setting in type to configure a resource instead of a location. The two are the same, except the Type field.

Creating Locations in the Calendar Service of Mountain Lion Server

Creating Locations in the Calendar Service of Mountain Lion Server

There are a number of settings that can also be configured. But those are exposed only at the command line. To configure them, open the command line and then review the list of Calendar service settings using the list option of the serveradmin command:

sudo serveradmin settings calendar

One of the more common settings to configure is the port number that CalDAV runs on. To configure HTTP:

sudo serveradmin settings calendar:HTTPPort = 8008

For HTTPS:

sudo serveradmin settings calendar:SSLPort = 8443

You can then start the service using the start option:

sudo serveradmin start calendar

Or to stop it:

sudo serveradmin stop calendar

Or to get the status:

sudo serveradmin fullstatus calendar

Once the Calendar server is configured, use the Calendar application to communicate with the server. Open the Calendar application and click on the Calendar menu and select Preferences. From the Preferences screen, click on Accounts to bring up a list of accounts. Here, click on the plus sign (“+”) to bring up the “Add an Account” screen.

Adding An Account In Mountain Lion's Calendar App

Adding An Account In Mountain Lion’s Calendar App

At the “Add an Account” screen, select CalDAV from the Account Type menu and then enter the User Name and password configured on the server, as well as the address of the server. The User Name is usually the name provided in Server app, followed by @ and then the address of the server.

Account Settings In Mountain Lion's Calendar App

Account Settings In Mountain Lion’s Calendar App

Once the server is configured it appears in the list of accounts in the sidebar of the Calendar app. Create calendars in the account and then to share a calendar, right-click on the calendar and click on Share Calendar…

Sharing a CalDAV Calendar

Sharing a CalDAV Calendar

At the Share Calendar screen, provide the name the calendar should appear as to others and click on the plus sign (“+”) and enter any accounts to delegate administration to.

Mountain Lion Calendar Settings

Mountain Lion Calendar Settings

Back at the Calendar Settings screen, use the settings to configure Availability and refresh rate of calendars, as seen above. Click on Server Settings to assign custom port numbers.

Mountain Lion Calendar Address Screen

Mountain Lion Calendar Address Screen

Click on the Delegation tab to view any accounts you’ve been given access to.

Account Delegation In Mountain Lion's Calendar Server

Account Delegation In Mountain Lion’s Calendar Server

Use the Edit button to configure who has delegated access to calendars, as opposed to configuring subscriptions.

Overall, the Calendar service in Mountain Lion Server is one of the easiest to configure. Most of the work goes into settings configured on client systems. This, as with Exchange, dedistributes administration, often making administration more complicated than with many other tools. But that’s a good thing; no one wants to access other peoples accounts, for calendars or mail for that matter, without those users knowing that it was done, as will happen when resetting passwords…

6 Comments

  • JayBe
    August 1, 2012 - 8:55 pm | Permalink

    Responses from invitees, notably google/gmail-based responses, seem to fail to update the status of the event.

    Note I am using an external IMAP/SMTP.

    Aware of any problems or reasons that would be occurring and how to overcome/fix?

    Note responses from, of course, other iCal users seems to work perfectly well.

    Thanks

    • August 27, 2012 - 8:29 pm | Permalink

      I’ve seen this happen when iMIP ports are not open to the server. If you check serveradmin settings calendar then you should be able to find iMIP and open those ports. Let me know if that doesn’t work as I’ve seen a couple of other things that might fix it as well.

  • JayBe
    August 27, 2012 - 8:50 pm | Permalink

    Thanks for the response and information.

    I forgot to come back and update my comment/question when I figured out what was going wrong. You’ve reminded me.

    This was extremely frustrating albeit a bit humorous, I suppose:

    Bottom line is… the failures from as a result of Gmail allowing and providing for dots/periods in Gmail usernames, and therefore, Gmail email addresses.

    To Google/Gmail, it’s OK, in their eyes, for the following:

    jay.be@gmail.com

    … to equal the following:

    jaybe@gmail.com

    To Google/Gmail, they are the “same”, as far as receiving mail and or logging in (at Google) are concerned.

    However, to the rest of the planet, the RFC’, and ultimately in my case, Mac OS X Server Calendar, it’s not the same.

    I was testing with a Google/Gmail account and not specifically using the EXACT SAME email address, including dots/periods, as I did when I initially signed up.

    For clarity, I originally signed up with the following:
    * Note this is NOT my real email address; it might be someones … don’t write to it.

    jay.be@gmail.com

    For my tests, I was sending to jaybe@gmail.com because Google/Gmail had gotten me used to breaking the specs/rules over time.

    As a result, things failed, because the calendar data includes the “real”, registered address, etc. … which contrasts the headers, etc. …

    … bottom line, mucking things up.

    Eventually, after a significant amount of serious annoyance, re-installations, filling sheets and sheets of paper with notes and scribbles and comparisons, I realized it.

    Hope this helps someone else in a similar situation.

  • Ken
    October 13, 2012 - 8:13 am | Permalink

    Great posts for Mt Lion Server!! I am planning an upgrade(seems to be a down grade again) soon from Lion Server. Very helpful. However what SSL cert does this iCal service use

  • Hexachrome
    October 19, 2012 - 3:59 am | Permalink

    I cannot get this to work…
    Email is hosted via Google Apps (Not Business – Free, up to 10 users) – not on the Server (Mountain Lion 10.8). This works for all client machines using mac mail.

    Server is up and running. DNS is correct. All required services work correctly apart for Calendar.
    Have created an email account on Google Apps for the Calendar on the Server to use. When these settings are input into Calendar (username, password, SSL, ports, etc) to enable invitations by email I get the following log error when trying to invite someone to an event created on a client machine ical app who is not in my domain:

    Could not do server-to-imip request : iMIP VFREEBUSY REQUESTs not supported.
    2012-10-18 16:51:31+0100 [-] [caldav-0] [PooledMemCacheProtocol,client] [twistedcaldav.scheduling.scheduler.ScheduleResponseQueue#error] Error during POST for mailto:user.name@example.com: iMIP request failed

    All event invites work if you are in my domain, as it should as I guess these are not being sent ‘out’ of my domain. Soon as you request someone at another domain this error occurs.

    Any help would be appreciated.

    Thanks.

  • Pingback: Bynari » Can I access my calendars and contacts with other clients, via CalDAV and CardDAV?

  • Comments are closed.