Hello,
I'm working on somewhat mimicking the auth/storage seperation
of dbmail in weDBmail, and noticed a couple things that I had
questions about, and possibly should be straightened out in dbmail.
First is with aliases - should they be part of the authentication,
or part of the storage? Both sets of functions work directly with
the aliases table, and it seems that is probably wrong (consider
ldap authentication - are aliases in ldap or the database?).
The second issue is auth_adduser() - it creates an INBOX for the
new user, which seems wrong, as that is definitely a storage related
function. Probably just having auth_adduser() call
db_createmailbox() would be a clean solution. (Aaron - how does
your ldap patch handle this?)
Awaiting comments/insight,
Jesse
--
Jesse Norell
jesse (at) kci.net
I'm working on somewhat mimicking the auth/storage seperation
of dbmail in weDBmail, and noticed a couple things that I had
questions about, and possibly should be straightened out in dbmail.
First is with aliases - should they be part of the authentication,
or part of the storage? Both sets of functions work directly with
the aliases table, and it seems that is probably wrong (consider
ldap authentication - are aliases in ldap or the database?).
The second issue is auth_adduser() - it creates an INBOX for the
new user, which seems wrong, as that is definitely a storage related
function. Probably just having auth_adduser() call
db_createmailbox() would be a clean solution. (Aaron - how does
your ldap patch handle this?)
Awaiting comments/insight,
Jesse
--
Jesse Norell
jesse (at) kci.net