Note: There are a few cases of duplicates in user autocompletion which are being worked on.

"delete mail marked as junk in this folder" doesn't clear 'new' flag on account (or biff tray icon)

NEW
Unassigned

Status

MailNews Core
Backend
--
minor
14 years ago
4 years ago

People

(Reporter: Jochen Eisinger, Unassigned)

Tracking

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [patchlove][has draft patch][needs new assignee])

Attachments

(1 obsolete attachment)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040118
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040118

Every nigh there are about 8-10 mails that manage to pass my spam filters. Those
end up in my (IMAP) inbox - and get automatically marked as junk. Since I don't
automatically move/delete mails marked as junk, they remain there.

Each morning I delete those using "Tools -> Delete mails marked as junk in this
folder". This works fine so far, however the biff state isn't reset (in case
there are no other new mails).

Reproducible: Always

Steps to Reproduce:

Comment 1

14 years ago
Same happens on Windows XP, with Mozilla 1.6 mail client using IMAP.

"Delete mail marked as junk" does not remove status bar notification about new
mails when all unread new mails are deleted.
Mail client should do a check after deleting junk mails whether
new-mail-notification is still accurate.

Comment 2

14 years ago
If you simply delete a new message using the context menu's Delete, that also 
does not clear the notification flags: bug 157115.

Comment 3

13 years ago
*** Bug 251451 has been marked as a duplicate of this bug. ***

Comment 4

13 years ago
Same problem in Thunderbird, by the way (seen in 0.7 & 0.8, Win2K).
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Summary: "delete mail marked as junk in this folder" doesn't reset statusbar biff → "delete mail marked as junk in this folder" doesn't clear 'new' flag on account (or biff tray icon)
Product: Browser → Seamonkey

Updated

12 years ago
Assignee: sspitzer → mail
Created attachment 196474 [details] [diff] [review]
half-baked attempt

I'm not sure this works at all since I can't build MailNews at the moment, but
it should have some impact, at least.

I should rather wait and not attach a patch before I know perfectly well what's
going on, but since I'm fairly certain this should work in most cases, I
thought I'd ask for some help in testing it ...

Comment 6

12 years ago
*** Bug 316027 has been marked as a duplicate of this bug. ***

Updated

11 years ago
Blocks: 370090

Updated

9 years ago
Component: MailNews: Notification → MailNews: Message Display
QA Contact: stephend → search
Assignee: mail → nobody
QA Contact: search → message-display

Updated

7 years ago
Component: MailNews: Message Display → Backend
Product: SeaMonkey → MailNews Core
QA Contact: message-display → backend
Blocks: 157115
Duplicate of this bug: 157115
Duplicate of this bug: 292120
does patch still apply?

may need someone to drive in Vidar's draft patch

no doubt also reported on getsatisfaction and mozillazine, but tad hard to track down a good match. But perhaps this bug or an offshoot will help http://getsatisfaction.com/mozilla_messaging/topics/mail_notification_doesnt_disappear_when_mail_moved_then_deleted
Whiteboard: [patchlove][has draft patch][needs new assignee?]
Vidar's done great work, but won't be working on this.
Whiteboard: [patchlove][has draft patch][needs new assignee?] → [patchlove][has draft patch][needs new assignee]
(In reply to comment #9)
> does patch still apply?

Nope.

$ patch -p0 --dry-run < ~/Desktop/attachment.cgi 
patching file mailnews/base/src/nsMsgDBView.cpp
Hunk #1 FAILED at 5659.
1 out of 1 hunk FAILED -- saving rejects to file mailnews/base/src/nsMsgDBView.cpp.rej
Attachment #196474 - Attachment is obsolete: true

Comment 12

4 years ago
1+

And this bug is still there in Thunderbird 17.0.8.
You need to log in before you can comment on or make changes to this bug.