Endless error prompts with send OUTBOX, when SMTP server is blocking + message copied to Sent even if not sent
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
People
(Reporter: Ulf.Zibis, Unassigned)
References
Details
Attachments
(1 file)
|
21.80 KB,
image/png
|
Details |
Blocking SMTP server.png
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
Steps to reproduce:
I had about 300 messages to send in OUTBOX and requested "Send all messages in OUTBOX".
Actual results:
- After a few messages send, I repeatedly got hundreds of the attached error message.
- The first not send message was copied to the IMAP Sent folder, even it was not really send.
Expected results:
- There should be a "Cancel" button.
- Don't copy messages to Sent folder in case of send fail.
Additional problems occur, if addons like "MailMerge" or "Send Later" are involved. They stop working, if this error message occurs.
If the error dialogue is acknowledged quickly, the addon hangs and must be killed. If the user waits for a few minutes, the addon continues working, but copies the not-send message(s) to the Sent folder, so later the user can't know, which message was really sent. The reason for this effect maybe is a timeout in the SMTP connection.
So a solution is needed, to report all not sent messages including the received error reports from the SMTP server. Maybe the standard error stream would be a good place for this.
|
||
Comment 2•4 years ago
|
||
I was able to reproduce a part of the problem:
If you send a message, e.g. using the toolbar button "Send" in the message compose window, and there is an error while sending the mail, then an alert error dialog is shown, e.g.:
An error occurred while sending mail. The mail server responded:
Requested action not taken: domain does not accept mail
Recipient address has null MX.
Please check the message recipient "info@example.com" and try again.
The user has to click "OK" in the alert error dialog, in order to gracefully return to the message compose window.
However, if the user waits long enough, before he actually clicks "OK" in the alert error dialog, then a TCP timeout will have occurred in the background. The timeout is controlled globally via "mailnews.tcptimeout". The default value is "100" seconds.
In this case, i.e. the user waited long enough for the timeout to occur, then the message compose window is closed automatically and a copy of the message is saved in the "Sent" folder of the current account.
For the user everything looks like the message has been sent successfully! However, the message is not actually sent at all!
|
|
||
Comment 3•4 years ago
|
||
The problem can also be triggered via "File -> Send Later" in the message compose window.
In this case the message is saved in the "Outbox". Once the user clicks "File -> Send Unsent Messages" in the main window of Thunderbird, then the alert error dialog is shown.
Again, if the user waits long enough for the timeout to occur and then clicks "OK", then the message is also copied to the "Sent" folder anyway - although the message is not actually sent at all!
|
|
||
Comment 4•4 years ago
|
||
To trigger this bug more easily, I used a GMX email account, which (fortunately) throws an error when you add "info@example.com" in the To field.
I also set "mailnews.tcptimeout" to "15", in order not having to wait for too long for the timeout to happen. (Thunderbird needs a restart for the change to take effect.)
I created a new message with a few valid email addresses of my own in the To field, followed by "info@example.com", followed by another valid email address of my own. Then I clicked the toolbar button "Send". The alert error dialog was shown. I waited about 20 seconds for the TCP timeout to occur in the background. Then I clicked "OK" in the alert error dialog.
The message compose window was closed automatically and a copy of the message was saved in the "Sent" folder. However, none of my own email addresses in the To field received the sent email in their Inbox. (The message was definitely not sent at all.)
Tested with Thunderbird 68.11.0 (64bit) and Thunderbird 78.2.0 Build 1 (64bit) on Windows 10 (64bit).
(In reply to Alexander Bergmann from comment #4)
Great additional findings Alexander. Please leave a vote.
(In reply to Wayne Mery (:wsmwk) from comment #6)
Are you also seeing this with version 78?
I can not test, as on Ubuntu there still is only version 68.
Do you know, when TB 78 is ready for Ubuntu?
|
||
Comment 8•4 years ago
|
||
(In reply to Ulf Zibis from comment #7)
(In reply to Wayne Mery (:wsmwk) from comment #6)
Are you also seeing this with version 78?
I can not test, as on Ubuntu there still is only version 68.
Do you know, when TB 78 is ready for Ubuntu?
Are you sure about that?
https://launchpad.net/ubuntu/+source/thunderbird
In general, it is up to Ubuntu's maintainers to decide which version of Thunderbird is to be shipped with ubuntu. Thunderbird 78 is out for about half a year already.
(In reply to John Bieling (:TbSync) from comment #8)
Are you sure about that?
https://launchpad.net/ubuntu/+source/thunderbird
For the LTS release Focal there is only TB 68 released:
https://launchpad.net/ubuntu/focal/amd64/thunderbird
And there is only an old TB 78.05 as "proposed".
|
||
Comment 10•4 years ago
|
||
A possible reason could be some SSL related things. missing ciphers . End of date in server certificate ...
I saw a quite equal TB information window at the thime where TB and out old mail server couldn't find a matching algorithm ...
|
Reporter | |
Comment 11•4 years ago
|
||
Fortunately version 78 now is available from Ubuntu repository since some weeks, so since yesterday I'm on 78.
The bug still occurs. I used the test procedure from comment 4.
The not sent message was copied in the SEND folder and the composition window was closed.
|
||
Comment 12•2 years ago
|
||
Does this reproduce with the updated SMTP in version 102?
|
|
||
Comment 13•2 years ago
|
||
Let us know if the problem still occurs.
Description
•