Yet Another Mail Client Problem... :-(

[Luca Villani]

Alle 16:07, martedì 29 giugno 2004, Bernhard Reiter ha scritto:


> Build the client once per platform and then just roll out the tarball
> from the directory you have installed in (like /usr/local/koab-kolab).

This is not a chance, it's simply a workaround: I'm administering more than 
200 workstation, in this situation I must have a native binary package 
(.deb, .rpm) to put into internal package repository. If I start installing 
software via tarball, I will go into te blue in a few weeks... :-(



> > Well, it don't work: my own prepackaged kontact seem don't handle all
> > kolab features except from IMAP e-mail retrieving: I had done a test with
> > a simple kalendar appointment, but receiver see the requesting e-mail
> > like this:
[...]
> This is not the raw email, so nobody can say if this is correct or not.
> If you attach an email, please attached the relevant parts completely with
> headers and everything.

Our kolab server is correctly installed and configured, and this e-mail work 
fine with Mdk 9.2 client, Aethera (windows version), The Horde and with 
OutLook+Bynari connector. I do not report raw e-mail but only how other linux 
clients show to the users...



> > Now, I don't know if kontact is misconfigured, or if it has no kolab
> > support built in it:
>
> Did you configure the resources in Kcontrol and activated groupware
> and KMail and KOrganizer for Kontact?

Yes, I do: I think there was no kolab support in sources...


> >  I get kde source from
> > 	ftp://ftp.kde.org/pub/kde/stable/3.2.3/src
> > are there another source?
>
> Currently clients for Kolab2 are only in KDE CVS head.
> Some of them are alpha quality, but usable for initial testing.

I like kolab, but I think this is a *BIG* limit for his adoption: especially 
for corporate users, individual building from source is simply *NOT* a chance 
for every sysadm.
All sysadms are very, *VERY* lazy, they do not like tarballs, they only want 
to put something like "apt-get update && aptget -u upgrade" in crontab...
And last but not least, with more than 10 workstation tarballs are not a 
chance.


Can you give me the correct checkout procedure for KDE 3.2.3 kdepim? All 
instructions on http://kroupware.org/howto-kolab-kde-client.html seems to be 
KDE 3.1 specific...



-- 
Luca Villani                Wireless Solutions spa - DADA group
NOC manager                 Europe HQ, via Castiglione 25 Bologna
http://www.wseurope.com     Tel: +39 051 2966826    Fax: +39 051 2966800
GPG public key available    Mobile: +39 348 5298542 UIN: 76272621