1801668 - Send Message Error - The server responded: Error: timeout exceeded

Status: RESOLVED FIXED

(MailNews Core :: Networking: SMTP, defect, P2)

Description

[Paul Littlefield]

Attachment: Pop Up Window - Send Message Error

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36

Steps to reproduce:

Send message.

Actual results:

At regular intervals, the pop-up window titled "Send Message Error" appears with the attached image content.

Expected results:

There are no messages in the queue or local Outbox, and the SMTP server I use works perfectly. If I send a new message to my other email it sends and arrives at the destination normally. So there appears to be something stuck or wrong with TB. This error window did not appear in 107beta.

Comment 1

[Magnus Melin [:mkmelin]]

I think this would be fallout from bug 136871

Comment 2

[Wayne Mery (:wsmwk)]

Good catch. I've been seeing this. I use send in the background, if that makes a difference.
I didn't find any duplicates https://mzl.la/3TY6Ncm

Comment 3

[Ping Chen [:rnons] (away)]

Can we uplift bug 1766382 comment 17 first? I think it will fix 90% of the problem, I will make a patch to fix the remaining 10%.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to Ping Chen (:rnons) from comment #3)

Can we uplift bug 1766382 comment 17 first? I think it will fix 90% of the problem, I will make a patch to fix the remaining 10%.

Uplift approved.

So that patch does more than just apply a potential increase in the TCP timeout?
And if that is the case, does it fix other previously user reported problems?

Comment 5

[Ping Chen [:rnons] (away)]

Before bug 1766382, there was no explicit timeout in SmtpClient, so it depended on the system socket timeout. After 1766382, TCPSocket.cpp should notify SmtpClient after being inactive for mailnews.tcptimeout seconds.

And if that is the case, does it fix other previously user reported problems?

Not sure which problems you mean.

Comment 6

[Wayne Mery (:wsmwk)]

Before bug 1766382, there was no explicit timeout in SmtpClient, so it depended on the system socket timeout. After 1766382, TCPSocket.cpp should notify SmtpClient after being inactive for mailnews.tcptimeout seconds.

That's the impression I had, and so ...

Not sure which problems you mean.

I'll try a different question - so with Bug 136871 - reuse server connection, especially for slow or overloaded network - there is possibility of using a connection that has exceeded or is near its timeout? And bug 1766382 resolves that issue?

Comment 7

[Ping Chen [:rnons] (away)]

And bug 1766382 resolves that issue?

90% as I said in comment 3. The other 10% may be a timing issue I guess, a socket is timeout when we are about to reuse a connection. I will make a patch to reconnect immediately instead of showing error.

Comment 8

[Daron Brewood]

Any news on this being fixed guys as I'm seeing it now since I've upgraded to Supernova? I never had it with the old release version. I've uninstalled TB and twice re-added the account and nothing seems to help.
I reported it twice (in error) as bug reports 1843696 & 1846531, I get a slightly different error message.
I have tried increasing the SMTP server timeout value to 200 but it doesn't help. Also the error seems to occur even when I have no mail to send out.

Comment 11

[Daron Brewood]

