I seem to have some corner case bug and I would really appreciate help with debugging this as I have run to the end of my abilities with HTTP knowledge and understanding of the logging. Any help is appreciated!
I have a Samsung Galaxy S22 Ultra using the samsung builtin email client with activesync to sync mail and calendar. When any user on my SoGo instance creates a calendar event and invites me to it, I see the invite in my inbox. When I click on accept in the mail client (or any of the options), I get a message at the bottom of my screen that says Sending failed. My wife has a Samsung S21 and sees the same error. The rather odd thing about all of this is that the sender of the invite sees a response confirming the user accepted the invite in their inbox, so whatever happens within SoGo, it seems the only impact is the response to the activesync request to accept the invite fails. I did take a traffic capture and verified the response was a 200OK, so there is something deeper within the data that is bad. Both the web ui and outlook seem to be working fine and do not error when accepting an invite. I have tried many things: 1.) Created 2 brand new users to test with to verify there isn't something odd about the users involved. 2.) Logged into the web UI, went to Calendar, 3 dots, sharing, then set permissions to all objects to modify and checked both options for create/delete permissions. My assumption here was if this was internal to SoGo somehow that ACLs could be a problem. I did restart services after the modifications. 3.) Enabled debugging for activesync and stared at logging. To be fair, I don't really know what I am looking for, but I don't see any errors. When I tail -f the logfile, I see where the accepted response comes in and there is logging and actions to email the user that created the calendar event. Nothing too special, but I can attach them if anyone wants to stare at it. 4.) Wireshark capture, decrypted the SSL and stared at the (wbxml I assume?) The response to the accept was a 200OK and there was data in the stream. Wireshark has a WBXML decoder but could not read the response. I am wondering if this is exactly what the issue is - somehow the response is corrupted. However ... Wireshark cannot read any of the request/response pairs as WBXML, so maybe I am assuming things. Thank you, Chris
