View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004755SOGoActiveSyncpublic2019-05-28 06:002019-06-11 06:01
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version4.0.7 
Target VersionFixed in Version 
Summary0004755: Character ???? (Unicode U+1F3FF) in mail subject brake synchronisation with ActiveSync
DescriptionE-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 ReproduceSend a mail with ???? in the subject to a SOGo user then trying to synchronize his mailbox from an ActiveSync device.
Additional InformationThe 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.
TagsNo tags attached.
Attached Files? file icon [^] (1,560 bytes) 2019-05-28 06:00

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
tfu (reporter)
2019-05-30 09:39

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)).

- Issue History
Date Modified Username Field Change
2019-05-28 06:00 MartinL New Issue
2019-05-28 06:00 MartinL File Added:
2019-05-30 09:39 tfu Note Added: 0013584

Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker