Closed Bug 512917 Opened 15 years ago Closed 15 years ago

gloda needs to mark some messages as damaged and never try and index them

Categories

(MailNews Core :: Database, defect)

Product:
MailNews Core
Component:
Database
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
Thunderbird 3.0rc1

People

(Reporter: asuth, Assigned: asuth)

References

Details

(Whiteboard: [no l10n impact][gloda key][fixed in correctness patch]) 

Some messages are just bad eggs.  Gloda needs to give up on them and not try to index them again.  It may be worth delineating two levels of badness such as "bad to the bone", and "poseur bad".  The former cannot be rehabilitated, perhaps because it was no author.  The latter may just seem bad because of bugs in Thunderbird and should be re-tried when a Thunderbird upgrade (or notable nightly change) occurs.
Whiteboard: [gloda key]
In reality, this is blocking.
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
Flags: blocking-thunderbird3?
agreed
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Whiteboard: [gloda key] → [no l10n impact][gloda key]
And I'm pretty sure there should be a way to inform user, that there are some messages not indexed, so one can fix them, delete or move...
Now that bug 505221 is fixed, I hope we'll have taken a big bite out of the mime crashers in Thunderbird, fwiw.
test_index_bad_messages.js in the gloda correctness patch verifies this and passes.
Whiteboard: [no l10n impact][gloda key] → [no l10n impact][gloda key][fixed in correctness patch]
Fixed in gloda correctness patch tracked on bug 465618.
trunk commit: http://hg.mozilla.org/comm-central/rev/413b2018349c
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Keywords: fixed-seamonkey2.0.1
Keywords: fixed-seamonkey2.0.1
You need to log in before you can comment on or make changes to this bug.