Hey,
Long story short, I no longer maintain an Active Directory user base, and I
don't have my configs around to double check my memory. So I'll do my best...
and if we get descriptive enough, let's make this thread part of the
documentation project, LDAP could really use a help text!
I'm pretty sure that there are Exchange2k-ism's that need to be worked out --
in particular, I'd like to be a near drop-in replacement for qmail-ldap and to
function with inetOrgPerson and posixPerson accounts. Let me know if you have
any trouble getting things to work!
More inline...
Paul J Stevens <paul@nfg.nl> said:
>
> Hi all, and esp Aaron,
>
> I'm trying to test/debug the authldap layer, but I'm not exactly clear
> as to how all the fields are supposed to operate.
>
> Could you Aaron please document the fields as allowed in the dbmail.conf
> file.
>
> I'm all clear on these:
Ok, I'll try giving a brief explanation anyways, for future posterity and
those who might be new to LDAP and not recognize as many key words yet.
>
> "BIND_DN"
This is the Distinguished Name of the user who has read access to the LDAP
server. It is not recommended to use an Administrator or Manager account, as a
precaution in case the mail server is compromised.
> "BIND_PW"
The plain text password of the account above. Again, preferably not an
Administrator or Manager account.
> "BASE_DN"
The root or starting point from which searches will be conducted. All searches
use the LDAP_SCOPE_SUBTREE option to search everything in this base and below.
> "PORT"
The port number that the LDAP server is listerning on. By default, 389 for
insecure and 636 for secure, however secure LDAP is currently unsupported.
> "HOSTNAME"
The hostname of the LDAP server. May be an IP address.
> "OBJECTCLASS"
The object class to use as a search filter, typically 'user', 'inetOrgPerson'
or possibly something else in more complex LDAP environments.
> "FIELD_UID"
The field which contains the user login name of the user. Required.
> "FIELD_CID"
The field which contains the group id number of the user. Not required.
> "FIELD_QUOTA"
The field which contains the quota, in bytes, of the user. Not required.
> "FIELD_PASSWD"
The field which contains the password of the user. Not implemented.
>
> but how exactly are the following fields supposed to work/interact or
> map to authsql:
>
> "FIELD_MAIL"
The field which contains the primary email address of the user. Required.
> "FIELD_MAILALT"
The field which contains an alternate email address of the user. Not required.
> "FIELD_NID"
The field which contains the user id number of the user. Required.
> "MAILALTPREFIX"
A prefix which may appear on the MAILALT entry and should be ignored. MS
Exchange 2000 uses the prefix 'smtp:'. Not required.
> "FIELD_FORWARD"
The boolean field which indicates if email should be forwarded or not.
> "FIELD_FWDSAVE"
The boolean field which indicates if email should also be delivered locally if
it is forwarded.
> "FIELD_FWDTARGET"
The field which contains a destination email address for forwarding mail.
> "FWDTARGETPREFIX"
A prefix which may appear on the FWDTARGET entry.
> "FIELD_MEMBERS"
The field containing a list of DN's to users in the email distribution group.
>
> I would much appreciate some enlightenment regarding this issue.
>
> thanks,
>
>
> --
> ________________________________________________________________
> Paul Stevens paul@nfg.nl
> NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
> The Netherlands_______________________________________www.nfg.nl
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
--