Some of you have already noticed, so this makes it official. We have done a soft launch of our exchange support for MooseSync. This version supports only basic/realm authentication (i.e. if you get a little dialog pop up when you want to log in to the web/OWA version of your email). Forms authentication will be later this week.
With this release, MooseSync will monitor your exchange server and publish your primary exchange based calendar to the Google calendar of your choice. That means even when you are offline, Google remains up to date. There is no Outlook requirement, so if you use the OWA (web) interface to exchange, use a third party client, or are primarily a Windows Mobile/Blackberry/iPhone user, this is ideal.
The public beta is free, so we would love to hear your feedback. I have personally been using it for about a week without issue.
I am trying to use the exchange option but not having much luck. Is there anything I am missing?
Posted by: Jim | September 24, 2007 at 12:09 PM
Hi Jim,
Drop me a line at support@2glue.com and I bet we can get you unstuck.
(Thanks for giving us a try, BTW.)
-Brian
Posted by: Brian | September 24, 2007 at 01:15 PM
What prevents you from reading other people's emails when they setup their MS Exchange Server?
Posted by: bob | October 03, 2007 at 02:33 PM
I'm not having luck with the Exchange option. I get the message "Property [username] of class [class UpdateExchangeCommand] with value [] does not pass custom validation"
When I use the 2003 option, all I see is "busy" appointments in GCal - no other info. Is that what I'm supposed to see?
Posted by: Tina | October 09, 2007 at 12:11 PM
Hi Tina,
Yes unfortunately all Outlook 2003 and earlier publishes is FreeBusy information (basically all it sends is a list of times you are not available). To get better info you can either upgrade to 2007 or use our Exchange integration.
Drop me a line at support@2glue.com on the problems you're having with the exchange signup and I bet we can get it resolved.
-Brian
Posted by: Brian | October 09, 2007 at 04:29 PM
You should be using certificates on your website for security. Not using SSL is a bad idea. I'll not pass passwords through non-encrypted sites.
Posted by: Dave | October 13, 2007 at 04:44 PM
I got a Grails Runtime Exception. I used "Domain\username" as the user name.
Posted by: Bharat | December 30, 2007 at 10:42 PM
"Forms authentication will be later this week."
I take it this never happened -- this product isn't still under development, isn't it? The publishing mechanism is clever, though I sure would love to have bidirectional sync in the cloud.
Posted by: Tim Smith | January 10, 2009 at 06:07 PM