6.0.0-beta1
7/11/25

[#14362] ActiveSync: Problem with the encoding of email subjects
Summary ActiveSync: Problem with the encoding of email subjects
Queue Horde Framework Packages
Type Bug
State Not A Bug
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester alexander (at) areim (dot) de
Created 05/12/2016 (3347 days ago)
Due
Updated 05/23/2016 (3336 days ago)
Assigned 05/20/2016 (3339 days ago)
Resolved 05/23/2016 (3336 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/23/2016 02:21:49 PM Michael Rubinsky State ⇒ Not A Bug
 
05/23/2016 07:45:12 AM alexander (at) areim (dot) de Comment #13 Reply to this comment

[Show Quoted Text - 16 lines]
It seems that Iconv is broken in my case. I commented out the 
following code and my problems are solved:
File: Horde/String.php
Line: 147
->
         /* Try iconv with transliteration. */
         if (Horde_Util::extensionExists('iconv')) {
             unset($php_errormsg);
             ini_set('track_errors', 1);
             $out = @iconv($from, $to . '//TRANSLIT', $input);
             $errmsg = isset($php_errormsg);
             ini_restore('track_errors');
             if (!$errmsg && $out !== false) {
                        echo "2";
                 return $out;
             }
         }
<-

I already tried to remove "//TRANSLIT" and tried to use "//IGNORE" but 
anythings fails.
05/20/2016 05:16:37 PM Michael Rubinsky Comment #12
State ⇒ Feedback
Reply to this comment
Very strange, as the subject is not related to any specific mime
part, and it doesn't differ depending on text/plain vs text/html.
Does the Subject: header in the raw email text look the same for both
emails?
Yes, it does.
I have no idea what is causing this, and I can't reproduce it. As 
mentioned, the subject text is handled outside of any code dealing 
with the content-type of the body part. If the subject header and 
charset are *exactly* the same in both emails, you are going to have 
to figure out where this is failing for you, as I cannot reproduce.

This is likely happening in Horde_ActiveSync_Utils::ensureUtf8(), 
being called from 
Horde_ActiveSync_Imap_MessageBodyData::_validateBodyData().
05/19/2016 01:42:45 PM Michael Rubinsky Comment #11
State ⇒ Assigned
Assigned to Michael Rubinsky
Reply to this comment
Ok. I'll take a closer look at that.
05/19/2016 01:36:01 PM alexander (at) areim (dot) de Comment #10 Reply to this comment
Very strange, as the subject is not related to any specific mime 
part, and it doesn't differ depending on text/plain vs text/html. 
Does the Subject: header in the raw email text look the same for 
both emails?
Yes, it does.
05/19/2016 01:28:27 PM Michael Rubinsky Comment #9 Reply to this comment
Very strange, as the subject is not related to any specific mime part, 
and it doesn't differ depending on text/plain vs text/html. Does the 
Subject: header in the raw email text look the same for both emails?
05/19/2016 09:10:26 AM alexander (at) areim (dot) de Comment #8
New Attachment: AMDVE9TO891S5A64SU9UIUSUH8.txt Download
Reply to this comment

[Show Quoted Text - 18 lines]
I disabled Ioncube but it doesn't solve that problem.

I attached a detailed activesync debug log. There are 2 E-Mails. 
ServerEntryId:1 is a html-mail and ServerEntryId: 2 is a 
plaintext-mail. The first is broken but  the second show correct chars 
at my Iphone. It seems that only html-mails don't work correctly.
05/17/2016 03:14:08 PM Michael Rubinsky Comment #7 Reply to this comment

[Show Quoted Text - 13 lines]
I also haven't tested using ioncube, which you are using, but we 
haven't had any other reports of issues with this so...
05/17/2016 03:13:02 PM Michael Rubinsky Comment #6 Reply to this comment
Works fine here on all my test devices, including iOS. Screenshot attached.
Could something be wrong with my php- and/or webserver-configuration?
Always a possibility. You can check your webserver/horde/sync logfiles 
for hints.
Or has something important changed between the release and git-version?

I attached my phpinfo to this comment. Could you take a look at this please?
Aside from the fact that you are running on windows - which we haven't 
fully tested in a while - I don't see anything obvious.

05/17/2016 06:39:55 AM alexander (at) areim (dot) de Comment #5
New Attachment: phpinfo.htm Download
Reply to this comment
Works fine here on all my test devices, including iOS. Screenshot attached.
Could something be wrong with my php- and/or webserver-configuration?
Or has something important changed between the release and git-version?

I attached my phpinfo to this comment. Could you take a look at this please?
05/16/2016 04:53:13 PM Michael Rubinsky Comment #4
New Attachment: IMG_0010.jpg Download
Reply to this comment
Works fine here on all my test devices, including iOS. Screenshot attached.
05/12/2016 01:12:13 PM alexander (at) areim (dot) de Comment #3
New Attachment: Email.eml Download
Reply to this comment
Here is an example...

05/12/2016 01:04:57 PM Michael Rubinsky Comment #2
Priority ⇒ 1. Low
State ⇒ Feedback
Reply to this comment
Please provide the source of an email that triggers this behavior.
05/12/2016 12:59:54 PM alexander (at) areim (dot) de Comment #1
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
New Attachment: beispiel.jpg Download
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ ActiveSync: Problem with the encoding of email subjects
Type ⇒ Bug
Reply to this comment
On my IPhone the email subjects are wrong encoded. All german umlauts 
are wrong. The body and anything else is shown correctly. There are no 
problems with notes, calendar, tasks, ...

Iphone: IOS 9.3.1
Horde Framework and applications: latest stable release (pear)

Saved Queries