Closed Bug 539947 Opened 16 years ago Closed 16 years ago

growl notifications on new mails totally off on 3.0.1

Categories

(Thunderbird :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 540554

People

(Reporter: axel, Unassigned)

Details

(Keywords: regression)

I just got the 3.0.1 update on the beta channel today, and growl notifications for new mails went totally bazooka. It seems to include all my mails, prompting me with 12k unread mails, while I only have 3 unread mails in my inbox on that account. I suspect this is a regression from 3.0.
It doesn't do that here. I've seen this in the past but I've never been able to pinpoint what the issue was. I suppose Tools -> Error console is empty ?
Yeah, and I don't see anything in the activity manager either. javascript.options.showInConsole is true, checked that as well.
Fixes possibly relating to dock icon counts in TB 3.0.1: Bug 516477 Dock shows a double count of unread messages in smart folder view Bug 517461 Perfolder unread e-mail count sometimes is wrong on a IMAP server (IMAP server, dovecot, supports CONDSTORE) Bug 524902 Thunderbird sometimes fetches read/unread flags from the wrong IMAP folder Axel - do you know what sort of server you are using? An IMAP log may be useful - bienvenu will be able to comment more.
blocking-thunderbird3.0: --- → ?
That's my mozilla.com zimbra account. I wonder, is there something I could test without restart? I don't want to loose data points if a restart would magically fix it. PS: My doc-icon shows a different count, now that the "Hide Dock Count" extension doesn't hide that. I wonder if that extension made things work on the notifications side.
Just randomly glancing, could this be a regression from bug 517461?
This bug got to be the same as bug 476215 - Zimbra accounts seem to be involved too.
This should be fixed in 3.02pre nightly builds.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
blocking-thunderbird3.0: ? → ---
You need to log in before you can comment on or make changes to this bug.