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)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M14
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
Updated•25 years ago
|
Assignee: phil → jefft
Comment 1•25 years ago
|
||
Reassign to jefft :-)
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?
Updated•25 years ago
|
Target Milestone: M14 → M13
Comment 4•25 years ago
|
||
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.
Comment 7•25 years ago
|
||
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. ***
Comment 10•25 years ago
|
||
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
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•