Closed Bug 115316 Opened 23 years ago Closed 17 years ago

Dragging mail from Inbox to folders causes spurious mail to be created

Categories

(MailNews Core :: Backend, defect, P2)

x86
All

Tracking

(Not tracked)

RESOLVED INCOMPLETE
mozilla1.2alpha

People

(Reporter: johng, Assigned: Bienvenu)

References

Details

PROBLEM: Occassionally, when dragging mail from the Inbox into folders, spurious emails are created in these folders. Sometimes they appear with no Body text, or Subject text, but they always have a date and time of 01/01/1970 and a time of 00:00. When these spurious messages appear in the folder, they are 'unread' i.e. they appear in bold. REPRODUCABILITY: If I drag the mail from the Inbox to the folder very quickly, i seem to get the most problems with this bug, where as if I drag the mail slowly, and hover over the folder for a while I can be sure that the mail will be deposited in the folder without this problem occurring. I am using Mozilla 0.9.6
QA Contact: esther → sheelar
I'm seing this same problem. Probably a dupe of bug 119493. It has not to be a mail from the inbox. I could reproduce that problem in the "local folders", by dragging a msg from any folder to any other. However I don't think the speed you drag really makes any difference. I've seen the problem too when dragging quite slowly.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bug 119493 is only the unread count in the folder not updated correctly after the move. This bug is similar to bug 78785 however, there is no crash in this bug. But gives a bogus date when moved within local folders.
Assignee: sspitzer → naving
Component: Mail Window Front End → Mail Back End
*** Bug 119493 has been marked as a duplicate of this bug. ***
Please ignore my last comments because they are the same bugs. See last comments in bug 119493. Navin, I too have seen this problem moving message between local folder that I get a weird date. But I have not yet figured out how to reproduce this problem. It does not happen all the time.
Status: NEW → ASSIGNED
Keywords: nsbeta1
*** Bug 114774 has been marked as a duplicate of this bug. ***
*** Bug 121097 has been marked as a duplicate of this bug. ***
Do you lose the original message from the original folder when this happens?
Severity: trivial → major
Keywords: nsbeta1nsbeta1+
Priority: -- → P1
Target Milestone: --- → mozilla0.9.9
No, I don't lose the original message(s)
that lowers the priority a bit then.
Priority: P1 → P2
This is also happening sometimes when shift deleting multiple mails.
I am not able to reproduce this using fast d&d. On second thought how can shift-delete cause this bug. We don't copy message to trash on shift-delete.
Added info: when mine does this, a second "Move" operation will usually succeed in moving the mail item, but BOTH copies in the destination folder then show up as dated 1/1/70. Clicking "Mark All Read" will clear the "unread" flag, whereupon BOTH copies move to the correct date. BUT ... deleting one of the two will make the second copy disappear also.
moving it to 1.0
Target Milestone: mozilla0.9.9 → mozilla1.0
Discussed in Mail News with Mktng, QA, Engineering and PjM. Decided to minus this bug.
Blocks: 122274
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla1.0 → mozilla1.2
Bug is still there in 1.0. It will lose mail if a "duplicate" caused by the error is deleted. Both duplicate and original then disappear.
QA Contact: sheelar → stephend
mass re-assign.
Assignee: naving → sspitzer
Status: ASSIGNED → NEW
See this on Red Hat Linux too (see bug 209501 comment #44 and bug 209501 comment #47 for details).
OS: Windows 2000 → All
taking - these are local msgs, correct? Is this reproducible? If you take the same messages and move them again, does the same thing happen? I've never seen this myself. If it is reproducible, does it have to do with the messages themselves?
Assignee: sspitzer → bienvenu
Product: MailNews → Core
no reponse from reporter, so resolving incomplete. though seems like some of these comments are bug 209501.
Status: NEW → RESOLVED
Closed: 17 years ago
QA Contact: stephend → backend
Resolution: --- → INCOMPLETE
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.