Kolab.org Groupware Solution

A couple days ago, the Roundcube Next crowdfunding campaign reached our initial funding goal. We even got a piece on Venture Beat, among other places. This was a fantastic result and a nice reward for quite a bit of effort on the entire team's part. ... [More] Reaching our funding goal was great, but for me personally the money is secondary to something even more important: community. You see, Roundcube had been an Internet success for a decade now, but when I sat to talk with the developers about who their community was and who was participating from it, there wasn't as much to say as one might hope for such a significant project used by that many people. Unlike the free software projects born in the 90s, many projects these days are not very community focused. They are often much more pragmatic, but also far less idealistic. This is not a bad thing, and I have to say that the focus many of them have on quality (of various sorts) is excellent. There is also a greater tendency to have a company founded around them, a greater tendency to be hosted on the mostly-proprietary Github system with little in the way of community connection other than push requests. Unlike the Free software projects I have spent most of my time with, these projects hardly try at all to engage with people outside their core team. This lack of engagement is troubling. Community is one of the open source1 methodology's greatest assets. It is what allows for mutual interests to create a self-reinforcing cycle of creation and support. Without it, you might get a lot of software (though you just as well might not), but you are quite unlikely to get the buy-in, participation and thereby amplifiers and sustainability of the open source of the pre-Github era. So when we designed the Roundcube Next campaign, we positioned no less than 4 of the perks to be participatory. There are two perks aimed at individual backers (at $75 and $100) which get those people access to what we're calling the Backstage Pass forums. These forums will be directed by the Roundcube core team, and will focus on interaction with the end users and people who host their own instance of Roundcube. Then we have two aimed at larger companies (at $5,000 and $10,000) who use Roundcube as part of their services. Those perks gain them access to Roundcube's new Advisory Committee. So while these backers are helping us make Roundcube Next a reality, they are also paving a way to participation for themselves. The feedback from them has been extremely good so far, and we will build on that to create the community Roundcube deserves and needs. One that can feed Roundcube with all the forms of support a high profile Free software product requires. So this crowdfunding campaign is really just the beginning. After this success, we'll surely be doing more fund raising drives in future, and we'd still love to hit our first stretch goal of $120,000 ... but even more vitally this campaign is allowing us to draw closer to our users and deployers, and them with us until, one hopes, there is only an "us": the people who make Roundcube happen together. That we'll also be delivering the most kick-ass-ever version of Roundcube is pretty damn exciting, too. ;) p.s. You all have 3 more days to get in on the fun! 1 I differentiate between "Free software" as a philosophy, and "open source" as a methodology; they are not mutually exclusive, but they are different beasts in almost every way, most notably how one is an ideology and the other is a practice.   [Less]

