Kolab uses IMAP as an underlying protocol for email, contact, and calendar entries. These entries are saved in IMAP folders in Kolab XML format, and the IMAP server controls storage and access rights. Configuration and maintenance of Kolab is done by LDAP.
Kolab Clients and the Kolab server use well established protocols and formats for their work (i.e. IMAP as mentioned above, vCard, iCal, XML and LDAP). This allows the Kolab Format specification framework, or even portions of it, to be utilized as an open set of specifications for groupware clients and servers to communicate with each other. Third party implementations began almost immediately; for example, the Citadel groupware server began supporting version 1 of the Kolab Format specification in March 2004.[2]
The concepts on which Kolab relies are laid out in the Kolab Format Specification and Architecture Paper[3] for Kolab 2, and for Kolab 1 in the Kroupware Contract, Architecture Paper and Technical Description.[4]
SyncKolab[4]Archived 2020-01-25 at the Wayback Machine,[5] starting with version 3.0.0, is a Mozilla Thunderbird/SeaMonkey and Lightning extension (Free Software);
Kolab Desktop Client is a stabilized and professionally supported version of KDE Kontact.
evolution-kolab (integrated in GNOME / Evolution since v3.4, see,[6][7]) extends GNOME'sEvolution and EDS (Evolution-Data-Server) to be a full-featured Kolab-client (Free Software)
Kolab's integrated Horde also provides a SyncML interface, over which SyncML-capable mobile phones can synchronise PIM-data on a Kolab-server (Free Software)
Z-Push (integrated in Kolab since v2.3.0) enables ActiveSync-capable clients to access their server mailboxes and to use Kolab-provided PIM-functionality (Free Software)
Kolab-WS extends Kolab to provide Kolab-functionality as a web-service; Kolab-WS was originally part of Syncphony, which utilises Kolab-WS since their split (Free Software)
Syncphony (initially "kolab-sync") connects Kolab-WS with a Funambol sync-server, thus enabling devices supported by Funambol to synchronise their PIM-Data with a Kolab server (Free Software)
kolab-android[8] synchronises Android's addressbook and calendar to IMAP-folders in the Kolab2 format (Free Software)
Kolab 3.0 was released,[14] featuring the improved Kolab 3 format based on xCard and xCal, the Roundcube web-client, a new ActiveSync component called Syncroton and other new properties.
Kolab Now hosted solution was launched. It lets customers create individual accounts or managed domain accounts, with the possibility to move data to a self-hosted Kolab 3 installation any time. The service is operated by Kolab SystemsArchived 2013-11-08 at the Wayback Machine in Switzerland.
2012:
evolution-kolab had its first release as part of the GNOME initiative in Evolution 3.4.[15]
SyncKolab was massively overhauled and released as version 2.0 for Thunderbird / SeaMonkey (optionally with Lightning for calendaring and tasks).[16]
evolution-kolab was vastly enhanced and had its second release as part of the GNOME initiative in Evolution 3.6.[7]
SyncKolab 3.0 was largely rewritten, yielding speed and feature improvements, and now supports the Kolab 3 format.
2011:
Kolab 2.3.0 was released, containing many updated core components and other improvements, the new Z-push synchronization for clients using ActiveSync (in addition to the already existing SyncML support) and an overhauled web-based administration front-end.
Kolab 2.3.1 was released shortly thereafter, as a bugfix release.
Kolab 2.3.2 was released as a regular maintenance release of the Kolab 2.3 branch, with updated Postfix and Z-push components.
Kontact 2 was released[17] next to KDE SC 4.6.4, with many improvements related to Kolab.
evolution-kolab was released, which extends GNOME's Evolution and EDS (Evolution Data Server) to become a full-featured Kolab client.
Kolab 2.3.3 was released, providing a lot of bugfixes for the Horde components and many updated base components (Apache, Cyrus IMAP, OpenLDAP, OpenSSL and PHP).
Kolab 2.3.4 was released as a bugfix release.
Kolab-WS was split out of Syncphony as a standalone web service, providing Kolab functionality. Hence Syncphony solely becomes a Funambol connector.
2010:
KolabiPhone,[18] a Kolab sync connector for the iPhone, had its first pre-alpha release.
Two new Free Software Kolab sync connectors for Android and Outlook were announced[19] and their first alpha releases published.[20][21]
Syncphony was released, which extends Kolab with a Funambol connector and offers Kolab functionality as a web service.
SyncKolab 1.5 for Thunderbird 3 / SeaMonkey 2 (optionally with Lightning 1.0 beta for calendaring and tasks) was released.
Kolab 2.2.4 was released as a maintenance release of the Kolab 2.2 branch.
Kontact Touch was released,[22] offering full Kolab functionality on mobile devices, such as smartphones and tablets.
2009:
Kolab 2.2.1 was released, as an enhancement and maintenance release, integrating an updated web client (Horde) and preliminary SyncML support.
Kolab 2.2.2 was released, as a maintenance release of the Kolab 2.2 branch.
Kolab 2.2.3 was released, further enhancing functionality, stability and scalability of the Kolab 2.2 branch.
2008:
SyncKolab 1.0 for Thunderbird 1.5 and 2.0 as well as SeaMonkey 1.0 and 1.1 (optionally with Lightning 0.9 for calendaring and tasks) was released.
Kolab 2.2 was released, with full support of multiple mail domains, integrated Horde web front-end, updated base packages (OpenPKG, OpenLDAP, Cyrus IMAP, Postfix, Perl, Apache, PHP, etc.), easier integration in operating system distributions, and many other new features.
2007:
Kolab 2.1 was released.
A third Outlook connector was released.
2006:
Kolab 2.1 was designed with many significant enhancements over 2.0.
2005:
KolabSyncML[23] ("Sync4j Kolab Connector / SyncSource"), a Kolab Java interface and Funambol connector,[24] had its first alpha release.
Kolab 2.0 was released.
A second Outlook connector appeared on the market.
The SyncKolab project started developing a Mozilla Thunderbird / SeaMonkey and Lightning connector.
2004:
Aethera became a Kolab 1 groupware client.
Citadel/UX learned how to mimic a Kolab 1 groupware server.[25]
Kolab 2 was designed as a general overhaul and implemented utilizing the versatile and extensible Kolab Open Format[3] to store groupware data.
Kolab 1 / Kroupware was designed[4] utilizing iCal and vCard formats to store calendar entries, contacts, notes, tasks etc. in Kolab's IMAP directories.
