Closed
Bug 306446
Opened 19 years ago
Closed 19 years ago
No way to reclassify messages in "junk" folder as "not junk"
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: boutell, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 When I set up the junk filtering features, I'm able to classify messages in my inbox as "junk." Messages that are sniffed out as junk then begin appearing in the "junk" folder. This is fine. However, when I look in the "junk" folder and select a message that I recognize is NOT spam, I still see the "junk" button in the toolbar. Thunderbird should know what the junk folder is and provide the ability to un-junk messages found there. I notice that I can click "Junk" (redundantly classifying the message as junk...) and then the "Not Junk" button appears. I'm experimenting and don't know yet whether this actually has the right effect on the classifiction of future messages. But it's not a friendly UI for un-junking things that Thunderbird should already know are classified as junk. Reproducible: Always Steps to Reproduce: 1. Turn on adaptive junk filtering with default settings 2. Use the junk button to classify a message as junk 3. Go to junk folder 4. Select the junked message 5. Notice that "junk" button appears, where "not junk" ought to appear Actual Results: "Junk" appears even though the message is already in the "junk" folder Expected Results: "Not Junk" should appear. Also, un-junking the message should move it back to the inbox, at least optionally.
| Reporter | ||
Comment 1•19 years ago
|
||
Hmm, I now see that messages do show up as "JUNK" with a "NOT JUNK" button available if the classifier currently thinks they are junk. Sometimes I have things in my junk folder that the classifier doesn't currently believe to be junk, perhaps? Not sure, yet, so I'll stop calling this a bug. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•