As I have mentioned in earlier blog entries, Kolab Enteprise has gained data loss prevention (DLP) functionality this year that goes above and beyond what one tends to find in other groupware products. Kolab's DLP is not just a back-up system that ... [More] copies mails and other objects to disk for later restore, it actually creates a history of every groupware object in real-time that can later be examined and restored from. This will eventually lead to some very interesting business intelligent features. The storage system for the Kolab DLP system is Basho's industry-leading distributed NoSQL database, Riak KV. (The "KV" stands for key/value.) We chose Riak KV because it scales naturally (it is designed to be run as a cluster of nodes by default), is robust by design (CAP Theorem ftw), and is dead simple to deploy on development and production machines alike. A further key factor for us is that Basho provides proven enterprise-grade support for its line of Riak products. This was a requirement for us as we need to provide enterprise-grade support for the entire Kolab Enterprise stack. (It was a nice coincidence that both Riak and core parts of Kolab's DLP system are written in Erlang. ;) I sat down with Manu Marchel, Managing Director for EMEA at Basho Technologies Inc., recently for a mutual interview. You can read my interview on the Basho blog (I'll update this entry with a link to their blog when it is published lived); here is a transcript of my conversation with Manu: NoSQL is a quite a new technology in the Big Data space. Many people might have heard about things like Hadoop but how does NoSQL fit in? Could you give everyone the quick cheatsheet on what NoSQL databases are and specifically what is RiakKV your key value NoSQL database? NoSQL databases are the new generation of databases that were designed to address the needs of enterprises to store, manage, analyse and serve the ever increasing amounts of unstructured data that make over 80% of all data being created nowadays in public clouds or private infrastructures. Apache Hadoop has done a great job of handling batch analytics use cases at massive scale for unstructured data, what I would call exploratory or discovery analytics. What NoSQL databases like riak do in comparison is help organisations manage their active data workloads as well and providing near real time operational analytics at scale. Most importantly, most businesses need scalability, availability and fault tolerance attributes as core requirements to their current and future applications architecture and these are deciding factors for NoSQL against traditional relational databases. NoSQL databases started as one of 4 types: Key-Value, Column store, Document and Graph but nowadays they are becoming multi model whereby for example riak can efficiently handle key value, but also documents as well as log/time series as demonstrated by our wide range of customers including Kolab Systems. Riak KV is the most widely adopted NoSQL Key Value database with scalability, high availability, fault tolerance and operational simplicity as its key properties. It is used most often for mission critical use cases and works great for handling User Data, Session Data, Profile Data, Social Data, Real-time Data and Logging Data use cases. It provides near realtime analytics with its secondary indexes, search through Solr, in-situ Map/Reduce and soon to come Apache Spark support. Finally its multi data center replication capability makes it easy to ensure business continuity, geo location of data for low latency access across continents or by segregating workloads to ensure very reliable low latency. RiakKV is known for it’s durability, it’s part of the reason we chose it for Kolab's DLP system. Could you give us some insight into how RiakKV achieves this? Hardware does fail, and when it does your IT Infrastructure needs to be able to cope and your systems must continue to operate while getting the resources back online as soon as possible. Riak KV was designed to eliminate the impact of the unexpected. Even if network partitions or hardware failures cause unanticipated outages, Riak KV can still read and write your data. This means you never lose data even when the part of the system goes down. For Kolab customers, it means that they have the security of knowing that the data loss and auditing that they are paying for is backed up by the best system available to deliver on this promise. Availability seems to be a very important thing for databases in today’s digital age. How is Riak providing this key feature to Kolab and how does this enhance the Kolab offering? Simply, Riak KV is designed to intelligently replicate and retrieve data making sure that applications based on the database are always available. Scalability also comes into play here as well. Unlike traditional databases, Riak is designed to respond to the billions of data points and terabytes of data that are being produced -- often in real-time -- as it is able to scale in a near linear fashion to give Kolab the best possible performance. Ultimately this means that Kolab’s application is always available so as an end-user you don’t experience any system outages no matter how busy or active your users are. We integrate RiakKV with Kolab’s data loss prevention system to store groupware object histories in realtime for auditing and roll-back if needed. Is this unique? Yes! This is a great example of two great technologies working together to provide an excellent customer experience. Combining the power of Riak KV’s high availability, fault tolerance, and scalability with Kolab’s data loss prevention system means that you have an incredibly strong and powerful system. Basho is a really unique name for a technology company - is there any history or background to it? Thank you, we really like our name too. Basho’s name was inspired by the real life Matsuo Basho (1644 – 1694) who is considered by many to be Japan's most renowned and revered writer of haiku. Haiku are known for their balance of lines and syllables where the simplicity of the structure is important. This is a founding, guiding principle that Riak KV is based on, as our operational simplicity is core to our architecture eliminating the need for mindless manual operations as data can be automatically and uniformly distributed. To see the partnership of Basho's Riak and Kolab Enterprise in action together, come see us in Munich at the TDWI European Conference 22-24th June. We'll be in a booth showing both Riak KV and Kolab Enterprise, and will be happy to answer your questions!   [Less]

