Kolab2 Server Important Information
===================================

For more information on Kolab, see http://www.kolab.org

Quick install instructions
--------------------------

For a fresh install /kolab needs to be an empty directory with enough space.
You can use a symlink, but do _not_ use an NFS mounted drive.
Make sure that the following names are not in /etc/passwd or /etc/groups,
as openpkg will want to create them: "kolab" "kolab-r" "kolab-n"

Check the www.openpkg.org documentation for your platform.
E.g. some platforms need gettext installed 
or the locale set to C during installation, like:
        LC_ALL=C
        LC_MESSAGES=C
        LANG=C
        SUPPORTED=C
        export LC_ALL LC_MESSAGES LANG SUPPORTED

Make sure the locale you want to set is supported by your c-library.
Otherwise the webadmin interface might only be in English.

To install the Kolab2 server, you need to download the files from the
directory containing this file (1st.README) to some local directory,
then as root, chdir into that local directory and run

# ./obmtool kolab 2>&1 | tee kolab-build.log

to build and install packages in /kolab.
By default, the Kolab Server will now be started at boottime.
After the build/install is complete, please run

# /kolab/etc/kolab/kolab_bootstrap -b

and follow the instructions.


General update instructions
---------------------------

Usually an update of the Kolab 2 server works as described here.  In
some cases you will need to deviate from these instructions a bit.  All
such cases are documented below, so read the release specific update
instructions for all releases newer than the one you already have before
you start the update.

The installation of the new packages works just as for the initial
installation.  Download the files as described above and run

# ./obmtool kolab

obmtool will usually automatically determine which packages need to be
built.  If you have made changes to the configuration files in
/kolab/etc/kolab/templates/ and the new release has a new kolabd package
you may need to transfer your changes from the backups created by rpm
(the *.rpmsave) files to the new template files.  Then regenerate the
configuration with

# /kolab/sbin/kolabconf


You may want to check the permissions of your files in /kolab/etc/kolab/
after installing or upgrading, as there have been problems with this in
the past.  Especially kolab.conf and copies shall only be readable to
the owner (usually "kolab").  The installation and configuration scripts
should make sure that the permissions are correct but there's a chance
that the permissions can still go wrong, especially if you upgrade from
pre Beta1 releases.


Upgrading from earlier versions
-------------------------------

Direct upgrade from Kolab1 is not recommendable at this point. We
suggest that you back up your IMAP store, install Kolab2 and manually
recreate user accounts and then restore the IMAP data from the backup.

After an upgrade, always run /kolab/sbin/kolabconf to make sure the
configuration files are regenerated from your templates.


Upgrade from 2.0 releases to pre-2.1-snapshots
----------------------------------------------

An upgrade from a 2.0 release to a 2.1 snapshot is not yet recommended.
These instructions are incomplete.  Please take a look at README.1st from
the latest 2.0 release, too.

Manually add two LDAP objects:

dn: cn=domains,cn=internal,<base_dn>
objectClass: top
objectClass: kolabNamedObject
cn: domains

dn: cn=domain-maintainer,cn=internal,<base_dn>
objectClass: top
objectClass: kolabGroupOfNames
cn: domain-maintainer
member: cn=manager,cn=internal,<base_dn>

Also, after the upgrade the attribute "postfix-mydestination" of the
k=kolab ldap object has the value "$mydomain".  Change this to the real
domain (should be the same value as that of the "postfix-mydomain"
attribute).


$Id: README.1st,v 1.30 2005/11/25 12:56:19 bh Exp $