message list isn't updates

RESOLVED INCOMPLETE

Status

--
major
RESOLVED INCOMPLETE
18 years ago
10 years ago

People

(Reporter: lferro, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: closeme 2009-06-01, URL)

(Reporter)

Description

18 years ago
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    2001062004

When trying to open a index list of a folder with has almost 4000 messages, the 
messages aren't shown

Reproducible: Always
Steps to Reproduce:
If you have a folder with too many messages (like 4000) and you stop a message 
operation (delete, copy, and the like) the folder message list becomes 
outdated. If you try to select de folder, compress the folder, close the mail 
client and open it again and so on, you still can't access it's list.

Actual Results:  Doesn't do anything not even update the window content.

Expected Results:  Should rebuild the message list at least with the compress 
this folder command.

deleting the .smf file and reentering the mail client solves the problem.

Comment 1

18 years ago
might be a dup.
Assignee: bienvenu → naving
Status: UNCONFIRMED → NEW
Ever confirmed: true
this bug has not been touched since 2001-08-15, therefore this reminder.

Reporter could you please retest with a current mozilla build and let us know if
the problem is still present or the bug can be closed.
mass re-assign.
Assignee: naving → sspitzer
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
QA Contact: esther → database
(Assignee)

Updated

11 years ago
Product: Core → MailNews Core
still see this problem?
Status: NEW → UNCONFIRMED
Whiteboard: closeme 2009-06-01
=> incomplete - no response (but not unlike the threading / index bugs that are currently being worked on
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.