Sometimes when Thunderbird cannot send a message it is put in Sent folder anyway



MailNews Core
2 years ago
2 years ago


(Reporter: jon bondy, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [dupme])



2 years ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160502172042

Steps to reproduce:

Write an email and send it. 

Actual results:

I use a GoDaddy email server; connections to that server fail about 15% of the time; it is a **** shoot.  If I click through the various error messages and retry the send, the email goes after between 1 and 5 attempts.  But, very rarely, the email is put in the Sent folder even though it was never sent.  I know this because when I resend the email with a disclaimer ("not sure this went through the first time") I am told the recipient never saw the original. When the problem occurs, the message disappears immediately after I click the final error message, so quickly that it is clear that no attempt has been made to send it.  I understand how difficult it is to reproduce erratic bugs.  I will try to collect more information each time it occurs and append to this report.  This has been going on for a few years.

Expected results:

When the transmission fails, keep the message visible and inform the user that there was an error, so s/he can retry.

Even better, allow Thunderbird to retry periodically in the background (once this bug is fixed, so that we are sure that messages in the Sent folder were really sent).

Comment 1

2 years ago
It just happened again.  I saw the Login Failed message, and clicked Cancel.  Then the message disappeared from the screen, without being sent, but it was visible in the Sent folder.


2 years ago
Component: Untriaged → Backend
Product: Thunderbird → MailNews Core
Whiteboard: [dupme]
Version: 45 Branch → 45

Comment 2

2 years ago
There is something wonky about error handling in Send. See bug 1150799 for a related issue with STR.
You need to log in before you can comment on or make changes to this bug.