Closed Bug 24377 Opened 25 years ago Closed 25 years ago

[Regression] [Pop3] Shift-click select/delete all messages never finishes

Categories

(MailNews Core :: Backend, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jefft, Assigned: jefft)

References

Details

o Use Pop3 o Select a folder o Shift-click to select all messages o Hit delete o Messages seems get copied to the trash folder o Meter is running but never ends o The system is still functional
Assignee: phil → jefft
Reassign to jefft :-)
Status: NEW → ASSIGNED
Target Milestone: M13
QA Contact: lchiang → esther
I should say that the incorrect information recorded in the database causes this problem. Removing the msf file fixes the problem. What can we do to prevent this incorrect information written to the database?
Target Milestone: M13 → M14
M14 ... more likely
Target Milestone: M14 → M13
I don't have any good answer, except to write bug-free code. One problem that I've had frequently is that the file stream code does not give you the correct offset when calling tell unless you flush first. So if you ask for the file position from the stream, you probably should flush first. Other bugs include when you copy a msg hdr from another database and just use the key from the first header, which won't be correct for the second database. When we try to read a message given a file offset/message key, and the message doesn't start with "From ", we could fail and mark the database invalid.
Are you sure we need to fix this in M13?
Target Milestone: M13 → M14
Back to M14 ...
Are the messages deleted?
This apparently has been fixed by hyatt.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
*** Bug 24747 has been marked as a duplicate of this bug. ***
Using builds 2000-05-17 on win98, mac and linux this is fixed. I deleted all of the messages in a POP folder, all messages were deleted. Verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.