Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-03 Thread Chris
On Tue, 30 Oct 2018 21:40:07 +0100 Rene Schroth wrote: > Could it be that in order to use both LDAP and SQL user sources some > further configurations have to be performed? Ok, I read in your other post, that you're using LDAP for resources with proper attributes now. I think the LDAP / mySQL

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-02 Thread Michal Kminek
Hi Irma, in SOGo you can set a superuser in sogo.conf then under that user you can set rights to any calendar in SOGo Web GUI. Alternatively set a password to your resource and login into its SOGo Web GUI. Kind Regards, Michal Dne 02.11.2018 v 17:14 Rene Schroth (rene.schr...@mmlab.de)

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-02 Thread Rene Schroth
Hi Michal, the question was, how are you able to set the ACL, if you cannot login with your resource's account into SOGo Web GUI in order to manipulate the "Sharing" settings. BR Irma ___ Am 02.11.2018 um 16:05 schrieb Michal

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-02 Thread Michal Kminek
Hi Irma, use the email attribute with your resource and use any email address. For me "View Time and Date" for "All Authenticated Users" was sufficient. You can set higher rights for certain users so they can see event details. Regards, Michal Dne 02.11.2018 v 12:06 Rene Schroth

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-02 Thread Rene Schroth
Hi Michal, > It's not important whether you have mailGroup objectClass or not I know. Any oC providing the mail attribute is required. >Just > review the objectClasses you mentioned for the email attribute and > choose one. My LDIF has objectClass mailUser and inetOrgPerson. Both of them

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-02 Thread Michal Kminek
Hi Irma, It's not important whether you have mailGroup objectClass or not. You need to add any objectClass that contains an email attribute. Just review the objectClasses you mentioned for the email attribute and choose one. Then check all attributes of the objectClasses, some attributes can

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-01 Thread Zhang Huangbin
> On Nov 1, 2018, at 8:47 PM, Rene Schroth (rene.schr...@mmlab.de) > wrote: > > 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 >

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-01 Thread Rene Schroth
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

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-11-01 Thread Rene Schroth
Hi Michal, thank you very much for your reply. Great to know, that generally LDAP calendar resources in SOGo work without restriction. I guess that you do not use the iRedMail OpenLDAP server, because I do and there's no objectClass mailGroup available. My iRedMail OpenLDAP installation

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-31 Thread Michal Kminek
Hi Irma, we use LDAP for users and resources. Just to comment some entries, Multiplebookings attribute works as expected the resource can be booked only once if set to 1, free/busy is shown correctly. We use mailgroup class so that our resource can have its own email address, the email

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-30 Thread Rene Schroth
Hi Chris, thanks for your suggestion using SQL for calendar resources. I added it to my sogo.conf to give it a try. Unfortunately, the SOGo Web Interface is not accessible anymore having added it (502 Bad Gateway). Could it be that in order to use both LDAP and SQL user sources some

[SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-30 Thread Rene Schroth
Approved that it is an LDAP issue: - Removed objectClasses calEntry and CalendarResource from Meetingroom's LDAP set. - Result: Free/Busy times are being displayed during event creation! Again the question: Is there anybody with a working LDAP resources setup who could provide a sample

[SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-30 Thread Rene Schroth
My resources' Free/Busy times still won't work. For normal users, Free/Busy times work fine! Here's more detail about the configurations. (1) Resource 'meetingroom' created in LDAP, resides in the same OU as the normal users. Has same objectClasses and attributes as normal user accounts PLUS

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-23 Thread Zhang Huangbin
> On Oct 23, 2018, at 11:29 AM, Christian Mack (christian.m...@uni-konstanz.de) > 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

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-23 Thread Christian Mack
Hello Am 22.10.18 um 16:00 schrieb Rene Schroth (rene.schr...@mmlab.de): > Hi SOGo Users and Admins! > > My setup consists of iRedMail (current version) with OpenLDAP and SOGo > Groupware. > > I almost implemented the calendar resources, using calendarResource and > calEntry objectClassings. >

Re: [SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-22 Thread Chris
On Mon, 22 Oct 2018 16:00:16 +0200 Rene Schroth wrote: > In the SOGo Installation manual > https://sogo.nu/files/docs/SOGoInstallationGuide.html I read about a > further attrbute called 'MultipleBookingsFieldName'. BUT: LDAP does > not provide this attribute! If one modified the schema, maybe

[SOGo] SOGo Calendar Resources | Free/Busy Times

2018-10-22 Thread Rene Schroth
Hi SOGo Users and Admins! My setup consists of iRedMail (current version) with OpenLDAP and SOGo Groupware. I almost implemented the calendar resources, using calendarResource and calEntry objectClassings. Only remaining issue is, that the resource's (for instance: meetingroom) FREE/BUSSY