> On Oct 23, 2018, at 11:29 AM, Christian Mack (christian.m...@uni-konstanz.de)
> <users@sogo.nu> 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
--
users@sogo.nu
https://inverse.ca/sogo/lists
