Dear developers,
Is it possible to use a separate filter for searching members of LDAP contact group in Roundcube-0.6-beta? I'm not so clear how to achieve this after reading comment in main.inc.php.dist.
Currently, my LDAP structure looks like below:
,ou=Groups,dc=xxx.
mail=user01@domain.ltd,ou=Users,dc=xxx, with attribute 'memberOfGroup=group01@domain.ltd' to identify group membership.
How can i list members of contact group in Roundcube Address Book? Maybe add 'filter_members' in "groups => array();" like below:
'groups' => array( 'filter_members' => '(memberOfGroup=%u)', ... ),
Thanks for your great work, and looking forward to your reply.
List info: http://lists.roundcube.net/dev/ BT/aba52c80
Hei Zhang well, the implementation of the contact groups is a first start, and your situation is not yet implemented! One reason is that I have not found a 'standard' like this! The current implementation just uses standard LDAP schemas: contacts in ou=Contacts,dc=xxx groups in ou=Groups,dc=xxx (or even ou=Contacts,dc=xxx in as well) and the group membership is stored in the 'member' attribute of the group record, using the groupOfNames capability of the core.schema
To improve your feedback: please give me the informations:
To conclude: your solution has some advantages over the current in RC, I am thinking about an implementation for it, but I have to find out about "standards" first.
thanks for feeback Andreas
Am Samstag, 20. August 2011, um 16.58:34 schrieb Zhang Huangbin:
Dear developers,
Is it possible to use a separate filter for searching members of LDAP contact group in Roundcube-0.6-beta? I'm not so clear how to achieve this after reading comment in main.inc.php.dist.
Currently, my LDAP structure looks like below:
- All groups are placed under ou=Groups,dc=xxx. e.g.
mail=group01@domain.ltd ,ou=Groups,dc=xxx.
- Group members are placed under ou=Users,dc=xxx, e.g.
mail=user01@domain.ltd,ou=Users,dc=xxx, with attribute 'memberOfGroup=group01@domain.ltd' to identify group membership.
How can i list members of contact group in Roundcube Address Book? Maybe add 'filter_members' in "groups => array();" like below:
'groups' => array( 'filter_members' => '(memberOfGroup=%u)', ... ),
Thanks for your great work, and looking forward to your reply.
List info: http://lists.roundcube.net/dev/ BT/aba52c80
Hi Andreas,
Sorry for your late response.
On Sat, Aug 20, 2011 at 11:31 PM, Andreas Dick andudi@gmx.ch wrote:
To improve your feedback: please give me the informations:
- what server do you use?
I'm core developer of iRedMail[1] project, it's a free and open source mail server solution, works on 7 major Linux/BSD distributions.
With iRedMail, you can store mail accounts in OpenLDAP or MySQL. We have our own OpenLDAP schema to store mail accounts: http://code.google.com/p/iredmail/source/browse/iRedMail/samples/iredmail.sc...
- homebrew, public, commertial?
iRedMail should be considered as public + commercial, many users are running iRedMail on production servers. Success stories: http://www.iredmail.org/stories.html
- what schema do you use for the 'memberOfGroup' attribute? kind of
standard?
OpenLDAP has a default attribute "member" for membership, you must use full dn as value. If you moved an object to another container, you have to update value of attribute 'member'. It's not flexible enough.
We create our own attribute "memberOfGroup" for this purpose, use email address as value, each email address can identify an mail user object. So that you don't need to care about full dn.
[1] iRedMail: http://www.iredmail.org/
List info: http://lists.roundcube.net/dev/ BT/aba52c80
On Sat, Aug 20, 2011 at 11:31 PM, Andreas Dick andudi@gmx.ch wrote:
To improve your feedback: please give me the informations:
- what server do you use?
I'm core developer of iRedMail[1] project, it's a free and open source mail server solution, works on 7 major Linux/BSD distributions.
well, interesting.
With iRedMail, you can store mail accounts in OpenLDAP or MySQL. We have our own OpenLDAP schema to store mail accounts:
http://code.google.com/p/iredmail/source/browse/iRedMail/samples/iredmail.sc... ok, thats verry proprietarry!
OpenLDAP has a default attribute "member" for membership, you must use full dn as value. If you moved an object to another container, you have to update value of attribute 'member'. It's not flexible enough.
yes. RC is handling this. I do not see why it is not flexible enough four you, but you will have a reason for it.
We create our own attribute "memberOfGroup" for this purpose, use email address as value, each email address can identify an mail user object. So that you don't need to care about full dn.
You just do it the other way arround. One problem of your sollution is that other LDAP addressbook clients can not be used out of the box., a pro is that group lists and member filters can be made easier.
To conclude: I am looking for a solution like yours, but it shoud use per default the standard schema features of e.g. a plain OpenLDAP server (like core.schema).
Andras _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/aba52c80