Closed Bug 287217 Opened 20 years ago Closed 20 years ago

Thunderbird doesn't check all IMAP folders on startup

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: david, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050226 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050226 Firefox/1.0.1

I run a local Exchange 2003 server with IMAP4 support, I've set up Thunderbird
to work with it (including the infamous "Trash / Deleted Items" hack (can you
fix that too?), but whenever I boot T-Bird, it doesn't check my account folders
for new messages, which is a minor inconvinience, I'm used to booting T-Bird,
looking at the folder list, then closing it if there's nothing new. Now I have
to click on each message folder to see if there's any new messages.

Reproducible: Always

Steps to Reproduce:
1. Set up an Exchange 2003 server and enable the IMAP4 Virtual-Server
2. Set up Thunderbird to work with it
3. Send an email to yourself that gets filtered by Exchange to be routed to a
particular mailbox folder
4. Boot up Thunderbird and notice that it doesn't say if any new messages have
arrived
5. Click on the subfolder you know the message to be in, and T-Bird will
announce that new mail has arrived

Actual Results:  
T-Bird only checked the mailbox folder after clicking on it

Expected Results:  
T-Bird should have checked all folders on startup
No it does not check all imap folders for new messages, only the ones that you
selected that it should check. Is it? Right-click the folder, Properties, check
this folder for new messages. 
Hmmm, (I'm not currently able to confirm this myself, since I'm in the middle of
a format) But in which case could they change the IMAP4 setup dialog to
explicitly mention Thunderbird's behaviour?
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.