[Kroupware] Kroupware replacing Exchange

[Ivaylo Toshev]

На ср, 2003-02-05 в 12:00, Tassilo Erlewein записа:

> The KDE client AFAIK does not yet support IMAP shared folders.
> Support for shared folders is not part of the existing contract.
> 
Maybe i am wrong but native Kmail supports Shared(Public) Folders, so
what is the problem KDE Kolab Client not to support them ?
	And if there will not be Shared Folder support, and there will not be
support for Shared Calendars, Tasks etc. , then i cannot see the point
!?!
	 I am now using Evolution, which has all of this things (PERSONAL Only
Calendar,tasks, etc.) like client, but have not Server part which
support them and cannot write contacts,calendars and tasks on IMAP
server but just locally on hard-disk
	Now you Build Server which can do these things, but the Kolab Client
will use IMAP to store (JUST PER USER PERSONAL ONLY) tasks, calendar and
contacts on IMAP server, but cannot use such things on shared IMAP
Folders. 
	So where is difference in using Evolution or Kolab ? 
	Just that with Kolab your own Calendars, Tasks... are on IMAP server
and not locally ?! 
	But with both of them the only way to "share" Calendars, Tasks and
others is to "invite users" and to use SMTP for transport layer (as
regular e-mails).
	I am using notebook and i don't care if my PERSONAL (because there is
no SHARED no in Kolab, nor in Evo) calendar, tasks etc. are on my hard
disk or on IMAP (i prefer hard-disk in that situation, because it is
faster ).
	Why every efforts in Open-Source World to build Groupware Solutions
blow over with user expectations ? I know that this is hard to do and to
be free ! But as was said here, most of the things exist in "raw" format
as features and maybe it is not so easy to be cooked ;-)

Keep the good work.


> Outlook can at this time communicate with the Kolab server via
> the Bynari Connector Plugin. It's a commercial product beyond our 
> reach. Bynari, Inc. sells and supports it (www.bynari.net).
> Please contact me personally if you are interested in our
> experiences during testing.
> 
> There are several projects on the way to provide further support for 
> Outlook. Namely, effords are going towards a so-called MAPI storage provider.
> That could be a thing that talks MAPI to outlook and IMAP over
> the network to Kolab. At the same time it converts the proprietary
> TNEF encoding to the open format we use within Kolab (VCAL, VCARD, 
> Multi-Part-MIME). So the server is open source and the email format
> on the server would be standard-conformant.
> 
> >  I would like to know if it is a "philosophical" target to build a 
> > OSS-replacement for Exchange.
> 
> We are formally contracted to build an Open Source Groupware Solution. 
> The focus lies on the KDE client. For some time Outlook shall be usable 
> with the server via additional software. 
> 
> It is important to understand that we are not contracted to replace
> Exchange. We also emphasize that we do _not_ rebuild Exchange 
> to run on the Linux platform.
> All components of our solution are existing, proven open source projects
> which we integrate to form Kolab. No effords are made to somehow
> rebuild MAPI etc. Only standardized, open protocols with open source 
> implementations available are used to communicate with the Kolab 
> groupware server. 
> 
> We are however aware that Outlook is a very good Windows Groupware 
> client and are concerned about supporting it. Right now that is done via
> the Bynari plugin. Later that year alternatives may exist.
> 
> Tassilo
> _______________________________________________
> Kroupware mailing list
> Kroupware@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kroupware