Author Archive for Mads Petersen

In September we moved to a new and smarter user account administration tool. Just navigate back a few entries in the blog to read about that event.

This new tool was built with new technology and more modern models, and the team was rethinking the architecture from the ground up. The new module, which has taken a more central position in Kolab, makes it easier to make changes and improve the feature sets. It has put us in a position to move forward faster and more effective than ever before. The cockpit (also sometimes referred to as the dashboard) will become the central hub for a variety of new features that we’ll add over time.

This is of course no news. As mentioned above, we have been babbling about that for a while on this blog. The news in this post is that we have made a change. Based on feedback from User Experience specialists and (mostly) You, our customer, we have made a change to the menus in our systems. Let’s take a look at the changes:

> Continue Reading

It’s time!

If you followed our blog over the latest months, surely you have seen that we are working on our new user management module (called HKCCP). This is the module that manage your cockpit; it is where you login when you want to set and change the features supported by your subscription such as Mobile Connectivity, 2FA, Disk space’, etc..

We are now in a position to release and deploy the first production iteration of the module, and we therefore announce a service window for:

Sunday 13th of September 2020, between 07:00 UTC and 11:00 UTC 17:30 UTC. 

During that period the cockpit will be unavailable for a short period, but there will be no impact on other feature or functionality of the service. If you are not working with the cockpit during that time you will not experience any issues at all.

> Continue Reading

Late Sunday night at 21:31 CET we were alarmed by lost connections. Symptoms seemed to point to a networking issue in the datacenter. Our datacenter provider was alerted, we sent our own emergency team onsite to assist in resolving the issue, and to deal with any fallout.

A faulty firewall was recovered, and mail started flowing again at around 00:10. Our ops team is now investigating why the firewalls didn’t fail over as they are configured to do in such situation.

At about 04:15, long after the system had recovered from the firewall issue, one system started to throw disk errors, which was leading to some users not being able to access the data in their folders. As this was a separate issue, the symptoms were only discovered at around 06:45, as it was assumed to be recovery issues from the previous outage. As soon as the disk error issue was realized, it was fixed and recovered. Connection to data was available again for all users at 07:10.

Where as we are still investigating the root cause for both of these issues, we can state, that no data was at risk at any time during the events.

We apologize for any inconvenience this has caused.