99727 - msf file corruption

Status: VERIFIED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[Steven Miller]

There is another bug in the list of IMAP bugs where sending a message and 
coying to the sent folder takes bloody forever.

If you hit the get new message button while the message is still being sent you 
will quite often experience mozilla deciding to reload the entire IMAP message 
headers from the server.

When this happens the in-memory list of messages is completely corrupted.  
Sometimes every message is listed 2 maybe 3 times!  Sometimes you click on a 
message and it shows you a completely different message!

Workaround is to immediately quit netscape.  If you are seeing 2 or more copies 
of a message workaround is to delete INBOX.msf.   But, sometimes INBOX.msf 
comes up with a sharing violation even though netscape has quit. When this 
happens you have to reboot, delete INBOX.msf and then start mozilla.

Overall the mozilla IMAP client is very unstable and unreliable.  I would very 
much like to see this bug fixed, the copy to sent bug fixed, and the takes 
forever to quit bug fixed.   Then someone can make select all work in a search 
folder and mozilla will finally catch back up with Netscape 4.77.

Comment 1

[Esben Mose Hansen]

This bug needs a build ID to pass the uncomfirmed review. Otherwise it seems ok
to me.

I seem unable to reproduce this on my build, but maybe my IMAP server is too fast. 
Win ME, Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.4+) Gecko/20010928, 
build: 2001092803.

Comment 2

[Matthias Versen [:Matti]]

Reporter: 
Which build are you using ? (Please include in all bug reports the build ID)
Can you reproduce this with a recent nightly build ?

Comment 3

[R.K.Aa.]

Steven Miller:
Many of the .msf file corruption bugs have been fixed or resolved as WFM by now.
Can you please check if you are still seeing this bug in recent builds, and add
comment here on web in form for "Additional Comments":

http://bugzilla.mozilla.org/show_bug.cgi?id=99727

Comment 4

[Steven Miller]

I have not seen this problem in the last couple of releases of mozilla.

Comment 5

[Matthias Versen [:Matti]]

thanks -> wfm

Comment 6

[Karen Huang]

Verified based on above reporter's comments and my verification on 
Windows 2000 04-10-06-trunk build.