Closed Bug 90683 Opened 24 years ago Closed 23 years ago

sub folders of inbox assumes uppercase INBOX

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 60344

People

(Reporter: martin.sillence, Assigned: mscott)

Details

Select for sub folders of inbox assumes case of all uppercase i.e. INBOX. Actual case for my subfolders is Inbox. This works in netscape 4.7. Error message is select failed for mailbox INBOX/test Manualy logging on to the imap server and doing a select does indeed fail for this and a select Inbox/test reports OK. Unselecting/selecting them using the subscribe feature makes no difference though the case appears correct for the select dialogue. Using washington university imap server 4.7c-1 on debian 2.2 and maildir format mailboxes.
Marking dup of bug 60344, which is about using the boxname as sent by the server instead of "INBOX". (imap) *** This bug has been marked as a duplicate of 60344 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Verified as dup.
Status: RESOLVED → VERIFIED
I think this is not a duplicate of 60344. 60344 is about cosmetic stuff, displaying to the user the special folder "INBOX". This bug is about accessing folders that are subfolders of a folder named "inbox", "INBOX", "Inbox", "iNBoX", ... Here is the precise situation where I hit this bug: I'm using UW IMAPD, in "no folders containing both messages and subfolders" mode. The user has both an INBOX (the special magic folder, containing messages) and a folder called "Inbox", that contains subfolders, e.g. "foo". In the mailboxes pane, foo is shown as a subfolder of INBOX instead of as a subfolder of a separate folder "Inbox". When trying to access this "foo" subfolder, Mozilla Mail tries to access "INBOX/foo" instead of "Inbox/foo". The former doesn't exist and thus the operation fails. As a conclusion, please re-open (and fix ;) ) this bug.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.