An Oracle blog about Openomics

  • sun
    April 20, 2009

Sun Calendar Sync for Apple iCal : Releasing icalds 2.1

Guest Author

Thanks to the user community, which reported issues on my original blog release of icalds, I am able to release today icalds 2.1 which includes one minor fix --icalds now strips out the MEMBER params when subscribing to a Sun Calendar server-- and a first validation of the Publish use case --you maintain your calendar in iCal and publish it out to a Sun Calendar server through icalds. You can download the icalds.pl Perl script from the same location at opensolaris.free.fr.

Please refer to the original blog post for the icalds documentation for installation --steps 1 to 4-- and calendar subscribe --step 5. To publish, do this next :

  1. Publish from iCal
    • publish calendar as <calname>
    • publish on a private server with base URL http://localhost:7081/<username>
    • use username and password

Step 6 will publish one local iCal calendar to the sub-calendar <username>:<calname> on a Sun Calendar server. I have not yet tested to publish to the main calendar --I do use my main calendar for work and did not want to mess it up :)-- but it should work by entering <username> as the publishing name or leaving it blank. If you are getting Error 29 --turn on debugging to log the exchanges with the Sun Calendar server--, check for typos in the Publish window, check whether the sub-calendar was created earlier on the Sun Calendar server side.

Please use the comment section below for sharing about your usage of icalds and/or reporting issues.

Join the discussion

Comments ( 8 )
  • Frederic Pariente Thursday, September 10, 2009

    chrid reported that icalds stopped working with Mac OS X 10.6 aka Snow Leopard, with the following error message : Can't locate Crypt/SSLeay.pm in @INC

    I have not upgraded myself to 10.6 yet --does not bring much, I'm told, and smart groups in Address Group are even more broken than before :(-- but I have a German colleague that did. I hope he can have some time for you to try to reproduce the problem.

    It may simply be an issue of the 10.6 upgrade wiping out the Perl updates that you had performed in Step 2 of the icalds installation. Try re-downloading the SSL module and re-running CPAN. Please post here if that solves it. Thanks.

  • chrid Friday, September 11, 2009

    could it be that the SSL module disapeared from that location

  • Frederic Pariente Friday, September 11, 2009

    You should be able to download it from http://search.cpan.org/dist/Crypt-SSLeay/ or directly thru the CPAN Perl interface, I'm guessing --sorry, I am no regular Perl programmers either :)

  • chrid Friday, September 11, 2009

    hi frederic,

    i followed instructions in here and now it seams to work again

    i installed both new the io and the ssl ....

    thx for help

  • Dominique Launay Thursday, August 26, 2010

    Hello Frederic,

    My iCal never ask for user/password when I subscribe to my calendar.

    Dis I miss something ?

  • Frederic Pariente Monday, August 30, 2010

    Could it be that you were asked a password already and it is saved in your Keychain? I've experienced that MacOS does not necessarily re-ask for password if you've stored a wrong / outdated password. Go to Utilities > Keychain Access and delete all stored passwords for Internet / localhost.

  • chrid Sunday, January 30, 2011

    hi frederic,

    i bought a new macbook and reinstalled everything. it woks but just i have a timezone problem as it seems that everything is one hour early.

    any simple trick where i could change this.


  • Frederic Pariente Monday, January 31, 2011

    I'd check 3 things:

    (1) is time zone support enabled in iCal? see the Advanced tab in Preferences.

    (2) is the timezone selected on your laptop the same as the one on the server?

    (3) could it be a DST setting mismatch? Just one hour also hints to the summer vs winter time issue.

    HTH, Frederic.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.