Found while verifying bug #18062. Using 2000-02-17-08m14 commercial builds, all platforms 1. Find a large local folder with thousands of messages, delete the msf file, and then try to open it with mozilla. While it's parsing, press stop. 2. Exit mozilla, reopen that folder. Note you still only have a portion of the message headers displayed in thread pane and message count is left at the point where you'd stopped parsing. Result: doesn't reparse folder, not all messages in folder are displayed in thread pane. You must remove the msf file in order to correct the problem. Expected: should reparse on next startup so you see all the messages in the folder.

this worked at one point, because I remember fixing it - someone was setting the folder info valid when they shouldn't have - it looks like someone is doing it again.

Putting on PDT+ radar for beta1.

set ETA.

worked fine for me - I pressed stop, restarted, and the folder was reparsed. So I guess I'm still working on recreating this. Moving ETA out accordingly.

looks like you have to mark a message read or unread after stopping parsing to cause this problem.

fix checked into mailnews/db/msgdb/src and mailnews/local/src

OK using 2000-02-23-08m14 commercial build NT 4.0 Tried both cases: 1. not reading/marking a message after partial download, then relaunching. 2. reading messages after partial download, then relaunching.

OK using 2000-02-23-08m14 mozilla build mac OS 9.0

Taking longer to verify on linux -- need to workaround profile bugs 28243 and 28879.

OK using 2000-02-24-09 commercial build on linux rh6.0