How to install a working Kolab 3.2 server?
ITSEF Admin
itsef-admin at brightsight.com
Thu Mar 20 09:38:05 CET 2014
On Wednesday 19 March 2014 19:15:18 Christian Hügel wrote:
> > I believe, kolab-3.2 still has many issues.
[...]
>
> I can speak only for the rpm-based release of Kolab 3.2 for CentOS:
[...]
That's what we were using. I very much appreciate your insights on the matter!
However, for me, the point is now moot - our tests with 3.1 yesterday showed
clearly that the groupware functionality of Kontact has worsened significantly
for the newer releases (KDE 4.12.3) when compared with the older e35 (which,
in turn, was extremely unstable...) - the way the free-busy information is
presented is close to unusable at the moment (*if* you can convince it to pull
in free-busy information at all), as are multiple calendars in tabbed view
(for n>3) - both show-stoppers with regard to the workflow here. It is really
a shame, as the e-mail side of Kontact has improved a lot. Nonetheless,
together with the akonadi instabilities (have your IMAP server disconnect
unexpectedly => risk a corrupted akonadi cache) this was enough for management
to pull the plug. Given that Kontact is pretty much the only Linux desktop
client for Kolab (Thunderbird + plugins wasn't convincing, either, the last
time we tried) that pretty much pulls the plug on Kolab as well. We will now
investigate other options (I just hope we can get away with not having to
install MS products... ...Linux groupware seems still a mess with regard to
Linux desktop support, even after so many years... :-( ). We will see.
Regards,
Thomas
--
------------------------------------------------------------------------------
Thomas Ribbrock, IT-Team brightsight
More information about the users
mailing list