[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-pim
Subject: [Kde-pim] A big thank you and some remarks about kolab 2
From: Holger Schroeder <holger-kde () holgis ! net>
Date: 2004-12-04 15:46:14
Message-ID: 200412041646.14835.holger-kde () holgis ! net
[Download RAW message or body]
Hi,
in the last two days i installed the development version of the kolab server,
and i am quite impressed, that it all works together son nicely. a big thank
you for that.
but the documentation for kolab 2 is still really bad.
although i fiddles around with kolab 1 about a year ago, i couldnīt find out
how to install kolab2. to get an impression of what i mean, imagine you are
some linux admin, and you heard of kolab and want to try it. so you go to
www.kolab.org. now try to find out how to install kolab 2... i couldnīt, but
google was my friend and i found this: www.pokorra.de/kolab/kolab2.html
so when you want to have some beta testers, please put a kolab 2 page up on
www.kolab.org, perhaps under "How to install/Download" on the right side.
something like this would be a good starting point:
Kolab 2 server
What is the kolab 2 server ?
<short but descriptive answer here>
How can i download/install it ?
there are two ways of installing kolab:
-debian packages:
for debian, go to ftp://<foo>, download the packages and install them
<more info about debian here>
-install from sources:
kolab makes use of the openpkg packaging system to install itself on a
computer, it runs on linux(gentoo, ...) and <fixme>. it is an rpm-based
system, which installs all its own packages under the /kolab directory on
your host system. because of this it doesnīt interfere with your host system,
and we only have to support one set of packages.
you can download the packages either by ftp or by rsync. rsync is the
preferred way, because you can then update your source packages from time to
time, and you only transfer the changed files, and not all files again as
with ftp.
when you want to use ftp, go to
ftp://ftp.kolab.org/kolab/server/development/current/sources and download all
files in that directory.
when you want to use rsync, do the following:
rsync -L -rtzvP
rsync://rsync.kolab.org/ftp/kolab/server/development/current/sources/
this shows which files would be downloaded. if it looks ok, something like
this:
rsync server - Intevation GmbH, Germany
All transactions are logged. Mail problems to root@intevation.de.
This server is primarily for developers and mirrors.
Please be gentle and choose a mirror site from mirrors.txt for downloads.
receiving file list ...
78 files to consider
drwxr-sr-x 4096 2004/12/02 19:12:35 .
-rw-r--r-- 1241 2004/12/02 20:37:22 README.1st
-rw-r--r-- 479122 2004/12/01 18:10:27 amavisd-2.1.2-2.2.0.src.rpm
-rw-r--r-- 10335194 2004/12/01 18:10:28 apache-1.3.31-2.2.1_kolab.src.rpm
-rw-r--r-- 1691035 2004/12/01 18:10:29 autoconf-2.59-2.2.0.src.rpm
-rw-r--r-- 951549 2004/12/01 18:10:29 automake-1.9.2-2.2.0.src.rpm
-rw-r--r-- 10650844 2004/12/01 18:10:31 binutils-2.14-2.2.0.src.rpm
-rw-r--r-- 1807888 2004/12/01 18:10:32 bison-1.35-2.2.0.src.rpm
-rw-r--r-- 673046 2004/12/01 18:10:32 bzip2-1.0.2-2.2.0.src.rpm
-rw-r--r-- 2700217 2004/12/01 18:10:32 clamav-0.80-2.2.0.src.rpm
-rw-r--r-- 4097473 2004/12/01 18:10:33 db-4.2.52.2-2.2.0.src.rpm
-rw-r--r-- 85851 2004/12/01 18:10:33 dbtool-1.6-2.2.0.src.rpm
-rw-r--r-- 1066580 2004/12/01 18:10:33 diffutils-2.8.7-2.2.0.src.rpm
-rw-r--r-- 324415 2004/12/01 18:10:33 expat-1.95.8-2.2.0.src.rpm
-rw-r--r-- 374812 2004/12/01 18:10:33 file-4.10-2.2.0.src.rpm
-rw-r--r-- 1250076 2004/12/01 18:10:33 flex-2.5.4a-2.2.0.src.rpm
-rw-r--r-- 1497744 2004/12/01 18:10:33 fsl-1.5.0-2.2.0.src.rpm
-rw-r--r-- 27377410 2004/12/01 18:10:38 gcc-3.4.2-2.2.0.src.rpm
-rw-r--r-- 234732 2004/12/01 18:10:38 gdbm-1.8.3-2.2.0.src.rpm
-rw-r--r-- 84573 2004/12/01 18:10:38 getopt-20030307-2.2.0.src.rpm
-rw-r--r-- 6564624 2004/12/01 18:10:39 gettext-0.14.1-2.2.0.src.rpm
-rw-r--r-- 2216157 2004/12/01 18:10:39 gmp-4.1.4-20040924.src.rpm
-rw-r--r-- 691304 2004/12/01 18:10:39 grep-2.5.1-2.2.0.src.rpm
-rw-r--r-- 339295 2004/12/01 18:10:39 gzip-1.3.5-2.2.0.src.rpm
-rw-r--r-- 2206089 2004/12/01 18:10:39 imap-2004a-2.2.0.src.rpm
-rw-r--r-- 1963164 2004/12/01 18:14:51 imapd-2.2.8-2.2.1_kolab.src.rpm
-rw-r--r-- 3790631 2004/12/01 18:14:52
kolab-resource-handlers-0.3.9-20041131.src.rpm
-rw-r--r-- 183762 2004/12/01 18:14:52
kolab-webadmin-0.3.4-20041201.src.rpm
-rw-r--r-- 96184 2004/12/02 18:58:56 kolabd-1.9.3-20041201.src.rpm
-rw-r--r-- 3647342 2004/12/01 18:10:41 libiconv-1.9.2-2.2.0.src.rpm
-rw-r--r-- 3888495 2004/12/01 18:10:42 libxml-2.6.14-2.2.1.src.rpm
-rw-r--r-- 2609697 2004/12/01 18:10:42 libxslt-1.1.11-2.2.0.src.rpm
-rw-r--r-- 432989 2004/12/01 18:10:42 lzo-1.08-2.2.0.src.rpm
-rw-r--r-- 353853 2004/12/01 18:10:43 m4-1.4.2-2.2.0.src.rpm
-rw-r--r-- 1222380 2004/12/01 18:10:43 make-3.80-2.2.0.src.rpm
-rw-r--r-- 334193 2004/12/01 18:10:43 mm-1.3.1-2.2.0.src.rpm
-rw-r--r-- 2713964 2004/12/01 18:10:43 ncurses-5.4.20041009-2.2.0.src.rpm
-rwxr-xr-x 34068 2004/12/01 18:14:52 obmtool
-rw-r--r-- 5172 2004/12/02 19:00:20 obmtool.conf
-rw-r--r-- 2590237 2004/12/01 18:10:44 openldap-2.2.17-2.2.0.src.rpm
-rw-r--r-- 18184949 2004/12/01 18:10:48 openpkg-2.2.1-2.2.1.src.rpm
-rw-r--r-- 19736576 2004/12/01 18:10:51 openpkg-2.2.1-2.2.1.src.sh
-rw-r--r-- 121198 2004/12/01 18:10:52 openpkg-tools-0.8.21-2.2.0.src.rpm
-rw-r--r-- 2813410 2004/12/01 18:10:52 openssl-0.9.7d-2.2.0.src.rpm
-rw-r--r-- 207698 2004/12/01 18:10:52 patch-2.5.9-2.2.0.src.rpm
-rw-r--r-- 664172 2004/12/01 18:10:53 pcre-5.0-2.2.0.src.rpm
-rw-r--r-- 11880958 2004/12/01 18:10:54 perl-5.8.5-2.2.0.src.rpm
-rw-r--r-- 153928 2004/12/01 18:10:54 perl-comp-5.8.5-2.2.0.src.rpm
-rw-r--r-- 349700 2004/12/01 18:10:54 perl-conv-5.8.5-2.2.0.src.rpm
-rw-r--r-- 453357 2004/12/01 18:10:54 perl-crypto-5.8.5-2.2.0.src.rpm
-rw-r--r-- 230703 2004/12/01 18:10:54 perl-db-5.8.5-2.2.0.src.rpm
-rw-r--r-- 374612 2004/12/01 18:10:54 perl-ds-5.8.5-2.2.0.src.rpm
-rw-r--r-- 58790 2004/12/01 18:10:54 perl-kolab-5.8.5-20041123.src.rpm
-rw-r--r-- 226663 2004/12/01 18:10:54 perl-ldap-5.8.5-2.2.0.src.rpm
-rw-r--r-- 1986273 2004/12/01 18:10:55 perl-mail-5.8.5-2.2.0.src.rpm
-rw-r--r-- 816500 2004/12/01 18:10:55 perl-net-5.8.5-2.2.0.src.rpm
-rw-r--r-- 9928 2004/12/01 18:10:55 perl-openpkg-5.8.5-2.2.0.src.rpm
-rw-r--r-- 393965 2004/12/01 18:10:56 perl-parse-5.8.5-2.2.0.src.rpm
-rw-r--r-- 233531 2004/12/01 18:10:56 perl-ssl-5.8.5-2.2.0.src.rpm
-rw-r--r-- 721959 2004/12/01 18:10:56 perl-sys-5.8.5-2.2.0.src.rpm
-rw-r--r-- 258454 2004/12/01 18:10:56 perl-term-5.8.5-2.2.0.src.rpm
-rw-r--r-- 503380 2004/12/01 18:10:56 perl-time-5.8.5-2.2.0.src.rpm
-rw-r--r-- 1060284 2004/12/01 18:10:56 perl-util-5.8.5-2.2.0.src.rpm
-rw-r--r-- 1832519 2004/12/01 18:10:56 perl-www-5.8.5-2.2.0.src.rpm
-rw-r--r-- 2317471 2004/12/01 18:10:56 perl-xml-5.8.5-2.2.0.src.rpm
-rw-r--r-- 4908549 2004/12/01 18:10:57 php-4.3.9-2.2.0.src.rpm
-rw-r--r-- 239667 2004/12/01 18:10:57 php-smarty-2.6.3-20040702.src.rpm
-rw-r--r-- 2302424 2004/12/01 18:10:57 postfix-2.1.5-2.2.0.src.rpm
-rw-r--r-- 240498 2004/12/01 18:10:57 procmail-3.22-2.2.0.src.rpm
-rw-r--r-- 935145 2004/12/01 18:10:57 proftpd-1.2.10-2.2.0.src.rpm
-rw-r--r-- 646144 2004/12/01 18:10:57 pth-2.0.2-2.2.0.src.rpm
-rw-r--r-- 1825014 2004/12/01 18:10:58 readline-5.0.0-2.2.0.src.rpm
-rw-r--r-- 1554345 2004/12/01 18:10:59 sasl-2.1.19-2.2.0.src.rpm
-rw-r--r-- 776153 2004/12/01 18:10:59 sed-4.1.2-2.2.0.src.rpm
-rw-r--r-- 694858 2004/12/01 18:10:59 sharutils-4.3.77-2.2.0.src.rpm
-rw-r--r-- 1085013 2004/12/01 18:11:00 spamassassin-3.0.0-2.2.0.src.rpm
-rw-r--r-- 1992279 2004/12/01 18:11:00 texinfo-4.7-2.2.0.src.rpm
-rw-r--r-- 353595 2004/12/01 18:11:00 zlib-1.2.1-2.2.0.src.rpm
wrote 112 bytes read 2790 bytes 5804.00 bytes/sec
total size is 184712064 speedup is 63649.92
then you can enter this line to download the files to the directory kolab:
rsync -L -rtzvP
rsync://rsync.kolab.org/ftp/kolab/server/development/current/sources/ kolab/
when you want to update that directory in the future, simply repeat that
command.
installation of the kolab server:
<please correct things, that are wrong here ...>
follow these instructions to install kolab on a server for the first time. for
updating a kolab
server follow the instructions in the next section.
first create a directory under /usr/local to be compatible to the FHS
> mkdir /usr/local/kolab
then link that to /kolab
> ln -s /usr/local/kolab /kolab
now build the openpkg package management system on your computer:
> cd kolab
> ./openpkg-2.1.2-2.1.2.src.sh --prefix=/kolab --user=kolab --group=kolab 2>&1
| tee kolab.log
> install it
sh openpkg-2.1.2-2.1.2.ix86-om1.5.0-kol.sh
<is this neccessary ?>
> mv *.src.rpm /kolab/RPM/SRC
now let openpkg build all the rpms for kolab
> ./obmtool kolab
the following ports are needed for kolab:
checkPort("webserver",80);
checkPort("webserver",443);
checkPort("imap server",143);
checkPort("imap server",220);
checkPort("imap server",585);
checkPort("imap server",993);
checkPort("pop server",109);
checkPort("pop server",110);
checkPort("pop server",473);
checkPort("pop server",995);
checkPort("smtp server",25);
checkPort("smtp server",465);
checkPort("ftp server",21);
checkPort("Amavis Virus Scanner Interface",10024);
checkPort("Kolab daemon",9999);
checkPort("OpenLDAP server",636);
checkPort("OpenLDAP server",389);
checkPort("Sieve server",2000);
now stop all services, that bind to ports, that kolab needs:
> /sbin/service httpd stop
> /etc/rc.d/init.d/xinetd stop # to stop imaps
> /etc/init.d/sendmail stop
configure kolab (this asks for your domain, and adapts the config files for
the different
services, which it is made of. for details see
ftp://ftp.kolab.org/kolab/contrib/kolab-bootstrap.pdf )
> /kolab/etc/kolab/kolab_bootstrap -b
you have to know the following data about the server:
- hostname : this is the dns name of the server
- maildomain : this is the mail domain. (the part of your email-addresses
after the @ sign.
this is only the primary domain, you can add aliases for users with other
domains later in
the web admin interface.)
- a password for the manager of the kolab web interface
- <some explanations about certificates here>
in the last few lines of the last command there are instructions about how to
access the admin interface. you should write down/remember the username and
password
for the admin user.
now you can start the kolab server ( and all the "subservers" it depends on )
> /kolab/bin/openpkg rc all start
or
> /etc/init.d/kolab start
now point your favourite web browser to the admin interface of the kolab
server:
https://kolab.ict.om.org/admin
you can log in there with username manager and the remembered password. if you
lost the password,
you can find it in clear text in the file /kolab/etc/kolab/kolab.conf as the
value of bind_pw.
updating a kolab server:
<fill this section, please a little bit more detailed than in the README.1st
file. which files have to be
backuped, and where are they under /kolab/, and where should they be put after
the update?
how do i update kolab without turning it off for the time, when obmtool builds
all the new packages?
is there a way to build the rpms first with the server still "serving" mail,
and then do the update in say
two minutes instead of some hours ?>
using the kolab server:
now you can create users on the server.
<explain the differences between users, administrators and manager>
<<<end>>>
there are still some questions/wishes i have, perhaps there should be a kolab2
faq or wiki on kolab.org.
- how do all the kolab components work together ?
after a day of reading, i have an idea, what clamav, spamassassin and amavisd
are, but perhaps somebody could explain that with some ascii art or so.
- how can i change a template for kolab, e.g. for amavisd and tell kolab to
update the file generated from the template ?
- how can i tune spamassassin ( enable/disable it, (dis)allow to rewrite the
header of spam mails, allow it to delete spam or not, allow users to add
white/blacklists ) ? perhaps that could be integrated into the web interface.
- could the horde webclient be integrated into kolab in a way, that
installation is as easy as
> ./obmtool kolab
and then i can enable/disable horde in the webinterface ?
is cached imap able to recognize, that mails on the client are moved from one
folder to another, so that it can move the files on the server at the next
sync too? now i am filtering mails into different folders on download, and on
the next sync, kmail 1.7.1 seems to upload the moved mails to the server,
instead of moving them on the server, which is quite slow.
- would it be possible to let the kmail mail filter rules "know" on which
server/mail folder they are working ? for example when i have my mails
filtered into the two folders A and B on the server, and i am in folder A and
want to filter sapm messages from there, i want them to go to folder A-spam,
and when i am in B i want them to go to B-spam. and for that the rule needs
to know in which folder it is applied.
thanks a lot, Holger
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic