mail.strict_threading + mail.correct_threading ignored in Tb3 beta2

NEW
Unassigned

Status

10 years ago
8 years ago

People

(Reporter: LpSolit, Unassigned)

Tracking

Trunk
x86
Linux
Bug Flags:
blocking-thunderbird3 -

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
Since I upgraded Thunderbird 3 from beta1 to beta2, it seems that the mail.strict_threading and mail.correct_threading prefs no longer work. New incoming bugmail is not in correct threads.

wicked, can you confirm?
I haven't witnessed any threading problems lately but I don't think I have received any problematic bugmail (like summary changes) recently. I also keep all the "new bugmail" so I have valid "pointed to msgid" messages for my threads. I haven't been looking for problems that hard either. :)

I also just tried to rebuild my BMO bugmail and Bugzilla ML folder indexes and threads seem to still be in correct order. So, unfortunately, I can't confirm this problem.

For the record, I'm currently using "Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20090226 Shredder/3.0b3pre ID:20090226032557" and usually update every few weeks for latest nightly.

BTW, you'd might want to consider disable mail.strict_threading and mail.thread_without_re (but leave mail.correct_threading enabled to enable my threading fixes!) so you get threading even for reply subject lines that have invalid reference headers (happens for mailman/newgroup gated mailing lists that are used). For full reference, please read https://wiki.mozilla.org/MailNews:Message_Threading
(Reporter)

Comment 2

9 years ago
This bug still exists in beta3. Having threads broken is really a pain.
Flags: blocking-thunderbird3?

Comment 3

9 years ago
minusing - can you give an example mailbox that doesn't thread correctly with the prefs set?
Flags: blocking-thunderbird3? → blocking-thunderbird3-
(Reporter)

Comment 4

9 years ago
These two are not in the same thread:


From - Wed Mar  4 10:54:58 2009
X-Account-Key: account2
X-UIDL: GmailId11fcedbb00fd805c
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Delivered-To: lpsolit@gmail.com
Received: by 10.181.27.18 with SMTP id e18cs32162bkj;
        Tue, 3 Mar 2009 16:21:59 -0800 (PST)
Received: by 10.114.150.1 with SMTP id x1mr3720298wad.93.1236126118242;
        Tue, 03 Mar 2009 16:21:58 -0800 (PST)
Return-Path: <bugzilla-daemon@mozilla.org>
Received: from dm-mail01.mozilla.org (dm-mail01.mozilla.org [63.245.208.150])
        by mx.google.com with ESMTP id k37si932237waf.5.2009.03.03.16.21.57;
        Tue, 03 Mar 2009 16:21:58 -0800 (PST)
Received-SPF: pass (google.com: domain of bugzilla-daemon@mozilla.org designates 63.245.208.150 as permitted sender) client-ip=63.245.208.150;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of bugzilla-daemon@mozilla.org designates 63.245.208.150 as permitted sender) smtp.mail=bugzilla-daemon@mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Received: from webapp-out.mozilla.org (mrapp51.mozilla.org [10.2.81.51])
	by dm-mail01.mozilla.org (Postfix) with ESMTP id 5C6DAB84BE
	for <LpSolit@gmail.com>; Tue,  3 Mar 2009 16:21:47 -0800 (PST)
Received: from mrapp51.mozilla.org (mrapp51.mozilla.org [127.0.0.1])
	by webapp-out.mozilla.org (8.13.8/8.13.8) with ESMTP id n240LlGR012256
	for <LpSolit@gmail.com>; Tue, 3 Mar 2009 16:21:47 -0800
Received: (from root@localhost)
	by mrapp51.mozilla.org (8.13.8/8.13.8/Submit) id n240Lkae012251;
	Tue, 3 Mar 2009 16:21:46 -0800
Date: Tue, 3 Mar 2009 16:21:46 -0800
Message-Id: <200903040021.n240Lkae012251@mrapp51.mozilla.org>
From: bugzilla-daemon@mozilla.org
To: LpSolit@gmail.com
Subject: [Bug 480235] mail.strict_threading + mail.correct_threading ignored
 in Tb3 beta2
X-Bugzilla-Reason: Reporter
X-Bugzilla-Type: newchanged
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Classification: Client Software
X-Bugzilla-Product: Thunderbird
X-Bugzilla-Component: Preferences
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wicked@sci.fi
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: --
X-Bugzilla-Assigned-To: nobody@mozilla.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: 
In-Reply-To: <bug-480235-120380@https.bugzilla.mozilla.org/>
References: <bug-480235-120380@https.bugzilla.mozilla.org/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

Do not reply to this email.  You can add comments to this bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=480235





--- Comment #1 from Teemu Mannermaa <wicked@sci.fi>  2009-03-03 16:21:37 PST ---
I haven't witnessed any threading problems lately but I don't think I have
received any problematic bugmail (like summary changes) recently. I also keep
all the "new bugmail" so I have valid "pointed to msgid" messages for my
threads. I haven't been looking for problems that hard either. :)

I also just tried to rebuild my BMO bugmail and Bugzilla ML folder indexes and
threads seem to still be in correct order. So, unfortunately, I can't confirm
this problem.

