mrubinsk Fri, 17 Jan 2014 19:49:30 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 237
Change log: Start basic section on S/MIME support/issues
@@ -147,8 +147,14 @@
* Deleting 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.
* Deleting from a MUA: If the MUA is not configured to move messages
to the trash, and instead just flags them as deleted, these message
deletions will NOT be synched to the !ActiveSync client, as there is
no equivalent command in the protocol. These messages will only be
removed from the !ActiveSync client once expunged from the mailbox.
This is in accordance with the !ActiveSync protocol specs. If you wish
to ensure all message deletions are synched quickly to the device, you
should configure the use of a Trash folder.
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.
+
+++ S/MIME Support
+
+||~ Client ||~ S/MIME support ||
+|| iOS || Can sign and encrypt outgoing email and successfully
validate/decrypt received email. Some issues with validating
certificates on emails sent from iOS > 6.1. ||
+|| Android || Most clients do not support this AT ALL. Some, such as
Samsung's proprietary client, can send encrypted/signed email but
cannot decrypt or validate received email. The third party client
Touchdown supports this well. ||
++ Autodiscover
Some devices attempt to use Exchange's Autodiscover 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.
See the notes in the compatibility grid for any known information
regarding device support for this feature.
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
