mrubinsk  Mon, 14 Nov 2011 14:35:32 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  112
Change log:  Be consistent

@@ -57,9 +57,9 @@
|| HP !WebOS || 2.1.0 || Yes || ? || Contacts, Calendar, Tasks are working, for SSL with a private certificate you have to trust the certificate in the browser || || HTC Desire Z / HTC Desire HD || 2.2 || ? || ? || Contacts and Calendar via native !ActiveSync, SSL untested || || HTC Desire S || 2.3.3 || ? || ? || Contacts and Calendar via native !ActiveSync, SSL ok ||
 || HTC Magic || Android 2.2.1 unbranded || ? || ? || Contacts, Calendars ||
-|| iOS Devices || 3.1.3 -> 4.3.5 || Yes, with Bugs. Certain versions of iOS - 4.3(8F190) for one, go into a provisioning loop due to a bug in iOS (it continues to send the OLD X-Ms-Policykey value after it receives a new one). || Yes || Contacts and Calendar || +|| iOS Devices (iPhone, iPad, iPod) || 3.1.3 -> 4.3.5 || Yes, with Bugs. Certain versions of iOS - 4.3(8F190) for one, go into a provisioning loop due to a bug in iOS (it continues to send the OLD X-Ms-Policykey value after it receives a new one). || Yes || Contacts and Calendar || || iOS Devices (iPhone, iPad, iPod) || 5.0 || Yes || Yes || Contacts and Calendar, and basic support for Tasks via the Reminders App. || || Motorola Droid || 2.0.1, 2.1, 2.2, 2.3 || No (See above) || No native support, but the //Corporate Directory// app in the Marketplace works well. || Contacts and Calendar data. On Froyo/2.2 SSL connections will NOT work with a self signed certificate even if the "Accept All Certificates" checkbox is selected. See http://www.google.com/support/forum/p/android/thread?tid=45e6836618212fdf&hl=en (A (Free) Level One certificate from http://www.startssl.com/ seems to work well here).|| || Motorola Milestone || 2.1, 2.2 || ? || Yes, via //Corporate Directory// app || Contacts and Calendar ||
 || Nokia E90 || !MfE 3.0 || ? || ? || Contacts verified to work. ||

__
commits mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

Reply via email to