You can find the packages on the download pages of the Kolab Sync for Outlook und Kolab Sync for Android projects.

Please use the issue trackers there for feedback.

Using this software you will be able synchronize your contacts and calendar to any IMAP folder. Every item is saved in a separate Email using the Kolab Storage Format. This allows for interoperability with other Kolab Clients.

Please join us on the Google code projects for the Android and the Outlook connectors.

Since there are still quite a few rough edges, this is only a developer preview to publish the already done work. Read on for a more detailed status of the development so far.

Status

• Sync Infrastructure: although the two projects are written in Java and C#, they share the basic algorithms and principles of operation. This groundwork is also shared between the addressbook and contacts synchronizers of each project. This is already stable. Some edge cases still require a second synchronization run to converge.
• Addressbook Synchronization: being the easier part of the two, this is mostly finished and working.
• Calendar Synchronization: Arthur is currently implementing the last piece here: reading and writing of recurrences.
• Managing Edit Collisions: If two copies of the same item are edited and then synchronized, there is no easy way to automatically manage the merge. On the Android the server item always wins. For the Outlook plugin we plan on implementing a conflict resolution dialog where the user can pick and choose from the conflicting items.
• Managing Duplicates: When starting to use synchronization tools, users often end up with multiple copies of the same entries (especially in the addressbook) when multiple data sources are added. Currently the only way to work around this problem is to use a third-party duplicate-detector or wipe all but one device clean before synchronizing. A way to handle this could be added similar to a edit conflict resolver.
• Multiple Calendars, multiple IMAP Folders: planned.
• Testing: Currently there are only manual test routines.

[2009-10-16 15:02:09 - ddms]Failed to reopen debug port for Selected Client to: 8700
[2009-10-16 15:02:09 - ddms]Address family not supported by protocol family: bind
java.net.SocketException: Address family not supported by protocol family: bind
	at sun.nio.ch.Net.bind(Native Method)
	at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
	at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
	at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
	at com.android.ddmlib.MonitorThread.reopenDebugSelectedPort(Unknown Source)
	at com.android.ddmlib.MonitorThread.run(Unknown Source)

[2009-10-16 16:29:40 - ddms]Can't bind to local 8600 for debugger
[2009-10-16 16:30:14 - ddms]Can't bind to local 8601 for debugger
[2009-10-16 16:30:14 - ddms]Can't bind to local 8602 for debugger
[2009-10-16 16:30:15 - ddms]Can't bind to local 8603 for debugger
[2009-10-16 16:30:25 - ddms]Can't bind to local 8602 for debugger
[2009-10-16 16:30:25 - ddms]Can't bind to local 8606 for debugger
[2009-10-16 16:30:25 - ddms]Can't bind to local 8607 for debugger
[2009-10-16 16:30:25 - ddms]Can't bind to local 8610 for debugger

As it turns out, the debugger tries to connect to “localhost” which is resolved by Windows Vista via the Windows\System32\drivers\etc\hosts file, which contains the IPV6 address “::1″. Since Android’s IPv6 support is still under development, none of the development tools can cope with it, resulting in above error messages.

Substituting the IPv4 127.0.0.1 as localhost address made it work fine.