85057 - wrong message offset/size written into mail db

Status: VERIFIED DUPLICATE of bug 90186

(MailNews Core :: Backend, defect)

Description

[Dwayne]

Build 2001-06-09-20 (from win32-installer), Win2k sp2

Behavior:
Mail window shows incorrect Subject line in header pane, message body is cut off.

Expected:
Correct subject line listed, no data loss in message body.

Steps to reproduce:
I don't know, this is a weird one.  I don't know if this was visible before with
build 2001-06-05; I just realized it now.  I have a screenshot attachment to
show you what's up (should be coming next...)

Other info:
I set the priority to critical because of the data loss; whether or not it's
truly 'critical' is to be debated.

Comment 1

[Dwayne]

Attachment: 33KB image showing incorrect info

Comment 2

[Dwayne]

Ooops, sorry for the spam...

I forgot to mention this error is true for more than one message.  Some messages
even have extended header information *after* the message body is cut off, as if
it were just plain text.

Like I said, I never noticed it before but it's possible it was like this before
the current build.  I have a hunch this could be nothing more than a
bugzilla-daemon email creation issue.

Comment 3

[Oliver Klee]

Confirming on 2001060820 Win2k and over to Mail Database.

This has to do with a corrupted *.msf file. Deleting the corresponding *.msf
file and rebuilding it (by clicking on that folder) should fix this temporarily.
But usually this problem keeps coming back for the same folder after a while.
Could you attach the "misbehaving" mail folder file + its *.msf file (*before*
rebuilding the msf file, of course)?

Comment 4

[Dwayne]

Hmm, can't find the 'folder' but I do have the .msf file.  But if I remember
correctly, a folder is not created unless it contains subfolders.

Also, if I attempt to delete the file, won't this delete all the messages that
are in that folder?  I don't want to do that.  Is there any way around it?

Changing summary to reflect findings.

Comment 5

[Dwayne]

Attachment: Ok, I did find the 'folder' *file* (no extension)

Comment 6

[Dwayne]

Attachment: ...and here is the .msf file

Comment 7

[David :Bienvenu]

The mail database is just responsible for returning the message size/offset that
it is given when the mail is downloaded by the download code. My guess is that
the wrong offset is given at that time, so changing summary and component. 

Comment 8

[Oliver Klee]

Yeah, "folder" like "mail folder", not like "directory folder".

Deleting the *.msf file won't delete your mails. Your mails are stored in the
file without extension.

Comment 9

[Dwayne]

Thanks for the clarification.

Should this be dogfood/catfood?  Not sure on the definitions, but I think
dogfood is a blocker (i.e. blocking a user from using the program), where
catfood is a very visible bug.

If I'm right on those assumptions, I would nominate this for dogfood.

Comment 10

[David :Bienvenu]

the problem is that it may be dogfood for you, but we don't have a way of
recreating the bug and without steps to reproduce it, we can't fix it. Do you
use mail filters? Is it only filtered messages that are messed up?

Comment 11

[Dwayne]

Well, it just so happens I have one filter and one extra folder.  And it appears
this is the only one that's corrupt, so yes.

The filter says to look for the sender 'bugzilla-daemon' and move it to the
bugzilla subfolder.

Comment 12

[Oliver Klee]

I also experienced this with a mail folder that does not get any mail filtered
into it. Instead, I have moved quite a few messages there by draggin and
dropping. Maybe this has to with moving messages.

Comment 13

[Oliver Klee]

s/has to/has to do

Comment 14

[Dwayne]

Ok, this bug has already been confirmed.  Shouldn't it be classified as NEW?

Comment 15

[Dwayne]

oh
my
god...

ignore me!

Comment 16

[Dwayne]

Guys, I am now on build 2001-06-30-08 from Installer...

I tried moving some files around to subfolders in Trash, and it corrupted the db
again.  So I deleted the .msf files for the subfolders.  When it rebuilt, the
same  exact problem occurred right away.  Even the newly recreated db is faulty.

Comment 17

[David :Bienvenu]

Could you dup this one, Navin? Looks like the message copy bug.

Comment 18

[Navin Gupta]

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

Comment 19

[Dwayne]

Sigh, fundamentally I hate to do this, but seeing as it's already closed, I'll
verify this *earlier* bug (pthbhth :P ) as a verified dup.