[null, {"document_url": "https://en.opensuse.org/User:Aeneas_jaissle/SDB:Kolab_2", "unformatted_src": "https://static.opensuse.org/themes/bento/images/sponsors/sponsor_ip-exchange2.png", "src": "https://static.opensuse.org/themes/bento/images/sponsors/sponsor_ip-exchange2.png", "formatted_filename": "sponsor ip exchange", "alt_text": "Sponsor"}, null, {"document_url": "https://en.opensuse.org/User:Aeneas_jaissle/SDB:Kolab_2", "unformatted_src": "/images/7/76/Working-korganizer-groupware.png", "src": "https://en.opensuse.org/images/7/76/Working-korganizer-groupware.png", "formatted_filename": "Working korganizer groupware", "rendered_width": 500, "rendered_height": 358}, null, {"document_url": "https://en.opensuse.org/User:Aeneas_jaissle/SDB:Kolab_2", "unformatted_src": "/images/f/f6/Kronolith-agenda.png", "src": "https://en.opensuse.org/images/f/f6/Kronolith-agenda.png", "formatted_filename": "Kronolith agenda", "rendered_width": 100, "rendered_height": 128}, null]
User:Aeneas jaissle/SDB:Kolab 2

< User:Aeneas jaissle
Warning: Most of this page is about Kolab 2, which is deprecated. More information is available at features.opensuse.org/307846 and kolab.org as well as docs.kolab.org. Kolab upstream is very willing to help packagers with Kolab 3.
Warning: Due to time restraints Kolab was no longer built and supported on openSUSE. If you want to obtain information about building and maintaining Kolab on openSUSE, contact the retired packager (for the email address see the changelog in the kolab package: rpm -q --changelog kolab).
Packagers are currently working on building Kolab 3.x for openSUSE.



All packages will be available via openSUSE's build service, they are retrieved from several repositories, such as php:applications and a Kolab specific repository. The packages in the server:Kolab:UNSTABLE repository are based on code from Kolab git. Hopefully, this page helps you to get Kolab installed natively on openSUSE.


The packages can be installed with yast, yum, smart, zypper or with apt.
Kolab on openSUSE-10.3 and later needs the non oss repository, to be able to install the rpm unace. That package is required by amavisd-new.

You also have to add the server:php:applications and server:Kolab:UNSTABLE buildservice projects to your packagemanager in order to fulfill all dependencies. Kolab can be installed with, YaST, Zypper, Smart and apt. Which one to use is up to reader.


To install Kolab, you need to add two of the following repositories to your package installer, one of them being Kolab:Extra:

Version: 12.2

Version: 12.3

Version: Factory

Once the repositories have been configured, Kolab and all it's dependent packages can be installed:


Service configuration

The changes that are needed for kolab to the sysconfig files can be performed by running the script:

The script will make the following changes to get kolab running:

The instructions given below are not needed to be executed manually, as that is done by the script mentioned above!

Edit the file /etc/sysconfig/apache2 and add the following apache2 modules to the APACHE_MODULES variable:

If freshclam is installed as dependency of kolab, the ownership of the freshclam log file is wrong. The file must be owned by vscan. In case the ownership is not correct (please check), it can be corrected with the following command:

The amavisd log file and the clamav log file must be created with the right user:

Make sure that you run freshclam before you start the clamd-daemon, otherwise it'll complain during the next step

Bootstrap Kolab

Bootstrap kolab, some errors might be seen during the initial run of kolab_bootstrap. Ignorable errors are:

Create the aliases.db and the postfix indexed maps:

It is now possible to start kolab:

Go to the kolab admin webpage (url is shown by kolab_bootstrap) and create a user.

When no users appear in the directory mentioned above, check the file /var/log/messages for errors from cyrus.

If it does not work (see note), check /var/log/messages if you see a line with:

Stop cyrus:

Remove all the files in /var/lib/imap (only the files, not the directories!)

Start cyrus

Now magically all the created users should appear in /var/spool/imap/domain....

Here Clam Antivirus-clamd av-scanner might fail with the error message: Can't connect to UNIX socket /var/lib/clamav/clamd-socket (see /var/log/messages). If this happens stop clamav (rcclamd stop), remove the socket (rm /var/lib/clamav/clamd-socket), restart clamav (rcclamd start). Wait a bit and after some time the socket should appear and clamav will be working fine.

If kolab seems to work, it is now possible to activate all services during system startup:

After this you can enable the involved using yast:

This will activate many other services as dependencies as well, like: ldap, saslauthd, cyrus, apache2. But the services: spamd, freshclam, clamd and amavis are not activated automatically as in some cases kolab does not need them (when spam and virus scanning are not required). In case you want those services activated you have to do this manually, either with yast or with chkconfig (e.g.):

By enabling kolabd, the following message:

