212481 - IMAP folders deeper then 2 do not expand on startup of mail app..breaks filters

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[NBW]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624

Start MAIL app. Select IMAP/SSL account, click on "Get Messages". I am prompted
to accept the certificate. During this time period my IMAP folders are properly
expanded in (the deepest I have are 3 deep). As soon as I accept the
certificate, the folder view collapses to 2 levels deep. Some of the arrows next
to folder which have three levels stay there, some of the arrows next to folders
containing a 3rd level disappear. The INBOX begins to update and my filters
begin to process the messages, as it moves mail into folders which are at the
3rd level it fails saying it can't find the folder and it deactivates the filter. 

After all filters run, I can click on the expand arrow next to the folders which
contained the folders which Mail "couldn't find" and they will expand revealing
the third level folder. Then I have to re-run my mail filters.

Also, for those folders which contained a 3rd level but whose expand tab
'disappeared', I can click on the folder and an expand table will appear and I
can drill down to the 3rd level. After which all folders will appear properly,
until I quit and restart mail. At that point the problems begin again.

This happens on my OS-X 1.4 final client which I am reporting this bug using.
However, I also use a Windows 1.4 final client and don't have this issue.

-Noah

Reproducible: Always

Steps to Reproduce:
1. See bug details for steps
2.
3.

Actual Results:  
See bug details.

Expected Results:  
It should have not lost track of IMAP folders nested deeper then 2 levels.

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.