[Kroupware] clean install?

[Andrew McDonald]

Thanks for the reply Nicolas.

Unfortunately I wasn't so successful.

You wrote the basic steps to what I did.  

I did the following today.

1) /kolab/etc/rc.d/rc.kolab stop
2) rename /kolab to /kolabXXXXX
3) using the QIM Jul 31 20:49 I installed the rpm's
4) after /kolab/etc/rc.d/rc.kolab start I get 
LOGIN failed at /kolab/lib/perl/site_perl/5.8.0/i686-linux/Cyrus/IMAP/Admin.pm line 118
could not authenticate with Cyrus IMAP daemon () at /kolab/etc/kolab/kolab line 439.

At this point I am reluctant to try the Insight Connector again.

Andrew


> Nicolas Huillard wrote
>
> We recently did a reinstall from kolab beta 1 to the latest.
> We did teh following :
> * shutdown kolab beta
> * rename it's home directory
> * install a fresh release
> * recreate users (login were just 'username', and are now 
> 'username at domain') from the beginning
> * import messages from the old kolab to the new one
> * done.
> We had problems to import messages : a simple "cp -a" of the mail 
> directories does not work.
> The /kolab/var directory tree has changed from beta 1 ro the latest 1.0 
> > /kolab/var/spool/... is now in /kolab/var/imapd/spool/... Logs are not 
> at the same place, etc.
> Now everything works great.
> One Outlook 2000 with Insight Connector did not like the login/password 
> change : it kept crashing until I totally recreated the whole Windows 
> Messaging profile from the start.
> 
> NH
> 
> Andrew McDonald wrote:
> 
> > I had an older version of kolab installed which due to workload never got up and running \
> > correctly.  
> > Now I've tried the current rpm version and am getting a cyrus authentification error.
> > 
> > I've also noticed that a directory tree is missing /kolab/var/spool/(etc.) is not being \
> > created. 
> > I think I am doing the installation incorrectly as I had to force the last line in the QIM \
> > i.e. >>> /kolab/bin/rpm -Uhv kolab*kol.rpm --force 
> > Andrew