On Wed, Jan 17, 2001 at 05:10:15PM -0500, Chad Leigh, Shire.Net LLC wrote:

No, that is not the way to do what you want. It is not good practice to hardcode any sort of DN or DN hierarchy - any LDAP reference book will advise you against it.

You can use whatever hierarchy you like, but instead you need to put an attribute _within_ the LDAP entry with the E-mail address (or POP3/IMAP username) for that person.

e.g.

[dn: accountname=fred, domain=example.com, dc=mydomain, dc=net]

mail: fr...@example.com maildrop: /users/e/x/a/example/

You then configure Courier with a basedn of 'dc=mydomain, dc=net' and LDAP_MAIL attribute of 'mail'

When fr...@example.com logs in, Courier will do a search on the LDAP tree for "(mail=fr...@example.com)", and find the entry above. It then extracts the other parameters from this search (e.g. home directory, maildir, quota)

Optionally, you can configure Courier to do an LDAP bind to authenticate. In this case, rather than reading the password from a field in the entry, it will rebind to the LDAP server (using the DN of the record it just found in the search - so still no need to hardcode the DN format - plus the password supplied by the user)

Something you might want to do with virtual domains is have all mail for <anyone>@example.com going to one maildir. In my case I modified OpenLDAP, but in fact you could get Exim to do two LDAP lookups: first lookup "(mail=$local_part@$domain)", and if that fails, lookup "(mail=*@$domain)"

Then the LDAP database can have an entries like this:

mail: fr...@example.com maildrop: /users/e/x/a/example/

mail: *@example.com maildrop: /users/e/x/a/example2/

Then mail to 'fr...@example.com' will hit the first maildir, but ji...@example.com and bo...@example.com will hit the second. There's lots of flexibility to play with here. In my case I use a different LDAP attribute for the E-mail address (which Exim uses) and the POP3/IMAP username (which Courier uses), since our users historically don't use their full E-mail address as their POP3 login.

HTH,

Brian.