Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

NetworkTimeoutError after 115.13.0

  • 1 odgovor
  • 0 ima ovaj problem
  • 101 prikaz
  • Posljednji odgovor od sjf8

more options

Thunderbird updated to 115.13 today and since then I can't receive mail from outlook.office365.com. (Could just be coincidence). Outgoing mail is OK.

Error Console gives:- 20:49:11.948 pop3.server2.7: SecurityError info: Pop3Client.sys.mjs:422:20

   _onError resource:///modules/Pop3Client.sys.mjs:422

20:52:21.344 pop3.server2.8: NetworkTimeoutError: a Network error occurred Pop3Client.sys.mjs:380:18

   _onError resource:///modules/Pop3Client.sys.mjs:380

I've tried removing the saved passwords and have also tried upgrading to 128.0.1.

I can log into webmail with the password OK, so I'm sure I'm using the correct credentials.

Server Settings are:-

account2 (pop3) outlook.office365.com:995 SSL/TLS OAuth2 smtp.office365.com:587 STARTTLS OAuth2 true

Thunderbird updated to 115.13 today and since then I can't receive mail from outlook.office365.com. (Could just be coincidence). Outgoing mail is OK. Error Console gives:- 20:49:11.948 pop3.server2.7: SecurityError info: Pop3Client.sys.mjs:422:20 _onError resource:///modules/Pop3Client.sys.mjs:422 20:52:21.344 pop3.server2.8: NetworkTimeoutError: a Network error occurred Pop3Client.sys.mjs:380:18 _onError resource:///modules/Pop3Client.sys.mjs:380 I've tried removing the saved passwords and have also tried upgrading to 128.0.1. I can log into webmail with the password OK, so I'm sure I'm using the correct credentials. Server Settings are:- account2 (pop3) outlook.office365.com:995 SSL/TLS OAuth2 smtp.office365.com:587 STARTTLS OAuth2 true

Izabrano rješenje

Has starting working again without any further intervention from me. I can only assume the issue was something at the server end and it's been reset or otherwise unfankled.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (1)

more options

Odabrano rješenje

Has starting working again without any further intervention from me. I can only assume the issue was something at the server end and it's been reset or otherwise unfankled.