Update: kolab-freebusy 1.1.1

We’re pleased to announce an update for the kolab-freebusy, version 1.1.1

This update is a bugfix release for Kolab 16, available for CentOS 7, Debian 8, Debian 9, Red Hat Enterprise Linux 7 and Ubuntu 16.04.

The following issues are fixed;

  • T110991: When an event had no organizer (pure time reservations) they were not considered by Kolab-Freebusy. This has been fixed.

Update: pykolab 0.8.10

We’re pleased to announce an update for the pykolab packages, version 0.8.10.

This update is a bugfix release for Kolab 16, available for CentOS 7, Debian 8, Debian 9, Red Hat Enterprise Linux 7 and Ubuntu 16.04.

The following issues are fixed;

  • T75735: Manage the pool of processes for Wallace; allow a certain process to not get stuck, and clean up afterward.
  • Fix using an attendee object in a debug message
  • The command ‘kolab undelete-mailbox’ now correctly “undeletes” mailboxes
  • Correct a reference to legacy username ‘clam’, now ‘clamupdate’, for the initial setup
  • T114576: Correctly parse iTips that do not have an organizer
  • T114576: Fix error in invitation policy reply for invitations without an organizer
  • Correct handling empty trimmed comments (i.e., from our friends at Microsoft Outlook)
  • T75978: Read the DTSTART properly before we read RECURRENCE-ID
  • T2274: Increase the maximum length of an email address in the policy cache tables
  • T2274: Add an option –drop-tables to /usr/libexec/postfix/kolab_smtp_access_policy

Update: kolab-webadmin 3.2.12 (Updated)

We’re pleased to announce a further update for the kolab-webadmin packages, version 3.2.12.

This update is a bugfix release for Kolab 16, available for CentOS 7, Debian 8, Debian 9, Red Hat Enterprise Linux 7 and Ubuntu 16.04.

While our previous release of the kolab-webadmin did resolve the issues mentioned in the errata, an old regression defect was sneaking into the final package. After update, the kolab-webadmin would show up with all fields grayed out and unavailable for change.

This regression was fast eliminated, and a new package created and released. If you update at this time, there is no such issue present.

We ask you to please accept our apologies for the inconvenience this has caused.