false/incorrect repeating New mail notification, but there is no new mail. (imap)



Mail Window Front End
a year ago
a year ago


(Reporter: David, Unassigned)


45 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [dupme?])


(1 attachment)

141.35 KB, application/x-zip-compressed


a year ago
Created attachment 8836000 [details]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
Build ID: 20170125094131

Steps to reproduce:

I have one account (IMAP) in Thunderbird and a New mail sound enabled
Open Thunderbird.
Leaving Thunderbird open.

Actual results:

On startup a New mail alert appears with New mail sound but no new mail is received.
After a few minutes New mail alert appears again (repeatedly) with New mail sound and still there is no new mail.

Expected results:

No New mail alert if there is no new mail.
If I use POP3 on the same mail account, everything is OK.


a year ago
OS: Unspecified → Windows 7
Hardware: Unspecified → x86_64

Comment 1

a year ago
Just to clarify - "New mail alert appears" = tray icon appears


a year ago
Summary: IMAP: Repeating New mail notification, but there is no new mail → false/incorrect repeating New mail notification, but there is no new mail. (imap)
Whiteboard: [dupme?]

Comment 2

a year ago
I've had this issue for years and only recently stumbled across the cause.  I believe it has to do with the control characters issue listed on http://kb.mozillazine.org/New_messages_do_not_appear , though it wasn't blocking my receiving of e-mail, just causing endless new mail notifications.

Going into my webmail, I found the troublemaking spam e-mails and was able to mark them as read/delete them and the notifications have stopped.  My webmail also had issues rendering the e-mails though; in the list view it would show without any From/To/Subject though some of these e-mails had those specified when opened.  I'll try to pin down what it is about these e-mails that are causing an issue or I'll just their source here if I can't figure it out.
You need to log in before you can comment on or make changes to this bug.