[Date Prev][Date Next]
Re: ldap structure for multi domain.tld email hosting
--- Edwin Culp <firstname.lastname@example.org> wrote:
> Quoting "Gary C. New" <email@example.com>:
> | I am attempting to setup an email hosting
> | with postfix, cyrus-imap, and openldap that will
> | support several of my current clients and those
> that I
> | wish to bring on in the future. Each client has
> | individual domain.tld or domains.tld with various
> | users under each domain.tld.
> | I've seen a few postings regarding the subject,
> but am
> | wondering what might be the best structure for
> this in
> | ldap?
> | One posting suggested seperate o= attribs:
> FWIW, I would change the dn to use mail to simplify
> the seperation
> of multiple gary's - gary@domain1 gary@domain2, etc.
> dn: firstname.lastname@example.org,o=yourcompany.com
> I actually throw in an ou=people for
> | dn: uid=someuser, o=someorg, c=us
> | uid: someuser
> | userpassword: somepassword
> | maildrop: email@example.com
> | mailacceptinggeneralid: someuser
> | mailacceptinggeneralid: somealias
I appreciate your reply and suggestion. I have a
couple of more questions I thought you might know.
I am new to the ldap architecture, but understand that
like any structure it is important to develop a good
understanding of what is needed and then decide on the
best way of implementing it. In terms of ldap, I've
read that there are 2 basic types of structures used:
flat and hierarcle. It has been suggested that the
flat structure is the better way to go and am trying
to decide on a flat scheme that will best suite my
needs for ldap authentication using postfix,
cyrus-imap, and a ldap based per organization address
book. I am also trying to tie all this in using SASL
(simply for digest-md5 authentication while user
passwd's will be stored in plain text in their ldap
I previously outlined a few of the basic attributes
that will be needed per ldap entry, but for security
purposes would it be better to separate each client
company's entries per an organizational unit?
Wouldn't this better segment the entries and allow a
distinct per organizational unit address book list?
This would further allow me to continue my use of the
uid attribute (which I believe is required for SASL
authentication) rather than being forced to use the
mail=user@domain attribute in a single group. Any
idea how I might tie a mailling list to a client
company's group? I guess my real problem, at the
moment, is the fact that I don't know how ldap's
default attributes work (i.e., o=, ou=, objectclass).
This is how I currently picture the structure in my
mind (a kind of 2 tier then flat model):
rootdn -- company2 -- user1 -- user2 -- user3
As always, comments and suggestions are appreciated
(especially ldif examples).
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes