-(NB: Don't use the C syncfolder tool yet; use the shell scripts)
=======================
0. AUTHENTICATION
-Authentication can be either with Kerberos or NTLM. If you have Kerberos
-set up (it's easy to do), then just having a valid ticket will suffice.
+Kerberos authentication doesn't work with libsoup. NTLM only kind of
+works -- it needs you to provide the password directly, and can't just
+delegate to the Samba/winbind 'ntlm_auth' helper.
-If you want to use NTLM, you have to pass your userid and password to the
-scripts on the command line. NTLM is faster, especially for the first sync.
+You also have to provide your full DOMAIN\username on the command line.
+
+ https://bugzilla.gnome.org/587145
+ https://bugzilla.gnome.org/624613
=======================
3. SYNCHRONISE CALENDAR
- $ ./syncfolder.sh $EWSURL $USERNAME $PASSWORD
+ $ ./ews_syncfolder $EWSURL $DOMAIN\\$USERNAME $PASSWORD
This should fetch all calendar items from the Exchange server and convert
-them into ical files in ~/ews-sync/ical/. It will also combine them all
+them into ical files in ~/ews-sync/. It will also combine them all
into a single ~/ews-sync/all.ics file. You can put this file on a web
server and point Evolution at it as an 'On The Web' calendar, etc.
-Run this from cron (you'll want to be using Kerberos, not leaving your
-password lying around in scripts), and put the resulting file somewhere
-web-accessible, and you have an automatically-updating copy of your Exchange
-calendar which you can use from Linux.
+If libsoup supported Kerberos (or even delegated NTLM properly), you
+could run this from cron. Or if you didn't care about leaving your password
+lying around in shell scripts. But you wouldn't be that silly, right?