Closed
Bug 275771
Opened 20 years ago
Closed 20 years ago
Watch and Ignore no longer work on newsgroup threads after installing Enigmail
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jdg, Assigned: mscott)
Details
After installing the Enigmail extension, the commands "Ignore thread" and "Watch thread" under the Messages menu, and their keyboard equivalents K and W, no longer work on any newsgroup thread. The commands, whether entered by mouse or keyboard, are simply ignored. This happens both under Thunderbird 0.8 and the recent 1.0 release. I apologize for not knowing how to tell whether the actual problem lies in TB or the extension. If anyone can suggest ways to investigate this question, I'll be happy to try.
| Reporter | ||
Comment 1•20 years ago
|
||
Let me be more precise: the "watch thread" command is simply ignored. The "ignore thread" command behaves as "mark thread read" (T on the keyboard), but does not perform its proper function of preventing me from seeing subsequent posts in that thread.
Comment 2•20 years ago
|
||
I'd suggest contacting the enigmail people - I don't think it's a thunderbird problem.
| Reporter | ||
Comment 3•20 years ago
|
||
Reported for Enigmail also, at http://bugzilla.mozdev.org/show_bug.cgi?id=8585
Comment 4•20 years ago
|
||
I'm the author of Enigmail. I can't confirm this, it works fine with Enigmail enabled. Actually, Enigmail does not do anything related to the thread pane, nor does it overlay any of the functions in the View and Message menus, nor does it redefine the keys K and W
Comment 5•20 years ago
|
||
do you have any other extensions besides enigmail? It does seem unlikely that enigmail could be messing with this...
| Reporter | ||
Comment 6•20 years ago
|
||
At the urging of Barry Porter barry@bpuk.net, I created a new profile as instructed at http://enigmail.mozdev.org/newprofile.html, and it made the problem go away. I don't know why.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•