>oCDO=CREATEOBJECT('CDO.Message')
>>cServer = oCDO.Configuration.Fields(15).UnderlyingValue && User's smtp
>>cSender = oCDO.Configuration.Fields(13).UnderlyingValue    && User's email
>>cRecipient = "myemailaddress@.....", cSender &&(me and the user get a copy)

>Assuming it worked. You're sending back an activation key? What prevents them from copying n times on different boxes with the same key. Or if you're not sending back but generated and sent to you, they simply do not set 'outgoing' email server.

THanks Cetin - it didi work on my home-office box - which will be like most of the anticipated target users. CDO is only being used to get the smtp server and the user's email account. I also plan to use the smtp prg to send error reports back to my email account. I can send you my working version - it is only about 6KB.

It may be different on an enterprise desktop (an office computer)

I used the winsock DLL function portion of the SendMail sample - it is really trimmed down from the published version.There is an alternative way for the user to get an activation key (an encrypted key is on the about screen, and the user can "hand" email that to me, and I would "decrypt" it an return the "real" activation key.

If the users do not install through the installer - and attempt to run with a "copied" version (unlikely - the user base is not that sophisticated), a file that can only be created by the installer will not be present and they will be locked out! Should they uninstall, and then download anothe eval copy, a reminant of the original install will also be present - and lock them out.

I think wipstuff uses the same declarations as the winsock dll version of SendMail.prg. I am just using CDO to get the server and email information.