Closed
Bug 11578
Opened 25 years ago
Closed 25 years ago
IMAP: Expunged message headers never get removed from the database
Categories
(MailNews Core :: Database, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
M11
People
(Reporter: jefft, Assigned: Bienvenu)
Details
Step to reproduce the problem: o Delete some messages from an Imap folder o Compact that folder (permanently removed from the server) o Shutdown the app then relaunch o Notice that the expunged message headers appear then disappear o Shutdown the app then relaunch o The problem remain exists
Assignee | ||
Comment 1•25 years ago
|
||
I know for a fact that the headers are removed from the database...I've stepped through the code. I can imagine that RDF is having trouble unasserting the headers.
Comment 2•25 years ago
|
||
I don't understand the steps to reproduce. Are you saying that even after shutting down they come back? If that's the case then I don't think RDF would be involved.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M11
Assignee | ||
Comment 3•25 years ago
|
||
I haven't looked into it; I'm just saying what I know. Jeff seemed to be saying that headers aren't getting removed from the database. I think they are.
They did come back and disappear after shutdown and relaunch. Sounds confusing, right?
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 5•25 years ago
|
||
this is simply not true. I believe Jeff was seeing some different problems having to do with database corruption introduced by undo.
Liunx RedHat 6.0 (1999-08-16-08 M9) Win_nt 4.0 (1999-08-20-16 M9) Mac (1999-08-20-16 M9) Even though this was marked invalid, I went ahead and check it again. True, I not see any problem. Following the steps as described dated 8/10/99, I do not see any problem.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•