For the record, I'm currently using "Mozilla/5.0 (Windows; U; Windows NT 6.0;
en-US; rv:1.9.1b3pre) Gecko/20090226 Shredder/3.0b3pre ID:20090226032557" and
usually update every few weeks for latest nightly.

BTW, you'd might want to consider disable mail.strict_threading and
mail.thread_without_re (but leave mail.correct_threading enabled to enable my
threading fixes!) so you get threading even for reply subject lines that have
invalid reference headers (happens for mailman/newgroup gated mailing lists
that are used). For full reference, please read
https://wiki.mozilla.org/MailNews:Message_Threading

-- 
Configure bugmail: https://bugzilla.mozilla.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.




From - Tue Aug 11 01:39:33 2009
X-Account-Key: account2
X-UIDL: GmailId12306ade54297637
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Delivered-To: lpsolit@gmail.com
Received: by 10.204.100.11 with SMTP id w11cs186168bkn;
        Mon, 10 Aug 2009 16:39:04 -0700 (PDT)
Received: by 10.115.109.1 with SMTP id l1mr7041583wam.174.1249947543042;
        Mon, 10 Aug 2009 16:39:03 -0700 (PDT)
Return-Path: <bugzilla-daemon@mozilla.org>
Received: from dm-mail02.mozilla.org (dm-mail02.mozilla.org [63.245.208.176])
        by mx.google.com with ESMTP id 29si13386297pzk.34.2009.08.10.16.39.02;
        Mon, 10 Aug 2009 16:39:03 -0700 (PDT)
Received-SPF: pass (google.com: domain of bugzilla-daemon@mozilla.org designates 63.245.208.176 as permitted sender) client-ip=63.245.208.176;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of bugzilla-daemon@mozilla.org designates 63.245.208.176 as permitted sender) smtp.mail=bugzilla-daemon@mozilla.org
X-Virus-Scanned: amavisd-new at mozilla.org
Received: from webapp-out.mozilla.org (pm-app-bugs01.mozilla.org [10.2.82.51])
	by dm-mail02.mozilla.org (Postfix) with ESMTP id C8DB5824252
	for <LpSolit@gmail.com>; Mon, 10 Aug 2009 16:38:57 -0700 (PDT)
Received: from pm-app-bugs01.mozilla.org (localhost.localdomain [127.0.0.1])
	by webapp-out.mozilla.org (8.13.8/8.13.8) with ESMTP id n7ANcvu9025016
	for <LpSolit@gmail.com>; Mon, 10 Aug 2009 16:38:57 -0700
Received: (from root@localhost)
	by pm-app-bugs01.mozilla.org (8.13.8/8.13.8/Submit) id n7ANcuSU025011;
	Mon, 10 Aug 2009 16:38:56 -0700
Date: Mon, 10 Aug 2009 16:38:56 -0700
Message-Id: <200908102338.n7ANcuSU025011@pm-app-bugs01.mozilla.org>
From: bugzilla-daemon@mozilla.org
To: LpSolit@gmail.com
Subject: [Bug 480235] mail.strict_threading + mail.correct_threading ignored
 in Tb3 beta2
X-Bugzilla-Reason: Reporter
X-Bugzilla-Type: newchanged
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Classification: Client Software
X-Bugzilla-Product: Thunderbird
X-Bugzilla-Component: Preferences
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bienvenu@nventure.com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: --
X-Bugzilla-Assigned-To: nobody@mozilla.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: CC Flag
In-Reply-To: <bug-480235-120380@https.bugzilla.mozilla.org/>
References: <bug-480235-120380@https.bugzilla.mozilla.org/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

Do not reply to this email.  You can add comments to this bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=480235


David :Bienvenu <bienvenu@nventure.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bienvenu@nventure.com
               Flag|blocking-thunderbird3?      |blocking-thunderbird3-




--- Comment #3 from David :Bienvenu <bienvenu@nventure.com>  2009-08-10 16:38:50 PDT ---
minusing - can you give an example mailbox that doesn't thread correctly with
the prefs set?

-- 
Configure bugmail: https://bugzilla.mozilla.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.
(Reporter)

Comment 5

9 years ago
(In reply to comment #1)
> BTW, you'd might want to consider disable mail.strict_threading and
> mail.thread_without_re (but leave mail.correct_threading enabled to enable my
> threading fixes!)

For the record, that's what I have already, since beta 1.

Comment 6

9 years ago
 Frédéric are you still seeing this?
(Reporter)

Comment 7

9 years ago
(In reply to comment #6)
>  Frédéric are you still seeing this?

Oh yes! :( (Tb 3.0.3)

Comment 8

8 years ago
I'm still having threading problems as well (3.0.4). My related config settings are as follows:

mail.strict_threading;false
mail.thread_without_re;true
mail.correct_threading;true

Yet, In-Reply-To: still seems to take precedence over Subject:. This is particularly annoying in mailing lists where people reply to messages to start a new thread (bad list etiquette, I know, but people still do it). It seems like turning strict_threading off should solve the problem, but it doesn't.
(Reporter)

Comment 9

8 years ago
Maybe this helps: compacting the folder (manually) fixes the problem. Threads are correct again. But this should be done automatically, ideally.
You need to log in before you can comment on or make changes to this bug.