Bug 617987 - Insufficient email threading
Summary: Insufficient email threading
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: thunderbird
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Red Hat Gecko Maintainer
QA Contact: desktop-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-25 13:08 UTC by Tomas Von Veschler
Modified: 2010-07-25 13:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-07-25 13:42:07 UTC

Attachments (Terms of Use)

Description Tomas Von Veschler 2010-07-25 13:08:08 UTC
Description of problem:

thunderbird 3 now uses by default uses strict thread sorting. This is, only group by thread those emails following the RFC (References, In-Reply-To) but not by subject.

Suggestion is to change the following thunderbird config values to:

mail.correct_threading: false (default true)
mail.strict_threading: false (default true)
mail.thread_without_re: true (default false)

This will result in a much better threading logic. It can be manually changed from: Edit -> Preferences -> Advanced -> Config Editor (if you had already emails indexed a "Rebuild Index" is needed: Right click over an email folder -> Properties -> Rebuild Index)

While my impression is that the mozilla guys want to enforce standards, which is good, the reality is that there're far too many devices today that can send emails, including mobiles, tablets, etc which are usually v1.0 versions, have several limitations in terms of hardware and finally can not being so strict. Following mailing lists with default settings results in a poor user experience.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install thunderbird
2. Get email
3. Sort by thread
Actual results:

Only few emails get grouped by thread

Expected results:

All/most emails are grouped in threads/conversations

Additional info:

Comment 2 RHEL Product and Program Management 2010-07-25 13:37:37 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Christopher Aillon 2010-07-25 13:42:07 UTC
While I respect your opinion and don't necessarily disagree, I am not going to modify default standards compliance behavior.  Having FF/TB treat standards differently based on where you get your package from is something that is just not going to happen on my watch.  This change needs to happen upstream or not at all.

Note You need to log in before you can comment on or make changes to this bug.