MAPI

[Enrico Weigelt]

Hi folks,

i've seen that mapi is currently not implemented. Well, I'd like 
to sit down and code it, but I require several tools for that:

a) mapi documentation (no, I didnt ask google yet ...)
b) a small test application 
c) some shorts words about what I may do and what I may not do 
(i.e. may I call external unix processes ? whats about fork() ?)

cu

[Vizzini]

On Thu, 2004-02-19 at 16:27, Enrico Weigelt wrote:
> i've seen that mapi is currently not implemented. Well, I'd like 
> to sit down and code it, but I require several tools for that:
>
> a) mapi documentation (no, I didnt ask google yet ...)

There is information in the platform sdk and on msdn.microsoft.com,
which mainly documents the programming interface for mapi clients and
servers.  Should be enough to get you seriously started, though.  Some
investigation of your own will probably be necessary, too.
> b) a small test application

There are sample MAPI clients floating around microsoft.com in various
places, as well.  I'd recommend starting there.  There are lots of other
mapi clients on the web, too, but they're probably too complicated to be
really useful during the development phase.
> c) some shorts words about what I may do and what I may not do 
> (i.e. may I call external unix processes ? whats about fork() ?)

I can't speak for wine policies, but we (ReactOS) really like it when
the code is written in a very windows-like way - don't assume you're
running on unix, and it'll make it easier for us to use your work too.

-Vizzini

[Enrico Weigelt]

* Vizzini  [2004-02-19 17:11:35 -0600]:

Hi folks,

<snip>
> There is information in the platform sdk and on msdn.microsoft.com,
> which mainly documents the programming interface for mapi clients and
> servers.  Should be enough to get you seriously started, though.  Some
> investigation of your own will probably be necessary, too.

Okay, I'll have a look at it.

BTW: are the necessary structures already defined somewhere or do I
have to add them ?

<snip>
> > c) some shorts words about what I may do and what I may not do 
> > (i.e. may I call external unix processes ? whats about fork() ?)
>
> I can't speak for wine policies, but we (ReactOS) really like it when
> the code is written in a very windows-like way - don't assume you're
> running on unix, and it'll make it easier for us to use your work too.

hmm, I first wanted to start with a small stub which calls sendmail.

before I'd start implementing the whole framework, I'd better start
writing a cross-platform-mailapi, which could replace things like
libclient+co and be reused in a write range of MUAs (i personally would
start with hacking it into mutt :)). 
this framework could also be ported to ros, and the mapi would just
be a adaptor between its clients and the crossplatform messaging api.

cu

[Dimitrie O. Paun]

On Fri, 20 Feb 2004, Enrico Weigelt wrote:
> BTW: are the necessary structures already defined somewhere or do I
> have to add them ?

There is already a file include/mapi.h, but it will probably need
some work.

[Joerg Mayer]

On Thu, Feb 19, 2004 at 11:27:02PM +0100, Enrico Weigelt wrote:
> i've seen that mapi is currently not implemented. Well, I'd like 
> to sit down and code it, but I require several tools for that:

AFAIK, the network format isn't documented anywhere. Ethereal is trying
to dissect some of it, but there are lots of "This may be wrong.",
"DISSECT_UNKNOWN" and "Unknown string.". In case you want to look at
the network side of it: The code is in packet-dcerpc-mapi.c

Ciao
  Jörg