Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

False Timeout Error Message

  • 4 răspunsuri
  • 1 are această problemă
  • 1 vizualizare
  • Ultimul răspuns de logan5

more options

Due to changes in my Microsoft account, I had to update my outgoing mail server to smtp.office365.com with SMARTTLS. My email works, but I always receive the following error immediately after sending a message:

Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.office365.com timed out. Try again.

This is clearly a false positive, but it's annoying and also doesn't instill confidence when sending important emails.

As some other posts have suggested, I tried increasing the value of mailnews.tcptimeout, but this made no difference, which makes sense since it's not even a real timeout. Again, sending mail works, the error is false.

Due to changes in my Microsoft account, I had to update my outgoing mail server to smtp.office365.com with SMARTTLS. My email works, but I always receive the following error '''immediately''' after sending a message: ''Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.office365.com timed out. Try again.'' This is clearly a false positive, but it's annoying and also doesn't instill confidence when sending important emails. As some other posts have suggested, I tried increasing the value of mailnews.tcptimeout, but this made no difference, which makes sense since it's not even a real timeout. Again, sending mail works, the error is false.

Toate răspunsurile (4)

more options
more options

Thanks, Matt! The log results are as follows:

window.controllers/Controllers is deprecated. Do not use it for UA detection. blank NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194 mailnews.smtp: Sending message <07125a1e-bdfb-f492-3b76-67add8f67eb6@loganbecket.com> SmtpService.jsm:84:18 mailnews.smtp: Connecting to smtp://smtp.office365.com:587 SmtpClient.jsm:121:17 mailnews.smtp: Connected SmtpClient.jsm:387:17 mailnews.smtp: S: 220 BN0PR02CA0044.outlook.office365.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jun 2022 13:13:16 +0000

SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [IPV6:2601:483:4600:8630:3adf:b047:4b6d:fb9e] SmtpClient.jsm:579:19 mailnews.smtp: S: 250-BN0PR02CA0044.outlook.office365.com Hello [2601:483:4600:8630:3adf:b047:4b6d:fb9e]

250-SIZE 157286400

250-PIPELINING

250-DSN

250-ENHANCEDSTATUSCODES

250-STARTTLS

250-8BITMIME

250-BINARYMIME

250-CHUNKING

250 SMTPUTF8

SmtpClient.jsm:413:17 mailnews.smtp: C: STARTTLS SmtpClient.jsm:579:19 mailnews.smtp: S: 220 2.0.0 SMTP server ready

SmtpClient.jsm:413:17 mailnews.smtp: C: EHLO [IPV6:2601:483:4600:8630:3adf:b047:4b6d:fb9e] SmtpClient.jsm:579:19 mailnews.smtp: S: 250-BN0PR02CA0044.outlook.office365.com Hello [2601:483:4600:8630:3adf:b047:4b6d:fb9e]

250-SIZE 157286400

250-PIPELINING

250-DSN

250-ENHANCEDSTATUSCODES

250-AUTH LOGIN XOAUTH2

250-8BITMIME

250-BINARYMIME

250-CHUNKING

250 SMTPUTF8

SmtpClient.jsm:413:17 mailnews.smtp: Possible auth methods: LOGIN SmtpClient.jsm:899:17 mailnews.smtp: Maximum allowed message size: 157286400 SmtpClient.jsm:905:19 mailnews.smtp: Current auth method: LOGIN SmtpClient.jsm:617:17 mailnews.smtp: Authentication via AUTH LOGIN SmtpClient.jsm:625:21 mailnews.smtp: C: AUTH LOGIN SmtpClient.jsm:579:19 mailnews.smtp: S: 334 VXNlcm5hbWU6

SmtpClient.jsm:413:17 mailnews.smtp: AUTH LOGIN USER SmtpClient.jsm:1007:17 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:575:19 mailnews.smtp: S: 334 UGFzc3dvcmQ6

SmtpClient.jsm:413:17 mailnews.smtp: AUTH LOGIN PASS SmtpClient.jsm:1022:17 mailnews.smtp: C: Logging suppressed (it probably contained auth information) SmtpClient.jsm:575:19 mailnews.smtp: S: 235 2.7.0 Authentication successful

SmtpClient.jsm:413:17 mailnews.smtp: Authentication successful. SmtpClient.jsm:1135:17 mailnews.smtp: C: MAIL FROM:<logan@loganbecket.com> BODY=8BITMIME SIZE=451 SmtpClient.jsm:579:19 mailnews.smtp: S: 250 2.1.0 Sender OK

SmtpClient.jsm:413:17 mailnews.smtp: MAIL FROM successful, proceeding with 1 recipients SmtpClient.jsm:1169:17 mailnews.smtp: Adding recipient... SmtpClient.jsm:1174:17 mailnews.smtp: C: RCPT TO:<loganbecket@gmail.com> SmtpClient.jsm:579:19 mailnews.smtp: S: 250 2.1.5 Recipient OK

SmtpClient.jsm:413:17 mailnews.smtp: RCPT TO done, proceeding with payload SmtpClient.jsm:1234:19 mailnews.smtp: C: DATA SmtpClient.jsm:579:19 mailnews.smtp: S: 354 Start mail input; end with <CRLF>.<CRLF>

SmtpClient.jsm:413:17 mailnews.smtp: Sending 451 bytes of payload SmtpClient.jsm:549:17 mailnews.smtp: S: 250 2.0.0 OK <07125a1e-bdfb-f492-3b76-67add8f67eb6@loganbecket.com> [Hostname=MN2PR16MB3118.namprd16.prod.outlook.com]

SmtpClient.jsm:413:17 mailnews.smtp: Message sent successfully. SmtpClient.jsm:1293:21 mailnews.smtp: C: QUIT SmtpClient.jsm:579:19 mailnews.smtp: error { target: TCPSocket, isTrusted: true, name: "NetworkError", message: "Network", errorCode: 2152398868, srcElement: TCPSocket, currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable: false, … } SmtpClient.jsm:434:17 mailnews.send: Sending failed; The message could not be sent because the connection to Outgoing server (SMTP) smtp.office365.com timed out. Try again., exitCode=2153066800, originalMsgURI= MessageSend.jsm:336:27 mailnews.smtp: S: 221 2.0.0 Service closing transmission channel

SmtpClient.jsm:413:17 mailnews.smtp: Closing connection... 3 SmtpClient.jsm:153:17 mailnews.smtp: Socket closed. SmtpClient.jsm:487:17

more options

The reply to email I just read indicates that this is something that is fixed in V102. Could you please try it?

Currently it has to be updated by going to Thunderbird.net and downloading and installing. Updates are still some time away. https://bugzilla.mozilla.org/show_bug.cgi?id=1606047#c26

more options

I'm running Linux and the manual upgrade seems like a bigger risk than the false positive notification, so I'll wait for the official release and let the normal system updates take care of it whenever that time comes. Thank you for the help, Matt!