Open Bug 234010 Opened 21 years ago Updated 2 years ago

Unable to create subfolders in IMAP accounts. POP works. No error generated, but folder never appears, not created on Server.

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
Windows 2000
defect

Tracking

(Not tracked)

People

(Reporter: george, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

User-Agent:       
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

Cannot create second order folders below Inbox, or any fodler parallel to inbox.
 Creation dialog box appears and allows information entry, but folder is never
created on Server or client display.  No errors generated.  Works fine for POP
and have tested to 6 levels below the Inbox folder.

Reproducible: Always
Steps to Reproduce:
1.Select folder at Inbox level.  Inbox itself will work for this purpose.
2.Right click and select New Subfolder
3.Enter name and click OK

Actual Results:  
No folder created.

Expected Results:  
Folder should be created
In TBird 0.6, I see a similar problem, with the following exception:
Scenario: 3 IMAP accounts

A. first IMAP account - can create subfolders, no problem.
B. second and third IMAP accounts - cannot create subfolders.  directories
(foo.sbd) are not created, subfolders (bar.msf) are not created.  
C In addition, cannot create subfolders (menu option does not appear) until
hierarchy for that host is collapsed, then expanded.
I have been using this in .7 and .8 and have been able to create IMAP Folders fine.

Just tested with another folder 3 levels deep and it was created fine.

What IMAP server are you using?  Are you sure it is not an issue with what the
IMAP server is recieving from Thunderbird?

I am using courier-imapd as my IMAP server.
I can create subfolders, but when I try to create folders parallel to inbox
nothing happens.
(In reply to comment #3)
> I can create subfolders, but when I try to create folders parallel to inbox
> nothing happens.

I run Suselinux 9.2 with KDE. I have the same problem. I can create new folders
on the same level as inbox. Creating subfolders is only an option if I shut down
thunderbird first after creating the account. But the subfolders won't be
created.I have set up two different accounts on two different servers, same
problem. When creating new folders the foldername is prefixed with INBOX^ e.g.
Personal folder becomes "INBOX^Personal" if you dont shut down thunderbird first.

I'm taking the liberty of confirming this - I cannot create a folder parallel to
inbox. I see this problem with a Courier IMAP server. The Courier FAQ claims
this is the reason:

http://www.courier-mta.org/FAQ.html#namespace

After a quick look at an Ethereal trace, I tend to agree - the server says:
* NAMESPACE (("INBOX." "."))

and Thunderbird seems to have understood - in the advanced server settings,
personal namespace is set to "INBOX.". However, when creating a new folder XXX,
Thunderbird sends
create "XXX"

when it should be sending
CREATE "INBOX.XXX"

A second problem here is that Thunderbird ignores the negative response
NO Invalid mailbox name.

It really should give some kind of error indication.

Blocks: 160644
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → Trunk
QA Contact: front-end
Seems to not be an issue anymore at least with thunderbird 2.0.0.6 an OpenSUSE 10.3(Linux) , Windows XP and Windows Vista Home Basic.
=> WFM per comment 6
(reporter's address is dead)
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Using 2.0.0.9, still getting the same behaviour as in comment 5.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Phil, can you search bugzilla to find similar bugs and cite them here?  There should be some which have additional detail and examples.
See bug 80858 for more details.
Depends on: 80858
Assignee: mscott → nobody
Status: REOPENED → NEW
Component: Mail Window Front End → Folder and Message Lists
QA Contact: front-end → folders-message-lists
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.