a few more questions

[Gustavo Michels]

I "kind of" have Kolab2 working with pam_ldap and nss_ldap. As I nedded an 
OU to hold all the users (so that nss_ldap works), and kolab creates users 
on the root of the ldap server, I am doing all user administrative tasks 
thru an ldap tool (phpldapadmin), since kolab will move the user back to 
its default if I edited in the web interface. Also, I added the nis schema 
to the kolab openldap template.

What I do is create users with uid as "user" and add the attribute email as 
"user at domain". When the email attribute is added, kolab detects the new 
user and does normal process of creating mailbox, etc.

At first everything looks ok, although I haven't done much testing yet. I am 
going to try it with a few clients on a test lab, and if it goes ok, I will 
try to change the php code on the web interface to use the OU I created 
when managing users.

Now my question is: does any developer see any problem in Kolab usability by 
doing these changes?

cheers
Gustavo

Em Wednesday 08 September 2004 12:53, Jean-Michel Dault escreveu:
> On Wed, 2004-09-08 at 02:58, Bo Thorsen wrote:
> > > Completely separated virtual domain aka multidomain are not supported
> > > with the upcoming Kolab2, because it is difficult to handle this
> > > within the ldap.
>
> The way I handle it, is to get rid of the @domain part for the uid, and
> just use the user. Then create an alias for the user.
>
> I don't understand why kolab insists on having user at domain. It means you
> can't use Kolab for pam_ldap, samba, etc.
>
> The only advantage is to be able to have the same user on multiple
> domain, but since Kolab doesn't support virtual domains, it's totally
> useless.
>
> Besides, what most ISPs do these days is assign a random user, for
> example b1i8rug6, which gives 36^8 possibilities (enough for every human
> on the planet and their dog) and they let people choose their own e-mail
> and possibly aliases.
>
> > Would it be an idea to have a webpage with kolab hacks? If someone can
> > tell me how to hack cyrus for this, I will definitely write a page with
> > it.
>
> I have rewritten Kolab 1.0 to manage user without an @domain part, and
> made it work with Samba and pam_ldap. There will be a lot of work to
> port it to Kolab 2.0, but IMHO it's definitely the way to go.