315680 - stuck copying mail to sent folder

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Andy Burns]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
Build Identifier: thunderbird 1.5rc1

had long term install of TB1.0.6, upgraded to 1.5rc1 keeping same profile

sending message results in message being sent ok, but stuck saving copy to sent folder, this happened on both an IMAP account, and a POP3/localstore account.

exited/restarted TB, still same
stopped/started dovecot, still same
reverted to 1.0.6 all working correctly

sorry this is a bit brief, but couldn't see anyone else with similar problem and wanted to get it reported in case it is a general problem and slips out with 1.5

I can re-install 1.5rc1 and sniff with ethereal if there's anything anyone would like checked ...



Reproducible: Always

Steps to Reproduce:
1. install 1.5RC1
2. send messsage
3.

Actual Results:  
waits "forever" saving message to sent items

Expected Results:  
message save to sent items

Comment 1

[Mike Cowperthwaite]

There have been several fixes between 1.0 and 1.5 to the code saving the Sent message to an IMAP folder, but those changes were supposed to prevent these kinds of problems, not cause them.

Is the Sent folder on the IMAP server for the IMAP account?  For the POP account?

If the folder is on the IMAP server, you can generate a protocol log; that 
might be helpful in troubleshooting:
  http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html

Comment 2

[Andy Burns]

For the IMAP account the sent folder was on the server, for the POP3 account the folder was within the profile directory. 

I will take the time to re-install and test 1.5RC1 again in the morning, and try the protocol trace, is it valid to install 1.5RC1 and re-use the existing 1.0.x profile?

Comment 3

[Andy Burns]

1.5rc1 reinstalled, I've been batting replies back and forth between the POP account and the IMAP account all morning and not seen the issue at all.

If it happens again I'll try the IMAP trace and report here again, but for now perhaps this is a WORKSFORME after all ;-)