unmarking Junk flag resets read status

RESOLVED INVALID

Status

Thunderbird
Mail Window Front End
RESOLVED INVALID
9 years ago
9 years ago

People

(Reporter: Gary Hooper, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [doc comment 5])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7
Build Identifier: 8.0b6

i have an unread message not marked as junk.  i mark it as junk, and it correctly sets the message as read.  however, if i have a read message marked as junk, and i unset the junk marking, the message is also marked as unread.  it should remain as read.

Reproducible: Always

Comment 1

9 years ago
Assigning to Thunderbird as this is not unique to Penelope.
Assignee: mozilla-bugs → nobody
Component: Mail Window → Mail Window Front End
Product: Penelope → Thunderbird
QA Contact: mail-window → front-end
It is the same here on 

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090616 Lightning/1.0pre Shredder/3.0b3pre ID:20090616031827

but I think is an desired behavior (for me is right).
OS: Mac OS X → All
(In reply to comment #2)
> It is the same here on 

So you reproduce ?
 
> but I think is an desired behavior (for me is right).

I don't If I have an unread message mark it as junk - remove the junk flag read status stays the same.
(In reply to comment #3)
> (In reply to comment #2)
> > It is the same here on 
> 
> So you reproduce ?

yes, it is. 


> I don't If I have an unread message mark it as junk - remove the junk flag read
> status stays the same.

I think that is marked as unred (when is unmarkes as junk) for better visibility, but maybe I'm wrong.

Comment 5

9 years ago
this is deliberate - if you don't want this behavior, you can toggle the hidden pref mail.spam.markAsNotJunkMarksUnRead using the config editor.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
Whiteboard: [doc comment 5]
You need to log in before you can comment on or make changes to this bug.