322978 - "Mark messages determined to be Junk as read": Option not working, mails are always marked as read

Status: RESOLVED DUPLICATE of bug 306026

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Johannes Kastl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8) Gecko/20051219 SeaMonkey/1.0b Mnenhy/0.7.3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8) Gecko/20051219 SeaMonkey/1.0b Mnenhy/0.7.3.0

In the Junk filter controls the option "Mark messages determined to be Junk as read" is not working. no matter if it is checked or not, all mails manually marked as junk are marked as read.
Maybe related to https://bugzilla.mozilla.org/show_bug.cgi?id=253234



Reproducible: Always

Steps to Reproduce:
1. Find a mail that is unread and not already marked as junk
2. Look at the options, and uncheck the "Mark messages determined to be Junk as read" box
3. Mark that mail as junk

=> it gets marked as junk, and it is marked as read.

Actual Results:  
The option is not working.

Expected Results:  
The Mail should ONLY be marked as read when the option is checked (i.e. "on").

Happens on XP and Linux, with 
SeaMonkey 1.0b
Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8) Gecko/20051219 SeaMonkey/1.0b Mnenhy/0.7.3.0

and newer, both trunk and branch (1.8.0 and 1.8)

Comment 1

[Bruno 'Aqualon' Escherl]

According to http://lxr.mozilla.org/seamonkey/source/mailnews/base/src/nsMsgDBView.cpp#2889 this is intentionally behaviour. The pref "mailnews.ui.junk.manualMarkAsJunkMarksRead" didn't work for me, but you could give it a try.

Comment 2

[Johannes Kastl]

(In reply to comment #1)
> "mailnews.ui.junk.manualMarkAsJunkMarksRead" didn't work for me, but you could
> give it a try.

I do not have this one, I only got mail.server.default.markAsReadOnSpam, which is false at the Moment.

Ill try yours, if it is a Seamonkey one, not Thunderbird.

Comment 3

[Bruno 'Aqualon' Escherl]

This is fixed in (In reply to comment #1)
> According to
> http://lxr.mozilla.org/seamonkey/source/mailnews/base/src/nsMsgDBView.cpp#2889
> this is intentionally behaviour.
This was only fixed in trunk by patch for bug 306026. Should this bug be marked as duplicate or keep it open for a future patch perhaps going into SeaMonkey 1.1?

Comment 4

[Mike Cowperthwaite]

This is a dupe, and the code is *in* Seamonkey for trunk builds.  The 1.0 
branch does not have the fix, and I doubt it's going to be allowed in at this point.  You can request approval, on the patch at that bug, for inclusion in 
a branch build; it's up to drivers whether it will be included.

*** This bug has been marked as a duplicate of 306026 ***