If the calendar does not exist yet, the last example will not work when using a zarafa-admin user. This needs to be done as the user itself. There is a workaround however if you need to do some massive scripting on this and you don't know the users' passwords.

You will need to run the zarafa-ical service and zarafa-server on the same host and the zarafa-ical service needs to run as root. Change the server_socket in /etc/zarafa/ical.cfg to:

server_socket = file:///var/run/zarafa

After this change restart the zarafa-ical service.

You can now import calendars (both to default calendars and to calendars that need to be newly created) as the user. But now the zarafa-ical service will accept any password as the users' password as long as it is not empty:

Important: Revert the server_socket back to it's original setting before going into production, as setting the server to a unix socket creates a security leak. So edit the file /etc/zarafa/ical.cfg and change server_socket back to:

server_socket = http://localhost:236/zarafa

Compatibility issue: Importing large ics files with Zarafa 6.40 beta fails. Tested this on Centos 5.4 Final with stock curl version and latest compiled curl version. Thanks to the community for this input.