256735 - clicking 'next message' prompts to move to unread in next server

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[Aaron Solochek]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: version 0.7.3 (20040803)

With multiple servers, thunderbird prompts the user to move to the next message
on the next server when there are no more unread messages on the current server,
and the user has hit 'n' or clicked 'next.'  If server A has two folders being
checked for incoming mail, foo and bar, and foo is currently selected and has no
more unread messages, clicking next should take you to the first unread message
in folder bar.  However, the messages in folder bar haven't yet been downloaded,
since bar hasn't been selected since they arrived, and although thunderbird
knows there are new messages awaiting download (the folder is bold, and says how
many new messages there are), clicking next brings up the prompt to move to the
next unread message on server B.  

Reproducible: Always
Steps to Reproduce:
1.setup two imap mail servers, referred to as A and B.
2.On server A, create a subfolder of INBOX (called foo) and tell thunderbird to
check it for incoming mail.  Have new mail for a specific address (like
[e-mail]) go to foo, and other mail goto INBOX. 
3.select INBOX on server A.
4.send mail to all addresses, so that A.INBOX, A.INBOX/foo, and B.INBOX all have
new mail in them.
5.click 'next' or hit 'n' to go to the next unread message.  do this until all
messages have been read.

Actual Results:  
After all the messages in A.INBOX are read, a prompt shows up asking if you want
to go to the next unread message in B.INBOX

Expected Results:  
After all the messages in A.INBOX are read, hitting 'n' should take you to the
next unread message in A.INBOX/foo

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.