275707 - Unable to save sent mail in Send folder every now and then

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Marcus Wendel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Thunderbird version 1.0 (20041206), Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Every now and then my Thunderbird is unable to save any sent messages to the
Sent folder (sent emails should be placed in the "Sent" folder among the "Local
Folders) and once I've got that with one email (the only thing to do is cancel
the attempt) I then have to restart Thunderbird for it to be able to save them
again.
This is a problem that I've been having with several versions of Thunderbird.

I've so far not been able to find out what to do to reproduce the problem as it
normally works fine.

Reproducible: Sometimes

Comment 1

[b]

I can confirm the exact same thing happens on my SUSE9 linux machine. 
After using thunderbird 0.8 and 0.5 for some time (perhaps 10 hours) messages
stop getting sent to the sent folder. I have to restart thunderbird to get
messages to be sent properly to the sent folder again. Between working and not
working it seems to randomly send some messages to sent and not others. 

The message goes through the process of sending, connecting to server,
delivering and then sticks on "copying to sent folder" during this time the CPU
usage jumps way up and stays up. This can stay on screen for up to 15min or
longer, I cancel "sending" the message when I see its not getting copied. If I
wait long enough I do get a message saying "copy to sent failed" 

Comment 2

[jerry asher]

Yep.  It happens to me with Thunderbird 1.0, Windows XP SP2, running IMAP
against courier imap and qmail on rh9

Comment 3

[Emmanuel Blot]

*** Bug 283958 has been marked as a duplicate of this bug. ***

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 6

[Ian P. Christian]

duplicate of bug 314730