When invoking Outlook's Automation interface, you need to invoke the VBScript from my previous message twice per email - once whenever you invoke Outlook.Application's CreateItem method to create a MailItem, and then again when you invoke the MailItem's Send method. The FAQ entry has been updated to include this information.

I'm thinking about releasing a compiled .Net monitor to bypass the script; it will absolutely require (1) the .Net runtime environment and (2) Outlook 2000 or Outlook XP/2002. Using the monitor will require that the user be granted specific system privileges, and at this point, since the security object model isn't fully supported under Win9x, I doubt very much it will be supported under Win9x.

It is possible to code the delay-based keystroke direction in VC++ or VB6 as an out-of-proc server or standalone executable; I've done so, but from my POV, there's no advantage to doing so, since it adds to the installation file set - at a minimum, the compiled executable or COM object and selected runtime components, which I find more obtrusive than a little WSH script I can create on the fly if I don't want it left lying about.