Kolab

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent

Kolab
by a.c. on Thursday 19/May/2005, @00:53

Kolab needs to be split into into 2 groups. The intention of Kolab is to develop a server that is easy to set-up and can serve 1000s. Cool. Except in some ways, these are competiting against each other.

It would be nice to see the parts be swapable. In particular, it would be nice to see a simplified Kolab run on top of Postfix using flatfiles (/var/spool/mail) rather than ldap. Likewise, it should use the standard imap/pop to work with this.
and you ask why?

For the home to the small business. Speed is not the big need there, but simplicity is.

It needs to be something that is easy to use. Of course, now, that Kolab has moved away from using imap to using ldap only, it would mean that imap would have to work against /var/spool/mail files, and I do not know if that is easy. IOW, it removes the very ease that version 1 had.

Related Links

·   Articles on Interviews
·   Also by a.c.
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

Re: Kolab
by am on Thursday 19/May/2005, @02:14

"In particular, it would be nice to see a simplified Kolab run on top of Postfix using flatfiles (/var/spool/mail) rather than ldap"

I believe Kolab uses Cyrus-IMAP (fastest IMAP server around) for mail storage and only stores user info in ldap.

I think that Kolab needs a much simpler setup then it has now. It just takes too much effort to install. It needs more distro support to really take off.

[ Reply To This | View ]

Re: Kolab
by Till Adam on Thursday 19/May/2005, @03:13

Have you tried Kolab2? It's rather easy to install, we think, there's a script that basically does all the work for you. But we'll work with distributors to make sure it can be nicely installed on top of popular distros as well.

[ Reply To This | View ]

Re: Kolab
by am on Thursday 19/May/2005, @03:41

The question is... is it easy to maintain/upgrade after installation. Installing from source usually isn't the best maintenance path for large groups of server.

What about adding MailScanner as an optional package for virus/spam filtering?

I love kolab by the way, I tried to get my organization to switch to it. Currently we use Sendmail/Cyrus/OpenLdap/Kerberos/MailScanner (hell this is pratically Kolab :) ) for all of our big setups. (all have rpms with good support). but without support from a big distro Kolab was always a no go. :(

Keep up the good work! I am looking forward to switching when the time comes around!

[ Reply To This | View ]

Re: Kolab
by Till Adam on Thursday 19/May/2005, @05:30

Since Kolab relies on OpenPkg, it's very easy to install updates and fixes. As for feature requests, please send them to https://kolab.org/mailman/listinfo/kolab-devel or https://kolab.org/mailman/listinfo/kolab-users, where they can be discussed more appropriately. The parts that come from the OS are supported by the OS, the rest is supported by OpenPkg, where Kolab uses the unmodified packages, or the Kolab project where they are changed or extended.

[ Reply To This | View ]

Re: Kolab
by Andy on Thursday 19/May/2005, @07:54

I blelieve Kolab to be rather easy installable. I put the /kolab tree onto a own disk and can use it, no matter i run Suse or Fedora, even from inside of Xen. I like this separation very much, especially when dist upgrading, since i can revert to the old version without touching the precious data stored in Kolab.
Integrating it into different distributions in different ways (or even the same ways) would open it to the same vulnerabilities as every other package, different patchsets by different distributors and so on.
The main advantage of Kolab is its own tree, everything else doesn't matter. With the Linux ELF-module it should without changes be useable on *BSD too I guess.

[ Reply To This | View ]

Re: Kolab
by mdouhan on Thursday 19/May/2005, @11:00

Kolab runs perfect on FreeBSd, and has been prooven to scale very well in our experience, from small installations of 20 users up to serious enterprise solutions serving several thousand users and still growing

[ Reply To This | View ]

Re: Kolab
by anonymous on Thursday 19/May/2005, @09:11

Please don't forget Slackware, thank you!

[ Reply To This | View ]

Re: Kolab
by Richard on Thursday 19/May/2005, @12:30

Please, check out this
http://wiki.kolab.org/index.php/Kolab2_linux_distribution_integration wiki
page. In some cases the kolab code contains hardcoded values, and this need
to be tackled, before distributions can integrate a unpatched kolab.
Some hard work is being done to replace the hardcoded values, see:
http://www.kolab.org/pipermail/kolab-devel/2005-May/003441.html
As usual any help with this is welcome!

And oh, the cyrus imap patches should be submitted upstream so the
distributions can disitribute a unpatched cyrus. At the end I think this
may be the biggest showstopper to integrate kolab into a distribution.
See http://wiki.kolab.org/index.php/Kolab-major-app-patches

[ Reply To This | View ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"KDE: The news ticker with integrated desktop environment." -- Frerich Raabe
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.