>MAPI -
>Allows user to alter message or recipients prior to pushing 'send'. On completion puts message in 'sent messages' folder.
>
>Direct SMTP -
>Easier to set up on client computer.
>
>Is this the jist of it?

Roughly that's correct yes...

I don't think the MAPI control actually uses MAPI any longer, because
it now works on machines that don't have MAPI installed. Really
MAPI just is a higher level interface to different mailing systems,
so eventually the MAPI interface talks SMTP to a mail server as
well. As such pure SMTP access is going to be faster and overall
more lean on resources. If you use MAPI you're using an ActiveX
control that must be installed and accessible on a client. With
pure SMTP access you may or may not need an ActiveX control.
wwIPStuff doesn't use ActiveX, but does require a support DLL
to handle the SMTP access.

>Allows user to alter message or recipients prior to pushing 'send'. On completion puts message in 'sent messages' folder.

That depends on whether MAPI is actually installed on the machine
and whether the mail client you're using is using Windows
Messaging Services. If you use Outlook with the Enterprise
options and Exchange server that may be the case, but isn't
if you're using Internet Only services.

I don't know what you mena by editing prior to pressing Send.
That's a program issue that can be controlled any way you implement
your email client.