Known ActiveSync Issues

The following issues are mostly due to buggy clients and/or variable implementation details between clients. In most cases there is nothing Horde can due to work around these issues.

iOS Mail: Certain messages always display This message was downloaded as plaintext.

Messages that are over a certain size will always display the This message was downloaded as plain text message along with a button to download the message. Attempting to download the message results in an error displaying the email. This is an issue (feature?) with iOS. Viewing the attachments by clicking the download link for each attachment works as expected.

iOS 6 Push fails.

Push email may fail completely in iOS6, requiring manual email checking. There are also issues with meeting requests and responses that can cause incorrect response/cancellation emails to be sent out.

Cannot delete email on iOS devices.

iOS devices attempt to move the email to the Trash folder on the client side instead of sending a move command to the server as the protocol dictates. This means that if there is no configured Trash folder on the device, the deletion will fail. If using iOS, you MUST have IMP configured to use move messages to a Trash folder on deletion.

Birthdays displaying offset by a certain number of days.

This is a known issue with most ActiveSync clients. It's due to the variable way in which clients represent the birthday field of the contact. There is, unfortunately, nothing Horde can do to work around this issue.

There is an extra citation line when replying to email.

Some ActiveSync clients automatically append the citation line to outgoing reply text. Due to this, and the way Smart Reply works in ActiveSync this can lead to duplicate citation lines when replying to email on these clients.

Autodiscovery fails.

To start with, not all devices support this. Of those that claim to, some do not implement it correctly. For example, Android clients send broken Autodiscover requests where they pass the full email address as the username in the HTTP Authorization data, and don't even bother with sending the XML request. We work around these issues where we can, but simply cannot work around every single possible device issue. If Autodiscover fails, you simply have to configure the client manually - usually not more than an additional one or two fields.