View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006111 | SOGo | ActiveSync | public | 2025-04-04 10:46 | 2025-04-04 10:46 |
Reporter | leecher | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | [Client] Microsoft | OS | Windows | OS Version | 7 |
Product Version | 5.9.0 | ||||
Summary | 0006111: When a client proposes an UID with a non-ascii character, SOGo takes it, but xml2wbxml failes on ActiveSync | ||||
Description | When a Client proposes an UID with a non-ascii character, like an accent circonflex in it, See attachment for creation-messages and error response I suggest either to not use original uid for non-ascii characters or fix xml2wbxml to process such characters properly (if allowed by specification). | ||||
Steps To Reproduce | Make an invitation with "Fête blanche" in the subject and accept it on an IPhone conneted via EAS and let SOGO write it to the calendar. You will end up with an EAS <Sync> message like the attached one. | ||||
Tags | No tags attached. | ||||
sogo-log-feteblanche.txt (2,416 bytes)
When a Client proposes an UID with a non-ascii character, like an accent circonflex in it, SOGo takes it, but unfortunately xml2wbxml then fails parsing the entry. Creation: Apr 03 22:18:30 sogod [31638]: <0x0x56094182b4b0[SOGoActiveSyncDispatcher]> EAS - request for device ******: <?xml version="1.0"?> <!DOCTYPE ActiveSync PUBLIC "-//MICROSOFT//DTD ActiveSync//EN" "http://www.microsoft.com/"> <Sync xmlns="AirSync:"> <Collections> <Collection> <SyncKey>1743681071</SyncKey> <CollectionId>vevent%2Fpersonal</CollectionId> <GetChanges/> <WindowSize>25</WindowSize> <Options> <BodyPreference xmlns="AirSyncBase:"> <Type>1</Type> <TruncationSize>32768</TruncationSize> </BodyPreference> </Options> <Commands> <Add> <ClientId>60820</ClientId> <ApplicationData> <Body xmlns="AirSyncBase:"> <Type>1</Type> <Data>(redacted)</Data> </Body> <TimeZone xmlns="Calendar:">(redacted)</TimeZone> <AllDayEvent xmlns="Calendar:">0</AllDayEvent> <BusyStatus xmlns="Calendar:">2</BusyStatus> <DTStamp xmlns="Calendar:">20250403T201820Z</DTStamp> <EndTime xmlns="Calendar:">20250706T170000Z</EndTime> <Location xmlns="Calendar:">(redacted)</Location> <Sensitivity xmlns="Calendar:">0</Sensitivity> <Subject xmlns="Calendar:">(redacted)'s F�te Blanche & BBQ</Subject> <StartTime xmlns="Calendar:">20250706T160000Z</StartTime> <UID xmlns="Calendar:">20250403T201820Z-20250706T180000-F�teBlanche&BBQ@guest-messaging</UID> <MeetingStatus xmlns="Calendar:">0</MeetingStatus> </ApplicationData> </Add> </Commands> </Collection> </Collections> </Sync> Apr 03 22:18:30 sogod [31638]: <0x0x56094182b4b0[SOGoActiveSyncDispatcher]> EAS - Use original serverId: 20250403T201820Z-20250706T180000-F�teBlanche&BBQ@guest-messaging (null) Result in ActiveSync dispatcher: -------------------------------- Apr 04 12:23:30 sogod [31551]: [ERROR] <0x0x558c6b1642e0[NSDataMalloc]> xml2wbxml failed: Parsing of XML Document Failed Apr 04 12:23:30 sogod [31551]: [ERROR] <0x0x558c6b1642e0[NSDataMalloc]> Original data written to: /tmp/server_7b3f_2d9fe1e4_5.data I suggest either to not use original uid for non-ascii characters or fix xml2wbxml to process such characters properly (if allowed by specification). |
|