| Description | When calendar events from internal users are sent via mail, they are automatically added to the calendar in an unconfirmed state. Then the user just has to accept/reject the event in their caldav client, to confirm/deny the meeting.
This does not work that way for external calendar events, which caught us by surprise when migrating away from Zimbra to SOGo. With Zimbra, all events were treated that way. As a user with lots of calendar events, the following workflow was possible and appreciated:
- Open the caldav client (say on the mobile phone in the morning).
- Easily see the confirmed events, as well as the requested ones.
- Quickly confirm the ones one planned to attend.
- Begrudgingly attend meetings.
With SOGo it seems like this is something that the application can do, but choses not to for external events. It may be more complicated than that, but since it works for internal events, why won't it work for external events? Is this something we would need to configure? |
|---|
| Additional Information | We doubt this is a bug, but it has been a major issue for us, coming from Zimbra. Users relying on Zimbra's behavior have been missing meetings, and we are at a point where we are considering writing our own mail filter that takes ics files and applies them to user calendars, just to work around this issue. |
|---|
