We can't send SMTP mail from within SurferScript. Both 
the 
TEDECLARE MAILPROFILE and the TEMAIL and TERECIPIENT tags 
look correct. As it seems, the value of the USERID 
parameter does not get copied on to the FROM address. Here 
follow the TEDECLARE MAILPROFILE and TEMAIL tags:

<TEDECLARE MAILPROFILE 
Name="Alex"
Service="SMTP"
userid="alex <pippo@bancodisicilia.it>"
SMTPServer="127.0.0.1">

<TEMAIL SUBJECT="ScreensurferState" Profile="Alex">
  <TERECIPIENT Address="pippo@bancodisicilia.it" Type="TO">
  <TESHOW "Hello">
</TEMAIL>

When we run the script and try to send mail, an error row 
is added to the Event log and a "MailFailure" file is added 
to the Event folder, whose contents are:

DURING: Opening Smtp Connection to "127.0.0.1" INFO: EMPTY 
email address.-- Third and Final try: saving mail item in 
Events directory SER
 

Please add a LOGFILENAME attribute to your mail profile, 
with a file name fully described, such as:

<TEDECLARE MAILPROFILE 
               Name="Alex"
               Service="SMTP"
               userid="alex <pippo@bancodisicilia.it>"
               SMTPServer="127.0.0.1"
               LOGFILENAME="c:\smtpmail.log">

Then, run your test, and send the smtpmail.log file to 
surfer@ie.com, referencing Ticket #513 in the subject...(you 
can also look at the log yourself--maybe you will see 
something too...).

We just added a LOGFILE (not LOGFILENAME) attribute to the 
mail profile and tried again, but the file we specified was 
not created.

Sorry, LOGFILE was correct--we tested successfully against 
our e-mail server using your exact code but with changed 
e-mail target.

One thing we noticed was that the e-mail profile doesn't 
update very well just from a compile--can you please try 
shutting-down Screensurfer in-between changing the e-mail 
profile, then re-test.

Hopefully then you will get something in the log file...

You can also try pointing to "mail.amazonweb.com" for the 
e-mail server--you should get a relaying not allowed message 
from that, but at least it will be different.

When we restarted Screensurfer, our code finally worked. 

Yet we found another problem. We stopped the SMTP server 
and have Screensurfer try to send a mail message. That 
confused Screensurfer in such a way that it wasn't able to 
send mail even after the SMTP server was restarted. We had 
to restart ScrenSurfer to have the mail feature work again. 

We are able to provide some information. What we see is 
that the SMTP client successfully opens a socket with the 
SMTP server, after the server is restarted, but as soon as 
the server sends the "220" greeting, the client closes the 
socket, as if it weren't expecting that string.

Good to hear it is working in the optimal environment.  We 
will investigate what is required to improve reliability 
when the SMTP server drops off line and comes back up.

Sorry for the long delay--we have fixed the SMTP support so 
that if the server drops off line, then comes back-up, 
Screensurfer will start working again.

While the SMTP server is down, the e-mails that are 
attempted to be sent will be logged into the 
\screensurfer\hostserver\events directory with original 
from, to and so on in a file 
MailFailure_yyyy-mm-dd-hhmmss.html (which until now would 
just keep happening if the SMTP server only goes down for 
one second).

This is incorporated into build 2.0.9Z, available at:

ftp://www.screensurfer.com/T2_0_9Z.zip

Thank you