1290693 - Mail status not updated if I move it into another folder while replying is in sending phase

Status: RESOLVED DUPLICATE of bug 268589

(Thunderbird :: Mail Window Front End, defect)

Description

[csongor]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160604131506

Steps to reproduce:

- I right click an email in the Inbox folder I received right now and select Reply To All
- compose the response message
- click the Send button
- while the response email is being sent, I move the original email from the Inbox folder into my Done folder
- the sending of the response email gets finished within a couple of seconds
- I check the Status of the moved email which I have just replied. 


Actual results:

The status is Read in the Status column and no symbol is displayed in front of the Subject.




Expected results:

The status should be Replied instead of Read and the purple curly left arrow also should be displayed in front of the subject. 



Additional comments:
If I move the incoming email later, after the reply has been sent then the status is what I expect and the symbol is also displayed correctly. 

The problem with the present behaviour is that 
- if I am not aware of this bug then I don't understand why I haven't replied the email if I strongly remember I have replied it. 
- if I am aware of this bug then I cannot move the email from my Inbox into the Done folder until the reply gets sent. This enforces me to wait unnecessarily and decreases my productivity.

Comment 1

[WADA:World Anti-bad-Duping Agency]

"Replied status of replied mail in msgDatabase=msf file" is set after successfull mail sending of reply mail.
"Move a mail between folders" == "Copy a mail to other folder" + "Delete the mail in original folder".
If the replied mail is deleted before "Replied status of the replied mail" is stored after successfull mail sending of reply mail, anyone can not store "Replied status of the replied mail in msgDatabase=msf file".
So, there is no difference between this bug and bug 268589 in phenomenon.
This is current implementation.