Open Bug 799040 Opened 11 years ago Updated 8 months ago

"Ignore Subthread" works incorrectly

Categories

(MailNews Core :: Backend, defect)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

People

(Reporter: robert.h.henson, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

Added a "bozo" filter - If "From" contains "bozo's e-mail address" then "ignore subthread". 


Actual results:

The filter works, but the remainder of the thread no longer responds to the View > Threads > Threads with unread" setting and stays visible and underlined all the time, even when there is no new mail in the thread. Eventually the list of message fills the headers pane making further reading difficult. 


Expected results:

The message should not remain in view and underlined in the message header pane when "Threads with Unread" is selected.
New messages which are posted to the ignored subthread do not show up as intended, but they show up as unread messages in the folder tree entry for the group. It is necessary to "mark newsgroup read" to get rid of the entries. Ignored messages should not show up anywhere.
i had some strangeness with ignore this weekend (not with filters though, just manual marking), but i ignored it :)

mrmazda, can you reproduce this?
Can confirm that answers to postings with "ignore subthread" are listed as x unread in the message pane and the thread remains underlined while it is collapsed although it won't offer these messages in the message-tree when expanding it. (underline will also disappear then)

(Seamonkey on WinXP x86 also affected, confirming and moving to MailNewsCore and AllPlattforms/OS)
Status: UNCONFIRMED → NEW
Component: Folder and Message Lists → Backend
Ever confirmed: true
OS: Windows 7 → All
Product: Thunderbird → MailNews Core
Hardware: x86_64 → All
Summary: "Ignore Subthread" filter works incorrectly → "Ignore Subthread" works incorrectly
This bug has not even been assigned to anyone yet. Is there no interest whatever in fixing this coding error?
There is interest, but there is also lack of necessary volunteer manpower.
When someone with both the time and interest comes along they will assign the bug to themselves. That could be a short time, or it could be a very long time.

It may help if you can narrow the time range in which the behavior began.
As far as I know, it has been there since the "ignore subthread" option was added. It certainly has not functioned correctly since I first tried to use it.
Severity: major → normal
duplicate of bug 595005?
Wayne,

Going by just the two bugs' summary, it is unlikely one is a dupe of the other.

At the moment, this is (for my own use-case) the worst bug in TB/SM.

It is hard to kill-file jerks on Usenet with SM.

If I kill *threads* where $JERK posts, I might miss interesting threads where $JERK's disruption is minimal.

If I kill *subthreads* of $JERK, TB/SM does not mark $JERK's message (and its children) as read, meaning the entire thread still shows up in the "Show only threads with unread" view, even if I actually delete these messages manually after the fact. Something is broken in the index.

Regards.
(In reply to Mason from comment #10)
> Wayne,
> 
> Going by just the two bugs' summary, it is unlikely one is a dupe of the
> other.
> 
> At the moment, this is (for my own use-case) the worst bug in TB/SM.
> 
> It is hard to kill-file jerks on Usenet with SM.
> 
> If I kill *threads* where $JERK posts, I might miss interesting threads
> where $JERK's disruption is minimal.
> 
> If I kill *subthreads* of $JERK, TB/SM does not mark $JERK's message (and
> its children) as read, meaning the entire thread still shows up in the "Show
> only threads with unread" view, even if I actually delete these messages
> manually after the fact. Something is broken in the index.
> 
> Regards.

Agreed. This is still the worst bug left in Thunderbird, and still causes a great deal of difficulty to newsgroup users. I can't see any connection to the other bug, and this should not be marked as a duplicate.
Yeah, I tried ignoring Threads and SubThreads, and the "always underlined" issue got me to stop doing that; I just nuke (delete) the offending messages instead (but of course I get to see the stupid replies). Not sure if it's limited to Ignore SubThread, or if Ignore Thread is also affected. The unread message count also counts the ignored messages, making one wonder "where are those unread messages?" ...
See Also: → 595005
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.