Hello Lars Wessels
On 2012-07-23 19:43, Lars Wessels wrote:
>
> We started to use SOGo a short while ago and so far we're quite happy
> with it. :-)
>
> system setup:
> - SOGo 1.3.16 running on Debian with MySQL-Backend and OpenLDAP for
> authentication purposes
> - clients mostly TB 10 ESR with lightning add-on
>
> However our users have recently started to use the handy appointment
> request/invitation function provided by the SOGo webinterface or TB
> Lightning add-on and have run into the following problem which might
> point to a bug SOGo. Or is at actually a feature? ;-)
>
> All users at our site have two calendars configured. Example for user XXXX:
>
> "/Users/XXXX/Calendar/personal" = {
> acl = {
> "<default>" = (
> None
> );
> };
> displayname = Private;
> records = (
> (...)"
>
> and
>
> "/Users/XXXX/Calendar/347A-4FFAFC00-2F-XXXXXX" = {
> acl = {
> };
> displayname = Business;
> records = (
> (...)"
>
>
> ACLs on calendar "Private" are configured to deny viewing/editing by
> other users whereas calendar "Business" has ACLs according to our SOGo
> default setup ("PublicViewer", "ConfidentialDAndTViewer").
>
> If user YYYY is now sending an appointment request to user XXXX this
> request is always posted to XXXX's "Private" calendar (SOGo Webinterface
> or Lightning doesn't make any difference). Why? I'd expect SOGo to take
> into account the restrictive ACLs set on calendar "Private" an thus
> choose the next public writable calendar "Business" as target for an
> appointment request. Or is it true that appointment request to XXXX are
> always sent to the "../Calendar/personal" or his "first calendar" since
> there is no option for user YYYY to choose the target calendar? If yes,
> is there any option to change this behavior? Or alternatively how can a
> user move an appointment request from another user to a calendar of his
> choice (I didn't find any option in the appointment response user dialog
> to do this)?
>
SOGo (and any other calendar server I know of) use a 'special' calendar
for adding invites.
As SOGo has to know the calendar name in advance, it uses
.../Calendar/personal for every user.
This calendar is created by SOGo on first login.
That calendar can also not be deleted by the user, because this would
break filing new invitations to it.
So yes, it is by design that SOGo uses this one calendar to
automatically store invitations in.
You should be able to move such events to other calendars, but there is
currently a bug, which prevents automated updating of these events after
such a movement (eg. when the owner/organiser changes the schedule for
this event).
By the way, if you don't give XXXDAndTViewer privileges for the private
calendar, you will not include these events in the free/busy information.
Kind regards,
Christian Mack
--
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
--
[email protected]
https://inverse.ca/sogo/lists
