User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016 When accessing an IMAP account (my global email archive) on a remote linux station SSL accessed via a proxy I can't see nor open folders beneath the outer level. I didn't experience that problem with mozilla releases prior to 1.2b. Since archiving incoming and outgoing emails to the archive in question is essential I have to stay with release 1.2a until this problem has been solved. Reproducible: Always Steps to Reproduce: 1. repeatedly shift releases 1.2a and 1.2b to verify that the problem persists 2. 3.
I ought to specify that by 'proxy' I mean an ssh tunnel.
Looks like I must withdraw my bug report. Even upon downgrading to release 1.2a I still didn't get access to all subfolders. Probably the real cause of the problem was that my home directory must have been corrupted upon a crash (I don't know where and what). Now I've re-created my home directory and *can* again see all sub directories of the IMAP account in question. Sorry for the inconveniance.
Resolving as invalid due to comment 3. Christian, you should be able to do this yourself on your own bugs.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
It seems that I should reopen this bug. The reported problem persists after I have reorganized my home directory. What happens repeatedly is that my folder hierarchy of my IMAP email archive 'suddenly' is gone such that I see only the outermost folders. Now I've also experienced that problem with the most recent stable mozilla version 1.2.1. The remedy for the problem is still to downgrade to the stable version 1.1. When I launch its messenger on the said IMAP account I regain access to my folder hierarchy and keep it for some - unpredictable time - after having again upgraded mozilla. Since my original bug report I've modified my IMAP access from being SSL based to a port forwarding SSH tunneling. This does not prevent the reported problem to pop up.
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
Ditto. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021202 Using the WU imapd, I used to have IMAP/Archive/inbox/2002, ... but now can only see the folders immediatly below IMAP. It does not help to hit the refresh button in the subscribe dialog. Where does mozilla store the directory layout? I'd be willing to remove that file in hopes of forcing mozilla to pay attention.
Here mozilla happily displays subfolders up to two levels, but the third level is most often not visible, i.e. sometimes i get INBOX.Mailing-Lists.security-focus.bugtraq etc.. but most often i only get INBOX.Mailing-Lists.security-focus and that's it
related to bug #232077
Robert: only drivers can set (+) blocking flags. you can request (?) them.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago → 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.