Hi all, Did tried domain based UID but need full MUA support and intensive tests before putting into production. Domain base LDAP seems more logical. Currently we are implementing this method with online maintenance program to control for duplication UID and written batch extraction program from the ou in LDAP for /var/qmail/locals and rcpthosts every day mid-night.
In fact we did use qmail-ldap-control patch in one project. The problem caused in patching and finding error ine qmail-quotawarning program path nearly delayed our system delivery. This ended up with online maintenance program with qmail-ldap-control-patch schema and daily batch extraction from the LDAP to file based /var/qmail/control. KF ----- Original Message ----- From: "Adriano Nagelschmidt Rodrigues" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 01, 2002 12:07 AM Subject: Re: Large Number of Virtual Domains > K. F. Yim writes: > > 1) Domain based LDAP user entries that allow dynamic searching and POP3 > > authentication mechanism (uid=loginid,ou=virtualdomain.com) that allow > > duplicate UID under different domains. e.g. dn: uid=loginid, > > ou=virtualdomain.com,dc=domain,dc=com. > > Why not include the domain in the uid attribute? Eg > > [EMAIL PROTECTED] > > (some old MUAs don't like the `@', it has never been a problem for me) > > > 2) /var/qmail/control/locals and virtualdomains files that allows the > > handling of =>10,000 virtual domains > > You can try the qmail-ldap-control patch (I haven't used it yet). > > > 3) Domain based directory structure that support the above. > > dc=eg,dc=com > | > ou=domains > | > +---------------------------------- > | | | > ou=foo.com ou=bar.com ou=... > | > +---------... > | > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > Regards, > > -- > Adriano
