Kolab Operations

Zero-moderation status updates straight from the horse's mouth.

Like with most horse's mouths, dialogue is going to be near impossible.

[Kolab Operations @kolabops]

webmail functionality is restored

[Kolab Operations @kolabops]

working to restore web client functionality

[Kolab Operations @kolabops]

email submission from your external clients is available now, as well as outbound email traffic

[Kolab Operations @kolabops]

we're having some challenges with restoring mail sending functionality, but users should be able to receive email and update their calendars and sync their contacts

[Kolab Operations @kolabops]

people are receiving email again -- this includes imap, activesync users

[Kolab Operations @kolabops]

activesync and dav are reported to be working -- still working on the fixing of email flows

[Kolab Operations @kolabops]

Limited IMAP access is restored, we're now working on some SMTP functionality

[Kolab Operations @kolabops]

so, it's two nodes down, both with corrupted firmware

we're working on alternative approaches to bring back some services

[Kolab Operations @kolabops]

a small update, without an ETA;

node rescue in progress, then off to treat the other node

[Kolab Operations @kolabops]

We're having some problems on our infrastructure and are looking for the cause / solutions.

[Kolab Operations @kolabops]

An unexpected result of the update done this morning was a miscalculation of quota. As I am typing this we are fixing the issue across the board.

[Kolab Operations @kolabops]

The last IMAP issues should be fixed now. Again, please let Support know of any issues.

[Kolab Operations @kolabops]

We have been made aware of an issue with the IMAP connections. We are looking into it with highest priority.

[Kolab Operations @kolabops]

The changes has been performed. The Service window is done. All services are back online.

Please let Support know of any issues.

[Kolab Operations @kolabops]

The 'last second' synchronizations of a few backend servers are taking a little longer than expected. That is why the connection is still not there. we're working on it.

[Kolab Operations @kolabops]

Service window is opened and the changes are in progress. Connections to backend servers are blocked at the moment to prevent traffic from getting in troubles.

[Kolab Operations @kolabops]

webmail and general access are back, activesync and *DAV are waiting for the flood of backlog items to come and pass

[Kolab Operations @kolabops]

The database cluster is back up, we're purging some voluminous tables of obsolete/irrelevant entries, and then we can start restoring service.

[Kolab Operations @kolabops]

I'm afraid we're going to need to reinitialize the database cluster.

[Kolab Operations @kolabops]

There's some performance problems with our database layer, so activesync and *DAV are temporarily disabled