The email related code has not changed at all in months. Yes, you do need to use smtp for your mail server. The specific error information is a little unclear, but it seems like there was a problem either actually reaching your email server, or the remote server closed the connection without responding.
The email related code has not changed at all in months. Yes, you do need to use smtp for your mail server. The specific error information is a little unclear, but it seems like there was a problem either actually reaching your email server, or the remote server closed the connection without responding. This very well be that the port you are trying to reach is unavailable, or it could be that the remote server is rejecting your sign-int (user name/password) and is closing the connection. With respect to the user name/password issue, I've found (and other people have agreed) that you should make sure your user name includes your domain (
you@xyzd.com).
Another thing to try would be using a different email client to reach your server using an identical set of parameters (user name, password, port and "SSL". However, note that in my case Outlook won't accept my user name with the @ in it while On Guard requires it.
I don't know exactly how "universal" the functionality provided by the support library from Microsoft is in reaching
every potential type of email server. I would expect it to be, but am not certain. It is possible that your email server will have different ports or a different address for SMTP than for other email protocols.
The other issue to consider is your anti-virus software. You could try turning that off for 15 minutes or so and giving it another try. If that works then you'd need to make sure that your anti-virus is configured to white list On Guard.
Please let me know what you find out.