On Fri, Jan 14, 2005, Paul J Stevens <[EMAIL PROTECTED]> said: > Why do we want to store alias information in the database: delivery > Why do we want to store user information in the database: authentication > > Both are at present totally intertwined, both in the code, and in the > perception of many users. However, if we can separate them, great things > are suddenly possible like pam-authentication (users in > ldap,passwd,radius...) while leaving the aliases in the database, or > even storing them elsewhere.
DBMail's authldap was designed to work with three well-known and working LDAP schemas: inetOrgPerson, qmail-ldap and Exchange. All three keep aliases together with user accounts, as does DBMail, both now and at the time I wrote the authldap module. So this is a natural. Separating them out might give huge new opportunities for people who go through the effort of making it work, but they can *already* do that. So all separating would do is kill what works now and is simple and straightforward to use. Authenticating from PAM would be neat, but unfortunately it isn't such a great database of user information beyond what's in a typical /etc/passwd file. Aaron