Any news on this being fixed guys as I'm seeing it now since I've upgraded to Supernova? I never had it with the old release version. I've uninstalled TB and twice re-added the account and nothing seems to help.
I reported it twice (in error) as bug reports 1843696 & 1846531, I get a slightly different error message. (I've now closed these bugs out and marked them as duplicates of this bug.
I have tried increasing the SMTP server timeout value to 200 but it doesn't help. Also the error seems to occur even when I have no mail to send out.

Comment 12

[Wayne Mery (:wsmwk)]

(In reply to Ping Chen [:rnons] (away) from comment #7)

And bug 1766382 resolves that issue?

90% as I said in comment 3. The other 10% may be a timing issue I guess, a socket is timeout when we are about to reuse a connection. I will make a patch to reconnect immediately instead of showing error.

I'm not finding a bug created by ping to do this, so it still needs to be done?

Comment 13

[betterbird.project+8]

(In reply to Wayne Mery (:wsmwk) from comment #12)

I'm not finding a bug created by ping to do this, ...

This bug here. He sketched the solution in comment #7, but never got to it. Sounds like Fermat.

Comment 14

[Wayne Mery (:wsmwk)]

https://support.mozilla.org/en-US/questions/1418967

Comment 15

[Abelardo A.M.]

Attachment: Thunderbird-TimeoutError-Debugger-Information.png

I don't know if this information can be useful.

Comment 17

[Magnus Melin [:mkmelin]]

I doesn't seem this would be Thunderbird's fault, given the smtp 421 error code. It is odd that that shows up though as the server has already said it accepted the mail.
Doesn't seem like there has been a lot of reports about issues either, so may just be some fluke...

Comment 18

[Daron Brewood]

I see this on a regular basis on macOS, reported it ......

Comment 19

[Magnus Melin [:mkmelin]]

Please attach an smtp log for when it happens, with 115 or later. See https://wiki.mozilla.org/MailNews:Logging

Comment 20

[Abelardo A.M.]

Attachment: SendEmail.txt

Hi,
I have activated the logging system for SMTP and it shows the same as the image I attached. I forward this information again in TXT. It happens to me almost every time I send an email.
Indicate that the email is sent. It is stored in the sent folder and it is after 20-30 seconds that it shows the error message.

Console Error:
[ImapModuleLoader] Using nsImapService.cpp
console.log: Calendar: [CalTimezoneService] Timezones version 2023c loaded
console.debug: Calendar:
[CalMetronome] Scheduling one-off event in 56295ms
console.log: Calendar: Start loading of locale dependent preference default values...
console.log: Calendar: Loading of locale sensitive preference default values completed.
console.warn: services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource.
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource:///modules/AddrBookManager.jsm, line 271: NS_ERROR_FAILURE: No directory for uri=moz-abldapdirectory://ldap_2.servers.DOMINIOLOCAL
JavaScript error: resource:///modules/AddrBookManager.jsm, line 271: NS_ERROR_FAILURE: No directory for uri=moz-abldapdirectory://ldap_2.servers.DOMINIOLOCAL
JavaScript error: resource://gre/modules/LoginManagerChild.sys.mjs, line 149: NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup]
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
JavaScript error: resource://gre/modules/crypto-SDR.sys.mjs, line 199: NS_ERROR_FAILURE: Couldn't decrypt string
console.debug: Calendar:
[CalMetronome] Starting repeating events
JavaScript error: , line 0: NS_ERROR_UNEXPECTED

Thanks you.

Comment 21

[Abelardo A.M.]

I use 115.2.0 version.

Comment 22

[Magnus Melin [:mkmelin]]

Attachment: Bug 1801668 - Avoid "Send Message Error" during idle. r=babolivier

We were logging out of order at one place, which made the logs difficult to understand.
The issue discovered was that now that we reuse connections, the connection to the server
is left open after send. After the send was successful, if the server decides it wants
us to disconnect and sends us 421, that was erroneously interpreted as a send failure.

Also did a bit of modernization.

Comment 23

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/fd461cee4898
Avoid "Send Message Error" during idle. r=babolivier

Comment 24

[Wayne Mery (:wsmwk)]

Good for beta?

Comment 25

[Magnus Melin [:mkmelin]]

Comment on attachment 9351742 [details]
Bug 1801668 - Avoid "Send Message Error" during idle. r=babolivier

[Approval Request Comment]
Regression caused by (bug #): bug 136871
User impact if declined: "send error" messages can be shown when they should not
Testing completed (on c-c, etc.): c-c
Risk to taking this patch (and alternatives if risky): safe

Comment 26

[Wayne Mery (:wsmwk)]

Comment on attachment 9351742 [details]
Bug 1801668 - Avoid "Send Message Error" during idle. r=babolivier

[Triage Comment]
Approved for beta

Comment 27

[Daniel Darnell [:dandarnell]]

Thunderbird 118.0b3:
https://hg.mozilla.org/releases/comm-beta/rev/7f3267c16ec5

Comment 28

[Wayne Mery (:wsmwk)]

Comment on attachment 9351742 [details]
Bug 1801668 - Avoid "Send Message Error" during idle. r=babolivier

[Triage Comment]
Approved for esr115

Comment 29

[Daniel Darnell [:dandarnell]]

Thunderbird 115.2.3:
https://hg.mozilla.org/releases/comm-esr115/rev/86ed70b96a25

Comment 30

[[e-mail]]

https://hg.mozilla.org/releases/comm-esr115/rev/86ed70b96a25

This broke my class that derives from MessageSend because QueryInterface is now a direct property of the object rather than being on the prototype. Is there really no better way of doing this with ES6 classes? It seems to be a bit of a backward step.

Comment 31

[Magnus Melin [:mkmelin]]

Hard to say without context. Can't the derived class override the QueryInterface property of MessageSend to be what it needs, if it needs to be something else?

Comment 32

[[e-mail]]

(It turns out that we don't actually need to override QueryInterface. And I've since noticed on MDN that this is a common pattern. It still seems to be a bit of an antipattern to me though, e.g. super won't work on functions defined like this.)