Bugzilla

Ben, Thanks for looking at this.
I've never had a real world case where I've actually seen this/these bugs, probably because I'm always home using TB on a fairly solid internet connection. However, over the years I've worked on this  (and several similar bug reports several times) and made several improvements,  I've simulated the causes and I it seemed like the problems were solved. My simulation uses blocking outgoing imap port with firewall (e.g., iptables) and with windows local firewall, forcing a weak wifi connection my moving out of range, disconnecting cables etc. while message is getting sent and saved to Sent folder.

The problem reported by Richard Leger (e.g., comment 75 and others earlier) is a bit different than the problem reported by Mitra Ardron (and others earlier in this bug report). It seems that /tmp files holding the message to send and/or the message to be saved to Sent folder are getting prematurely deleted or a reference to the tmp files are getting set null in JS code. So this may be related to the change from c++ to JS code for sending message that was done a couple years ago.  I did see this one time but haven't been able to duplicate it, but I had to build up about 6 messages with save to Sent errors causing 6 tmp files to be present at the same time.

Ben, Thanks for looking at this.
I've never had a real world case where I've actually seen this/these bugs, probably because I'm always home using TB on a fairly solid internet connection. However, over the years I've worked on this  (and several similar bug reports several times) and made several improvements,  I've simulated the causes and it seemed like the problems were solved. My simulation uses blocking outgoing imap port with firewall (e.g., iptables) and with windows local firewall, forcing a weak wifi connection my moving out of range, disconnecting cables etc. while message is getting sent and saved to Sent folder.

The problem reported by Richard Leger (e.g., comment 75 and others earlier) is a bit different than the problem reported by Mitra Ardron (and others earlier in this bug report). It seems that /tmp files holding the message to send and/or the message to be saved to Sent folder are getting prematurely deleted or a reference to the /tmp files are getting set null in JS code. So this may be related to the change from c++ to JS code for sending message that was done a couple years ago.  I did see something like this one time but haven't been able to duplicate it, but I had to build up about 6 messages with save to Sent errors causing 6 tmp files to be present at the same time.