|Anonymous | Login | Signup for a new account||2019-06-17 20:43 EDT|
|My View | View Issues | Change Log | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004755||SOGo||ActiveSync||public||2019-05-28 06:00||2019-06-11 06:01|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0004755: Character ???? (Unicode U+1F3FF) in mail subject brake synchronisation with ActiveSync|
|Description||E-Mail Synchronisation with ActiveSync fail when there is character ???? (Unicode U+1F3FF) in subject.|
The following error is reported in log file:
[ERROR] <0x0x563a87942da0[NSDataMalloc]> xml2wbxmlFromContent: failed: Parsing of XML Document Failed
|Steps To Reproduce||Send a mail with ???? in the subject to a SOGo user then trying to synchronize his mailbox from an ActiveSync device.|
|Additional Information||The subject appear as "(null)" in SOGo webmail.|
I made some test and this issue appear only with this specific character only in subject. Synchronization work fine with character in mail body or in a calendar event.
Synchronization work fine when this character is quoted in the subject like "Invitation acceptée : «test ????»" or simply 'test "????"'.
I didn't find this issue with other characters.
I did my test with a MySQL database and utf8mb4_general_ci character set.
|Tags||No tags attached.|
|Attached Files||test-02_1342_229c3d87_4.data [^] (1,560 bytes) 2019-05-28 06:00|
I tracked the problem to SOPE.
NSData+MimeQP.m (Line 223):
data = [data stringByTrimmingCharactersInSet: illegalCS];
The problem can be reproduced with U+1F3FF at the begin/end of the mail subject.
Having this character in the middle of the subject is not a problem.
Without this line the crash doesn't occure and the subject is correctly displayed in webUI (instead of (null)).
|2019-05-28 06:00||MartinL||New Issue|
|2019-05-28 06:00||MartinL||File Added: test-02_1342_229c3d87_4.data|
|2019-05-30 09:39||tfu||Note Added: 0013584|
|Copyright © 2000 - 2019 MantisBT Team|