Messages are not built properly when replying from a mobile client using activesync and are not readable when using accents

When replying from a BlackBerry 10 device, the message is no

Tue, 11 Feb 2014 18:56:58 +0000

When replying from a BlackBerry 10 device, the message is not properly "built" before being sent and there seems to be a mix of encoding which makes the message unreadable if using a lot of accentuated characters. This is a recent problem which may have been introduced in ActiveSync 2.12.4. This was tested on the Webmail edition version 5.1.3 with all the modules updated 15 minutes ago. Steps to reproduce: 1) Send an email from Outlook 12 or Thunderbird 24. The message will display fine on all mail clients. 2) Reply from a BlackBerry 10 device, but that shouldn't matter if that's an AES problem. The original message is quoted in the message. Result: The message will not be readable in any client, except IMP. The quoted message is not readable in IMP (and is broken in two if you have your preference set to "reply at the bottom" in ActiveSync prefs) Differences I've noticed Original message Content-Type: text/plain; charset=UTF-8 Reply Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes The reply seems to be built by Horde: User-Agent: Horde Application Framework 5 I'm keeping this report public and the original message and the reply will be sent privately.

I've just tested with a reply using HTML and I did not have

Tue, 11 Feb 2014 22:14:05 +0000

I've just tested with a reply using HTML and I did not have the problem, so maybe this fix will take care of the problem? https://github.com/horde/horde/commit/aaa3cfa5e8231db7f71784ddfd0d130cedb5d0a6

> I've just tested with a reply using HTML and I did not hav

Tue, 11 Feb 2014 22:28:21 +0000

> I've just tested with a reply using HTML and I did not have the > problem, so maybe this fix will take care of the problem? > https://github.com/horde/horde/commit/aaa3cfa5e8231db7f71784ddfd0d130cedb5d0a6 This commit would have nothing to do with the problem you describe. Also, I have not received any email attachments outside of this ticket yet.

>> I've just tested with a reply using HTML and I did not ha

Tue, 11 Feb 2014 22:37:39 +0000

>> I've just tested with a reply using HTML and I did not have the >> problem, so maybe this fix will take care of the problem? >> https://github.com/horde/horde/commit/aaa3cfa5e8231db7f71784ddfd0d130cedb5d0a6 > > This commit would have nothing to do with the problem you describe. > Also, I have not received any email attachments outside of this > ticket yet. OK. I've checked my mail server logs and the message has been grey listed, so I don't know how much time it will take to reach you.

Changes have been made in Git (master): commit c18e7dc879db

Sun, 16 Feb 2014 03:38:24 +0000

Changes have been made in Git (master): commit c18e7dc879db5b6f99b08d09522d7d6be7f22ce2 Author: Michael J Rubinsky Date: Sat Feb 15 22:32:04 2014 -0500 Bug: 12969 Ensure we always use valid UTF-8 text. .../Core/lib/Horde/Core/ActiveSync/Driver.php | 18 ++++++++++++++---- 1 files changed, 14 insertions(+), 4 deletions(-) http://git.horde.org/horde-git/-/commit/c18e7dc879db5b6f99b08d09522d7d6be7f22ce2

Fixed in Horde_Core 2.12.0 and Horde_ActiveSync 2.13.0

Sun, 16 Feb 2014 03:42:04 +0000

Fixed in Horde_Core 2.12.0 and Horde_ActiveSync 2.13.0