301176 - new messages not received after notification of new messages in task bar

Status: RESOLVED DUPLICATE of bug 273396

(Thunderbird :: General, defect)

Description

[Phil Hadley]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

I get a notification that new messages hve arrived in the task bar but when I 
open Thunderbird there are non. If I then open outlook Express and tell it to 
receive messages they are delivered to me.

Reproducible: Always

Steps to Reproduce:
1. Can't be reproduced as it is an auto function
2.
3.



Expected Results:  
Put mail into my inbox

Comment 1

[Adam Guthrie]

*** This bug has been marked as a duplicate of 273396 ***

Comment 2

[Walter Nicholls]

(In reply to comment #1)
> 
> *** This bug has been marked as a duplicate of 273396 ***

I don't think it's a duplicate - read the description!
 301176 describes being notified of mail, and it not arriving, when there IS mail to be read
 273396 describes being notified of mail when there is no mail to be read.

We seem to be getting the former on Kubuntu 5.10, TB 1.0.7 (got from the Ubuntu repositories).  Messages are being notified as arrived - against the account they belong, but there is a delay - 7 hours in at least one case - before the inbox for that account appears in bold and the message can be read. 
Can read in the message source the header is (may be couple of mistakes, I'm retyping this on different machine):
 From - Sun Nov 20 17:56:47 2005
 X-Account-Key: account7
 X-Mozilla-Status: 0211
 X-Mozilla-Status2: 00000000
 ...
 Delivery Date: Sat, 19 Nov 2005 17:20:10 -0500
 ...
 Received from ..... : Sat 19 Nov 2005 17:20:10 -0500

Note we are on UTC+1300, so in UTC that is delivered to the mail server at Sat 2220h, marked by Mozilla Sunday 0456h - a delay of nearly 7 hours.

This would seem to indicate that the mail simply wasn't checked (TBird "Get Mail" until 17:56 but it had been, several times, and other messages had arrived in the intervening period.
Seems only to be one account on this TB setup (there are a few..) so maybe dumping and redefining the account settings will fix for us.