Hello

If people are in multiple addressbooks, they will show up multiple times
on autocompletion in attendees search field.

In SOGo V2 the ones not from global addressbook (=non LDAP) will show a
pink square in front of them.
Therefore you can choose the one without a pink square and are done.

In V3 there is no such marking, but you almost always get the one from
global addressbook as first entry.
If this first one still shows "no Free/busy information", you have to
remove the attendee again, and add the second entry.

Hope that is clear enough.


Kind regards,
Christian Mack

Am 15.03.2018 um 13:41 schrieb Sascha Kasch ([email protected]):
> obviously the terms were wrong.
> people add users to a personal list within the addressbook. and users
> from this list are not being looked up in LDAP when invited to an event.
> i created a list and tried to add members from LDAP but this does not
> seem to be possible, at least not from sogo webfrontend.
> thunderbird allows to add users from LDAP.
> so my question: will members of a list in a private addressbook be
> considered when doing free/busy lookups?
> 
> thanks,
> 
> sascha
> 
> 
> Am 13.03.18 um 11:55 schrieb Sascha Kasch ([email protected]):
>> Dear List,
>>
>> does anyone know how to get SOGo to make a free/busy lookup for
>> persons in a private addressbook?
>> Current Case: we have LDAP with all Users inside. As projectgroups are
>> very dynamic, people make groups
>> in their private addressbook and add their team-members from global
>> addressbook (LDAP).
>> When they now want to invite the group to an event they have the
>> problem that a free-busy lookup is not possible/available
>> though all members of the group are also available within LDAP.
>>
>> Is there any chance to make this work or do we have to stick with
>> LDAP-Groups?
>>
>> thanks,
>>
>> Sascha
>>
> 


-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to