Closed Bug 231638 Opened 21 years ago Closed 21 years ago

Can't access Subfolders of Subfolders on an IMAP server

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: rtresidd, Assigned: Bienvenu)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 After createing numerous subfolders OF subfolders using Mozilla 1.6 and copying emails into them I am no longer able to see them when I open up mozilla mail... I know that the messages are there and the IMAP server is working fine because Ximian is able to view all of these subfolders and messages that are within them.. The subfolders are all showing up in the Subscribe window but are not present in the list for browesing through the messages.. BIG pain.. and I though I finally had this IMAP thing going.. Thanks Richard Reproducible: Always Steps to Reproduce: 1. 2. 3.
OK, this is probably fixed in 1.7. Are you using imap subscription (mail & newsgroup account settings) imap server | advanced | show only subscribed folders. If you've turned off that checkbox, you'll need to either use 1.7, or turn that checkbox back on. If you expand and collapse the parent folders, do the child folders show up?
Hi That worked :) some other instructions I found said to turn that checkbox off.. I'll see how it goes with it set and get back to you in about 24hours..
You're much better off using subscription. The only valid reason I've heard not to use subscription is if some other app is creating folders in your account, but not subscribing you to them...
Yep It was a silly option to not check.. thats what happens at 4 in the morning though.
resolving wfm - this is fixed on the trunk.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
All has been going well thanks just to let you know...
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.