156591 - Corrupt mail database: Truncated messages and misbehaving filters

Status: VERIFIED DUPLICATE of bug 136559

(MailNews Core :: Backend, defect)

Description

[Rob North]

Using Mozilla 1.0 (build 2002053012)
This problem's severity has been increasing over time.

Phase 1:
(Occured after ~2-3 weeks of MailNews use)
Would display no header, or body, yet would show up in the mail list.
I checked back to the underlying mail files. The message existed.
Moving the message would only move the mail list entry, and create a minimal
entry for message in the underlying mail file.

Phase 2:
(Has been occuring for ~1 week, daily e-mail downloads)
I saw messages that should match one filter, but fell beck onto a catch-all
filter. Some of these messages were truncated, and some were complete.
I could find intact copies of the truncated messages in the inbox mail file.

Phase 3:
(Occured today)
In addition to the symptoms in Phase2, I'm now seeing mail list entries bring up
incorrect messages. Normally messages from same folder, but in one case a
message that should be in different folder, and message was truncated.
Attempting to copy this message to a differnt folder resulted in a blank messsage
being copied: no header, or body, but with a valid entry in the mail list.
Searched the inbox mail file for messsage IDs of couple of truncated messages.
Inbox file still contains complete copies of the truncated messages.
Additionally the mail list entry which referred to a message that should be in
differnt folder was still present after restart of mozilla. Did not check any
other faulty mai list entries.

Other points of note:
This problem only seems to be occuring on filtered messages.
Messages in the in-box seem to be intact.


The structure of my my filters:
All mail comes in on one POP account. This account has a number of filters.
Most filters move messages to inbox subdiretories.
3 Other filters move messages to a dummy account's in-box, and it's sub drectories.

Comment 1

[David :Bienvenu]

I believe this is a dup of a bug that has been fixed for a while now. You should
be running a much more recent build (I think any trunk build after 06/14 would
be good). Navin can tell you for sure.

Comment 2

[Rob North]

Bienvenu, Is Bug 122361 the bug you think was a duplicate?
Navin, would you care to comment?

Comment 3

[David :Bienvenu]

that's one of them - there are others referred to in the comments for bug 122361.

Comment 4

[Navin Gupta]

Did mozilla 1.0 branched from mozilla 1.0 branch. That happened on 04/09. The
fix in bug 136636 was checked on 04/14 on mozilla 1.0 branch. I don't know if we
missed mozilla1.0 builds. If we have missed it then this is a dup of bug 136636

Comment 5

[Navin Gupta]

From tree depcition www.mozilla.org/roadmap it does appear we branched for
mozilla 1.0 from 1.0 branch. Created a static tag may be. So I'll mark this as
dup of bug 136636 that contained the fix for this problem or rather mark as dup
of bug 136559 which is the correct dup bug. 

Please use latest mozilla builds like the mozilla 1.0.1 build but don't use
mozilla 1.1 alpha, that has other problems (bug 150716) 

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

Comment 6

[laurel]

marking verified as duplciate