Folders get messed up if selecting "Next Message" that is located in an unexpanded account



Mail Window Front End
15 years ago
13 years ago


(Reporter: wallycrooze, Assigned: Scott MacGregor)


Firefox Tracking Flags

(Not tracked)




15 years ago
Build Identifier: Mozilla/5.0 (X11; U; IRIX64 IP30; en-US; rv:1.6) Gecko/20040210 Thunderbird/0.5

When I get a message for an unexpanded account, I casually hit "Next Unread
Message" and after the prompt attempt to jump to the message, but instead of
expanding the account and displaying the message it messes up the folder pane
with multiple copies of the main (first) account.

Reproducible: Always
Steps to Reproduce:
1. Require multiple accounts with messages.
2. Mark a message unread in the second account (preferably in a deep nested folder).
3. Unexpand the account that has the unread message.
4. Select the Inbox of the first account.
5. Go->Next->Unread Message.
6. Accept yes to jump to unexpanded folder.
7. First account folders should be duplicated outside its account.

Actual Results:  
First account folders appear duplicated outside its account...

Expected Results:  
Should have expanded account and gone to unread message.
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.