Open Bug 456180 Opened 16 years ago Updated 2 years ago

IMAP shared folders / namespaces not updated from server

Categories

(MailNews Core :: Networking: IMAP, defect)

1.8 Branch
x86
Linux
defect

Tracking

(Not tracked)

People

(Reporter: sam, Unassigned)

References

(Blocks 1 open bug)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.2) Gecko/2008090211 Ubuntu/8.10 (intrepid) Firefox/3.0.2 Build Identifier: version 2.0.0.16 (20080725) I'm using citadel imap server. When the thunderbird connects to the imap server it see's two folder hierachies; "INBOX" and "Main Floor". This seems to correspond to account settings in "server settings/advanced/public (shared) namespace" value of "Main Floor/" I added a new floor in citadel called "blogs" containing a folder called "sam" but could not get thunderbird to notice. I created a new imap account and it noticed right away, giving for "public (shared) namespace" this value: "blogs/","Main Floor/" I've tried putting that value in the namespace slot for the previous account, and refreshing the folder list but it still won't show the new shared folder collection. I t seems that the only way to show a new folder collection is to delete and re-create the entire account Reproducible: Always Steps to Reproduce: 1. 2. 3.
Component: General → Networking: IMAP
Product: Thunderbird → Core
QA Contact: general → networking.imap
Version: unspecified → 1.8 Branch
The extra folder tree showed up in the end, it just took a few days. One of the citadel guys responded saying that it just took thunderbird a long time no enumerate all the folders. Perhaps as a low priority fix, thunderbird could enumerate namespaces first, and enumerate new namespaces before the existing ones as it would help usability no end. Perhaps it could enumerate folders before fetching messages?
Product: Core → MailNews Core
Sam I think Thunderbird 3.0 beta does that now (we use both lsub and xlist). Would you mind checking with a build from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/ and report if we behave better ?
Whiteboard: closeme 2009-09-24
all the xlist support does is discover some special folder flags set on the server. It doesn't fix general folder/namespace discovery issues.
(In reply to comment #3) > all the xlist support does is discover some special folder flags set on the > server. It doesn't fix general folder/namespace discovery issues. Sam no need to test then.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: closeme 2009-09-24
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.