Closed
Bug 24376
Opened 25 years ago
Closed 25 years ago
[Pop3] Unable to delete messages after getting into a certain state
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M17
People
(Reporter: jefft, Assigned: Bienvenu)
Details
o Use Pop3
o Select any messages, single or multiple
o Hit delete
o Nothing gets deleted
o Though message display move to the next unselected message
o This might also cause Move messages to fail
jeff - in the release Win32 build from today (2000-01-19-13-m13), I created a
new POP account and was able to delete messages and have them move to the trash
folder.
Severity: normal → critical
QA Contact: lchiang → esther
Summary: [Regression] [Pop3] Unable to delete messages → [DOGFOOD][Regression] [Pop3] Unable to delete messages
Hmm.. I pulled my tree this morning. I'll try it again to make sure.
Looks like the problem is manifest from a corrupted database. If I removed the
*.msf everything works fine. The question would be how can a database get
corrupted and is there anyway we could detect it and then correct it.
| Assignee | ||
Comment 6•25 years ago
|
||
FWIW, I've never seen a corruption in msf files. What I have seen is headers put
into msf files with the wrong message keys, status offsets, etc. This gets fixed
when we reparse the folder, which happens when you delete the .msf file.
Linux (2000-01-20-08 M13)
FYI:
I try it in today's linux build again. The problem still exists.
After a crash, I relaunch Messenger and try to delete a message in the POP
account, Delete does not work. But if I remove the .msf files, it works.
However, I have not seen this problem in the IMAP account.
| Reporter | ||
Comment 10•25 years ago
|
||
Okay, I am clearing the [PDT+] flag.
Status: NEW → ASSIGNED
Whiteboard: [PDT+]
Comment 11•25 years ago
|
||
removing dogfood entry. There is a workaround for this.
Summary: [DOGFOOD][Regression] [Pop3] Unable to delete messages → [Pop3] Unable to delete messages after getting into a certain state
| Assignee | ||
Comment 12•25 years ago
|
||
David, could you try to reproduce this problem and figure out what's going on?
Assignee: jefft → davidmc
Status: ASSIGNED → NEW
Comment 13•25 years ago
|
||
It's hard to figure out why something does not happen, because the reasoning is
similar to proving a negative. I might need to study all the code which intends
to delete something, before I see why nothing happens. I can look into it.
| Assignee | ||
Comment 14•25 years ago
|
||
The first thing to try is to recreate the bug. Especially, play with things like
deleting a local message, then Undoing it, then deleting an other mesage, redo,
etc.
Comment 15•25 years ago
|
||
Sure thing. (I was trying to recreate the other bug for specifying a port for a
pop or smtp host, but I'm having trouble getting symbols where I crash even when
I load all the symbol files I can find.)
| Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14 → M16
Comment 17•25 years ago
|
||
Can we make it so we detect the crash and rebuild the .msf file in that case?
It seems like there's a high correlation between the crash and the symptom. Any
shutdown that's not "clean" might be the condition here.
(I know this has the effect of only hiding the symptom, but if it's caused by
crashing I think that's probably as good as it gets for now.)
| Assignee | ||
Comment 18•25 years ago
|
||
we probably do recreate the .msf file, Steve. But there's probably a problem
with the TRASH flag setting on the .msf file.
| Reporter | ||
Comment 20•25 years ago
|
||
I am sure this is fixed by now.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 21•25 years ago
|
||
Using build 2000-05-16-09 on win98, mac and linux this is fixed. I deleted a
few msgs in my POP acccount, the crashed the product with a known crasher
(expanding a newsgroup). Reopened Mail, selected my POP account and deleted
messages. If anyone is running into this again, please comment and give
a scenario, then reopen. Verified
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•