[commits] [Wiki] changed: ActiveSync

Michael Rubinsky mrubinsk at horde.org
Thu Apr 19 15:41:16 UTC 2012


mrubinsk  Thu, 19 Apr 2012 15:41:16 +0000

Modified page: http://wiki.horde.org/ActiveSync
New Revision:  136
Change log:  Some notes above Autodiscovery

@@ -34,14 +34,21 @@
  RewriteRule .* - [E=HTTP_X_MS_POLICYKEY:%{HTTP:X-Ms-Policykey}]
  RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
  </code>
  None of these issues have been reported using lighttpd/fastcgi.
+
+In order for the Autodiscovery service to work, you should also  
create an alias/rewrite rule for the URL  
/autodiscover/autodiscover.xml to horde/rpc.php as well:
+
+<code>
+Alias /autodiscover/autodiscover.xml /var/www/horde/rpc.php
+</code>


  For lighttpd:

  <code>
-alias.url = ("/Microsoft-Server-ActiveSync" => "/var/www/horde/rpc.php");
+alias.url = ("/Microsoft-Server-ActiveSync" => "/var/www/horde/rpc.php",
+             "/autodiscover/autodiscover.xml" => /var/www/horde/rpc.php");
  </code>

  ++ 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.
@@ -58,8 +65,12 @@

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

  Horde 5 adds support for !ActiveSync version 12.0 - the version  
shipped with Exchange Server 2007. This adds HTML email support, flag  
or followup, more atomic policy settings, additional search sources,  
local wipe rules, and WBXML based provisioning (instead of the XML  
used in 2.5). There are a few things to mention regarding 12.0 support:



More information about the commits mailing list