[commits] [Wiki] changed: ActiveSync

[Michael Rubinsky]

mrubinsk  Tue, 06 Nov 2012 22:27:54 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  159
Change log:  Add more visible links to issues

@@ -5,15 +5,18 @@
  Support for allowing Horde to sync with mobile devices using support  
for Microsoft Exchange/!ActiveSync. This functionality has been  
available and stable since Horde 4.
  ++ People

  [MichaelRubinsky Michael Rubinsky]
+
+++ Bugs
+
+See the [http://bugs.horde.org/queue/sync bug tracker] and the list  
of ((ActiveSync/KnownIssues|known issues)).

  ++ Description

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

  As of Horde 5, !ActiveSync support passes  
[https://www.testexchangeconnectivity.com Microsoft's Remote  
Connectivity Analyzer] - though you must disable provisioning on the  
account you use for testing since the analyzer doesn't respond to the  
449 Header that is sent when Provisioning is required.
-

  ++ 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.
@@ -55,9 +58,9 @@

  alias.url = ("/Microsoft-Server-ActiveSync" => "/var/www/horde/rpc.php",
               "/autodiscover/autodiscover.xml" => /var/www/horde/rpc.php");
  </code>
-Note that Autodiscovery support is VERY flaky in most clients that we  
have tested.
+Note that Autodiscover support is VERY flaky in most clients that we  
have tested.

  ++ 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.

@@ -74,9 +77,9 @@
  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.

-++ Autodiscovery
+++ Autodiscover

  Some devices attempt to use Exchange's Autodiscovery service to make  
it easier for both the user to setup the account and for the  
administrator to make drastic changes like moving the server to a new  
URL. Horde attempts to support this as best it can. For this to work,  
you must create the URL alias as described above, and Horde must be  
able to figure out the Horde username based on the email address the  
user provided to the device. The configuration screen provides  
multiple options for this. In the worst case, if Horde cannot  
authenticate based on the provided information from the Autodiscover  
request, the device will fall back to requiring manual configuration.

  ++ !ActiveSync Versions