AW: [Kroupware] Is Kolab Exchange structure compatible

[Tassilo Erlewein]

Thorsten,

after reading your email I think that such a tight integration with
exchange is beyond the scope of the Kolab project.

The main thing is, we don't want to re-implement mapi.
Re-*ing mapi has been _tried_ several times.
kolab bases exclusively on open protocols and standards;=20
a requirement that mapi surely doesn't fit.=20

- there is no free/oss implementation of mapi.
- we have no means to assure it's scalability
- it raises security concerns

But the scenario you describe is nevertheless interesting.

My approach would be to analyze what the really important
use cases are and how we can achieve them otherwise.

Exchange has for example a webinterface (owa) that is
widely used by other 3rd party software projects and could
be interesting with that regard.

Cheers

Tassilo


Am Montag, 28. Oktober 2002 07:33 schrieb M=FCller, Thorsten:
> Hi Tassilo,
> thanks for your interest.
> A site connector is a tool build in Microsoft Exchange Server.
> Think about the following szenario:
>
> A big company with several locations.
> Now every location has an exchange server with mailboxes and maillists.
> If one person is connected to the exchange in Hamburg and one is connec=
ted
> to the
> exchange in Munich the guy in Munich wouldn't be able to open the calen=
dar
> from the guy in Hamburg and reverse, because these objects are located =
on
> two different exchange servers.
> But if these are connected with an SiteConnector every exchange can ope=
n
> objects
> which are located on a different exchange server.
>
> Exchange Servers are very public in big companies and constructing Kola=
b
> Server with a possibility to connect into an existing Exchange Site wou=
ld
> make it more interesting for companies with existing exchange structure=
s.
>
> Company example.com
>
>
>   Location 1: hamburg.example.com (exchange server)
>
>
>   Location 2: munich.example.com (kolab server)
>
>
>   Location 3: rom.example.com (exchange server)
>
> All locations would be a part of the whole company exchange structure
> (no matter if it's an exchange or kolab server).
>
> In my opinion this would help Kolab for a better acceptance in big
> companies,
> because companies will not through away there complete exchange mail
> solutions
> because of this project.
>
> Hope you could understand what i mean.
> Sorry for my bad english.
>
> Regards
> Thorsten
>
> >Thorsten,
> >
> >Andreas does not speak for the project participants.
> >Please explain in more detail what you're aiming at.
> >I'm not familiar with siteconnector.
> >
> >Tassilo
> >
> >--
> >Dipl.-Ing. Tassilo Erlewein
> >
> >e r f r a k o n
> >Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
> >Germanenstra=DFe 15, 70563 Stuttgart, Germany
> >mobil: 0160 4442541
> >fax: 0160 13 4442541
> >email: tassilo.erlewein@erfrakon.de
> >
> >
> >_______________________________________________
> >Kroupware mailing list
> >Kroupware@mail.kde.org
> >http://mail.kde.org/mailman/listinfo/kroupware
>
> _______________________________________________
> Kroupware mailing list
> Kroupware@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kroupware

--=20
Dipl.-Ing. Tassilo Erlewein

e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Germanenstra=DFe 15, 70563 Stuttgart, Germany
mobil: 0160 4442541
fax: 0160 13 4442541
email: tassilo.erlewein@erfrakon.de