Aaron Stone wrote:
On Sun, Jan 30, 2005, Paul J Stevens <[EMAIL PROTECTED]> said:
Aaron, do you have any objections to my taking over authldap for a while?
I don't mind at all. Let me know if you have any questions about my screwy
code in there. First suggestion: throw away the lists of lists of lists.
That was me not understanding how to do it any smarter.
Like how much smarter is your current understanding then? But that's just me unfamiliar with the ldap api
asking :) And I'm seeing some serious code duplication between the __auth_get calls that need cleaning up. But
I first need to complete the test-cases and finish the missing parts in the user-management chain. I've got
adduser working just fine already, and I can live with the nested list calls for now. I'll just remap them to
glists, no sweat. It's the alias management where some real plumbing is missing. So I won't be unfamiliar with
the ldap api for much longer I guess...
In short: I think I will drop support for a couple of fields (for now):
field_mailalt, mailaltprefix, field_forward, field_fwdsave, fwdtargetprefix,
field_members. These fields either have no equivalents in the
aliases table, or they reflect logic already implied by the delivery chain.
I'll dig up a config file I had that worked with Active Directory. Many of
these prefix settings were needed because AD uses all sorts of
"smtp:<address>" prefixes in places that make it just hard enough to do
the normal inetOrgPerson stuff that you would pull your hair out, give up,
and buy Exchange.
Great. Keep me posted please, because being able to talk to act.dir is a major
foothold, er selling point.
Btw, I'm using dsn.c's logic as definitive regarding delivery policy, right?
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
