Closed Bug 1311023 Opened 8 years ago Closed 8 years ago

Thunderbird closes the compose window despite the mail is not saved to the sent folder

Categories

(Thunderbird :: Message Compose Window, defect)

45 Branch
x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 28211

People

(Reporter: daniel.b, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; HPDTDFJS; H9P; rv:11.0) like Gecko

Steps to reproduce:

I compose an email and then some network error occurs so that Thunderbird is unable to save the email to the sent folder on the server. Thunderbird gives an error message and if I click abort, Thunderbird closes the compose window so I loose the content of the email.


Actual results:

If I send an email and Thunderbird is unable to save the email it gives an error message and I have two options: Try again or abort. If I try again, Thunderbird will fail again if the network error is not resolved (the mail server may have gone offline). If I abort, Thunderbird closes the window and I loose the content of the mail.


Expected results:

If Thunderbird is unable to save the email to the sent folder, it must not close the compose window. It is rare that Thunderbird is unable to save the email to the sent folder because of network error, but then it does, I lost the content of the mail because Thunderbird closes the compose window even if it has not saved the email.

Then every thing works, it is great that Thunderbird closes the compose window then the email is sent and saved. But if the email cannot be saved, Thunderbird must not close the compose window.
What I mean is that Thunderbird should NEVER automaticly close the compose window unless the email has been saved to the mail server. In case of a network error, the compose window must stay open until I explicity close it.
OS: Unspecified → Windows 8.1
Hardware: Unspecified → x86_64
Yep, people have complained about this before. Bug 1263863 or much earlier: Bug 28211
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.