Archiving Email Using Always BCC

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.

Continue reading

Using Catch All Email Addresses

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.

Continue reading

Relay Outbound Mail Through a Third Party, Using Postfix

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.

Continue reading

Configure DKIM Signing and Verification Using Amavis

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.

Continue reading

Increase Web Client Performance with Memcache

Memcache is a protocol to access a simple key-value store, that is memory-backed, over a network socket. The memcached server does not perform any form of access control and is optimal for certain caches used in the Kolab web client (and associated HTTP-based access interfaces), by avoiding superfluous login, access control, and other such software policy considerations, as well as disk I/O.

This article outlines the installation and configuration of a single memcached server for use with the Roundcube web client for Kolab.

Continue reading

Changing the Cyrus Administrator or Kolab Service Account Password

Changing the Kolab Service account password can be cumbersome business, since most services are configured to use the account to bind to LDAP and be able to read the entries. Examples of such services include Postfix, the Kolab SASL Authentication Daemon, the Kolab Synchronization Daemon, Cyrus IMAP, Roundcube, Chwala, Wallace, iRony, the Kolab Web Administration Panel and Syncroton.

Changing the Cyrus Administrator password can be equally cumbersome, albeit it is used in fewer locations — these services are still critical.

This article provides a step by step guide to a smooth transition between the old password and the new password.

Continue reading