| Newsgroups |
gmane.mail.blat |
| Message-ID |
<[email protected]> |
Thanks Jeroen and Chip!
Two steps further ... Lets see if I ever climb the last step of the
ladder ...
First followed Chip's suggestion of running netstat -ab; I stored the
output in a .txt file, and searched for 127.0.0.1:25.
Success!
So lets now find, identify and terminate once and for all the little
bugger ....
Wait:
TCP 127.0.0.1:25 Zenbook:0 LISTENING
[stunnel.exe]
So, its stunnel that prevents stunnel ???
Anyway, I tried Port 8002 next, with success. Emails are successfully sent!
I then checked the Windows Firewall Gui, and found stunnel in the list
of allowed applications for private Networks.
And running stunnel Gui still gives the same error as before.
So, in less words:
stunnel did not work on Port 26 because the port was blocked by ...
stunnel???
Nevertheless stunnel now works using Port 8002, even though netstat now
shows 127.0.0.1:8002 is in use by stunnel.
And Stunnel Gui start produces the same kind of error independent of the
port, or if the application is working or not ...
Also there seems to be an issue with the Firewall, even though stunnel
has already modified the Firewall rules to allow itself.
Something is telling me I'm still far from a solution ...