Closed
Bug 659741
Opened 13 years ago
Closed 13 years ago
Thunderbird shows notifications for mail that has landed in Junk
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 272125
People
(Reporter: mconley, Unassigned)
References
(Blocks 1 open bug)
Details
No description provided.
Comment 1•13 years ago
|
||
This sure is a very sparse bug description ;-), so I'll chime in and describe the issue. i) I'm using Gmail, which does its own classifying on the server-side. ii) I do have mail.imap.whatever.check_all_folders_for_new_messages (I can never remember the name of that pref). iii) When a message arrives in the junk folder, because of ii), autosync (?) picks it up, and we go through the new mail notification code. iv) New libnotify mail alert is shown for a junk message. IMHO that shouldn't happen. (Hope that's clear enough!)
Updated•13 years ago
|
Blocks: biff
Component: OS Integration → Mail Window Front End
QA Contact: os-integration → front-end
Whiteboard: [duptome]
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Whiteboard: [duptome]
Comment 3•13 years ago
|
||
Aureliano, this issue is about server-filtered mail that goes directly into the Junk folder, not mails that first arrive in the Inbox and then are classified by Thunderbird into the junk folder as bug 272125 is about. Are you positive we can merge the two issues?
Comment 4•13 years ago
|
||
Ciao :protz ;-) > Are you positive we can merge the two issues? Yes, I'm inclined to consider dupe because the underlying problem is the same... see also :Bienvenu comment here https://bugzilla.mozilla.org/show_bug.cgi?id=272125#c8 Anyway feel free to reopen it if you don't agree.
Comment 5•13 years ago
|
||
I tend to think this is two separate issues, but I'll let mconley decide since he's the expert now =)
Reporter | ||
Comment 6•13 years ago
|
||
Just read through bug 272125, and it sounds like this is a duplicate. Let's keep this one closed. Thanks all!
You need to log in
before you can comment on or make changes to this bug.
Description
•