Sync Kolab

SyncKolab was written to add kolab functionality to thunderbird. It reads a selected Imap folder and synchronizes it with the local address book (and calendar in the future). It is currently under heavy development, so use with care!
It has been tested under Thunderbird for Windows, Linux and MacOSX.
For up-to-date information and most recent version, check out my regular homepage at www.gargan.org
Version 2.0 has tons of bugs fixed, a easier to understand configuration and autosync support - meaning you dont have to run a sync - when you do a change the imap folder is automatically updated and the other way round
Version 1.5 pushed the synckolab to full Thunderbird 3 and Lightning 1 support and finally includes all fields including mailing lists and photos.
Version 1.0 had 61 prereleases and 83 nightly releases with over 100 bugs fixed and is known to work nicely with Thunderbird 2 and Lightning 0.8.
Even with this extensive testing, there might still occur problems in combination with other extensions, operating systems, thunderbird versions and/or special characters in your contacts/tasks/calendar entries .
Because of this, you should make a backup of all your relevant data (server side or your profile directory) before doing your first sync. If seomthing happens because of a bug you can then easily restore your data afterward.

What is Kolab?

It loads all your contacts (from a selected address book), and synchronizes them with a selected imap folder. Where every contact is stored as an vcard. In the next version I also want to include calendar Entries (vCal)... For more information http://kolab.org/
The idea behind is, that you can now have your contacts+calendar entries stored on the imap server. so you can actually have the same addresses on more than one computer. The kolab project has a groupware server that uses imap to exchange calendar entries and vcards.

Server Requirements

IMAP server with read/write access
seperate IMAP directories for adress book/calendar

No KOLAB server?

No. A Kolab server is not required.

So why call it syncKOLAB?

Basically because the idea of using imap as central storage comes from the kolab guys.

What does the kolab server do then?

1.) Its a full collaboration server with loads of additional feature you know from ie. exchange (like free/busy management, shared folders, invites....)
2.) the whole group, right etc. mangement
loads of other small thngs you would expect a kollaboration server to do :)

So do I need the kolab server?

If you want full collaboration in your company/group - YES... if you didnt need it until now and only want to sync your data over multiple maches - or just have a simple shared calendar/adress book with a few buddies - no. you can happily live with just your imap server :)

SyncKolab Nightly

You can get a nightly build at synckolab NIGHTLY (rightclick).

Beware that this may easily break all you contacts/calender entries, altough we try to create stable nighlies.
So create a backup of your thunderbird profile folder before trying it out!

	-- no nightly since 2.0.2 yet

Status of the Kolab Extension

mailing list support
Allow Sync with file system
Add support to new thunderbird adress book features (ie. mac adress book support)
Better support of lightning features (free/busy)
support for notes (either through Message Notes or Notary)

Want to help out?

Best thing you can do is get the most recent release, subscribe to the mailing list and ask what needs to be done (also take a look at the known bugs section). There is especially a lot of plain testing required. Since the extension is pretty new there are people needed who can test the extension on different Operating Systems, with some combinations of contacts (if all fields are transferred correctly) and so on...

You may aquire the current source code from the mozdev cvs, or get it directly from the xpi (simply unzip the latest xpi found on gargan.org you will find all source files in there (js).

How does synckolab work?

For those interested here is a short explenation (pretty technical) on how Sync Kolab actually works.

get a list of all messages in the imap folder (only headers, which are cached locally. Thunderbird also makes sure that new messages are included)
check each message header with a local database of the previous sync for a change. Message size, date and subject are used there (subject is the key value)
if something changed or the message is new, download the message and strip everything except the message body (xml/ical/vcard). Save this part in the local sync database (=the file system)
parse the message body into a adress book card/calendar event/task (lets call it CUR)
get the id from CUR and check the local address book/calendar if there is an entry with the same id (lets call it ENTRY)
if we did not find an ENTRY, save CUR in the adress book/calendar and continue
if we found an ENTRY, make a comparison between CUR, ENTRY and LOCALDB (the entry stored in the local sync database (file system) from a previous sync)
- if CUR=LOCALDB but ENTRY!=LOCALDB -> we know we changed something locally (ie. changed the name) so update ENTRY on the server (update=delete and readd), also update the LOCALDB on the filesystem
- if CUR!=LOCALDB but ENTRY=LOCALDB -> we know the server entry changed, so we have to update ENTRY and LOCALDB
- id CUR!=LOCALDB!=ENTRY -> we know we have a local change AND soemone changed the server entry -> ask what we should do
- if CUR=LOCALDB but ENTRY is missing -> we know it has been deleted locally, so delete the entry on the server
remember all entries already processed (so we dont check it twice)
now go through all local entries (ENTRY) (except the one we already processed) and check:
- if ENTRY is in LOCALDB: delete it (means it has been deleted from the server since the last sync)
- if ENTRY is not in the LOCALDB: add it to the imap server
finish up (liek make all new messages unread, and run compact to make sure its all on the server)

A few Remarks:

if you uncheck "write to IMAP", nothing will be written on the imap server. So whatever you change locally (delete/modify entries) will result in messages "update on server" or "delete on server", but that wont happen. Next sync you will get "delete locally" "update locally" messages (since nothing changed on the server, but locally you had changed). This is because the sync DB needs two syncs to be in sync again
the "ignore entries older than XXX" applies for the timestamp on the messages AND for the calendar entries (enddate is used there). -1 will just sync all entires
the sync interval set to 0 will still produce debug messages (like "starting sync...") which is only an indicator that the check for an interval is working (should happen once a minute) - nothing is syncd if this is the only message
If you delete the snyc db from the filesystem (synckolab folder). Synckolab will try to resolve all differences automatically or ask you (will probably result in lots of "locally updated" messages)
If you have problem (especially entries which are not synced at all or wrong) make sure to check in the javascript Error-Console (Fehlerkonsole) for messages. Until 1.0 debug is FULLY enabled to help track problems. There is also a pause button available that helps you track problems.

In the wild...

I started a few threads around the globe on different sites during development. If you are interested in some insight you can check them out.

My homepage can be found in www.gargan.org including a mirror of this + some other usefull things

This one is for those who have ideas on how I overcome some of my biggest problems: open a tb message in read/write mode
Antoher problem I ran into (which could have been avoided if the rewrite stuff had worked): Copying mail folder content from temp folder to imap I took some of the code from the TB Attachment Tools and TB Header tools for the writing of messages. You can get those pretty usefull extensions from Frank DiLecce (Ausdilecce).