GNOME Bugzilla – Bug 272027
Don't mark Junk automatically as read
Last modified: 2013-09-10 14:04:26 UTC
Description of Problem: Messages that are moved to Junk (by the spamassasin filters) are automatically marked as read. This doesn't tell you that you've got new messages, so you don't check the Junk folder, and you can't remember to train the filters. I've had non-Junk messages end up there, but I only saw them when I clicked on the Junk folder.
workaround could be: add as the last incoming filter: If [Status][is][Junk] Then [Move to folder][INBOX/spam],[Stop Processing] so it does not get marked as read. it was posted by Eric Lambart on bug 260830.
Raised the Severity and set a Target Milestone for 2.3. Accepted this bug as well. This is a serious usability issue IMHO that should be resolved ASAP. It even came up on the mailing lists, so it really strikes the users. Wondering about the RFE keyword, as I consider this a bug, rather than an enhancement. Current behavior is broken.
*** Bug 305568 has been marked as a duplicate of this bug. ***
still in 2.5.4, retargetting
this isn't an enhancement, this is a bug, because i miss mail.
varadhan, jony? any comments? i miss email because of this bug, i expect new emails in a folder to bold this folder.
Ubuntu bug about that: https://launchpad.net/products/evolution/+bug/49703
Bumping version, still happens with 2.9.6.
Created attachment 94420 [details] [review] Preliminary patch! Needs some more testing !
Johnny I dont think you should reset the seen flag when it is done by pressing JUNK. It means that the user has seen it. It should be unread only if it is done through automatic junk filtering
Bumping version to a stable release.
just a ping -- per srag's comment, all we would need to do is take out the proposed changes to em-folder-view.c. If indeed this is correct, can we get this done?
Created attachment 116208 [details] [review] patch adapted to evolution-2.22.3.1 as shipped by ubuntu hardy adapted above patch to keep CAMEL_MESSAGE_NOTJUNK which seems to have been added recently
I disagree with Srinivasa Ragavan and don't think it's necessary to mark mail as read which has been explicitly marked junk via the button. This may be an attractive feature for some, but I would want to turn it off. Mail should only be marked read if I've seen it or explicitly marked it as such. This patch has been around for a year and is required to enable junk filtering for high volume mail accounts
cwehrmann, Its the same behavior when you delete a unread mail. Its set as deleted and seen. This way, the Junk folder shows some unread mails, that are automatically junked by the filter. So the user can validate at times. Also, you shouldn't set NOTJUNK. That has to be set only on mails that the user sets as NotJunk.
srag, I am unsure on your comment "you shouldn't set NOTJUNK". This was already in the code, and was not changed by the patch. Are you saying this was wrong in the code? Also -- although I am not yet taking a side on this... 1. if we mark a message as junk, then it is also marked as read. 2. if we mark a message as not junk, then -- currenlty -- its read status is not changed. This sounds a bit inconsistent: if an user's action is to force CAMEL_MESSAGE_SEEN, then it should do so at all points. Now taking a side: Personally, I am unsure if this is indeed inconsistent or not, but I think it is not quite right. Here's the reasoning: if I -- the user -- mark a junked message as not junk, this is because I am checking the junk folder for false-positives. I am not really *reading* the email, I just decided it is *not* junk, and should be marked so. I will probably -- later on -- go back to my Inbox and really, really, read the email... so I would like it to be marked NOT seen. On the other hand, if I explicitly mark a message as junk, then I see no reason for it to be marked unread -- I am done with it. So. Although I agree with you on " marking as junk also marks as read", I think we should force unread if a message is marked NOTJUNK. Does this warrant a new bug?
(In reply to comment #16) > srag, I am unsure on your comment "you shouldn't set NOTJUNK". This was already > in the code, and was not changed by the patch. Are you saying this was wrong in > the code? Ignore it, I was sleepy probably. > > Also -- although I am not yet taking a side on this... > > 1. if we mark a message as junk, then it is also marked as read. > > 2. if we mark a message as not junk, then -- currenlty -- its read status is > not changed. > > This sounds a bit inconsistent: if an user's action is to force > CAMEL_MESSAGE_SEEN, then it should do so at all points. > > Now taking a side: > > Personally, I am unsure if this is indeed inconsistent or not, but I think it > is not quite right. > > Here's the reasoning: if I -- the user -- mark a junked message as not junk, > this is because I am checking the junk folder for false-positives. I am not > really *reading* the email, I just decided it is *not* junk, and should be > marked so. I will probably -- later on -- go back to my Inbox and really, > really, read the email... so I would like it to be marked NOT seen. > > On the other hand, if I explicitly mark a message as junk, then I see no reason > for it to be marked unread -- I am done with it. > > So. Although I agree with you on " marking as junk also marks as read", I think > we should force unread if a message is marked NOTJUNK. When a mail comes, it is unread. When spam filter moves it to junk folder it will be unread. All such mails the user focus on the junk folder will be such mails. No need to explicitly set as unread. In a normal lifecycle, it doesnt affect anything or cause anything. > > Does this warrant a new bug? >
RFC 2060 describes the seen flag as an indicator for: "Message has been read". If I open with an email I expect the read flag to be set, thus I expect mails which I didn't interact with to have the flag set to unread. Evolutions junk mail filter breaks these exceptions: mail which is automatically handled has its read status altered. This is especially bad since: * bayes junk filters rely on user interaction to learn about false positives. * junk mail is hidden in original folder * no notification about new junk in the gui Not toggling the read flag for automatically detected junk would fix this issue. If I manually mark email as junk, I'd say this clearly is an interaction and justifies marking as read, but IMHO this is a different issue and works as expected. The patch works fine.
I think this changed in the newest version of evolution and this bug can be closed now. (At least it works for me, Evolution 2.26.2, Debian)
Johnny, Milan fixed this on bug 579550. As such, I will go ahead and mark this one as a duplicate, if you do not mind. *** This bug has been marked as a duplicate of bug 579550 ***