Closed
Bug 107646
Opened 23 years ago
Closed 23 years ago
Courier IMAP: All folders in IMAP Only appear under inbox
Categories
(MailNews Core :: Networking: IMAP, defect, P3)
Tracking
(Not tracked)
People
(Reporter: hanasaki-mozilla, Assigned: mscott)
References
Details
(Keywords: imap-interop)
Attachments
(1 file)
Using courier imap and have tried it with imap workarounds turned off and on.
Comment 1•23 years ago
|
||
*** Bug 107647 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
Based on the following description from Courier IMAP, I am updating this bug as NEW: -------------------------------------------------------------------------------- IMAP servers are free to use any folder namespace arrangement that's technically convenient for them. Courier-IMAP uses "INBOX." as the namespace for private folders, and "shared." as the namespace for public, shared, folders. The IMAP NAMESPACE extension (see http://www.rfc-editor.org/rfc/rfc2342.txt) allows IMAP clients to automatically discover where the server creates folders, and IMAP client should implement it. -------------------------------------------------------------------------------- Adding interop for the keywords and nominating nsbeta1 for next release since All folders in Courier IMAP shouldn't only appear under inbox. Ccing Cavin.
Comment 5•23 years ago
|
||
Comment 6•23 years ago
|
||
What's the bug here? If Courier IMAP only allows folders under the inbox (like Cyrus), then that's what we display and we're doing the right thing. In other words, it's the way the server works.
The courier page says: http://www.inter7.com/courierimap/FAQ.html#namespace I can't create any top-level folders, only subfolders of INBOX This is a configuration issue with your mail client. IMAP servers are free to use any folder namespace arrangement that's technically convenient for them. Courier-IMAP uses "INBOX." as the namespace for private folders, and "shared." as the namespace for public, shared, folders. The IMAP NAMESPACE extension (see http://www.rfc-editor.org/rfc/rfc2342.txt) allows IMAP clients to automatically discover where the server creates folders, and your IMAP client should implement it. This should be completely transparent to you, if your IMAP client properly uses the NAMESPACE extension. If your IMAP client were to automatically take advantage of self-configuration features offered by RFC 2060 and RFC 2342, it would automatically discover, without any additional configuration from the user, that: 1. The folder namespace hierarchy separator is the . character 2. Private folders are stored underneath the "INBOX." hierarchy 3. Public folders are stored underneath the "shared." hierarchy If you have to explicitly create folders that are subfolders of INBOX, or if you explicitly have to name that "INBOX.foldername", this is due to your IMAP client not being able to configure itself accordingly. Time for me to get out of the middle - will the Mozilla team please talk to the Courier team and get back to the Bugzilla list?
Updated•23 years ago
|
Comment 8•23 years ago
|
||
I'd say that this is a DUP of 80858. Wouldn't you?
Comment 9•23 years ago
|
||
It does look like a dup. *** This bug has been marked as a duplicate of 80858 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•