>This is a popular question but I really dont like any of the awnsers...
>
>I'm looking for an ActiveX that is a Simple MAPI client (SMC). I don't want to use the MAPI OLE that I can use in VFP6 because it is not a SMC, but an interface to a SMC like Outlook or Exchange. Using these for almost a year now I have determined that these are crap (trust me). Is Mabry what I'm looking for?
>
>I almost started to create my own from what I read in the MSDN disks that came with studio about SDK and all the messaging stuff there, but knowing nothing about VB or C++, I decided I was in over my head. Why can't you do this type of stuff with VFP? Is one of those limitations due to the nature of VFP that it will never be lifted?
>
>Also, is MS Exchange the only way to send utilize the MSMail service (non-InternetMail, sends through a local postoffice)? I would like this functionality.

I Mike,

I'm trying to use Mabry.
Mabry is a Native Mail OCX.
With it you can send and receive mail through SMTP and POP3 servers.
You have to build entirely your Client to use it.
The functionalities don't include means to save and keep anythig like inbox or sent items folders. you have to build it from scratch.
Anyhow it seems a very good control.
Regardind to your question, the client that you build with Mabry can't become a Simple MAPI Client.
This means that any Simple MAPI Client is used to send Mail when you use the MSMAPI32.OCX or any other OCX that talks to MAPI.

If you have Outlook Express 5 configured as your SMC, thats what your MSMAPI32.OCS is going to use. If in another computer (running the same EXE maybe) has Outlook 97 as SMC, than your MSMAPI32.OCS is going to use Outlook 97 in that machine.

With Mabry, all the work is done by the Mabry OCX independently of what SMC is installed in your computer.

I hope I have helped.