Closed Bug 223489 Opened 21 years ago Closed 19 years ago

Mail file does copy instead of file

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jay, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 I recently installed 1.4.0 (on Linux Red Hat 8) having previously been on 1.2.x. (This problem did not occur on 1.2.x.) I do use IMAP (but again, this problem only started when I moved to Mozilla 1.4.0 and my IMAP has not changed). Filing a mail message (using File button) SOMETIMES results in mail being copied instead of moved. A copy is created in the destination folder. The original is not deleted. This only seems to happen if I am moving quickly and incorrect deep folder levels are temporarily visible. If I slooowww down and carrreeefullly click and moooovve tooo the next folder depth, and hooooovvvveeer over the target folder for a count of 1,2,3,4,5, then the problem does *not* occur. Reproducible: Sometimes Steps to Reproduce: 1. Use File button (not sure about menu option) to file a mail message 2. Move too quickly when filing so that incorrect mail directories are temporarily visible before I get to the correct destination directory and mail folder. 3. Click quickly on destination mail folder to file message. Actual Results: Message is COPIED to destination, but original remains what it was. Expected Results: MOVED the mail message (created a copy in the destination and deleted the original). I am using default theme. I have no other special information. The only change in my environment was the installation of Mozilla 1.4. Though 1.2.x had lots of different problems, it did not have this particular problem.
Product: Browser → Seamonkey
Assignee: sspitzer → 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: 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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.