Closed Bug 264138 Opened 20 years ago Closed 14 years ago

IMAP messages do not display after a 1st time install

Categories

(MailNews Core :: Networking: IMAP, defect)

1.0 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: trix, Assigned: Bienvenu)

Details

After a first time setup of an IMAP account, the messages in the inbox are not displayed. Steps: 1. setup environment for a 1st time install(remove prior profiles). 2. launch and setup an IMAP account (assuming new messages currently avail in the Inbox). 3. login to mail account. Results: The Inbox icon displays the number of new messages, but no messages are displayed in the panel. Expected: Messages to be displayed. Note: If you click on other folders in your IMAP account and then click back on the Inbox, your messages will now display. If you reboot the app the messages will also appear in the panel. The issue is only an initial refresh problem.
I think I'm seeing this as well on aviary builds. It's regularly the case in the last week or so that I don't see any messages in my IMAP inbox until I switch to another folder and back to the inbox. Tested: latest aviary builds on winXP.
Flags: blocking-aviary1.0?
Assignee: mscott → bienvenu
Component: Mail Window Front End → Networking: IMAP
Product: Thunderbird → MailNews
Version: unspecified → Trunk
I was not able to reproduce this. Trix, can you get an imap protocol log, and also look to see if there are any errors in the js console? http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
i'm gonna minus this for now since we haven't been able to reproduce this yet. Trix, feel free to renominate if you can trigger this again.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
Product: MailNews → Core
Product: Core → MailNews Core
QA Contact: networking.imap
circa 6 years ago and trix is gone.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Version: Trunk → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.