[Kroupware] Running kolab server

[Tassilo Erlewein]

Am Dienstag, 4. Februar 2003 11:54 schrieb Carlos A. Rega:

> > you may want to test from the command line:
> > "testsaslauthd -u manager -a manager"
> > (give the password)
>
> I tested that (that command line did not work btw) with
>
> kolab$ testsaslauthd -u manager -p random_password
> but it did not work, I get:
>
> 0: NO "authentication failed"

this is bad.
do a /kolab/sbin/slapcat as root
and look at the ldap ldif data.

check that slapd comes up nicely.
It logs to the syslog.

do a ldapsearch -b "your base_dn" "(uid=*)" and test the running ldap server


> freed those ports for the time being, but I will need them in production, I
> would like to use the same machine we use for internal purposes, we have a
> small intranet webpage for sharing info, and need ftp to upload and
> download stuff, is it possible to reconfigure kolab to use the servers I
> have already running in the machine?

you can enter different ports for apache (80,443) and postfix (25) in the
configuration templates under /kolab/etc/kolab/httpd.conf.template
and /kolab/etc/kolab/master.cf.template
see that you take some high port you don't use otherwise.
ftp doesn't hurt unless you connect with outlook to the server.

if your ldap is up and running ok, you then can do a
/kolab/etc/kolab/kolab -o -v and create new configs for all
services. then the port change should be done.

(you may need to restart apache and postfix via
/kolab/sbin/apachectl restart and /kolab/sbin/postfix reload
be sure to configure your clients according to the new ports.
e.g. https://noonoo:<whatever>/admin

check the port usage afterwards.