On Mon, Feb 23, 2004 at 10:28:00AM -0600, Chris Garrigues wrote: > > dn: cn=users,ou=group,dc=trinsics,dc=com > > ------------------------------------------------------- > > objectClass: posixGroup > > objectClass: trinsixGroup > > objectClass: sambaGroupMapping > > objectClass: qmailGroup > > mail: [EMAIL PROTECTED] > > mailAlternateAddress: [EMAIL PROTECTED] > > uid: undefined (forward only account required) > > accountStatus: undefined -> active > > mailHost: undefined > > homeDirectory: /var/tmp > > aliasEmpty: using default > > qmailDotMode: ldaponly > > qmail-ldaplookup: fatal: qldap_get_uid: needed value is missing > > > > So....UID needs to be set to something? "alias"? > > Now I'm really confused. neither uid nor mailhost are valid fields for > qmailGroup. Does my object need to also be a qmailUser as well as a > qmailGroup? >
1. Yes. qmailUser is needed for qmailGroup, there seems to be a bug in the schema because we should enforce that right there. 2. your entry is missing the qmailUID and qmailGID values or the corresponding ~control files, so qmail-lspawn is unsable to setup and run qmail-local which would then call qmail-group. 3. normaly it is the best to setup a "normal" user and extend it to a group account. 4. the question about ldapobjectclass posted before should now be obvious. qmailGroup depends on qmailUser so we use the same ~contol/ldapobjectclass in qmail-group. The special group login and password control file are here to make it possible to use filter that produce a large number of results and would therefor end in the ldap limit. -- :wq Claudio
