Is live.co.uk using POP on a mail host out of order or discontinued.

hi

thanks for your reply i did follow your previous posts and have just cleared my DNS cache, after finding out how to do it. like you i am not very computer literate. i thought i had sorted it after i had reloaded windows live mail but i did get one message come through but now i've got the dreaded message

Unable to send or receive messages for the Msn (*****) account. Header download for the 'Archive' folder did not complete. Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity.

Server Response: Your IMAP command could not be sent to the server, due to non-network errors. This could, for example, indicate a lack of memory on your system.

Server: 'imap-mail.outlook.com'

Windows Live Mail Error ID: 0x800CCC0E

Protocol: IMAP

Port: 993

Secure(SSL): Yes

you'll notice i'm using imap as when i try to use pop it doesn't do anything.

yes i am WLM and also windows 7, i just can't get on with later versions of windows. i use windows live and i've just deleted it and installed another copy from the net but no different. i will have to look through the net because i only have one email(msn) and although i can access it directly from the msn webpage i prefer to have it on live. i used to have a fsnet email as well but that was finished a few years ago.

i will have a search on the net as it's beginning to annoy me only getting it connecting every 8 or 9 times of trying.like you this problem only started a couple of days ago. i have my automatic update disabled so it can't be anything from microsoft causing problems. mind you they have stopped support, as you know.

will look through your posts tomorrow and see if i can pick up anymore.

thankyou again.

My email account is a live.co.uk address. Yours seems to be an MSN email account. I am in UK, are you ? Whether live and MSN use the same server I don't know but I suspect they might, so it could be a server problem. At the moment I only connect about every 1 in 8 attempts. I too can pick up in webmail.

I wonder whether there is a time issue connecting to/from server. I have Server timeout set to 1 minute (just as I do for my other 5 email accounts with gmail, aol and btinternet). I tried increasing to 1min 30 but still had the same problem. Still only connects about 1 in 8 times. I have to keep closing WLM 2012 and restarting it.

I don't use IMAP and I don't use Windows Live.

I wish someone with technical knowledge would pick up this thread and help us out. This issue is so frustrating.

I hope you achieve success.

I've got quite a bit of technical knowledge, but I'm suffering this same problem too! It seems to be specific to Windows 7.

Once you've made the manual registry change I advised, your Windows 7 machine will then cope with the new protocol that now substitutes for SSL.

The 'trick' then is to change the imap - or POP - server address. If you don't connect on the original one, try substituting the new one then restart Windows Live Mail.

Today I'm getting a connection on IMAP using the original addresses, although yesterday only the new ones would connect!!

I'm currently having to change from the old to the new server address, or vice versa, in order to get connected.

I'm in the UK too. It isn't just live.co.uk that's affected. It seems to be any Microsoft account too. The original addresses for IMAP that I use are -

imap-mail.outlook.com

smtp-mail.outlook.com

Sorry but I don't see any "Once you've made the manual registry change I advised, your Windows 7 machine will then cope with the new protocol that now substitutes for SSL." What registry change do you mean please ?

I'm back to finding I have to close WLM and restart about 8 times before it connects.

I'm beginning to have the impression this is only happening in UK and only to Microsoft accounts using WLM & only on Windows 7. I think it could be related to SSL - but as I have no technical knowledge at all I'm simply guessing. If I happen to be watching as WLM goes through checking my 6 email accounts I can see it run through the other 5 quickly then taking a time to try to connect to live.co.uk then I get the error.

It seems to be related to the dns - but again I have no idea what this is and how it is affecting matters. I had a few days of the system working normally after I cleared the dns cache (Elevated command prompt, ipconfig /flushdns) and registered the dns (Elevated command prompt, ipconfig/registerdns), then it started going wrong again

I'm using POP3.live.com on Port 995 and smtp.live.com on Port 25 They've been working fine for many years now until 9th October 2021.

I have tried changing the server settings to outlook but it made no difference at all

For the last few days I've been getting a WERtmp file created each night but I don't think this is related because it has started being created more recently than this connection issue.

To do this registry edit manually, open the Windows Registry and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols

If the TLS 1.1 and TLS 1.2 subkeys are missing (i.e. if the "Protocols" key only has a single subkey named "SSL 2.0"), you need to create them manually. Here's how to do so:

1. Right-click on "Protocols". Select "New", then "Key". Name the new key "TLS 1.1" (without the inverted commas).
2. Right-click on that new key, then create another key underneath it named "Client" (without the inverted commas).
3. Right-click on the new "Client" key. Select "New", then "DWORD (32bit) Value". Name the new item "DisabledByDefault" (without the inverted commas). By default, its value is zero (which is what you need, so leave it as that).
4. Right-click on "Protocols". Select "New", then "Key". Name the new key "TLS 1.2" (without the inverted commas).
5. Right-click on that new key, then create another key underneath it named "Client" (without the inverted commas).
6. Right-click on the new "Client" key. Select "New", then "DWORD (32bit) Value". Name the new item "DisabledByDefault" (without the inverted commas). By default, its value is zero (which is what you need, so leave it as that).

Here is a link to an image which shows what the fixed registry should now look like:

https://learn-attachment.microsoft.com/api/attachments/20b2fcb9-e29d-4e52-b9fb-1231c5f6968f?platform=QnA