314603 - Folder disappears on default build

Status: RESOLVED INCOMPLETE

(Thunderbird :: Mail Window Front End, defect)

Description

[Alex Bligh]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.7.12) Gecko/20051010 Firefox/1.0.7 (Ubuntu package 1.0.7)
Build Identifier: Thunderbird Linux x86_64 1.5 Beta 2

Thunderbird 1.5 Beta 2 (Bug also appears identically on 1.0).

Prepare an IMAP server (cyrus-imapd here) with several folders, under INBOX, including "INBOX.sent" (that's with a small "s").

Launch Thunderbird from a completely clean config (i.e. delete preferences etc.). Put in IMAP server details. Expand IMAP account to show folders on the left. Note all folders display EXCEPT INBOX.sent.

Right click on the account, bring up the subscribe dialog, and expand INBOX. Note that Thunderbird does see "INBOX.sent" here.

I expect the problem is related to the fact it seeks to file sent messages under "INBOX.Sent" (that's with a capital "s"). However, it appears not to be possible to change this as the menu showing folders they can be filed in does not include "INBOX.sent".

Is there some unecessary case insensitivity somewhere?

Reproducible: Always

Steps to Reproduce:
1. Launch Thunderbird from install with IMAP server with INBOX.sent
2. Note INBOX.sent does not appear in folder window on left
3. Note it does appear in subscription dialog

Actual Results:  
INBOX.sent missing

Expected Results:  
INBOX.sent present

This bug present is also present 1.0 as shipped in Ubuntu Breezy Badger, on both AMD-64 and i386, as well as 1.5 Beta 2 as built from scratch on AMD64.

This prevents migration of users from mail programs which have used INBOX.sent as a default.

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?

(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.16)

Comment 2

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to previous comment. If you feel this change was made in error, please respond to the bug with your reasons why.