Re: [Evolution] wish-list (MS-Exchange support != MAPI support)

[Dylan van Iersel <dylan tcw2 ppsw rug nl>]

"Exchange done right"is exactly the phrase I was looking for, but I dont agree
with you that Exchange is a legacy system. Although it is a typical construct
of M$ Corp, it IS currently one of the best groupware solutions that I know of. 
Ofcourse should Evolution be directed to supporting open systems standards, but 
it would be very nice to see it extended with a few interoperability back-ends
for, for example, M$ Exchange, Lotus Notes (anyone using that still?) and
others. That would truly be in the spirit of free software: giving users
back their rights to choose!

:Dylan

On Mon, 22 May 2000, you wrote:
> Personally I think Evolution should end up being 'Exchange done right'.
>
> Which would be an open systems approach; that is, using standard internet
> technologies like imap, ldap, etc to perform the things that Exchange does
> using proprietry protocols.  And we all know that systems that work
> like that are known these days as 'legacy' systems.
>
> Supporting legacy systems like Exchange may be an option, but i 
> wouldn't see it as a primary goal, myself.
>
> But thats really only my own view, I dont know what 'the plan' is.
>
>  Michael
>
> > > -----Original Message-----
> > > From: Dirk-Jan C . Binnema (djcb) [mailto:bulkmail dds nl]
> > > Sent: Sunday, May 21, 2000 12:33 PM
> > > To: Gregory Leblanc
> > > Cc: evolution helixcode com
> > > Subject: Re: [Evolution] wish-list (MS-Exchange support != 
> > > MAPI support)
> > >
> > > On Sun May 21, 2000 at 09:39:21AM -0700, Gregory Leblanc wrote:
> > >
> > > > I think that there's a fair bit of demand for MS Exchange 
> > > MAPI support, but
> > > > I think that the demand for finishing the UI and the 
> > > backends for storing
> > > > local mail are just a wee bit more.  I'd suspect that there 
> > > won't be a lot
> > > > of MAPI work until Evolution gets to be at least useable 
> > > for local mail.  I
> > > > run VMware just so that I can get at my mail through 
> > > Outlook 2000, stored on
> > > > an Exchange server.  
> > > >         Greg
> > >
> > > Actually, MAPI is only one of the APIs MS provides for 
> > > accessing 'the messaging subsystem'. It's not the only one, 
> > > nor is Exchange the only mail server support it. While MAPI 
> > > is the API, the actual 'on-the-wire' format is not MAPI, but 
> > > the result of some exchange-library on your system 
> > > translating MAPI calls into the 'on-the-wire' format and vice versa.
> > >
> > > Unfortunately, while MAPI is documented pretty well, the 
> > > on-the-wire format is not widely available (AFAIK). The 
> > > short-term solution is to convince you sysadmin to install 
> > > IMAP support for Exchange to be able to access it...''
> >
> > That is why I said "MS Exchange MAPI", and not just "MAPI".  However,
> > Evolution is useless with only IMAP support on the Exchange server, as it
> > defeats the purpose of having Exchange.  Exchange is so much more than a
> > mail storage facility, it provides the framework for a "groupware" system.
> > It allows (relatively) easy group callendaring, messaging (email), tracking
> > of both email and other "office" products.  I hate to sound like I'm selling
> > Exchange, since I wouldn't wish that on any administrator, however, it
> > offers the best groupware systemt that I've seen, from the users point of
> > view.  I'll have to see what I can find about the wire format that
> > Outlook/Exchange speak, I haven't looked yet, since Evolution doesn't even
> > have a GUI that works.
> >     Greg
-- 
---
Dylan van Iersel