[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kroupware
Subject:    Re: [Kroupware] jabber
From:       Christian Ledermann <lists () futuresign ! de>
Date:       2004-03-06 21:19:35
Message-ID: 1078607975.17411.17.camel () web ! futuresign ! de
[Download RAW message or body]

Am Fre, 2004-03-05 um 22.09 schrieb Mathieu Chouinard:
> anyone worked to integrate jabber to kolab?
> Mathieu
I found on:


kolab-devel@intevation.org
                          Betreff: 
[Kolab-devel] Re: [Kroupware] how to
add more .templates

> On Thursday 15 January 2004 03:53 am, Bo Thorsen wrote:
> > I suggest to add a new subdir .../etc/kolab/templates where all
templates
> > are put and to change the scripts to go over all these instead of a
fixed
> > set of templates.
>
> This in fact would suit me perfectly.  What I have now is the
jabber.xml
> file and the auth config perl script as templates.  My goal is that
when
> they reconfigure the kolab server by running the script these files
will be
> populated with the correct data from the rest of the config and bang
you
> have a jabber server that uses the usernames, passwords and other
contact
> data from the kolab ldap database.
>
> I have to admit Im somewhat paranoid of the "simplicty" of the setup
of
> kolab.... but then again it may be unfounded as nothing has gone wrong
yet.
> We have installed 4 servers like this and not had any noticeable
issues.
>
> Well see what the 1.0 -> 2.0 migration looks like ;)
>
> Keep up the awesome work guys!
>
> -ian reinhart geiser

Sorry I lost the original post,but that will be a piece of cake to find.

I am  ineressted in Jabber-integration myself!

_______________________________________________
Kroupware mailing list
Kroupware@mail.kde.org
https://mail.kde.org/mailman/listinfo/kroupware
[prev in list] [next in list] [prev in thread] [next in thread]