Lineone emails stopped working via Outlook 2019

[Fingers]

I have several lineone.net email accounts via TalkTalk and they all stopped working several days ago via Outlook 2019, although they still work OK via webmail and Samsung smartphone.

I checked Outlook settings and they are as specified by TalkTalk and nothing has been changed, but talktalk.net emails have not been affected and are OK.

I am using a Windows 10 desktop PC. Error message: 0x800CCC0E Cannot connect to server, see error message attached.

What has happened at TalkTalk to cause this problem and how can it be resolved?

[KeithFrench]

Hi @angelique-TT 

You are very welcome.

[angelique-TT]

Good morning. Thank you for the support @KeithFrench 🙂

[KeithFrench]

That is not something that TalkTalk can answer, mine happened to both Outlook and Thunderbird perhaps a Windows issue?

[Fingers]

Thanks, this information from Keith French, has enabled me to cure the problem, all my lineone accounts are now working again.

It appears that somehow the passwords of all my three lineone accounts had disappeared from the incoming IMAP mail settings of Outlook 2019 (note that outgoing SMTP uses same settings as incoming).
This happened mid-afternoon (after 15:00 GMT) on Thursday 17th July, but talktalk accounts in Outlook were not affected, retained their password settings and had continued to work normally.

Is there any reason why this happened and only affected non-talktalk accounts?

[KeithFrench]

Hi @Fingers 

I have been doing more work on this and I am not convinced this is actually a TalkTalk issue. It looks like something has caused the SMTP mail server (outgoing emails) password to be erased in the email client. Putting it back seems to have resolved the issue. For more details, please see my post #20 in this thread of mine:-

https://community.talktalk.co.uk/t5/Email/TalkTalk-net-domain-SMTP-mail-server-not-responsive/m-p/31... 

[KeithFrench]

I have seen similar with my TalkTalk.net address, affecting both Thunderbird and New Outlook for Windows. I have resolved this issue and will finish the details of how I fixed it later today. Will give you a link to it later.