As I have mentioned in earlier blog entries, Kolab Enteprise has gained data loss prevention (DLP) functionality this year that goes above and beyond what one tends to find in other groupware products. Kolab's DLP is not just a back-up system that ... [More] copies mails and other objects to disk for later restore, it actually creates a history of every groupware object in real-time that can later be examined and restored from. This will eventually lead to some very interesting business intelligent features. The storage system for the Kolab DLP system is Basho's industry-leading distributed NoSQL database, Riak KV. (The "KV" stands for key/value.) We chose Riak KV because it scales naturally (it is designed to be run as a cluster of nodes by default), is robust by design (CAP Theorem ftw), and is dead simple to deploy on development and production machines alike. A further key factor for us is that Basho provides proven enterprise-grade support for its line of Riak products. This was a requirement for us as we need to provide enterprise-grade support for the entire Kolab Enterprise stack. (It was a nice coincidence that both Riak and core parts of Kolab's DLP system are written in Erlang. ;) I sat down with Manu Marchel, Managing Director for EMEA at Basho Technologies Inc., recently for a mutual interview. You can read my interview on the Basho blog (I'll update this entry with a link to their blog when it is published lived); here is a transcript of my conversation with Manu: NoSQL is a quite a new technology in the Big Data space. Many people might have heard about things like Hadoop but how does NoSQL fit in? Could you give everyone the quick cheatsheet on what NoSQL databases are and specifically what is RiakKV your key value NoSQL database? NoSQL databases are the new generation of databases that were designed to address the needs of enterprises to store, manage, analyse and serve the ever increasing amounts of unstructured data that make over 80% of all data being created nowadays in public clouds or private infrastructures. Apache Hadoop has done a great job of handling batch analytics use cases at massive scale for unstructured data, what I would call exploratory or discovery analytics. What NoSQL databases like riak do in comparison is help organisations manage their active data workloads as well and providing near real time operational analytics at scale. Most importantly, most businesses need scalability, availability and fault tolerance attributes as core requirements to their current and future applications architecture and these are deciding factors for NoSQL against traditional relational databases. NoSQL databases started as one of 4 types: Key-Value, Column store, Document and Graph but nowadays they are becoming multi model whereby for example riak can efficiently handle key value, but also documents as well as log/time series as demonstrated by our wide range of customers including Kolab Systems. Riak KV is the most widely adopted NoSQL Key Value database with scalability, high availability, fault tolerance and operational simplicity as its key properties. It is used most often for mission critical use cases and works great for handling User Data, Session Data, Profile Data, Social Data, Real-time Data and Logging Data use cases. It provides near realtime analytics with its secondary indexes, search through Solr, in-situ Map/Reduce and soon to come Apache Spark support. Finally its multi data center replication capability makes it easy to ensure business continuity, geo location of data for low latency access across continents or by segregating workloads to ensure very reliable low latency. RiakKV is known for it’s durability, it’s part of the reason we chose it for Kolab's DLP system. Could you give us some insight into how RiakKV achieves this? Hardware does fail, and when it does your IT Infrastructure needs to be able to cope and your systems must continue to operate while getting the resources back online as soon as possible. Riak KV was designed to eliminate the impact of the unexpected. Even if network partitions or hardware failures cause unanticipated outages, Riak KV can still read and write your data. This means you never lose data even when the part of the system goes down. For Kolab customers, it means that they have the security of knowing that the data loss and auditing that they are paying for is backed up by the best system available to deliver on this promise. Availability seems to be a very important thing for databases in today’s digital age. How is Riak providing this key feature to Kolab and how does this enhance the Kolab offering? Simply, Riak KV is designed to intelligently replicate and retrieve data making sure that applications based on the database are always available. Scalability also comes into play here as well. Unlike traditional databases, Riak is designed to respond to the billions of data points and terabytes of data that are being produced -- often in real-time -- as it is able to scale in a near linear fashion to give Kolab the best possible performance. Ultimately this means that Kolab’s application is always available so as an end-user you don’t experience any system outages no matter how busy or active your users are. We integrate RiakKV with Kolab’s data loss prevention system to store groupware object histories in realtime for auditing and roll-back if needed. Is this unique? Yes! This is a great example of two great technologies working together to provide an excellent customer experience. Combining the power of Riak KV’s high availability, fault tolerance, and scalability with Kolab’s data loss prevention system means that you have an incredibly strong and powerful system. Basho is a really unique name for a technology company - is there any history or background to it? Thank you, we really like our name too. Basho’s name was inspired by the real life Matsuo Basho (1644 – 1694) who is considered by many to be Japan's most renowned and revered writer of haiku. Haiku are known for their balance of lines and syllables where the simplicity of the structure is important. This is a founding, guiding principle that Riak KV is based on, as our operational simplicity is core to our architecture eliminating the need for mindless manual operations as data can be automatically and uniformly distributed. To see the partnership of Basho's Riak and Kolab Enterprise in action together, come see us in Munich at the TDWI European Conference 22-24th June. We'll be in a booth showing both Riak KV and Kolab Enterprise, and will be happy to answer your questions!   [Less]

