After having installed kolab (following the appropriate install guide in this knowledge base) it needs to be configured. The script ‘setup-kolab’ is distributed with the out-of-the-box installation and is taking care of the basic configuration, but a successful configuration is depending on the environment that Kolab is installed into. Many aspects and variables will have an impact on the configuration. This guide is only touching on the absolute basics. For information and assistance with more complex installation scenarios, please contact firstname.lastname@example.org
By default, Kolab ships with a configuration that lets Cyrus IMAP use LDAP roles as permission groups for IMAP folders. This article describes the configuration necessary to change a default Kolab deployment to use distribution groups instead of LDAP roles.
This HOWTO is a follow-up on Disabling and Enabling Webmail Plugins in Plesk Premium Email and deals with suppressing the availability of the folders other users share with one another, or global public folders shared with the user.
Sometimes, customers may wish to use, or avoid using, particular plugins in the web client.
This article outlines how to disable and enable plugins for the Plesk Premium Email webmail client for a specific domain.
Organizations that require or desire archiving of their communications often use an external solution distinct from the Kolab environment. Such appliances often support SMTP-based forwarding, and for those cases, this article explains how to configure Postfix such that all email is archived.
Collaborative editing, using Collabora Online, is an additional function that can be added to the out of the box Kolab 16 installation.
This article outlines how to install Collabora Online to a Kolab 16 installation on CentOS 7 or Red Hat Enterprise Linux 7.
A default Kolab environment uses default configuration for operating system packages, as they are shipped by your operating system vendor. This includes settings that limit the size of uploads accepted by the web server, and the maximum size of email messages.
This article outlines how to increase the mail and file size accepted.
A catch-all email address is an address that is used as a fall-back for when no other recipients are available. Ergo, it is the email address that receives all email for a domain that isn’t already delivered to other users or groups or shared folders.
A default Kolab environment is not configured to facilitate catch-all addresses, so this article outlines why and how to configure such a catch-all email address in a way that allows the use of another relatively obscure but very powerful feature — the use of address extensions.
John Doe administers a Kolab Enterprise installation, but the complete environment for what we’ll call “example.com” involves server systems hosted by third parties — such as a web server for the corporate website, and maybe other application servers.
This article outlines the possible solutions to one or more of these environments being restricted somehow.
Domain Keys Identified Mail (DKIM, or Mail Identified through Domain Keys) is a cryptographic technology using which domain owners publish the public keys of public-private key pairs used for signing email messages. This allows third parties to establish a degree of confidence about the message originating from designated and duly authorized infrastructure. In other words, it’s a been there ribbon.
This article explains how to configure a Kolab environment to sign mail messages with DKIM and verify DKIM signatures on inbound email.