C++/VB - Simple MAPI deprecated?

Asked By Davide Angeli

19-Nov-09 10:05 AM

Hi to everybody.

I saw that "simple MAPI" API may be removed from future releases of
Windows. There is a reason? There will be a substitute?

Now I use simple MAPI to send mail from my software through the
default mail client. My customers use MS Outlook, Outlook Express,
Windows Mail, Eudora, Thunderbird and all of these now are working
fine with simple MAPI (for MS Outlook i'm already using extended MAPI
but it is the only one that support it).

In the future, I will have to consider only MS Outlook with extended
MAPI and cut off the compatibility with the other mail clients?

Thanks in advance

Davide Angeli

19-Nov-09 11:32 AM

Simple MAPI implementation is provider by the corresponding mail client
(e.g. Eudora) and has nothing to do withWindows, or Microsoft for that
matter.

--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy  - Outlook, CDO
and MAPI Developer Tool
-

19-Nov-09 05:52 PM

Ok, but simple MAPI are Windows API and as you can see on
http://msdn.microsoft.com/en-us/library/dd296734%28VS.85%29.aspx all
Simple MAPI functions have been given the "Deprecated" status. I
suppose that in future Windows versions this kind of routines will not
be supported so even if a mail client still implements it if Windows
will not use it they will became uneseful.

19-Nov-09 01:31 PM

The way Simple MAPI works is that each mail client installs its own version
of the mapi32.dll, which implements the 12 Simple MAPI functions.

--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy  - Outlook, CDO
and MAPI Developer Tool
-

Ok, but simple MAPI are Windows API and as you can see on
http://msdn.microsoft.com/en-us/library/dd296734%28VS.85%29.aspx all
Simple MAPI functions have been given the "Deprecated" status. I
suppose that in future Windows versions this kind of routines will not
be supported so even if a mail client still implements it if Windows
will not use it they will became uneseful.

20-Nov-09 08:09 AM

on

Maybe I am a little bit confused, please help me :  now in my software
I am loading mapi32.dll from 'windows\system32' folder and I suppose
that this is the Microsoft wrapper standard wrapper to simple MAPI for
the default mail client, is it wrong? For example if I am using
Thunderbird the real file is C:\Program Files\Mozilla Thunderbird
\mozMapi32_InUse.dll but I do not care where this file is because I
know that mapi32.dll in windows\system32 directory do the job for me.
My question is : in feature Windows versions, Microsoft will delete
windows\system32\mapi32.dll file and so it will be necessary to load
directly the client own version of the mapi32.dll?

Thanks

osoft.com/en-us/library/dd296734%28VS.85%29.aspxall

22-Nov-09 10:29 AM

The way it used to work, mapi32.dll in the System32 folder got replaced.
Well behaved mail clients however leave mapi32.dll in System32 alone and
simply create a registry key that redirect calls to their dll that
implements Simple MAPI.
I very much doubt MS will break that. They might stop supporting Simple MAPi
in their own products (Windows Mail, Outlook, etc), but I do not see that
happening either.

--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy  - Outlook, CDO
and MAPI Developer Tool
-

Maybe I am a little bit confused, please help me :  now in my software
I am loading mapi32.dll from 'windows\system32' folder and I suppose
that this is the Microsoft wrapper standard wrapper to simple MAPI for
the default mail client, is it wrong? For example if I am using
Thunderbird the real file is C:\Program Files\Mozilla Thunderbird
\mozMapi32_InUse.dll but I do not care where this file is because I
know that mapi32.dll in windows\system32 directory do the job for me.
My question is : in feature Windows versions, Microsoft will delete
windows\system32\mapi32.dll file and so it will be necessary to load
directly the client own version of the mapi32.dll?

Thanks

23-Nov-09 12:57 PM

APi

Thank you very much, now is all clear for me.

Davide Angeli

nt
t
..
PI
d