View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005857 | SOGo | Backend Calendar | public | 2023-09-13 16:06 | 2024-08-16 10:24 |
Reporter | jordi | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Linux | OS | Debian | OS Version | 11 |
Product Version | 5.8.0 | ||||
Summary | 0005857: Appointments disappear if one of the invited participants reject the appointment | ||||
Description | Participants delete shared calendar events when denying participation to meetings This is just with Evolution, but I guess applies to any other client.
| ||||
Tags | No tags attached. | ||||
Hi! I have revisited this issue and I finally have some more information. We have a calendar setup using SOGo, users have their own personal calendar, and additionally there's a "Company events" calendar, owned by the Events on the Company Events calendar are normally created using the Sometimes, the whole participant list gets an "Event cancelled" email from SOGo, and indeed, the event has vanished from the calendar. This has been tracked down to Evolution (old and recent versions, up to 3.53.2) users that have the Company Events calendar configured in Evo, who decline the invitation with the "Company events" calendar selected in the dropdown. If the user had selected their personal calendar instead, the behaviour is correct: the attendee will be marked as declined and all is well. What we would expect is that the server gets a "Decline" from this user, and his attendance is marked as declined for the event. This is what happens with Thunderbird, as per our testing. Instead, Evolution seems to be sending a cancellation request to SOGo, which makes the event disappear for everyone. Is this problem something exclusive to Evolution, or is there room for SOGo to do better in this case. Note this upstream evolution bug which appears to be related and should mean that the Evolution version I'm running, 3.53.2, should not exhibit this behaviour, but still does: https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/59. It's hard for me to understand parts of the bug report as I'm not very acquainted with caldav protocol internals. Now that I know where the culprit lies and how to reproduce this easily, I can probably provide more information if needed. |
|
Also note the running version of SOGo is now 5.11.0. |
|