Open Bug 436857 Opened 17 years ago Updated 3 years ago

email notification flag

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
x86
Windows XP
Type:
defect

Tracking

(Not tracked)

People

(Reporter: r11rtrdr, Unassigned)

Details

(Whiteboard: [needs new summary and better STR])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: version 2.0.0.14 (20080421) When new mail arrives on my pop server the flag, in my system tray pops up. If I click on "GET MAIL" the mail is downloaded from my pop server but the flag doesn't go away. If I click on GET MAIL a second time the flag goes away. Reproducible: Always Steps to Reproduce: 1.New Mail arrives on my pop server 2. The flag pops up in my System tray 3.I click on GET MAIL 4. The flag doesn't go away. 5. I click on GET MAIL again and it goes away. Expected Results: The flag would go away after I download my mail
The icon is supposed to go away when you *read* mail, rather than when you *check* mail, so this behavior is intended (I'm not sure why it goes away after two Get Mails, but that's a different question. If you open one of the new messages, the icon should go away (and stay gone if you subsequently mark it as unread again).
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
I believe the user has it set so that check for new mail doesn't download pop3 headers. Technically, I think Greg is right ...
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
It's somewhat debatable about what the right behavior is here...I think it's useful to know if you've read the last new message...
Very debatable. My initial thoughts are that getting notification about receiving new mail is probably more important than an indicator that you have new mail. So many people use the read/unread status of emails to manage their Inbox that it's not valuable to indicate that unread mail exists as much as new mail has arrived.
This bug is currently not easy to act on: Per comment 2, this seems to involve non-default settings which are not mentioned in STR. Problem is not easy to understand, and Summary does not describe the problem at all. -> needs new summary -> needs better STR
Whiteboard: [needs new summary and better STR]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.