#TASKS & NOTES FOR MS EXCHANGE HOW TO#
#TASKS & NOTES FOR MS EXCHANGE PATCH#
#TASKS & NOTES FOR MS EXCHANGE WINDOWS#

ProxyPassMatch ^/autodiscover/autodiscover.xml$ unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1 You should allow the following URLs to be redirected:ДЄlias /autodiscover/autodiscover.xml /var//var//var/www/horde/rpc.php Note that the documentation specifies different case for the URL in different parts. For this, you simply create an Alias pointing /autodiscover/autodiscover.xml to /rpc.php. The easiest example is when Horde is running on the same domain, with NO subdomain as the email address domain. Autodiscover requests will NOT work without a valid SSL certificate. Note that for autodiscovery to work, the final endpoint MUST be over SSL. Below are a few examples to point you in the right direction. How it does this depends on your specific server setup. In order for the Autodiscovery service to work, a request to /autodiscover/autodiscover.xml needs to reach rpc.php. Since Horde ActiveSync connections are held open for a period of time up to 3540 seconds (depending on client and $conf setting, if using a proxy server you need to ensure it does not time out before the request is complete.

Note: If setting ProxyErrorOverride On then when testing the ActiveSync endpoint via a browser you may not see the expected activesync error message - as it would be replaced by the overridden Apache error message.

#TASKS & NOTES FOR MS EXCHANGE PATCH#

Note: Sockets are only available from Apache 2.4.8 or if the appropriate patch has been applied. ProxyPassMatch ^/Microsoft-Server-ActiveSync$ unix:/usr/local/php55/sockets/webapps.sock|fcgi://127.0.0.1:9000/var/www/html/horde/rpc.php$1 None of these issues have been reported using lighttpd/fastcgi or Apache+mod_fastcgi+php-fpm.ДЇor Apache + PHP-FPM using mod_proxy_fcgi However, if you are still having issues with ActiveSync complaining about no Authorization errors, you can try the following configuration: These are known issues and are should actually already be taken care of by the Horde_Controller_Request object.

There has also been a report from that the Authorization headers are not correctly passed when using mod_php with Apache. RewriteRule ^/Microsoft-Server-ActiveSync /horde/rpc.php This can be worked around by using a RewriteRule instead (adapted from ): Note: It has been reported that when running PHP via mod_fcgid on Apache that the Alias directive will not pass the correct URL to the fcgid-script handler. For Apache, something like:ДЄlias /Microsoft-Server-ActiveSync /var/www/horde/rpc.php How you do this depends on your webserver and it's configuration. You will need to configure your webserver to redirect the URL /Microsoft-Server-ActiveSync to your horde/rpc.php file.

The SQL tables that horde uses are created as usual from the Horde configuration screen. To activate the server, it needs to be enabled in Horde's configuration, on the ActiveSync tab. For the specific versions and features supported in different Horde versions, see the ActiveSync Feature Grid.ДЄs of Horde 5, ActiveSync support passes 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.ДЇor information on using this library in your own groupware stack, see the developer documentation. This page describes the use of this library for synchronizing a Horde Groupware stack. The Horde_ActiveSync library provides the framework for synchronizing a groupware server with an EAS client. See the bug tracker and the list of known issues and the list of broken client behavior. In addition to synchronization, the protocol provides some device management and security related features.

#TASKS & NOTES FOR MS EXCHANGE WINDOWS#

Android, iOS, Windows Phone, Blackberry, even current versions of Microsoft Outlook and Windows Mail include support for EAS. Just about every modern device capable of synchronization includes out of the box support for EAS. It was originally developed by Microsoft for synchronizing PocketPC devices with Microsoft Exchange servers, but has since become widely adopted as the preferred synchronization method. EAS is a WAP Binary XML (WBXML) based protocol and is communicated over HTTP/HTTPS.

Windows Mobile (very old, probably of little value):Д®xchange ActiveSync (EAS) is a protocol designed for client synchronization of Email, Contacts, Calendar, Tasks, and Memo data with a groupware/messaging server.

Using tshark (command line wireshark) to obtain a network capture.

#TASKS & NOTES FOR MS EXCHANGE HOW TO#

What to do if you have problems (or How to help us help you).Multiple sources in the same collection.Setting up Horde ActiveSync behind a Reverse Proxy Server.

Tasks & notes for ms exchange