Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

NetworkTimeoutError after 115.13.0

  • 1 odgovor
  • 0 ima to težavo
  • 126 ogledov
  • Zadnji odgovor od sjf8
  • Rešeno

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

Izbrana rešitev

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.

Preberite ta odgovor v kontekstu 👍 0

Vsi odgovori (1)

Izbrana rešitev

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.