254947 - MailNews should rebuild corrupted/outdated Inbox summary .msf file before fetching new mail

Status: RESOLVED FIXED

(MailNews Core :: Database, defect)

Description

[Max Alekseyev]

Linux build 2004080905

This bug is consequence of bug 253804. If Inbox summary file is corrupted or
outdated, then starting MailNews with turned on "Check for new messages at
startup" and "Automatically download new messages" options causes the following:
1. New mails are fetched.
2. A new mail indication appears, but MailNews does not show exact number of new
mails in the Inbox folder.
3. Junk mails are marked as 'Junk' but not filtered to the Junk folder. I assume
all other filters do not work either.

Comment 1

[David :Bienvenu]

I'll check into it.

Comment 2

[David :Bienvenu]

I tried this with a brand new trunk build. I "touched" Inbox so the .msf file
would be out of date, started up, and saw the Inbox.msf summary file get
regenerated, then new mail was retrieved, and my junk mail was moved to the junk
folder.

Are those the same steps you performed? Or did you try deleting your Inbox.msf file?

Comment 3

[Max Alekseyev]

I think that my Inbox summary file was really corrupted after a system crash. I
did not delete it. But maybe a deleted summary file will allow to reproduce the bug?

Comment 4

[David :Bienvenu]

if your system crashed, it's more likely that the summary file was just out of
date with the local mail folder, not that the summary file was corrupted.

Comment 5

[David :Bienvenu]

Attachment: fix for getting new mail when Inbox.msf is out of date

This fixes a related problem I discovered, which may or may not be what you saw
(probably not) - if you try to get new mail after we've opened the Inbox.msf
file, but the Inbox.msf file is out of date, we were failing to get new mail -
this is a regression due to the global inbox stuff, I believe...

I'll keep trying to reproduce the problem you saw.

Comment 6

[(not reading, please use [e-mail] instead)]

Comment on attachment 155831 [details] [diff] [review]
fix for getting new mail when Inbox.msf is out of date

r/a=sspitzer

Comment 7

[David :Bienvenu]

last patch checked into trunk and 1.0 branch - still trying to see if I can
reproduce other problems. I tried corrupting an Inbox.msf file and it was
regenerated correctly, before mail was fetched.

Comment 8

[David :Bienvenu]

Ironically, my power went out last night and when I launched after that, I did
see similar symptoms, especially junk mail not getting filtered. Not only was
the Inbox.msf out of date, and regenerated, but the panacea.dat was invalid as
well, which might be involved here.

Comment 9

[:aceman]

Maybe the fix in bug 221797 was not enough for this case...

Comment 10

[Max Alekseyev]

I've just got the same problem with Mozilla OS/2 build 2004082208.

Comment 11

[Sam Little]

FWIW, I'm also seeing a similar problem in OS/2 (build 2004081920). If I have a
system crash, on restarting Mozilla, the Inbox.msf file in "Local Folders" gets
zeroed out and won't rebuild.

A workaround seems to be to close Mozilla, delete Inbox.msf in Local Folders,
and rename the Inbox file to something else (InboxOld, for instance). Opening
Mozilla mail and choosing another, undamaged folder before chosing the "new"
InboxOld folder will result in a reindex. Then I can close Mozilla, rename
InboxOld and InboxOld.msf to Inbox and Inbox.msf and everything is hunky-dory
again. 

But I haven't found a step in there that I can skip to get it to work....

Comment 12

[Ben]

I see this problem with empty msf files (zero-size), not only for the Inbox, but
for any folder where I automatically filter messages to.

As such, closing TB, deleting the msf file and restarting TB solves the problem.
The folder files themselves are not corrupted in my case.

Compacting the folder with the empty msf file does not help. TB does not
regenerate the msf file, but rather keeps it empty. This means that the unread
count is not shown and the space and N keys don't work.

Comment 13

[Doug Wright]

Can someone knowledgeable take a look at 265930 and see if it's related to this?

Comment 14

[David :Bienvenu]

I've fixed several issues in this area today and yesterday. Can you try
tomorrow's nightly .8/.9 build or trunk build?

Comment 15

[Doug Wright]

This is now working fine for me with Tb 1.0. Is anyone still affected?

Comment 16

[David :Bienvenu]

marking fixed. no response...