Windows Live Mail cannot send, but it receives OK
If you ARE using Windows Live Mail (with IMAP) -
Note - If you are using pop3 instead of IMAP, try the following; but there are additional factors to consider with a pop3 account, so the chances of fixing this fault using the below are greater if your account is IMAP. I'll need to post extra advice if you are using POP3.
All e-mail programs (including Windows Live Mail) use one port to send messages, and a different port to receive them.
An error where you can send but not receive (or the other way round) is a classic sign that you are specifying the wrong port number in the e-mail settings for the service (send or receive) which is not working.
Don't make the mistake of assuming that because you didn't alter the e-mail settings, the port number can't have changed. Corruption can occur from many causes.
These account settings aren't stored in the Windows registry. Each account has a configuration file named "account{GUID}.oeaccount" in the account's sub-folder within the store folder (i.e. a file with the file type .oeaccount).
I've never actually known an .oeaccount file get corrupted, but there's always a first time.
It's an XML file (readable in Notepad), which contains all the account settings. These settings are viewable in the account's Properties: in the left-hand folders pane of Windows Live Mail, right-click on the e-mail account's name (e.g. someone @hotmail.com), then click on "Properties". The settings are found on three of the tabs there: "Servers", "Advanced" and "IMAP".
Check that your settings are correct.
The following settings are what you need with Hotmail.
If you use something other than Hotmail, do a Google search for its settings, but usually EVERYTHING will be the same EXCEPT the server address and port number. Alternatively, the correct settings you need to use will be available on the website of your Email Service Provider.
IMAP Settings (for Hotmail):
Incoming Mail -
Server type: IMAP
Server address: imap-mail.outlook.com (Port: 993)
SSL required: Yes
Authenticate using: Clear text
Logon Username: YourName @hotmail.com { Your details
Outgoing Mail -
Server type: SMTP
Server address: smtp-mail.outlook.com (Port: 25 or 587)
Requires SSL: Yes
Requires Authentication: Yes
POP3 Settings (for Hotmail):
Incoming Mail -
Server type: POP3
Server address: pop-mail.outlook.com (Port: 995)
SSL required: Yes
Logon Username: YourName @hotmail.com { Your details
Outgoing Mail -
Server type: SMTP
Server address: smtp-mail.outlook.com (Port: 25 or 587)
Requires SSL: Yes
Requires Authentication: Yes
An e-mail account with Microsoft can't use POP3 unless the account's settings on Microsoft's website are configure to let devices and apps use POP. You must do this in webmail, i.e. using a web browser; you can't do it in Windows Live Mail.
Alternatively, an SMTP error means that WLM cannot send. This usually means it can receive okay.
An intermittent error in connecting to SMTP suggests that every time you manually correct the problem, an automatic process undoes your corrective action on the next reboot. Or on the process's next auto-update or next scan.
Because there are so many possible causes, none of which have anthing to do with WLM, I can't guess at what program on your computer is really causing this. You may need to post in a Windows 10 forum for advice.
On a practical level, your approach should be to disable one of the processes that may be causing this, and see if the fault then reoccurs. Don't disable a whole bunch of processes: temporarily disable them one at a time, which is the surest means of finding the correct one.
Your main antivirus program has to be the most likely candidate, and is the obvious starting point.
This problem can be caused by enabing the Virtual Private Network (VPN) feature in your anti-virus program. For example, this VPN option is a new feature in McAfee's "Live Safe" anti-virus program. Set VPN to "Off" to be able to send e-mails. If VPN is set to "On", it stops WLM sending e-mails.
Second choice will be any anti-malware program(s) you might be running. Other candidates include any firewall running, such as Windows Defender. Other candidates include any browser plug-ins or add-ons running. Test for these by closing the running program or service in question before starting WLM.