On Wed, Nov 20, 2013 at 01:12:43PM +0100, edu.bit.es@gmail.com wrote:
Thanks a lot Peter,
Changed the port to 465 but not changed the option "protocol=smtp" because there was a timeout.
Stunnel config file--> stunnelconf.txt
Log file --> stunnel.txt
Hm, now this log file does not show an Stunnel-related problem at all. It seems that Stunnel gets a client connection, connects to smtp.gmail.com, successfully negotiates an SSL session and in the next second reports that the client (the program connecting to Stunnel on your machine) closed the connection, so it closes the other side, too (all the SSL close notification and session shutdown messages).
IMHO, your Stunnel configuration is fine now; if you are seeing problems while using it with some program, it remains to be seen what the program is doing and why the program thinks that there are problems serious enough to close the connection very quickly. What program did you use to test this? Did it report some kind of error? Is there any way to ask it to show you its own log of the session with its own error reporting?
G'luck, Peter