Apheleia IT AG keeps the Kolab repositories under maintenance and makes those available for users through a mirror. Recently the mirror infrastructure has been renewed and updated, and the old mirror is now deprecated. The new mirror is available at:
https://mirror.apheleia-it.ch/repos/Kolab:/16/
You have installed Kolab 16 on CentOS7 and you now want to secure it with SSL/TLS. This article describes how to do that with Let’s Encrypt.
In Outlook 2016/365 ActiveSync support is not enabled by default. While it is still possible to use the manual setup procedure through the Windows Control Panel, unfortunately auto-discovery does not work in this case.
Alternatively it is possible to enable ActiveSync support in Outlook by creating a registry key as follows (source):
You can now create ActiveSync accounts using the regular account creation wizard in Outlook by selecting Exchange ActiveSync as account type.
In a time when email addresses did not always make sense, email signatures served the purpose of identifying the author to the recipient. As described in RFC1855 (Netiquette), it had to be short and to the point. Evolution has since driven the feature of signatures into new functionality and areas, like marketing and legal recognition. Today many organizations has strict rules for signatures, the content and the format, and some countries demand business mails to have certain text and statements included in the signature.
Kolab has an option to automate this feature, so that organizations can be assured that rules and appliance are followed.
It is possible to connect to a kolab 16 server through the ActiveSync protocol. This makes it possible to use the Microsoft Outlook client in the most effective way towards Kolab. Kolab-syncroton, the kolab ActiveSync implementation, is installed together with the default installation.
Seafile is a GPL v3-licensed software designed to host files privately and securely on servers with access to the Web, in a fashion similar to some popular proprietary solutions. As of Kolab version 16, Chwala, the file storage component of Kolab, can use Seafile as a backend to store files.
This document outlines the steps needed to interface Chwala with Seafile.
files.example.com in this guide)This guide outlines various methods to allow Kolab components to log verbosely, for the purpose of troubleshooting.
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 sales@kolabsystems.com
Plesk Premium Email is compatible with a variety of desktop and mobile clients.
To connect your native MacOS clients use the “Internet Accounts” System Preference settings to add the following accounts:
Use the Exchange account with the default Android applications. All you need is your email address and password.
Should you want to use other applications, please refer to the generic settings below.
As long as your client application is following the standards, it can be used to connect to Plesk Premium Mail. Below is an overview of the various protocols we support along with the settings you need to enter in your client.
Please use your full and primary email address as username here.
Please use your full and primary email address as username here.
Please point your CalDAV and CardDAV capable client to these addresses:
For CalDAV: https://example.comor if that did not work: https://webmail.example.com/iRony/calendars/user%40example.com
For CardDAV: https://example.com or if that did not work: https://webmail.example.com/iRony/addressbooks/user%40example.com
When using the alternative address, please make sure to replace the last part (user@example.com and domain) with your actual username or switch to a client that is able to auto-discover the correct addresses based on the short address
Plesk Premium Mail also supports the proprietary ActiveSync protocol (often labelled Exchange in clients). In order to connect your client via this protocol, please use the following server address:
example.com
Your clients should always use https to connect to webmail, to avoid being vulnerable to attacks. A good method to ensure this is the case is to redirect from non-https to https.
To enable the https redirect got to the hosting settings of your domain and enable “Permanent SEO-safe 301 redirect from HTTP to HTTPS”.
Plesk Premium Email must be able to resolve the webmail url to the same system it is running on.
This indicates that you system does not support https. Ensure your system is properly secured with a suitable certificate (e.g. from Let’s Encrypt).
Plesk Premium Email relies on Roundcube being configured for the domain. If this is not the case the webmail will not be available.
To fix this go to the “Mail Settings” of this domain and select “Roundcube” as webmail.
Plesk Premium Email relies on Roundcube being configured for the domain. If this is not the case webmail will not be available.
To fix this go to the “Mail Settings” of this domain and select “Roundcube” as webmail.
Preferred domain redirects (e.g. “example.com” -> “www.example.com”) are currently not supported and will break various features, including seafile integration, activesync and collabora integration.
To disable the redirect got to the hosting settings of your domain and enable select “None” as “Preferred domain”.