mrubinsk  Mon, 19 Mar 2012 13:55:52 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  128
Change log:  Initial notes on ActiveSync Email support

@@ -9,9 +9,9 @@
 [MichaelRubinsky Michael Rubinsky]

 ++ Description

-The Horde !ActiveSync implementation provides over the air synchronization of contacts, calendar, and task data to devices such as the iPhone/iPod Touch, Android and any other system supporting !ActiveSync. This implementation supports Microsoft !ActiveSync protocol versions up to 2.5 - the version implemented by Microsoft Exchange 2003. +The Horde !ActiveSync implementation provides over the air synchronization of contacts, calendar, task, and Email (Horde 5) data to devices such as the iPhone/iPod Touch, Android and any other system supporting !ActiveSync. This implementation supports Microsoft !ActiveSync protocol versions up to 2.5 - the version implemented by Microsoft Exchange 2003.

 ++ Server Setup

!ActiveSync support is stable, but there are still devices on which it has not been tested yet. If you have used a device with Horde's !ActiveSync support that is not listed below, please feel free to let us know how it went.
@@ -46,8 +46,21 @@
 ++ Application Configuration
No additional steps are normally necessary for synchronization of the supported applications. However, each application that supports synchronization also has a user preference to determine which shares will be synchronized. For example, in Kronolith the user's default calendar is *always* synchronized, but the user can choose to add any additional calendars he/she owns. Whenever the user changes one of these settings, the device is always automatically re-paired with the server to pick up the change.

Users can also view all their paired !ActiveSync devices by visiting their //!ActiveSync Devices// preferences. This is located within Horde's //Global Preferences//. From here, it is possible to force a complete re-sync, or to request a remote wipe of a provisioned device (see below).
+
+++ Email Support
+
+Email synchronization has been added in Horde 5. Since !ActiveSync email support is inferior to many native email clients, this functionality is disabled by default. If you would like to enable Email support, you need to select this in the !ActiveSync tab of Horde's configuration screen.
+
+!ActiveSync email support requires an IMAP server, not POP3. It will use the same server that IMP is configured to connect to. It is recommended that this server support the QRESYNC server extension for performance reasons, though it will work without this. It can also help performance if an IMAP proxy is used.
+
+The only flag supported by !ActiveSync is the //seen// flag. Flag changes will be synchronized, but flag changes alone will not trigger a SYNC (again, for performance reasons). The only thing that will trigger a SYNC is the arrival of a new message (technically, an increase in the NEXTUID value). Once this SYNC is triggered though, all message changes are taken into account.
+
+Since !ActiveSync does not support the //deleted// flag, messages in a mailbox with this flag are ignored when syncing. Deleting a message on the device will do one of two things; If the user has enabled a Trash mailbox then the message will be moved to that mailbox. Otherwise, the message is immediately expunged. This is in accordance with the !ActiveSync protocol specs.
+
+Forwarding a message will always attempt to put the main message text body in-line and keep any original attachments. It seems that a number of devices cannot view message/rfc822 attachments, so any messages that have been forwarded as an attachment may not be viewable in the !ActiveSync mail client.
+

 ++ Administration
Administrators can view all of the !ActiveSync devices paired with the server. This is the //!ActiveSync Devices// link located under the Administration menu. From here an administrator can request a remote wipe, or force a re-provisioning of any device.


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

Reply via email to