Kolab Groupware is a Free Software groupware solution for Email communications, Events & Appointments, Contacts and more. It supports mixed client environments because of an open storage format, and the use of well-established, standard protocols such as IMAP and SMTP.
For the full Kolab experience, you need a Kolab server, and one or more Kolab clients. What makes Kolab a unique groupware solution is its focus on security, scalability, data ownership (aka privacy) and the use of proven components and protocols.
what should you do to continue to run the environment?
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/administrator-guide/index.rst, line 47.)
Is this list complete?
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/administrator-guide/upgrading-from-kolab-3.0.rst, line 212.)
Is this list complete?
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/administrator-guide/upgrading-from-kolab-3.0.rst, line 220.)
Document the concepts of a sealed system.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/architecture-and-design/index.rst, line 46.)
Administration Guide topic for LDAP deployments with single trees growing over 1.000 entries.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/architecture-and-design/ldap.rst, line 109.)
Somewhere other than here, document the process of scaling up from one single server on to multiple servers.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/deployment-guide/index.rst, line 88.)
We probably need to explain why we choose to use SMTP rather than LMTP.
State something about pre-authorizing LMTP, it happening over the network, murder topologies and LMTP proxying, the use of LDAP holding the mailHost attribute, accounting, etc.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/deployment-guide/multi-server.rst, line 198.)
Document an inventory of products and components along with the method of creating the inventory.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/developer-guide/bugzilla.rst, line 39.)
Document the inventory of package versions, product streams and product versions that are supported, along with the methodology of creating such inventory.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/developer-guide/bugzilla.rst, line 47.)
Install the NEEDSINFO extension, so that not only can the status be set, one can explicitly supply from whom the additional information is needed, said person is notified, and said person can “clear” the NEEDSINFO state when the requested information is supplied.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/developer-guide/bugzilla.rst, line 294.)
Write the section on running the Hosted Kolab Customer Control Panel from source.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/howtos/build-kolab-from-source.rst, line 550.)
Write the section on running Chwala from source.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/howtos/build-kolab-from-source.rst, line 558.)
Write the section on running iRony from source.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/howtos/build-kolab-from-source.rst, line 565.)
The installation chapter for SUSE Linux Enterprise Server should be written.
(The original entry is located in /home/kanarip/devel/tmp/kolab-docs/source/installation-guide/suse.rst, line 5.)