Importing ICAL ics files into Zarafa - Revision history

Decramy: ical & GMT

2010-09-07T16:19:01Z

ical & GMT

← Older revision		Revision as of 16:19, 7 September 2010
Line 1:		Line 1:
	This page describes the import of ICal calendar files into Zarafa via the zarafa-ical gateway.		This page describes the import of ICal calendar files into Zarafa via the zarafa-ical gateway.
		+
		+	<FONT COLOR=RED>Hint:</FONT> Ical will handle all timestamps in the .ics as GMT. Remember this if your appointments dont start at the correct time.

	For the import of the ICal ics files we will use curl. The curl package will be installable on most linux distributions via the default repositories.		For the import of the ICal ics files we will use curl. The curl package will be installable on most linux distributions via the default repositories.

Robin at 14:13, 15 March 2010

2010-03-15T14:13:15Z

← Older revision		Revision as of 14:13, 15 March 2010
Line 36:		Line 36:
	If you want to import calendars to different calendars then the default calendar, use:		If you want to import calendars to different calendars then the default calendar, use:
	<pre>		<pre>
-	curl -u [username]:[password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]	+	curl -u [username]:[password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]/
	</pre>		</pre>
	Or if you want to import to a subfolder of a yet existing calendar (in the next example we import to a subfolder of a calendar named "Calendar"):		Or if you want to import to a subfolder of a yet existing calendar (in the next example we import to a subfolder of a calendar named "Calendar"):

Msartor at 17:02, 13 November 2009

2009-11-13T17:02:39Z

← Older revision		Revision as of 17:02, 13 November 2009
Line 62:		Line 62:
	server_socket = http://localhost:236/zarafa		server_socket = http://localhost:236/zarafa
	</pre>		</pre>
		+
		+
		+
		+
		+
		+	<FONT COLOR=RED><b>Compatibility issue: </b></FONT>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.

Msartor at 14:44, 6 July 2009

2009-07-06T14:44:28Z

← Older revision		Revision as of 14:44, 6 July 2009
Line 58:		Line 58:


-	<FONT COLOR=RED>'''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:'''</FONT>	+	<FONT COLOR=RED>'''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:'''</FONT>
	<pre>		<pre>
	server_socket = http://localhost:236/zarafa		server_socket = http://localhost:236/zarafa
	</pre>		</pre>

Msartor at 14:44, 6 July 2009

2009-07-06T14:44:05Z

← Older revision		Revision as of 14:44, 6 July 2009
Line 56:		Line 56:
	curl -u [username]:[any password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]		curl -u [username]:[any password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]
	</pre>		</pre>
		+

	<FONT COLOR=RED>'''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:'''</FONT>		<FONT COLOR=RED>'''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:'''</FONT>

Msartor at 14:43, 6 July 2009

2009-07-06T14:43:10Z

← Older revision		Revision as of 14:43, 6 July 2009
Line 57:		Line 57:
	</pre>		</pre>

-	<FONT COLOR=RED>'''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 to:'''</FONT>	+	<FONT COLOR=RED>'''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:'''</FONT>
	<pre>		<pre>
	server_socket = http://localhost:236/zarafa		server_socket = http://localhost:236/zarafa
	</pre>		</pre>

Msartor at 14:42, 6 July 2009

2009-07-06T14:42:26Z

← Older revision		Revision as of 14:42, 6 July 2009
Line 51:		Line 51:
	</pre>		</pre>
	After this change restart the zarafa-ical service.		After this change restart the zarafa-ical service.
-
-	~~<FONT COLOR=RED>'''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.'''</FONT>~~

	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:		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:
	<pre>		<pre>
	curl -u [username]:[any password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]		curl -u [username]:[any password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/[calendar name]
		+	</pre>
		+
		+	<FONT COLOR=RED>'''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 to:'''</FONT>
		+	<pre>
		+	server_socket = http://localhost:236/zarafa
	</pre>		</pre>

Msartor at 14:39, 6 July 2009

2009-07-06T14:39:53Z

← Older revision		Revision as of 14:39, 6 July 2009
Line 11:		Line 11:
	apt-get install curl		apt-get install curl
	</pre>		</pre>
		+

	With curl you are able to import ICal ics files into Zarafa. Before you do this, you need to make sure that the zarafa-ical service is started:		With curl you are able to import ICal ics files into Zarafa. Before you do this, you need to make sure that the zarafa-ical service is started:

Msartor at 14:39, 6 July 2009

2009-07-06T14:39:25Z

← Older revision		Revision as of 14:39, 6 July 2009
Line 1:		Line 1:
		+	This page describes the import of ICal calendar files into Zarafa via the zarafa-ical gateway.
		+
		+	For the import of the ICal ics files we will use curl. The curl package will be installable on most linux distributions via the default repositories.
		+
		+	On Centos/Redhat:
		+	<pre>
		+	yum install curl
		+	</pre>
		+	On Ubuntu/Debian:
		+	<pre>
		+	apt-get install curl
		+	</pre>
		+
	With curl you are able to import ICal ics files into Zarafa. Before you do this, you need to make sure that the zarafa-ical service is started:		With curl you are able to import ICal ics files into Zarafa. Before you do this, you need to make sure that the zarafa-ical service is started:

Line 37:		Line 50:
	</pre>		</pre>
	After this change restart the zarafa-ical service.		After this change restart the zarafa-ical service.
		+
		+	<FONT COLOR=RED>'''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.'''</FONT>

	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:		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:

Msartor at 11:44, 6 July 2009

2009-07-06T11:44:32Z

← Older revision		Revision as of 11:44, 6 July 2009
Line 28:		Line 28:
	curl -u [username]:[password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/Calendar/[calendar name]		curl -u [username]:[password] -T [path to ics file] http://[zarafa-ical-server]:8080/ical/[username]/Calendar/[calendar name]
	</pre>		</pre>
		+

	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.		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.