[Kolab-devel] Re: Groupware object storage specfication

[Bo Thorsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart Bingë <list at codefusion.co.za> asked:

<quote>
I'm wondering where I could get some information regarding the storage 
format of the Kolab groupware objects - not the format of the actual data 
(such as an iCalendar block) but rather the format of the IMAP mail 
message that contains the object. I've checked the Kolab architecture 
documentation, however the format described in that document seems to 
differ from that which the KDE client uses.

Is there perhaps an updated specification where one can get the proper 
storage standard, or is the architecture document on the Kroupware pages 
the definitive source? This is in relation to the webclient - I'm not 
entirely sure what the 'correct' format is in which to save the messages, 
however I would like to ensure that the messages the webclient produces 
are correct (i.e. interoperable with other clients) before submitting the 
Kolab drivers to the Horde project.
</quote>

The IMAP resource saves the iCalendar contents directly in the mail and 
sets Content-Type to text/calendar. Here is an example from my IMAP 
Calendar folder:

<plaintext>
Content-Type: text/calendar;
  method=REQUEST;
  charset="utf-8"
From: Bo Thorsen <bo at sonofthor.dk>
Reply-To: 
Bcc: 
X-KMail-Fcc: sent-mail
To: 
Subject: iCal KOrganizer-938892849.824
Date: Mon, 23 Feb 2004 16:43:28 +0100
User-Agent: KMail/1.6.51
X-UID: 294
Status: RO
X-Status: O
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  

BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML KOrganizer 3.3 pre//EN
VERSION:2.0
METHOD:REQUEST
BEGIN:VEVENT
DTSTAMP:20040223T164328Z
ORGANIZER:MAILTO:bo at sonofthor.dk
CREATED:20040223T164328Z
UID:KOrganizer-938892849.824
SEQUENCE:0
LAST-MODIFIED:20040223T164328Z
SUMMARY:Borgermøde om kloak
CLASS:PUBLIC
PRIORITY:3
DTSTART:20040302T190000Z
DTEND:20040302T210000Z
TRANSP:OPAQUE
END:VEVENT

END:VCALENDAR
</plaintext>

It's possible that we will change this to be a multipart mime message 
later. This would give us more flexibility. But for now we will stay with 
this way.

Note that the IMAP storage in KMail can read the multipart mime messages 
already, it just doesn't store it this way. If it sees a message with 
mime parts, it will go through all of them and see which one has an 
iCalendar part and use that one.

Bo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFARxI2mT99lwfUS5IRAsE3AKDPht5uI8dWg3Jh21Z6X4/stN+gHACffpUq
I8RZmj79OgEind9WQOF84vU=
=McaQ
-----END PGP SIGNATURE-----