Closed Bug 278808 Opened 20 years ago Closed 20 years ago

new mail is automatically checked on IMAP accoun even when told not to

Categories

(Thunderbird :: General, defect)

x86
FreeBSD
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bhughes, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.3; FreeBSD 4.10-RELEASE-p2; X11; i386; en_US) (KHTML, like Gecko)
Build Identifier: Mozilla Thunderbird version 1.0 (20050103)

I have setup an IMAP account and turned off the "check new mail every XXX"   
feature.  However, after a few minutes and without having pressed the "get new   
messages" button/menu-entry, new mail shows up in the inbox.  This does not 
seem to be linked to the current folder (i.e. new mail shows up in INBOX even 
though it is not the current IMAP folder). 

Reproducible: Always

Steps to Reproduce:
1. compose mail to IMAP address   
2. wait a few minutes and don't select "get new messages", the message will   
arrive in the inbox and Thunderbird will show that new mail is available.  
  
Actual Results:  
New mail arrives into the inbox. 

Expected Results:  
New mail would arrive only after selecting the "get new messages" 
button/menu-entry. 

1. This does not seem to happen for IMAP folders other than the inbox.  New 
mail does arrive in the Junk folder when using the auto-spam feature. 
2. Leaving Thunderbird running for long periods of time (e.g. overnight) does 
not show all new mail in the inbox.  After returning in the morning, "get new 
messages" fetches mail previously unseen by Thunderbird.  The steps above 
reproduce the bug everytime, but for long periods of inactivity, it seems 
Thunderbird stops showing newly arrived mail.
Do you have IMAP idle support activated in the advanced preferences for the server?

If IMAP idle is on, the server will push folder updates to the client without
any more action from the client than a half-hourly I'm-alive-ping.
Yes, I did have IDLE support turned on.  Turning this off gives the behavior I 
was expecting.  Seems this is not a bug after all. 
 
Thanks :) 
per comment 2
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.