550331 - Sent mail error copying the message to the sent folder using IMAP caused by

Status: RESOLVED DUPLICATE of bug 530779

(Thunderbird :: Message Compose Window, defect)

Description

[Kevin A. McGrail]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.0.18) Gecko/2010020220 Firefox/3.0.18 GTB6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3

If you use IMAP and open a new write window, then close the Mail and Newsgroup window, upon sending the message (which does go out), TB has closed the connection to the IMAP server and is unable to save the Sent mail to the sent folder.

If the Mail and Newsgroup window is not closed, the issue does not occur.  Using ctrl+1 in the write window to try and open it back up, the client does not work.  

Tailing the server logs while doing this confirm my belief:

[Open Thunderbird]
Mar  4 18:02:49 intel1 dovecot: imap-login: Login: user=<kmcgrail>, method=PLAIN, rip=71.163.15.130, lip=38.124.232.10, TLS
[Click Write to Start a new message]
[Close Mail & Newsgroups but not File->Exit]
Mar  4 18:02:57 intel1 dovecot: IMAP(kmcgrail): Disconnected: Logged out bytes=191/322
Mar  4 18:02:57 intel1 dovecot: IMAP(kmcgrail): Connection closed bytes=574/12037

[Click Send on Email]
[Get Error since IMAP isn't connected!]

Reproducible: Always

Steps to Reproduce:
1.open thunderbird using IMAP
2.click write
3.close the mail + newsgroups window leaving write window open
4.send email 
5.error will occur saving in sent folder BUT email is sent.
Actual Results:  
Email is sent without saving Sent copy.

Expected Results:  
Thunderbird should likely not allow the mail and newsgroup window to be closed if active compositions windows are open.  Similar to the File->Exit behavior to avoid closing IMAP connections which invalidates the ability to save Sent folder copies on remote server.

Because I lose my only copy of the Sent mail, I consider this a loss of data severity issue.

Comment 1

[Nathan Tuggy (:tuggyne)]

This is a dup of bug 530779, but you're in luck: the patch has just been checked in, this will definitely be in 3.1, and most likely in a later 3.0.x release also.

Comment 2

[Kevin A. McGrail]

Thanks.  I did my best to search prior to opening but missed that one!  Count me in as someone who would like this to be in a 3.0.X releas for bug 530779!