Difference between revisions of "Kolab"

From ArchWiki
Jump to: navigation, search
(Removed stub and style templates, as the pase has been mostly rewritten)
(See also: Pointed Kolab manuals to the root of the documentation)
Line 87: Line 87:
* [http://kolab.org Official homepage]
* [http://kolab.org Official homepage]
* [http://docs.kolab.org/installation-guide/index.html Kolab manuals]
* [http://docs.kolab.org/index.html Kolab manuals]
* http://hosted.kolabsys.com/~vanmeeuwen/build/html/howtos/build-kolab-from-source.html
* http://hosted.kolabsys.com/~vanmeeuwen/build/html/howtos/build-kolab-from-source.html
* http://mirror.kolabsys.com/pub/releases/
* http://mirror.kolabsys.com/pub/releases/
* https://obs.kolabsys.com/project/show?project=Kolab%3A3.1
* https://obs.kolabsys.com/project/show?project=Kolab%3A3.1

Revision as of 11:32, 25 February 2015

Kolab is an unified communication and collaboration system, composed of a server-side daemon which offers storage and synchronization capabilities for contact, calendar, mail and file data. Clients can use several well defined formats like vCard, iCal, XML, IMAP and LDAP to communicate with the Kolab server.


Kolab server is available in the AUR via the kolabAUR meta-package. This package will install all Kolab components, as well as the neccesary external services: cyrus-imapdAUR, Postfix, 389-ds-baseAUR, MySQL, Amavis, ClamAV, SpamAssassin and Apache with PHP support.

Tip: As of 2015-02-25, pear-net-ldap2AUR and 389-ds-baseAUR do not compile. Until they are fixed, you can download fixed PKGBUILDs from [1]


Warning: Kolab changes the configuration of many system components. If you use any of the services listed above, you may want to backup your configuration, as the Kolab installation process is likely to overwrite part of it

At first, Kolab requires you to use a FQDN (fully qualified domain name), with at least three dot-separated parts. Therefore adjust and append:

/etc/hosts kolab.example.org

Write the same domain name into /etc/hostname. You should also check your DNS settings and reverse DNS resolution.

Arch-specific configuration

Kolab makes many assumptions about the system it is installing on. The kolabAUR packages ships with an script that brings the system to a state where the Kolab setup script is useful. Run it as root:

# arch-setup-kolab

This will:

  • Check your FQDN (can be skipped adding the --no-fqdn option)
  • Initialize or update the ClamAV and SpamAssassin databases
  • Initialize the Cyrus IMAP cache directory
  • Create the Postfix aliases database (aliases.db)
  • Configure ClamAV to be able to access Amavis directories
  • Enable the PHP module in Apache
  • Add all Kolab applications to Apache in /etc/httpd/conf/extra/kolab.conf
  • Add Roundcube to Apache
  • Enable the required PHP extensions, and condigure the include_path and open_basedir in {{ic|/etc/php/conf.d/kolab.ini)
  • Configure libsasl to use the SASL daemon shipped with Kolab
  • Create a dummy certificate for localhost (/etc/ssl/private/localhost.pem) and install it as a trust anchor (/etc/ca-certificates/trust-source/anchors/localhost.pem)

Kolab configuration

Kolab ships with its own configuration script (contained in pykolabAUR. Run it as root:

# setup-kolab

This runs all configurations steps neccesary for Kolab. During the process, multiple questions will be asked, regarding passwords, etc. The defaults are fine for all but two questions:

  • The password for the LDAP Directory Manager is the password you use for logging in to the web administration panel
  • When asked about MySQL, you should select 1: Existing MySQL server and then the password for the root MySQL user (by default, empty)

You can also list the steps with setup-kolab help and selectively run some of them.

First steps

The web admin panel is located at http://localhost/kolab-webadmin/. You can login using cn=Directory Manager as the user, and the password you chose during the previous step. You can recover the password by running:

$ grep ^bind_pw /etc/kolab/kolab.conf

You can then create an user and login as him in http://localhost/roundcube/ by using the email address or the UID of the user and the assigned password.

More information in the Kolab documentation: [2]


Roundcubemail Plugin

Besides the basic Roundcubemail installation and configuration, this roundcubemail-plugins-kolabAUR plugin package is needed for advanced groupware functionality.

Start/stop the services

The installation process should have enable and started all Kolab services. The following services are used by Kolab (and can be managed by systemctl):

  • 389-ds-base.target: LDAP directory for configuration and authentication
  • amavisd: Bridge from Postfix to ClamAV and SpamAssassin
  • clamd: Virus scanning
  • cyrus-master: IMAP/PÔP3 server
  • httpd: Apache web server
  • kolabd: Synchronizes LDAP configuration with Cyrus IMAP (list of mailboxes)
  • kolab-saslauthd: Handles SASL auth for Postfix
  • mysqld: Database engine for RoundCube and Kolab components
  • postfix: SMTP server
  • wallace: Scans incoming mail for groupware content

See also