This describes how to install a docker image of Kolab. Please note: this is not meant to be for production use. The main purpose is to provide an easy way for demonstration of features and for product validation. This installation has not been tested ... [More] a lot, and could still use some fine tuning. This is just a demonstration of what could be done with Docker for Kolab. Preparing for Docker I am using a Jiffybox provided by DomainFactory for downloading a Docker container for Kolab 3.4 running on CentOS 7. I have installed Fedora 21 on a Jiffybox. Now install docker: sudo yum install docker-io systemctl start docker systemctl enable docker Install container The image for the container is available here: https://registry.hub.docker.com/u/tpokorra/kolab34_centos7/ If you want to know how this image was created, read my other blog post http://www.pokorra.de/2015/06/building-a-docker-container-for-kolab-3-4-on-jiffybox/. To install this image, you need to type in this command: docker pull tpokorra/kolab34_centos7 You can create a container from this image and run it: MYAPP=$(sudo docker run --name centos7_kolab34 -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 443:443 -h kolab34.test.example.org -d -t -i tpokorra/kolab34_centos7 /bin/bash) You can see all your containers: docker ps -a You should attach to the container, and inside the container change the root password: docker attach $MYAPP # you might need to press Enter to see the login screen # login with user root and password root # enter a secure password: passwd root To stop the container: docker stop $MYAPP To delete the container: docker rm $MYAPP You can reach the Kolab Webadmin on this URL (replace localhost with the IP address of the Jiffybox): https://localhost/kolab-webadmin. Login with user: cn=Directory Manager, password: test The Webmail interface is available here: https://localhost/roundcubemail.   [Less]

This article is an update of the previous post that built a Docker container for Kolab 3.3 from September 2014. Preparation I am using a Jiffybox provided by DomainFactory for building the Docker container. I have installed Fedora 21 on a Jiffybox. ... [More] Now install docker: sudo yum install docker-io systemctl start docker systemctl enable docker Create a Docker image To learn more about Dockerfiles, see the Dockerfile Reference My Dockerfile is available on Github: https://github.com/TBits/KolabScripts/blob/Kolab3.4/kolab/Dockerfile. You should store it with filename Dockerfile in your current directory. This command will build a container with the instructions from the Dockerfile in the current directory. When the instructions have been successful, an image with the name tpokorra/kolab34_centos7 will be created, and the container will be deleted: sudo docker build -t tpokorra/kolab34_centos7 . You can see all your local images with this command: sudo docker images To finish the container, we need to run setup-kolab, this time we define a hostname as a parameter: MYAPP=$(sudo docker run --name centos7_kolab34 -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 443:443 -h kolab34.test.example.org -d -t -i tpokorra/kolab34_centos7 /bin/bash) docker attach $MYAPP # you might need to press the Enter key to see the login prompt... # login with user root and password root # run inside the container: echo 2 | setup-kolab --default --timezone=Europe/Brussels --directory-manager-pwd=test cd /root/KolabScripts-Kolab3.4/kolab ./initHttpTunnel.sh ./initSSL.sh test.example.org shutdown -h now Now you commit this last manual change: docker commit $MYAPP tpokorra/kolab34_centos7 # delete the container docker rm $MYAPP You can push this image to https://registry.hub.docker.com: #create a new account, or login with existing account: sudo docker login # there is currently an issue with the Fedora 21 rpm package (docker-io-1.6.0-4.git350a636.fc21.x86_64) # see also https://forums.docker.com/t/docker-push-error-fata-0001-respository-does-not-exist/1309/18 # solution: yum install --enablerepo=updates-testing docker-io sudo docker push tpokorra/kolab34_centos7 You can now see the image available here: https://registry.hub.docker.com/u/tpokorra/kolab34_centos7/ See this post Installing Demo Version of Kolab 3.4 with Docker about how to install this image on the same or a different machine, for demo and validation purposes. Current status: There are still some things not working fine, and I have not tested everything. But this should be a good starting point for other people as well, to help with a good demo installation of Kolab on Docker.   [Less]

