Tickets :: [#14362] ActiveSync: Problem with the encoding of email subjects

6.0.0-git

2019-03-20

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	2016-05-12 (1042 days ago)
Due
Updated	2016-05-23 (1031 days ago)
Assigned	2016-05-20 (1034 days ago)
Resolved	2016-05-23 (1031 days ago)
Milestone
Patch	No

2016-05-23 14:21:49	Michael Rubinsky	State ⇒ Not A Bug

2016-05-23 07:45:12	alexander (at) areim (dot) de	Comment #13	Reply to this comment
[Show Quoted Text - 16 lines][Hide Quoted Text] 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(). 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.

2016-05-20 17:16:37	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().

2016-05-19 13:42:45	Michael Rubinsky	Comment #11 Assigned to Michael Rubinsky State ⇒ Assigned	Reply to this comment
Ok. I'll take a closer look at that.

2016-05-19 13:36:01	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.

2016-05-19 13:28:27	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?

2016-05-19 09:10:26	alexander (at) areim (dot) de	Comment #8 New Attachment: AMDVE9TO891S5A64SU9UIUSUH8.txt	Reply to this comment
[Show Quoted Text - 18 lines][Hide Quoted Text] 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. I also haven't tested using ioncube, which you are using, but we haven't had any other reports of issues with this so... 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.

2016-05-17 15:14:08	Michael Rubinsky	Comment #7	Reply to this comment
[Show Quoted Text - 13 lines][Hide Quoted Text] 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. I also haven't tested using ioncube, which you are using, but we haven't had any other reports of issues with this so...

2016-05-17 15:13:02	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.

2016-05-17 06:39:55	alexander (at) areim (dot) de	Comment #5 New Attachment: phpinfo.htm	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?

2016-05-16 16:53:13	Michael Rubinsky	Comment #4 New Attachment: IMG_0010.jpg	Reply to this comment
Works fine here on all my test devices, including iOS. Screenshot attached.

2016-05-12 13:12:13	alexander (at) areim (dot) de	Comment #3 New Attachment: Email.eml	Reply to this comment
Here is an example...

2016-05-12 13:04:57	Michael Rubinsky	Comment #2 State ⇒ Feedback Priority ⇒ 1. Low	Reply to this comment
Please provide the source of an email that triggers this behavior.

2016-05-12 12:59:54	alexander (at) areim (dot) de	Comment #1 Type ⇒ Bug State ⇒ Unconfirmed Priority ⇒ 2. Medium Summary ⇒ ActiveSync: Problem with the encoding of email subjects Queue ⇒ Horde Framework Packages Milestone ⇒ Patch ⇒ No New Attachment: beispiel.jpg	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)