Hi,
We have recently discovered that end users can configure their SOGo
account to "prevent from being invited to appointments".
Good function.
However, it has the side effect, that when we (the institute) want to
invite [email protected], we can no longer send out that
invitation, as a single person has his agenda blocked for appointments.
Of course we can request that person to whitelist
[email protected]. That will solve it, but tomorrow another person
will discover the function, and we need to talk to that person again.
An idea could be to allow admins to populate the whitelist function
through sogo.conf, or using the SOGo administration screen in the web
interface.
Or perhaps a popup to say: "This invitation to [email protected]
will not be sent to userX, because he/she has configured his account to
prevent appointment invitations."
Is there a better way forward? It's a bit strange that with this (in
itself a useful) function, basically any person is able to make
institute-wide invites impossible.
Or are we missing something?
MJ
--
[email protected]
https://inverse.ca/sogo/lists
