***SPAM*** Re: OpenLDAP

John McMonagle johnm at advocap.org
Thu Mar 5 23:25:39 CET 2015


On Thursday 05 March 2015 9:25:54 AM Mihai Badici wrote:
> 
> On Thursday 05 March 2015 08:55:48 John McMonagle wrote:
> > I know this is a old thread but has anything been done to provide openlap
> > support yet?
> > 
> > I'm still running kolab 2.3.4.
> > We are a debian shop in many cities and 7 ldap servers.
> > Kolab is a small part of our ldap usage and see no rational upgrade path.
> > This is primarily caused by no way to sync between openldap and 389ds.
> > 
> > If I don't hear of a solution I'm going to something else.
> > 
> > John
> 
> 
> If you have your ldap infrastructure it means you have your user's management 
> mechansm.
> You can use elements of kolab but i think even if kolab support openldap by 
> default you cannot use the full suite but instead you can adapt it at yours 
> needs.
> 
> I use for years parts of kolab suite with dovecot and openldap ; some features 
> are not available but I take advantage of metadata addons from kolab which is 
> the main advantage of the product. 
> 
To what extent does your openldap and kolab interact?
Just user account info?

I'm using ldap account manager to manage ldap.
Using the the kolab plugin in ldap account manager to manage kolab.
The most important part is kolabd sees there is a new account and creates the inbox.
If I can't get that part working it's not worth doing.
I'd rather not have to have to create mailboxes separately.

I use scripts to archive old accounts and remove the mail spools with cyradmin.

Been running kolab this way for a long time.
I've upgraded kolab a couple times and it's always challenging dealing with the ldap changes.
The mail spool is the easier part, just takes a while.
I've been working with cyrus imap a lot longer than kolab.


John


> 
> > 
> > On Thursday 11 September 2014 11:18:27 AM Stuart Naylor wrote:
> > > I would also be interested in other LDAPs.
> > > 
> > > I am still trying to weigh up 389-DS winsync.
> > > 
> > > I did notice setup-kolab has an activedirectory parameter which would be
> > > great with samba4.
> > > 
> > > Also seems to be no documentation.
> > > 
> > > On Thursday 11 September 2014 12:54:34 Tobias Brunner wrote:
> > > > Hi,
> > > > 
> > > > It seems to be possible to use OpenLDAP as LDAP server instead of 389ds,
> > > > but the documentation has just a title and no more content:
> > > > http://docs.kolab.org/architecture-and-design/ldap.html?highlight=openld
> > > > ap#i ntegration-with-openldap
> > > > 
> > > > How do we use OpenLDAP instead of 389ds?
> > > > 
> > > > Cheers,
> > > > Tobias
> > > > _______________________________________________
> > > > users mailing list
> > > > users at lists.kolab.org
> > > > https://lists.kolab.org/mailman/listinfo/users
> > > 
> > > ____________________________________________________________
> > > FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
> > > Check it out at http://www.inbox.com/earth
> > 
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> 


More information about the users mailing list