119493 - Corruption of mail folder database files.

Status: VERIFIED DUPLICATE of bug 115316

(MailNews Core :: Backend, defect)

Description

[Quinn Yost (mythdraug)]

Build 2002011003 Win32

Occasionaly when filing messages away the following occurs:

1) I select more than one message
2) Drag them to the destination folder and release
3) One message does not move
4) The count of messages in the desination folder increases 
     by the initial number of selected messages.
5) The destination folder becomes bold (indicating an unread message)
6) The number of messages in the original folder decreases by the
     initial number of selected messages.

I can then move the single message.  There appears to be no physical
corruption of either folder, only cosmetic.  Deleting the .msf for
the affected folders corrects the problem.

Comment 1

[David :Bienvenu]

are you talking about local messages or imap messages? 

Comment 2

[Quinn Yost (mythdraug)]

Local folders as both source and destination

Comment 3

[David :Bienvenu]

-> Navin

Comment 4

[Erich 'Ricky' Iseli]

Confirming. It's what I see, but you seem to explain much better. I'm marking my
bug (bug 120050) as a dupe of this one.

Comment 5

[Erich 'Ricky' Iseli]

*** Bug 120050 has been marked as a duplicate of this bug. ***

Comment 6

[Erich 'Ricky' Iseli]

What I was describing in the other bug is the same, but with just one message
selected. This way, the message doesn't move, but a new, empty message with no
subject and no sender, just the date 1.1.1970 00:00 GMT and the size 1K.

Comment 7

[Navin Gupta]

sheela, can you reproduce this?

Comment 8

[Sheela Ravindran]

I will try and update the bug.  

Comment 9

[Sheela Ravindran]

Reporter,
When you say cosmetic corruption what is it? Are you seeing the same results as
another reporter here who explains that message in the destination folder has
bogus date and no subject or sender? 

Comment 10

[Sheela Ravindran]

Here is the list of bugs I found which I guess describes as the same problem.  
78785
105120
115316
I think depending on the os the date you see on the message moved is different.
 But none of these bugs give any clue as to how this can be reproduced. 

Comment 11

[Quinn Yost (mythdraug)]

I've never actually examined the destination folder to
see if this is the case.

Comment 12

[Erich 'Ricky' Iseli]

Sheela, the only way I can reproduce that is the following (however it doesn't
reproduce always, it's just a way which makes it likely that the bug happens).
1. I'm having about 10 folders in the "Local folders" with each between 5 and 10
subfolders, the subfolders being not on the same level)
2. The total messages which are stored in the "Local folders" is more than 1000.
3. Given this situation, move 1 or more messages from one folder to the other.
Sometimes, you'll have to drag-scroll-drop so you can file the message to the
right place. However drag-scroll-dropping is not the only way when this happens.
It could also be a simple drag&drop to the parent folder.

Comment 13

[Erich 'Ricky' Iseli]

Something that might help as well: the destination folder can be a fresh one,
while the source folder can have lot of noise in it (lots of messages moved away
without compacting folder before).

Comment 14

[Sheela Ravindran]

"  I've never actually examined the destination folder to
see if this is the case."

So what is the corruption you are seeing. Am I missing something here.

Erich.Iseli:  I am not sure if the reporter here is seeing what you are seeing.
 I want the reporter to be clear in defining the corruption.  I don't want to
assume he is seeing the same thing as you are.  

Comment 15

[Quinn Yost (mythdraug)]

Sheela:  I should have been more specific in my previous statement. 
   What I have not done is examine the file the folder represents.
   
Say that I select 5 read messages from the Inbox and drag them to 
some other folder.  When I release, the count of messages in the
destination increases by 5, the unread count increases by 1, the
folder becomes bold, and _4_ messages move.  The count of messages
in the source folder decreases by 4.

If I then exit mozilla, and delete the .msf file for the destination
folder; when I go back to that folder in mailnews, it rebuilds the
.msf with a correct message count and read status indication.

Is that clearer?

Comment 16

[Sheela Ravindran]

Reporter,
Thanks for clarifying what you really meant by corruption. I just felt we were
getting mixed up with what each person is describing in his own way what
corruption is.  

Erich 'Ricky' Iseli:  Now it is clear the results you are seeing is different
from what the original reporter logged this bug for. This bug will not get
resolved for the date issue.  As I mentioned here we have other bugs reported
you can include  yourself on the cc list for those bugs.   

Comment 17

[Erich 'Ricky' Iseli]

Sheela: Now I'm really confused. The reporter told me on IRC that he sees the
same thing like me (see my Comment #12) and I also see the same thing he
describes in Comment #15. So this is *the same* bug. The only difference between
my initial report and his one, is that I observed what happened when moving 1
message and he describes what happens when moving several messages.

Figure with several messages (let's say 5 messages)
1) select 5 msg
2) move them to another folder
3) physically only 5-1 msgs (4) moved
4) the msg count in the source folder makes -5
5) the msg count in the target folder makes +5
6) the target folder gets bolded (in the background, one message gets marked as
unread, but you CANNOT see that unread message)
7) if you delete the msf file, the source folder msg count is set to be only -4
(because only 4 messages have been actually moved and the target folder gets +4
(from the initial numbers)

Figure with one message
1) select 1 msg
2) move it to another folder
3) physically no message moved (1-1 =0)
4) the msg count in the source folder makes -1
5) the msg count in the target folder makes +1
6) the target folder gets bolded (in the background, one message gets marked as
unread, you CAN see it and it has a date set to 1.1.1970) THIS is the only
difference to the reporters, difference which can be explained because actually
no message has moved and the program already started to create some msg headers
in the msf file.
7) if you delete the msf file, the source folder and the target folder msg count
is set back to the initial number (because no message has been actually moved

Comment 18

[Sheela Ravindran]

Based on Erich's comments marking this bug a dup of 115316

*** This bug has been marked as a duplicate of 115316 ***

Comment 19

[Sheela Ravindran]

vrfy dup