v2.2.0 has been released today. The most important feature in this release is oAuth support. There are a bunch of bug fixes related to CardDAV and Google synching as well.

Go grab the latest release from the Downloads page!

v2.2.0-rc1 has been released today. This release supports oAuth support for Google Contacts. Make sure you go through the README file for gdata-oauth2.

Go grab the latest release from the Downloads page!

v2.1.0-rc2 has been released today.

1. This release supports like-pair synching. This means you can now use ASynK to copy contacts from one google account to another. As always this copy/synchronisation works at a Folder level, so you could synchronize your My Contacts from your Work email address to a specific folder in your personal Gmail account.

Go grab the latest release from the Downloads page!

v2.0.0 has been released today.

1. It includes MS Exchange support - see notes below for the -rc1 release. The present release includes all of those plus some minor bug fixes.
2. Bug Fix: Fixes a long standing bug in Google's contact API that was preventing contact udpates from being posted. If you were facing errors in synching to google contacts, you should be interested in this release.

Go grab the latest release from the Downloads page!

v2.0.0-rc1 with Experimental support for Microsoft Exchange server has been added to ASynK and just released. Key notes for this work:

1. It has been tested with Exchange Online / Office 365. However it should work with Exchange Servers 2007_SP1 onwards.
2. This release incudes a new submoduel. Ensure you fetch the code for that repo as well.
3. There are some additional python package dependencies that have been added. Install the dependencies in the requirements.txt file.
4. The config.json format has changed to accomodate the requirements of a new datastore. Your config will be seamlessly upgraded to the new format

Release v1.0.0 - With support for CardDAV. Key notes for this work:

1. It has been reported to work with the following servers:
   1. Apple CalendarServer
   2. Baikal
   3. OwnCloud.
2. The config.json format has changed to accomodate the requirements of a new datastore. Your config will be seamlessly upgraded to the new format

Experimental support for CardDAV servers has been added to ASynK. As this is still an early release the code lives in a separate branch on github. You can view and checkout the code here: https://github.com/skarra/ASynK/tree/carddav. Key notes for this work:

1. It is only tested with Apple's Calendar Server on my local Mac with a few test BBDB files . I would love to hear how this works with other carddav servers out there.
2. The new branch on the git repo has a bunch of new git submodules. If you are an existing user of ASynK, I would recommend you checkout a fresh copy of the carddav branch for your initial trials.
The config.json format has changed to accomodate the requirements of a new datastore. You should copy the config.json from the asynk source directory manually to your asynk user dir. This step will be automated at a later time before official release.
3. The CardDAV protocol does not have a batch write operation - but has a batch read method - which means that writing lots of contacts to a remote server may be slow - much slower than synching to a google contacts server using ASynK. This situation will not change unless something changes with the WebDAV protocol.

We have just pushed release v0.4.1 out. Key changes are:

1. Double-quote and newline characters in many fields are now quoted before being written to BBDB.
2. sync_dir profile config was when set to SYNC1WAY was being ignored; same was case with the conflict_resolve config variable
list-folders operation was not working with BBDB data stores
3. folder name field was getting written to BBDB multiple times
4. You can create new profiles to non-existent BBDB datastores; files will get created on sync.
5. Outlook backend was having issues with the BBDB timestamp format. Fix so BBDB<->Outlook sync works.
6. A bunch of errors flagged by pychecker static analysis have been fixed
7. A bunch of bugs fixed in handling of the 'affix' BBDB field and synching it to and from google google

Go grab the latest release from the Downloads page!

We have just pushed release v0.3.0 out. Key changes are:

1. ASynK now ships with two default sync profiles called: "defgcbb" and "defgcol", so there is out of the box support for what should be the most common use cases - synching entire ~/.bbdb or outlook contacts folder with google contacts. (Thanks to John Wiegley for the idea)
2. ASynK now uses ~/.asynk/ as the directory to store all state information, logs and backups. Thus you can now have a single installation of ASynK for all users in your system, and they will each get .asynk/ directory in their home directories. If you have any existing sync profiles and state, ASynK will notice this, and migrate your current sync state to the ~/.asynk/ directory. You can override the default directory name by passing the --user-dir command argument to any invocation of ASynK. (Thanks to Ivan Miljenovic for the idea)
3. ASynK can now be invoked from anywhere; earlier you had to ensure the present working directory was the root of the asynk source directory. (Thanks to Ivan Miljenovic for the idea)

   Important Note: The above two changes together imply that if you have existing sync state you want migrated, the first run after your upgrade to v0.3.0 should be from inside ASynK directory for us to be able to locate your config and state. Subsequent runs can be done from anywhere and we will pick up your stuff from ~/.asynk/

4. Bug fix: Google Contacts' multiple group membership information is now correctly synched back and forth to BBDB and Outlook.
5. Bug fix: The first email address in the BBDB email list is treated as the primary address, and marked accordingly in Google Contacts. Without this the order the email addresses in BBDB could have appeared random, and changing from one sync to another.

Go grab the latest release from the Downloads page!

We have just pushed release v0.2.2 out. Key changes are:

1. Now Item deletions are synched. i.e. if you have a sync profile set up between Google folder and a Outlook folder, say, and you delete a contact in Google, the next time you sync that entry will be deleted from the corresponding Outlook folder as well.

   For this to work correctly, it is recommended that you do a full sync of all your configured profiles once - note that a dry run is not sufficient.

2. Log files older than 7 days will be cleared every time asynk is executed - except if it is a dry run. The duration can be configured in config.json by changing the 'log_hold_period' parameter.
3. BBDB Backup files older than 7 days will cleared every time asynk is executed - except if it is a dry run. The duration can be configured in config.json by changing the 'backup_hold_period' parameter.
4. Misc bug fixes

Go grab the latest release from the Downloads page!

We have just pushed release v0.2.1 out. Key changes are:

1. BBDB file format 6 is now supported - with an important caveat - Please refer to the Dependencies section of the documentation. BBDB file format 6 is used by BBDB versios 2.x bundled with XEmacs.
2. Attempt is made to parse the BBDB file with multiple encodings - for now utf-8 and latin-1. Additional encodings can be specified in the config.json config file.
3. Building documentaiton from source is now trivial, and does not need autotools
4. Instant Messaging fields are now synched across all sources
5. Better error recovery in case of parse error with BBDB store
6. Bugs fixes dealing with fax, notes, and company fields in BBDB and Google Contacts

All in all an exciting release if you are a BBDB user! Go grab the latest release from the Downloads page!

We have just pushed release v0.2.0 out. Go grab the latest release from the Downloads page!