Moving messages between folders does not always work



13 years ago
13 years ago


(Reporter: Simon Goodall, Assigned: Scott MacGregor)


Windows XP

Firefox Tracking Flags

(Not tracked)




13 years ago
I am having huge problems moving messages from my inbox to other folders on an
imap server. Thunderbird appears to move them fine (they disappear out of the
inbox and the message bar at the bottom of the window says they are moving them.)

However if i quit out of thunderbird soon after and start it again, the messages
will all be in their original locations and i have to start again. This gets
very annoying when moving large numbers of messages. It seems that I have to
wait some amount of time (e.g. go off for a break) before the messages will
really be moved and i can safely quit out.
Quiting(termination) of Thunderbird while moving IMAP folder will terminate
"moving IMAP folder", because "moving IMAP folder" is executed on IMAP server
according to request by Thunderbird.
Which is your exact request?
(1) Termination of Thunderbird should be postponed when "moving IMAP folder" is
in progress.
(2) Progress or end of "moving IMAP folder" should be reported to user more kindly.
   (For exapmle, progress display by Download Manager.)

Comment 2

13 years ago
Some sort of feedback as to the state of this task would be good. A progress bar
would help, and some warning message when trying to exit.
Sounds Severity=Enhancement is appropriate.

And "progress feedback" request can be DUP of one of next bugs.
(Bugs which contains both "progres" and "folder" in Summary.
Bug  94788 No progress bar when copying to local sent folder
Bug 157991 Show total percent progress on compact folders
Bug 161752 Implement modal progress for compacting local folders
Bug 168602 Progress doesn't disappear when message/folder is finished loading
Bug 238764 Incorrect status in progress dialog while copying msg to IMAP sent folder
Bug 240185 Progress bar jiggles while compacting folders and getting mail
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.