John T. Guthrie III wrote: >> The foreign key would be useful in the case where someone wants to migrate >> an already existing database to LDAP authentication.
A constraint on deliver_to is not possible because that field is overloaded. It is also used for external delivery destinations (email addresses). Yes that is poor design. It's been there forever (well before I came on board anyway). And it's a known fixme. But then, once you use ldap it is not an issue any more. > I made this statement based on the statement in the README.ldap file that says > that the uidNumber in LDAP needs to be the same as dbmail_users.user_idnr. > But looking at dbmail.schema, it says that dbmailUser in LDAP can also have > a dbmailUID attribute. Does that attribute get used? If so, does it > obviate the need to go around changing UIDs? You can select whatever ldap attribute you like to map to the user_idnr column in dbmail.conf. That is LDAP for you, maximum flexibility. You don't even need to use dbmail.schema if you have another schema that provides all necessary attributes (like Active Directory does). I wrote (or rather finished) the ldap code and constructed dbmail.schema using the minimum set of attributes. It is meant to allow people to get started using authldap with a minimum fuss. uidNumber seemed most appropriate for anyone using posixUser or inetOrgPerson. Later someone proposed adding a dbmailUID attribute for easier deployment on their systems, but it's not used by default. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
