Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

NetworkTimeoutError after 115.13.0

  • 1 reply
  • 0 have this problem
  • 61 views
  • Last reply by 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

Chosen solution

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.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

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.

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.