Closed
Bug 455720
Opened 17 years ago
Closed 16 years ago
Moving messages from folder to folder needs to "delete" as it goes
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bruce, Unassigned)
Details
(Whiteboard: closeme 2009-11-13)
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: 2.0.0.16 (20080708)
If i am moving a large number of messages from folder to folder (in this case from one server to another), the program needs to "delete" as it goes ... otherwise, if it crashes, I have to manually determine what messages it has already "moved" so I can delete the originals before I try again. This is very painful.
E.g., if I have 60 messages in folder A and I am moving them to folder B on a different server, and either server throws an error say at message 28, I have to go manually delete the 27 messages that were successful from folder A before I begin again or I get duplicate messages.
It would be better if it moved message 1 (and really moved it - i.e. deleted it from folder A upon successful move) and then moved messages 2, etc.
Thanks.
Reproducible: Always
Steps to Reproduce:
1. Start moving a bunch of messages from folder 1 to folder 2 (on different servers)
2. Do something to interfere with the transfer (disconnect your internet perhaps)
3. Whatever messages successfully moved before the break will now be in both places.
Actual Results:
Manual intervention to keep from having duplicate messages when finished.
Expected Results:
Messages that were successful actually moved.
Comment 1•17 years ago
|
||
are you imap or pop?
Comment 2•16 years ago
|
||
Bruce could answer to comment #1, please?
Component: General → Folder and Message Lists
QA Contact: general → folders-message-lists
Whiteboard: closeme 2009-11-13
Version: unspecified → 2.0
Comment 3•16 years ago
|
||
RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•