is printed twice. If you don't like that, do not enable kolabd, as kolabd will only start all kolab required services. With the following command:

it is possible to check that all required services are active. Use this tool instead of enabling kolabd. If a service is not enabled, enable it with the command:


Add an alias to one of your users, that will accept email from email@example.com. In case e.g. cron sents an email notification, the email will arrive at the user that has the alias set for the root.

Groupware testing

All of these urls should show you ical formatted data.

Use this freebusy test script to test the freebusy functionality.


KDE client Configuration Groupware functionality provided by kolab on openSUSE in korganizer


Kolab 2.x has it's own modified Horde for webclient to use it install package kolab-webclient

After installing webclient you must run kolabconf -n and add following lines to /etc/crontab file if you want notifications to work

and add the following:

then you can access it from http://servername/client. Note that servername should be the same as given while running kolab_bootstrap.

If you have problems getting the login from webclient, check the error_log of apache for an php error on the Timezone database. You can fix this by defining your timezone in the value "date.timezone" of the php.ini. Don't forget to check your calendar!

Don't forget to check your calendar, as shown on the screenshot om the right. If the calendar is not checked it is not displayed. Although you can schedule events succesfully....

Personal Information synchronization

This is untested

If you want to synchronize e.g. your mobile phone with your information stored in the kolab server you can do this by installing the kolab-z-push package ($ zyp in kolab-z-push). This package seems to make this possible... Additional configuration must be performed, which is described in the kolab wiki.


Package upgrading

Postfix doesn't start

If Postfix doesn't start correctly have a look into the /var/log/mail file.

For 10.1: stop rcapparmor (or add "flags=(complain) to the postfix-profiles) as it prevents postfix to run succesfully:

Disable apparmor permanently using yast:

Or from the command line:

ClamAV (clamd) fails to start

If the clamAV demon (clamd) fails to start than upgrade to the most recent clamav version (0.90). Then try to restart the clamAV demon:

If this fails with:

Than change the settings of the clamav log file to:

php segfault

In a very special case, a php segfault might be seen in /var/log/messages. The details are described in kolab issue 3629. If anybody can help to debug this, that would be great.

openldap (2009-11-28)

(Seen under both suse 11.1 & 11.2)

Openldap will refuse to start if certs located in /etc/kolab are changed/updated or relocated elsewhere. Error is:

rckolab start Starting ldap-serverstartproc: exit status of parent of /usr/lib/openldap/slapd: 1 failed

ERROR: /etc/init.d/ldap start failed Run: kolabsrv rc all stop to stop all services

Even trying to restart it alone with rcldap start|restart doesn't work anymore...

Remember that kolab-related certs located under /etc/kolab should have file group ownership set to "pki", like:

Updating WebClient from Horde Groupware 1.2.0 to 1.2.4 (2009-11-28)

Work nicely under 11.1 with PHP 5.2.11 (NOT 11.2 and php 5.3)

Here is a little Step-By-Step "How-to":

Install Kolab-webclient 1.2.0 through your favorite tool (zypper|apt|yast | else). Check if you're able to log on and if all is working properly (don't waste your time to customize options yet). Then, logoff.

Just in case (a bit of recovery planning doesn't hurt) :

Get the latest Horde Groupware archive and horde passwd tool, untar:

Now, add passwd to the groupware folder and relocate the resulting stuff under apache2:

Create a storage space for horde parameters (starts under ./client like the one found under ./client120, You can move it later when all is done)

Adjust files' ownership for apache2 (usually wwwrun:www under suse)

Just in case (useful indeed...):

Time to upgrade with the nice Horde utility located in ./client/scripts

The utility provides a easy mean to upgrade Horde Groupware, First asking for the web root directory, which is /client (the default) then select option 5 (Update from an older Horde Groupware Webmail Edition version) for some config.

Exit (option 0)

You're good to go. Last step:

Just in case (again, if something happens while you're playing with the configs afterwards...):


Some facts

Normally Kolab prior to 3.x is installed using packages build with openpkg. The user needs to download just under 200MB of source rpms. These have to be build requiring about 850MB of disk space and quite some time on a not so modern system. On openSUSE one now only needs to download 12 MB of binary rpms, which are installed in just a second even on this not so modern system! Of those 12 MB, about 10 MB is needed for a patched rpm that is normally provided by suse. This rpm is cyrus-imapd that count for roughly 8.5 MB. The patches have been sent upstream but the respective projects are slow to include them. Imagine if those patches would be part of the projects and as such just be part of suse. Only 12 MB (2 in the future?) is needed for Kolab on openSUSE, while using openpkg just under 200MB has to be downloaded!


Retrieved from "https://en.opensuse.org/index.php?title=User:Aeneas_jaissle/SDB:Kolab_2&oldid=60270"