a few more questions
Stephen Hind
s.hind at rwp.co.uk
Wed Sep 8 18:07:06 CEST 2004
I couldn't agree more!
We use Kolab 1 on MandrakeLinux 10 and I re-use (hook into) the LDAP
database for some of the purposes Jean-Michel has outlined: multiple domain
handling; Samba and Apache Authentication.
Well done MandrakeSoft for taking this bold step, but a bigger thank you to
the Kolab project for making this an GPL Open Source project: without using
this software model MandrakeSoft could not make these changes.
Just to make a point has MandrakeSoft submitted these changes back to the
Kolab project.
Stephen Hind
> -----Original Message-----
> From: kolab-users-bounces at kolab.org
> [mailto:kolab-users-bounces at kolab.org]On Behalf Of Jean-Michel Dault
> Sent: 08 September 2004 16:54
> To: Bo Thorsen
> Cc: kolab-users at kolab.org
> Subject: Re: a few more questions
>
>
> 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.
>
> --
> Jean-Michel Dault <jmdault at mandrakesoft.com>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>
More information about the users
mailing list