This post originates in the idea from Stephen Gallagher, who is working on rolekit: “rolekit is a daemon for Linux systems providing a stable D-BUS interface to manage the deployment of [Fedora] Server Roles”. The code of Rolekit is available ... [More] here: https://github.com/sgallagher/rolekit On his blog, Stephen stated in this post: A few that I’d love to see (but don’t have time to start on yet): A fileserver role that manages Samba and NFS file-shares (maybe [s]ftp as well). A mail and/or groupware server role built atop something like Kolab A backup server This made me wonder, how would that be, if Kolab became a Server Role for Fedora, and could be installed from the Fedora repositories? Through my work on OpenPetra and Mono I got involved with Fedora, and noticed that the Fedora community tries out new technology, proves if it works, and then the technology will eventually end up in other distributions as well. First steps On IRC, we agreed that the first step would be to create a Copr repo, that contains the Kolab packages, and to write this blog post describing how to install and configure Kolab. Creating the Copr Repo So, here is the Copr repository for Fedora 22: https://copr.fedoraproject.org/coprs/tpokorra/kolab/ I created it by getting the src rpm packages from the Kolab repository, from 3.4 and 3.4 updates, in this order: kolab-utils roundcubemail-plugins-kolab kolab-webadmin kolab pykolab chwala iRony kolab-freebusy roundcubemail-skin-chameleon php-Net-LDAP3 roundcubemail kolab-syncroton roundcubemail-plugin-contextmenu kolab-schema kolab-autodiscover python-sievelib php-pear-Net-LDAP2 cyrus-imapd The packages libkolab and libkolabxml and kdepim are already in Fedora, and I did not update them: libkolab: https://admin.fedoraproject.org/pkgdb/package/libkolab/ libkolabxml: https://admin.fedoraproject.org/pkgdb/package/libkolabxml/ kdepimlibs: https://admin.fedoraproject.org/pkgdb/package/kdepimlibs/ Cyrus Imapd is also in Fedora, https://admin.fedoraproject.org/pkgdb/package/cyrus-imapd/, but not on the latest version. So I used version 2.5 from Kolab. Roundcubemail is uptodate in Fedora, https://admin.fedoraproject.org/pkgdb/package/roundcubemail, but somehow does not provide roundcubemail(core) >= 1.1 as required by some Kolab packages. So I also used the package from Kolab. I have patched the pykolab package, and backported some features to extend the setup-kolab command so that it can be used non-interactively, which is probably required to be integrated into rolekit. In Kolab 3.5 (release planned for August 2015), those features will be included. Installing Kolab from the Copr Repo I have tested this with Fedora 22. Please disable SELinux, since there isn’t a SELinux policy available yet for Kolab. Jeroen van Meeuwen has worked on it a while ago, but it probably needs updating and testing: https://github.com/kanarip/kolab-selinux Another thing: the server should have a FQDN, eg. kolab.example.org. See the installation instructions for details. dnf install dnf-plugins-core dnf copr enable tpokorra/kolab dnf install kolab mytz=Europe/Brussels pwd=test setup-kolab --default --mysqlserver=new --timezone=$mytz --directory-manager-pwd=$pwd On my setup, I need to add this line to /etc/kolab/kolab.conf, in section [kolab-wap], because I am running it inside an LXC container with an iptables tunnel for port 80, and the Kolab webadmin does not calculate the url for the API properly: api_url = http://localhost/kolab-webadmin/api You also need to add these lines to /etc/roundcubemail/config.inc.php (this will be fixed in Kolab 3.5): # required for php 5.6, see https://bbs.archlinux.org/viewtopic.php?id=193012 and http://php.net/manual/de/context.ssl.php # production environment requires real security settings!!! $config['imap_conn_options']=array( 'ssl'=>array( 'verify_peer_name'=>false, 'verify_peer'=>false, 'allow_self_signed'=>true)); $config['smtp_conn_options']=array( 'ssl'=>array( 'verify_peer_name'=>false, 'verify_peer'=>false, 'allow_self_signed'=>true)); After this, the Kolab Server should run, and you can go to http://localhost/kolab-webadmin and login with the user “cn=Directory Manager” (without the quotes) and the password that you specified as parameter for setup-kolab. The webmail runs at http://localhost/roundcubemail Conclusion I hope this shows the possibilities, and what amount of work still needs to be done. I guess the existing packages in Fedora should be kept uptodate, and missing Kolab packages need to be added to Fedora as well. Work on SELinux policy is also required (see above). The other thing: with the server role Kolab, how much should the role define how the server is configured securely? In Kolab Upstream, we documented how to secure the server, but left it to the Sysadmin to actually enforce security, because the Kolab community cannot take responsibility for the server. I have a number of scripts, that might be useful for rolekit: https://github.com/TBits/KolabScripts There is eg. a script for setting up a self-signed SSL Certificate, etc.   [Less]

