2.1 to 2.2-rc1 migration not advisable currently.

Hello,

For the benefit of others contemplating an early adoption,
I'd just like to
state that I will roll back my small setup to 2.1 after
dabbling in
2.2-rc1.
I had - not unexpectedly for a beta - a number of problems,
2 of which are
showstoppers for me and where not resolvable by community
input so far:
1) The Horde Web Client doesn't work for me. The
installation script did
nothing to the relevant configuration scripts and trying to
adapt them
manually did not yield a setup that I was able to log into
with credentials
perfectly fine when using kontact.
Manual/special configuration needs of horde where not
documented in
1st.readme for the beta.
2) Previously (2.1) setup shared imap resources (shared
contact
folders, ...) are not visible to kontact any more even
though the web-admin
interface shows them still present, owned by the right group
which still
contains the relevant users. A cyradmin investigation of the
folder(s) also
did not reveal anything obvious to the layman.

So my advise is: hold that curiosity and wait.

Joh

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Hi Johannes,

Johannes Graumann <johannes_graumannweb.de> writes:

> Hello,
>
> For the benefit of others contemplating an early
adoption, I'd just like to
> state that I will roll back my small setup to 2.1 after
dabbling in
> 2.2-rc1.
> I had - not unexpectedly for a beta - a number of
problems, 2 of which are
> showstoppers for me and where not resolvable by
community input so far:
> 1) The Horde Web Client doesn't work for me. The
installation script did
> nothing to the relevant configuration scripts and
trying to adapt them
> manually did not yield a setup that I was able to log
into with credentials
> perfectly fine when using kontact.
> Manual/special configuration needs of horde where not
documented in
> 1st.readme for the beta.

Manual configuration of Horde is definitely NOT advised  and
therefore we don't describe it in the 1st.readme.

If the configuration did not happen automatically in your
case then
this probably mean that kolabconf failed to correctly
transfer the
configuration templates in /kolab/etc/kolab/templates to
their correct
locations.

In that case there will be errors from kolabconf in your
syslog. Did
you check the log?

> 2) Previously (2.1) setup shared imap resources (shared
contact
> folders, ...) are not visible to kontact any more even
though the web-admin
> interface shows them still present, owned by the right
group which still
> contains the relevant users. A cyradmin investigation
of the folder(s) also
> did not reveal anything obvious to the layman.

Are they visible with another IMAP client like thunderbird?

Cheers,

Gunnar

>
> So my advise is: hold that curiosity and wait.
>
> Joh
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 700 6245 0000                         
Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users