Re: [Mingw-users] Complete MAPI.h?

[John F. <jo...@ti...>]

Yes, actually I got discouraged from using MAPI a while after putting
together the include file from a combination of factors, among them this
lack of clear standards. It worked OK when I started out just with
Netscape, but I think I remember tring it with MS IE and had similar
problems. I ended up just learning how to use winsock and talk to my email
server with SMTP directly, bypassing MAPI completely.

John

Danny Smith wrote:
> 
>  --- Jeanine Kwong <jea...@sc...> wrote: > John,
> >
> > The files are very helpful!  Thanks a lot.
> >
> > One problem still leaves me in confusion. If I use dlltool command to
> > create a library using the Netscape implementation of MAPI32.dll,
> > machines using Microsoft Outlook as the default e-mail client may
> > complain.  Now if I use the Outlook implementation of MAPI32.dll and run
> > it on a machine with Netscape Messenger as its default e-mail client,
> > the program will crash!  Is there a particular version of MAPI32.dll
> > that is relatively robust?
> >
> > Thanks,
> > Jeanine
> >
> The most robust way, would be to avoid import libs and use explicit
> loadtime imports using LoadLibrary/GetProcAddress.  I'm not sure that will
> solve the problem, but at least the app can fail gracefully if it can't
> find the correct export.
> 
> MS recommendation when Outlook reports a missing export is to rename or
> delete the "corrupt" version of mapi32.dll and use "their" version instead.
> 
> Hmmm.
> 
> I think the NetScape "solution" is to disable the option to use netscape
> Messenger from MAPI-based applications
> see: http://help.netscape.com/kb/consumer/19971014-39.html
> Danny