Some weeks ago, I did significant work on getting Kolab 3.4 running on Debian Jessie. I did this work in my own time, because at TBits.net we focus on CentOS7. Still the work was benefitial to CentOS as well, because I had to do some fixes for PHP ... [More] 5.6, which will eventually be part of CentOS sometime in the future. For your interest, here are the bugs I have worked on: Apache package conflict, rebuilt libcalendaring: https://issues.kolab.org/show_bug.cgi?id=5015 PHP 5.6 https://issues.kolab.org/show_bug.cgi?id=5033 https://issues.kolab.org/show_bug.cgi?id=5034 For several weeks, my nightly tests succeed now for Debian Jessie as well, on LBS: see https://lbs.solidcharity.com/package/tbits.net/kolab-test/kolab-test#Kolab3.4_debian/jessie/amd64 I just updated the installation instructions: https://docs.kolab.org/installation-guide/debian.html I am not using Debian Jessie in production, and that means two things: I cannot say if it actually works in production. I only can say that it passes my nightly tests. In the future, I think I might need to focus on CentOS more, and cannot invest so much of my own free time into the Debian packaging. I am open for suggestions or sponsorship (perhaps https://www.bountysource.com/?)   [Less]

I realized it would be good to blog here about updates for the Kolab 3.4 Community Edition. Although it is a community release, and therefore does not come with any guarantuee (that is up to the Enterprise version), some people are using the ... [More] community edition in production, and we as the community are contributing fixes and maintaining the release. Thanks to Daniel Hoffend, we now have the latest Roundcube 1.1.2 in Kolab 3.4 Updates. Just run yum update (CentOS) or apt-get update && apt-get upgrade (Debian)… Daniel also backported a week ago a fix for the installation of Kolab, the Roundcube configuration for the Addressbook was not correct. More details can be seen in the Change Reqest on OBS. You might want to manually update your existing installation in the same way… And another fix from 10 days ago: Daniel backported a fix for the Roundcube Context menu. See details in the Change Request on OBS. In the future, I will aim to post here as soon as we accept updates into Kolab 3.4 Updates. If you want to contribute to make the community edition of Kolab more stable and secure, please make suggestions on the mailing list about fixes that you know of, and if you enjoy creating a change request on OBS yourself, then go for it, you would be very welcome!   [Less]

We just published updates to both stable versions 1.0 and 1.1 after fixing many minor bugs and adding some security improvements to the 1.1 release branch. Version 1.0.6 comes with cherry-picked fixes from the more recent version to ensure proper ... [More] long term support especially in regards of security and compatibility. The security-related fixes in particular are: XSS vulnerability in _mbox argument security improvement in contact photo handling potential info disclosure from temp directory See the full changelog here. Both versions are considered stable and we recommend to update all productive installations of Roundcube with either of these versions. Download them from roundcube.net/download. As usual, don’t forget to backup your data before updating! And there’s one more thing: please support our crowdfunding campaign for Roundcube Next either directly or by spreading the word about it. You’re help is much appreciated!   [Less]

Some weeks after the official Kolab 3.4 release we finally released the Gentoo packages for Kolab 3.3 including the usual benefits like the CalDAV/iCAL ready calendar plugin and the Getmail plugin which allows fetching mails from any external email ... [More] account right into your Kolab Groupware. During this release some things required much more work than we've expected. To speed things up for the next time we plan to cooperate more closely with the Kolab developers and the community. For example we finally requested the multi-driver support for the calendar plugin to be pushed upstream. The required patch is currently pending and waiting for approval. Further we had some great release planning meetings with the Kolab guys where they announced to also keep focus on quality assurance and upgrade paths for the community version. For example, as a first result, a detailled migration guide for Kolab 3.3 can be found here. In the meantime we keep working on the upcoming Gentoo packages for Kolab 3.4. Included are the brand new chameleon skin and a lot of bugfixes which make the Kolab 3.4 release "probably the best quality assured stable release Kolab.org has yet performed". Find detailled installation instruction in our wiki: https://wiki.awesome-it.de/howtos/kolab Report bugs or patches to our Gitlab: https://gitlab.awesome-it.de/overlays/kolab/issues       [Less]