Quoting Claudio Jeker <[EMAIL PROTECTED]>:
a) neither qmailUser nor qmailGroup are structural object classes so qmailUser is not a user. It is an extension to an other object that give the object the necessary information about how to do mail deliveries in qmail-ldap. You could attach a qmailUser to a o, ou, c or whatever object in LDAP. There is no restriction that the result is a User -- actually the object becomes some sort of qmail-ldap (virtual) user. b) qmailGroup extends qmailUser so that the union of the two defines a qmail-ldap group. This are the basics of object oriented design. qmailGroup just defines and enforces the values that are neccesary. c) it is how qmail-ldap works. As you already noticed qmail-ldap may use the objectclass=qmailUser to tighten the search. d) qmailGroup automaticaly inherits all changes done in qmailUser
I'm always annoyed about schema definitions that where incorrectly done and most often end up as structural or overspecified. It seems like most people did not get the idea behind the objectclass model and correct schemas and so they fiddle around something till some version of OpenLDAP loads it. To be honest I have to include myself in that list because we still have some minor strangenesses in our qmail.schema but a lot was fixed lately. It took me years to understand the full concept of LDAP.
Is there any resource out there (web site, FAQ, etc.) that you've found helpful
in understanding how all this works / fits together? I've always been curious
about this and haven't found anything great about LDAP object/schema design.
Thanks Amith
