Mail messages lost on copy to IMAP server folder from local folder



Mail Window Front End
13 years ago
13 years ago


(Reporter: Mike Christie, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Thunderbird version 1.0 (20041206)

I use IMAP, and have an SMTP account via SBC that I can't persuade to work from
my office laptop.  When I bring my laptop home I use the MS webmail interface to
access the office exchange server, and I can send email that way.

If I want to reply to a message that's in a local folder, Exchange can't see it,
so in Thunderbird I copy it (by drag and drop) to the Inbox. Then Exchange can
see it and I can do a reply from Webmail.

The problem is that twice the message has disappeared.  It appears that the drag
and drop does a delete of the message in the local folder before it gets
confirmation that the message has been successfully copied into the target
server-side Inbox folder.  It works fine 19 times out of 20, but twice (so far)
I have had a popup message after the drag/drop saying that the server is in the
wrong state and cannot complete the command.  This popup actually appears twice.
 Once the popups are cleared the mail message is gone from the local folder and
does not appear in the server inbox.

I am reporting this as critical because this definitely causes data loss.

Reproducible: Sometimes

Steps to Reproduce:
1. Have IMAP folders on the server
2. Drag messages from local folders to these server folders
3. If a message appears saying that the server is in the wrong state, then I
believe the message will be lost.  This happened twice to me and both times the
message was lost.

Actual Results:  
The email was permanently deleted.

Expected Results:  
If the email could not be successfully copied it should have remained in the
local folder.
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.