Closed Bug 449444 Opened 16 years ago Closed 15 years ago

New mail threads appear buried inside old ones

Categories

(MailNews Core :: Backend, defect, P3)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Thunderbird 3.0rc1

People

(Reporter: nelson, Unassigned)

Details

(Keywords: qawanted, regression)

Using Gecko/2008080600 (SM trunk nightly) Incoming emails that do not reference any other mails, and hence should be shown as starting new threads instead get buried down inside other threads. This is seen in both POP3 and IMAP accounts. Rebuilding the Summary file (bonking the "Rebuild Summary File" button in the folder's properties dialog) fixes this (makes the new thread appear to be a separate thread again. Was not seen with 2008080100, but is being seen A LOT today. I'm having to rebuild the summary file of most folders that I read to see the threads threaded properly.
Marking as qawanted since it would be interesting to pin down the regression range more tightly, ideally to the point of associating it with a checkin. Marking as a blocker since it's a regression, and an annoying one at that.
Flags: blocking-thunderbird3?
Keywords: qawanted
Priority: -- → P3
Target Milestone: --- → Thunderbird 3.0rc1
Nelson, are the new messages buried in the thread because they have the same subject? We did change the threading rules IIRC. (changing the flag to correspond to what dmose said he did =)
Flags: blocking-thunderbird3? → blocking-thunderbird3+
David, the problem is seen with new messages with new (different) subjects.
Nelson, still see this?
Is anyone seeing this anymore? There have been a fair number of fixes, and no more reports that I know of about issues like this. My inclination is to take it off the blocking list unless someone is still seeing it.
(In reply to comment #5) > Is anyone seeing this anymore? assuming not. I haven't seen this in a long time => WFM but please reopen if you can reproduce with current trunk or recent beta.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.