diff options
author | paul <paul@7b491191-dbf0-0310-aff6-d879d4d69008> | 2005-08-01 07:57:58 +0000 |
---|---|---|
committer | paul <paul@7b491191-dbf0-0310-aff6-d879d4d69008> | 2005-08-01 07:57:58 +0000 |
commit | fa77ccc27f5b9fe10bb92e6d65800b4f13499135 (patch) | |
tree | f95ef3d072f989dd348960f3393a56cfa5cef326 /README.ldap | |
parent | d12ba13b7acd5dca39aa5ca098ed44de36e7b81f (diff) |
update README.ldap and close some memory leakages
git-svn-id: https://svn.ic-s.nl/svn/dbmail/trunk/dbmail@1828 7b491191-dbf0-0310-aff6-d879d4d69008
Diffstat (limited to 'README.ldap')
-rw-r--r-- | README.ldap | 28 |
1 files changed, 26 insertions, 2 deletions
diff --git a/README.ldap b/README.ldap index f330f04e..411b7ee7 100644 --- a/README.ldap +++ b/README.ldap @@ -1,9 +1,33 @@ $Id$ Dbmail-2 as of 2.1.0 supports ldap for authentication and delivery information. -For now, I'm just providing some more information on the new ldap related -configuration items. I'm also including an example dbmail.schema file. + +NOTICE: + +If you have an existing userbase in sql that you which to migrate to ldap-auth, you +must make sure that the uidNumber in ldap is the same as the dbmail_users.user_idnr +in sql. If your tables are in MySQL/innoDB or PostgreSQL, and you have a proper cascade +setup for the foreign key in dbmail_mailboxes like: + + CONSTRAINT dbmail_mailboxes_ibfk_1 FOREIGN KEY (owner_idnr) + REFERENCES dbmail_users (user_idnr) + ON DELETE CASCADE ON UPDATE CASCADE + +you should be able to issue simple UPDATE statements to reset the user_idnr values in sql. + + + +LDAP-SCHEMA: + +I'm providing an example dbmail.schema file that should get you started. + + + +CONFIGURATION: + +dbmail.conf contains some new ldap items: + --- "BIND_DN" |