| Summary | handling of INBOX in folder navigator |
| Queue | IMP |
| Queue Version | 4.1.3 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | stephan (at) stean (dot) ch |
| Created | 2/19/07 (7068 days ago) |
| Due | |
| Updated | 3/1/07 (7058 days ago) |
| Assigned | |
| Resolved | 3/1/07 (7058 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
namespace doesn't "live" under INBOX and why we don't show it that
way: for personal namespaces other than 'INBOX' you can have a
subfolder 'foo' under INBOX (INBOX.foo) and a folder 'foo' in the base
namespace and these folders are completely independent of one another.
(If the base namespace is 'INBOX' then adding a folder under INBOX
is identical to adding a base folder so you will never see a folder
living under INBOX in this situation.)
This works perfectly fine in HEAD too. Since the IMAP tree has been
totally rewritten for HEAD, we are not going to do anything about this
in 4.1.3.
Assigned to Michael Slusarz
State ⇒ Feedback
Or should we not allow this at all since they won't be displayed below
INBOX anyway?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ handling of INBOX in folder navigator
Queue ⇒ IMP
State ⇒ New
all flat, nothing below INBOX.
This means, at least this reflects the behaviour of my installation,
that creating a new folder inside INBOX will fail. In my configuration
with courier-imap, the request parameter sent to IMP is INBOX
without a dot at the end:
<option value="INBOX" selected="selected">Inbox</option>
<option value="INBOX.asdf">asdf</option>
<option value="INBOX.Trash">Trash</option>