mrubinsk Sun, 17 Nov 2013 17:02:19 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 222
Change log: Add info on multiple sources per collection, other minor tweaks.
@@ -116,15 +116,28 @@
You should make sure that the max_execution time is either set to 0
or at least twice the maximum heartbeat interval. This can be set in
Horde's general configuration tab.
++ 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.
+No additional steps are normally necessary for synchronization of the
supported applications. However, each application that supports
synchronization also has user preferences 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.
+
++++ Multiple sources in the same collection
+
+Prior to Horde 5.2, all non-email sources would be "multiplexed"
together so they appear as a single source on the client. For example,
all user calendars would appear as a single, combined calendar on the
client and any new events would always be added to the user's default
calendar. Starting with Horde 5.2, applications can be configured to
provide all user sources as discrete sources on the client. Since very
few EAS clients actually support this, there are a number of ways to
control this:
+* By enabling/disabling the discrete sources preference per
application. This, of course, affects all of a user's devices, so must
be set to the lowest common denominator. If it is desired to always
force the multiplexed collections, you can lock the preference.
+* By implementing the activesync_device_modify hook (see
//horde/config/hooks.php.dist//). There is a sample hook already
defined that performs some basic device sniffing to determine which
collections do not support discrete sources. For example, Android
devices typically do not support ANY discrete non-email sources, so we
disable this for any Android device, while iOS supports discrete
sources for everything exempt Memos.
+
+The following chart is meant to provide a general idea of what device
class supports this, not a listing of all devices and capabilities:
+||~ Device ||~ Calendars ||~ Contacts ||~ Tasks ||~ Memos ||~
Creating new sources ||~ Notes ||
+|| Android || || || || || || ||
+|| iOS || Yes || Yes || Yes || || Yes, for Calendars and Tasks || ||
+|| Windows Phone || || || Yes || || || ||
+|| Blackberry || Yes || Yes || Yes || || || Multiple sources are
accepted, but they are displayed as a single source. ||
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 in some
installs this could increase server load or may be otherwise
undesirable, it is possible to deactivate email support via Horde's
configuration, on the !ActiveSync tab.
+Email synchronization has been added in Horde 5. Since in some
installs this may be undesirable, it is possible to deactivate email
support via Horde's configuration, on the !ActiveSync tab.
!ActiveSync email support requires an IMAP server. POP3 is not
supported. When used in the Horde groupware stack, 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. Some IMAP servers like older
Cyrus versions (< 2.4) might support QRESYNC but do not enable per
mailbox MODSEQ by default. Enabling this on these servers will greatly
improve performance.
The only flags supported by !ActiveSync are the //seen// and
//flagged for follow up// flags. Flag changes will be synchronized,
but flag changes alone will only trigger a SYNC if per mailbox MODSEQ
is supported on the server. Otherwise, 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 - including any flag changes.
@@ -164,9 +177,9 @@
Clicking //Wipe// in the Horde interfaces for device management
flags the server to send the wipe command to the device the next time
it synchronizes. The next time the device attempts to request a
command other then PING or OPTIONS, it will be wiped. The !ActiveSync
preference page shows the status of all the user's devices. If the
status is listed as //Pending//, and you wish to cancel the wipe
request, you may do this by clicking the //Cancel Wipe// button. You
should see the status be reset to //Provisioned//. After it is wiped,
the status will be shown as //Wiped//, if you wish to allow the device
to connect to your server again, you need to explicitly remove the
device as a sync partner by clicking the //Remove// button. If you do
not remove this entry, the device will continue to be wiped each time
it reconnects to the server.
++ What works
-Contacts, Calendar, Task, Notes and Email syncing are all working.
Note that not all devices support Tasks or Notes. Of the tested
devices, iOS (versions < 5.0) and Android are lacking native Task
applications. The !TouchDown client, Moxier Mail, and Windows Mobile
both support Tasks. Windows Mobile is the only client found so far
that supports Notes.
+Contacts, Calendar, Task, Notes and Email syncing are all working.
Note that not all devices support Tasks or Notes. Of the tested
devices, iOS (versions < 5.0) and Android are lacking native Task
applications. The !TouchDown client, Moxier Mail, and Windows Mobile
both support Tasks. Windows Mobile, and iOS 7+ are the only clients
I've found so far that support Notes.
For the complete feature set, sorted by ActiveSync version, see
((ActiveSync/FeatureGrid|Supported ActiveSync Features)).
This following devices have been tested:
@@ -192,9 +205,9 @@
|| Nokia E5-00 || ? || ? || ? || Contacts & calendar via !RoadSync.
Calendar works native client but contacts do not seem to work. || 2.5
|| ||
|| Nokia E90 || !MfE 3.0 || ? || ? || Contacts verified to work. || 2.5 || ||
|| Nokia N900 || Maemo 1.3 || No || Yes, in the "contacts" app ||
Emails, events, contacts and tasks work. Earlier versions of firmware
are either broken, or only support !ActiveSync version 12.1. Sent
messages are only stored locally. The device always "pings" all
folders by default on the server, it might cause higher server load
with a lot of folders. You can adjust which folders to sync with the
mfefolders (http://mfefolders.garage.maemo.org/) app. || 2.5, 12.1 || ||
|| Samsung Galaxy Gio || 2.3.6 || Yes || Yes || Contacts and
calendar data works. SSL works as well. || 2.5 || ||
-|| Samsung Galaxy Nexus || 4.0.2 (ICS), 4.1.2 (Jelly Bean) || Yes,
full support. || Yes, native support via the search functionality. ||
Calendar, Contacts, and Email works. Be sure to ENABLE email syncing.
Disabling email syncing - even if enabling calendar and contacts -
seems to prevent the initial folder sync required for the account to
be initially set up on the phone. || 2.5, 12.0, 12.1 || Yes, though
the device defaults to using the email address as the horde login and
must be changed by the user if this is not the case. ||
+|| Samsung Galaxy Nexus || 4.0.2 (ICS), 4.1.2, 4.2.x, 4.3.x (Jelly
Bean) || Yes, full support. || Yes, native support via the search
functionality. || Calendar, Contacts, and Email works. Be sure to
ENABLE email syncing. Disabling email syncing - even if enabling
calendar and contacts - seems to prevent the initial folder sync
required for the account to be initially set up on the phone. || 2.5,
12.0, 12.1 || Yes, though the device defaults to using the email
address as the horde login and must be changed by the user if this is
not the case. ||
|| Samsung Galaxy S2 || 2.3.4 || ? || ? || GT-I9100 - Contacts and
calendar data works. SSL works as well (self-signed certificates
also). || 2.5 || ||
|| Samsung Galaxy S2 || 4.0.3 (ICS) || Yes, full support. || Yes,
native support via the search functionality. || GT-I9100 - Calendar,
Contacts and Email works. Be sure to ENABLE email syncing. Disabling
email syncing - even if enabling calendar and contacts - seems to
prevent the initial folder sync required for the account to be
initially set up on the phone. SSL works as well (self-signed
certificates also). || 2.5, 12.0 || ||
|| Samsung Galaxy S2 || 4.1.2 (JB) || Yes, full support. || Yes,
native support via the search functionality. || GT-I9100 - Calendar,
Tasks, Contacts and Email works. Be sure to ENABLE email syncing.
Disabling email syncing - even if enabling calendar, tasks and
contacts - seems to prevent the initial folder sync required for the
account to be initially set up on the phone. SSL works as well
(self-signed certificates also). || 2.5, 12.1 || ||
|| "Tasks and Notes" for Android || ? || ? || N/A || Requires Horde
>= 5.1.0. Available via the Android App store:
https://play.google.com/store/apps/details?id=org.myklos.inote ||
12.0, 12.1, 14.1 || No ||
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
