Earlier today, we have received a report where the web client may inadvertently disclose the so-called common name of accounts within the same domain name space.
Author Archive for Jeroen van Meeuwen
Service Window: Independence Day, July 4th
In what may come as a shock move to some, but is abundantly clear to need to have happened to many much more well informed, Kolab Systems AG, and therefore Kolab Now, is changing the IP space that it uses primarily.
A service window is needed to implement this progression, and this service window is, for now, scheduled early July 4th, 2019, from 05:30 to 07:00 UTC.
Rate Limits Are A Thing Now
We’ve been dealing with quite a number of spammers whom register accounts with us, and start spamming third parties.
As you might imagine, our environment is geared toward redundancy and load-balancing and high traffic — hundreds of messages, thousands of recipients, every minute. The capabilities of our infrastructure are therefore in and by itself not limiting the rate at which anyone can send any number of messages to any number of recipients.
But, this is the case no longer per se.
> Continue ReadingIncident Report: Cascading Performance Problems
From last Sunday afternoon onward, up to Monday evening and throughout the Monday night, performance problems have deteriorated the Kolab Now service up to and including services becoming unavailable.
Our statistics for 2018
Our terms of service state there’s basically no way for anyone to get any access to your data without us also being able to talk about the fact it happened, and further down nested in our legal framework outline do we have a list of 3 general types under which individual requests could be filed.
I recall that some place, we also promise to at least publish the statistics. I don’t recall where, but I seem to remember we have. In any case, here’s our summary for 2018.
Annual TLS Certificate Refresh
Our annual certificate refresh is coming up,with our TLS certificates expiring annually in January. December is included for a reasonable grace-period, because services will need to be switched over, which costs time.
A Knowledge Base Reimagined
Hi there,
we updated our Knowledge Base yesterday with a more friendly, Kolab Now branded theme. Go over there and check it out.
Our October Silence?
Hi there,
I just wanted to provide you with a quick note that our blog roll’s “October silence” is nothing but just that. Some of us became a father to a son, have needed to deal with some citizen/resident paperwork, some of us choose to entertain the fresh snowfall way up the Alps, others took some vacation time, and such and so forth.
In the all-work-no-play area, I think we’ve figured out webmail decryption/signing, a responsive skin to be made available to mainstream Kolab Now, new exciting service venture definitions even though still under development, and we have now been able to deal with our midterm election anxiety (albeit November 25th could incur some implications domestically).
Incident Report: Thursday, 20:25 – Friday 01:15 UTC
Last night, a failure in the storage layer caused most of our services to be unavailable. In the week before, we replaced a failed hard drive. In the week before that, a so-called Virtual Fabric Adapter failed, causing a hypervisor to shut itself off. Since the most recent incident was the more serious downtime, that’s what we’ll start our reporting on.
Collabora Online 3.2 for Kolab Now
Over the course of today, we’ve upgraded our environment to run Collabora Online 3.2. Having waited for a point in time where no collaborative editing sessions had been ongoing, no-one should have noticed any service interruption.
