How to install a working Kolab 3.2 server?

[ITSEF Admin]

On Tuesday 18 March 2014 06:01:22 James Mills wrote:
>
> On Tue, Mar 18, 2014 at 5:50 AM, Brady, Mike 
<mike.brady at devnull.net.nz>wrote:
> > 
> > Yes the default configuration certainly needs improving as there are quite
> > a number of issues with it.  You just have to search the list archives and
> > bugzilla for fixes.
> > 
> > In particular freebusy on 3.2 doesn't work due to the change to Cyrus IMAP
> > 2.5.  For a work around see
> > http://lists.kolab.org/pipermail/users/2014-March/016819.html .
>
> Perhaps it's worth noting all the fixes in this thread in one place?

Unless there is another, easy to find, "canonical" place for that I would 
appreciate if people were willing to do so.

On the other hand, given that what we want to have right now is nothing but a 
testnetwork for quick assessment of the current Kolab <-> Kontact state, I'm 
actually considering trying with Kolab 3.1 first - would that be the more 
stable option for now?

Regards,

Thomas
-- 
------------------------------------------------------------------------------
	Thomas Ribbrock, IT-Team brightsight