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 ******: 1743681071 vevent%2Fpersonal 25 1 32768 60820 1 (redacted) (redacted) 0 2 20250403T201820Z 20250706T170000Z (redacted) 0 (redacted)'s Fête Blanche & BBQ 20250706T160000Z 20250403T201820Z-20250706T180000-FêteBlanche&BBQ@guest-messaging 0 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).