Hi Huangbin,
it would be great if you could confirm that iRedMail/OpenLDAP/SOGo is
defective regarding the calendar resources' FREE/BUSY times.
As we figured out, running SOGo with different LDAP servers, the
calendar resources work without issues.
Maybe it helps you if I tell you what is the "breaking" point regarding
FREE/BUSY times:
As soon as you add the calEntry or calendarResource objectClass to an
LDAP user account, the BUSY time is not being displayed correctly
anymore. It will always show FREE!
Removing the objectClass again, BUSY time is being shown correctly, but
of course the account is no resource anymore and auto-accept on
invitation won't work anymore.
BR
Irma
_______________________________________________________________
Am 23.10.2018 um 15:30 schrieb Zhang Huangbin ([email protected]):
On Oct 23, 2018, at 11:29 AM, Christian Mack ([email protected])
<[email protected]> wrote:
multiplebookings set to -1 or 0 will not restrict overbooking at all, -1
will only show it booked already.
multiple bookings set to 1 will only accept an invitation automatically,
if there is no event already at that time.
Check if that blocking event has "show time as free" set.
In that case it will not block overbooking.
I once had a problem with a client who had set a non existing time zone
in his client, while inviting.
Just for completeness:
Overbooking is always possible by the owner of that account and everyone
who have direct write privileges.
Only invitations of that account are restricted.
MultipleBookingsFieldName is only used, if you do not use the standard
calendarResource and calEntry schemas.
Then you can give another LDAP attribute name for looking up the
MultipleBookings value.
Hi Christian,
How about add this info to the official SOGo document?
----
Zhang Huangbin, founder of iRedMail project: https://www.iredmail.org/
Time zone: GMT+2 (Slovenia/Ljubljana).
Available on Telegram: https://t.me/iredmail
--
[email protected]
https://inverse.ca/sogo/lists
