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.
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 ReadingFrom 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.
In the beginning of the week we got a list of reports from users of iPhone connected via IMAP. These users reported that they were unable to list their mail folders. You can read about this issue in a previous blog post on this blog.
Our local Swiss datacenter and internet provider is a great, professional and stable provider of data connectivity and datacenter services. These services however demands updates of infrastructure, and such maintenance work is happening in a planned service window the night between Saturday 23.02.2019 and Sunday 24.02.2019.
A while back, users started to experience issues with IMAP LIST Extension for Special-Use Mailboxes. This to a level where a decision was made to temporarily suspend supporting Special-Use at Kolab Now.
Lately we have found ways to get around the problems that were present back then, and over the change of the year we introduced an update that, among other great improvements, contained these solutions and re-enabled the Special-Use.
Unfortunately, meanwhile Microsoft has also updated Outlook, and their update has changed the return options that Outlook is using with the LSUB command on the IMAP server.
This has caused issues for some users, who connect Outlook to Kolab Now via IMAP. Those users are suddenly not able to see some of their folders and mails in Outlook. The folders are perfectly visible in the web client and in other IMAP clients like mobile clients, Mac Mail and Thunderbird.
While the RFC compliance issue (the LSUB command does not accept a client specifying RETURN options) certainly has been made visible by Microsoft changing the behavior of Outlook, inversely Kolab Now providing an update to the benefit of all other clients has suddenly shown the related Outlook behavior to be faulty.
The root cause of the issue can be narrowed down to the expectations from Cyrus IMAP while parsing the LSUB command. Besides filing an upstream ticket, Kolab Systems has engaged in this issue and is contributing a fix to the Cyrus IMAP code. This fix is now going through test and QA, and should be ready to be deployed to Kolab Now soon.
If you are one of the users, who has problems because you are connecting Outlook to Kolab Now via IMAP, then you can work around the issue by – either using another IMAP client – or by connecting your Outlook to Kolab Now via ActiveSync, until the fix for Cyrus IMAP is ready and deployed.
If you have any questions or concerns in this context, then please contact support@kolabnow.com.
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.
The change of the year is always a good opportunity to look back at what has happened, and to make changes for the future. Earlier we have been writing about the work put into the Responsive skin (elastic skin) and it’s now time to enjoy the result we got out of the work that was done.
A version of a responsive skin was available on beta.kolabnow.com/apps for a while, but now it has finally passed QA, and is made available for all Kolab Now users.
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.
