Kevin,
Few days ago I've posted a message under the subject of "The simplest DIT for working with virtual domains". I don't think you're looking for the simplest solution, but i'm cutting and pasting it here for you to see what I'm doing here in my installation.
Some fellows on the list told me they are running the same installation I'm doing and they're feeling fine.
bruno.
----- Original Message ----- From: "Bruno Negr�o"
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 07, 2004 8:00 PM
Subject: The simplest DIT for working with virtual domains
Hi all,
I'm the system administrator of an Internet Provider with lots of virtual domains. Each of them, full of e-mail accounts.
I'm thinking about which would be the simplest Directory Information Tree for working with these virtual domains.
I'm not interested here with the directory concepts of "gathering and
sharing enterprise information to many different applications..." etc. All
I want now is administer these virtual domains and email accounts. This
directory will be used just by my qmail-ldap mailserver (and the cluster
members).
I think a lot of system administrator have just the same interest as me.
So, I'm imagining what this simple DIT could be.
To start, the BaseDN would be simply: dn: ou=QMAIL-LDAP
Each domain would have its own DN, so i could set their e-mail accounts as
their child entries.
For example, the domain "somedom.com" would have the DN: dn: ou=somedom.com, ou=QMAIL-LDAP
Its e-mail account would have DN's like: dn: [EMAIL PROTECTED], ou=somedom.com, ou=QMAIL-LDAP dn: [EMAIL PROTECTED], ou=somedom.com, ou=QMAIL-LDAP
The same way, the domain "otherdom.com" would have the DN: dn: ou=otherdom.com, ou=QMAIL-LDAP
And it's users would be: dn: [EMAIL PROTECTED], ou=otherdom.com, ou=QMAIL-LDAP dn: [EMAIL PROTECTED], ou=otherdom.com, ou=QMAIL-LDAP
I think this is all that i need...
Does someone out there have a compelling reason for me to add those weird
"ou=braziliancorp, ou=com, c=br" as the basedn of my directory? Since I
don't need "integration of the enterprise information", wouldn't this
simple DIT suffice for my mailserver?
Is there some important point that I am missing? Setting the DIT this way,
would I invalidate some important feature?
Thank you all, bruno.
