Hello,

I remind my question, I still need some way to make the "LDAP Resource" turn off auto-acceptance. I think it's not user friendly to modify LDAP, for such banality.

Would you please consider this?

Thank you.

Some change for this ticket?

Thank you.

It is not clear to me, what you want to achieve.

If you do not want to allow invitation for that room from everyone, you can disable that in the settings under "Preferences" -> "Calendar Options" -> Appointments Invitations"
That will forbid invitations to this room except from the users allowed in the whitelist.

Is that what you want?

Thank you for reaction.

We probably don't understand each other. I don't want to block invitation for a user calendar, but for an "LDAP room" configured by http://wiki.sogo.nu/ResourceConfiguration with auto-accept.

This room can be added by user like "shared folder" in their subscription list. Then people adding their events into this shared calendar, by inviting this room as a participant of action. Room will automaticly accept the invitations (by auto-accept) according the triggers for concurrent actions in LDAP. But Sogo allows you to set only more then zero concurrent action, not zero.

I did understand that much.
You use a Resource account for that room.

If you set MultipleBookings to 0 it will allow unlimited concurrency.

I do not see any use case to set it to a new -2 or "don't allow automatic accepting at all".
As you get that with normal accounts anyway.
You just have to remove the additional attributes and objectClasses from that rooms LDAP entry, in order to get that functionality.

0 for unlimited
1 for 1
2 for 2
...
I meant "something for 0".

In documentation is written:
If set to -1, no limit is imposed but the resource will be marked as busy the first time it is booked.

That mean, -1 is for 0?

I'm trying it now, and that's not working. The event is still created.

"You just have to remove the additional attributes and objectClasses from that rooms LDAP entry, in order to get that functionality."
Modify ldap because of such things, seems to me unnecessarily complicated.

I used -2, because that is an unused value (currently illegal).
Which means that this value doesn't mean anything right now, but can be used for new features.

-1 means:
You have unlimited concurrence like 0, but you see it as busy, when someone has booked it already.

If LDAP changes are difficult, depends on your environment.
I can not comment on that.
But the point of a resource is to be automatically bookable.
If you don't want that, don't use it.

I suggested -2 as an alternative, to not having to make a change in ldap. I find it as a good idea, if you want to make a quick change, or you need to do it periodicaly.

If someone in future will have same usecase as we do, it will be annoying for them too. Probably it will have to do some script outside the Sogo for that.

Therefore I still ask for the addition of this feature. It's only one parameter, which can improve behavior of Sogo. For me a lot.

Thanks that you made time for me.

Some progress in this?

I still miss an opportunity to set up option to reject auto-accept event, when somebody try to create event first time.

Thanks.