jan Fri, 19 Jul 2013 14:33:53 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 205
Change log: Tweak tables
@@ -142,9 +142,9 @@
For the complete feature set, sorted by ActiveSync version, see
((ActiveSync/FeatureGrid|Supported ActiveSync Features)).
This following devices have been tested:
-|| Device || Version(s) || Provisioning || GAL Searching || Notes ||
Verified EAS Versions || Autodiscover ||
+||~ Device ||~ Version(s) ||~ Provisioning ||~ GAL Searching ||~
Notes ||~ Verified EAS Versions ||~ Autodiscover ||
|| !BlackBerry !PlayBook || 2.1.0.1088 || ? || ? || Emails, contacts
and calendars are synced, but the !PlayBook often resets the sync when
connecting to 2 accounts || 12.1 || ||
|| !BlackBerry 10 (Simulator) || 10.1 || Yes || Yes || Email,
Contacts, Calendars, Tasks, Notes || 14.1 || ? ||
|| Google Nexus 4 || 4.2.2 || ? || ? || Emails, contacts and
calendars || 12.1 || ||
|| Google Nexus 7 || 4.1.2 || ? || ? || Emails, contacts and
calendars.|| 12.1 || ||
@@ -208,17 +208,17 @@
* Configure Horde to send !ActiveSync log messages to a separate
logfile. This is configured on the !ActiveSync tab of Horde's
configuration screen.
* If you are able to, it would also be useful to run a wireshark
session to capture the network communication.
* In some cases, it might be useful for us to see the affected
device's state records in the database.
-++++Using tshark (command line wireshark) to obtain a network capture
+++++ Using tshark (command line wireshark) to obtain a network capture
If you want to sniff the traffic on your server, and wireshark is
not available becuase there is no windowing system, you can use the
tshark application instead. The following command will capture http
traffic on port 80, and will ignore most requests we are not
interested in. It's worth mentioning that for the capture to be
useful, you MUST not setup SSL on the device. Depending on your user's
rights, you may need to run this as sudo:
<code>
tshark 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) -
((tcp[12]&0xf0)>>2)) != 0)' -w /path/to/capture/file
</code>
-++++Debug logging on device.
+++++ Debug logging on device.
On Android devices, it is possible to enable debug level logging of
the !ActiveSync conversation as well:
To reach the Debug logging screen:
@@ -233,14 +233,15 @@
* "Enable Exchange parser logging" - If checked, logs a great deal
of the CONTENT of mail, contacts, and calendar entries (excluding the
text of emails other than perhaps the first line). This information
helpful for debugging things like missing folders, missing calendar
entries, etc.
* "Enable Exchange SD card logging" - If checked, puts all of the
Exchange related logging onto SD card in a file named emaillog.txt.
This file grows continuously until deleted (or the checkbox is
unchecked). This can be helpful in finding issues that are sporadic,
as the log is essentially unlimited in size.
++ Roadmap
++++ Horde 5.1
||~ Feature ||~ Status ||
-||||~ Horde 5.1 ||
|| EAS 14(.1) support.|| Complete. ||
|| Improved device management via hooks. || Complete. ||
-||||~ Horde 5.2/6.0 ||
++++ Horde 5.2/6.0
+||~ Feature ||~ Status ||
|| Support for SOFTDELETE || Planned ||
|| Improved email identity support.|| Planned ||
|| CLI admin tool. || Planned ||
|| Improved device management GUI. || Planned ||
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
