On Tue, Feb 01, 2005 at 06:09:27PM +0200, Zdravko Stoychev wrote: > Hi, > I am using latest qmail-ldap (dec 2004) and will not rallback to > Any previous release. > > You're right, remember > > "qmailGroup depends on qmailUser so we use the same > ~contol/ldapobjectclass in qmail-group" > > I propose and request an update where qmail-group would use > Different control file, for example: > ~contol/ldapGROUPobjectclass >
This does not work because of the following reasons. 1. qmailGroup depends on qmailUser is a schema restriction on OpenLDAP it is enforced so it is only possible to have a group entry with both objectclasses defined. objectclass: qmailUser objectclass: qmailGroup 2. a qmailGroup is just an extension of a qmailUser 3. qmail-ldap will use the ~control/ldapobjectclass to simplify the search and especially qmail-lspawn does not know the difference between a user and a group > Ignore caps. Here I suppose this behaviour: > > $ /var/qmail/bin/qmail-ldaplookup -m [EMAIL PROTECTED] > > Would first try to lookup with filter based on > ~contol/ldapobjectclass > > i.e. looking for an user, and if this fails a new lookup will > be executed with Filter based on > ~contol/ldapgroupobjectclass > > i.e. looking for group. > Or so, I don't know internal qmail logic. > This does not make sense. Why don't you just fix your LDAP entry by adding the needed objectclasses? In your case you need to added groups with objectclass: user objectclass: group -- :wq Claudio
