104525 - Unable to rename a folder in particular cases - the current command did not succeed. ... Mailbox already exists.

Status: NEW

(MailNews Core :: Backend, defect)

Description

[lchiang]

Unable to rename a folder in particular cases

Win32 build 2001-10-12 094 branch
IMAP

Here are the two cases I have:

Folder hierarchy (folder at top level, same as Inbox level):
! QA and Doc Plan
 Projects

! Me - To Do
 sun team

The problem folders are "Projects" and "sun team"

Steps:
1.  Start Mail and log in
2.  Select either one of the folders mentioned above and right mouse click to
bring up the Rename Folder dialog.  Here are the names I tried:

Projects --->  Projects and Proj Mgmt
         --->  one two three

sun team --->  Sun Team
         --->  one two three

3.  Each time, when I click OK out of the Rename Folder dialog, I get an error:
"The current command did not succeed.  The mail server responded.  Mailbox
already exists."

I tried this in N6.1 and the rename is successful.

I will send you my IMAP log and perhaps attach snippets of it here.  I do not
want to attach the entire log as it contains information on my mail contents.

Comment 1

[lchiang]

I don't think this is a general problem since I created a new folder and a
subfolder and it works fine.  Have to try more.

Comment 2

[lchiang]

I don't want to post my logs here.  Have sent to mscott, huang, and bienvenu via
email.

Comment 3

[Karen Huang]

I cannot reproduce this problem if without using same folder names as Lisa.
But, I can reproduce this problem if I used same folder names with Lisa for my 
test accounts. I will attach the IMAP log which generated from my test account 
here -- I am wondering to know whether these problems are from these specific 
folder names with "!".......

Comment 4

[Karen Huang]

Attachment: IMAP log for renaming subfolders names of 1st level folders with "!" character

Comment 5

[Karen Huang]

David, there were bug 20324 & bug 29890 related to some special characters for 
IMAP folders. Do you think that "!" character should be part of those bugs that 
we need to fix in the future?

Comment 6

[David :Bienvenu]

I don't think '!' is special for imap folders. It might be special for uri parsing.

Comment 7

[WADA:World Anti-bad-Duping Agency]

Bug 92165 is Mozilla mail&news bug for this problem.

Comment 8

[Jo Hermans]

*** Bug 292836 has been marked as a duplicate of this bug. ***

Comment 9

[domi]

something new with TB 1.0.7 on win98 second

i've got some subfolders under inbox.sbd in local folder
with filters sending new mails in the subfolders
it was OK

one day ??? without update
two of the subfolders where renamed automatically by thunderby while launching TB
in uppercase
for example the subfolder Machin was now MACHIN
i tried a rename under TB and get the message "unable to rename name Machin already exist"

closing TB i went in the profile and found
a file Machin (ok) and MACHIN.msf and MACHIN.sbd. !!!
i saved MAchin and the others subfolders outside the profile
launch TB and drop all the subfolder
quit TB, => inbox.sbd was emptied (ok)
1 put the file Machin only (no .msf or .sbd) in the inbox.sbd
launched TB and THE SAME AGAIN with MACHIN.sbd and MACHIN.msf
???
drop the subfolder again, quit TB
put Machin in the inbox.sbd but renaming it as Truc
launched TB => ok with Truc , Truc.msf and Truc.sbd
quit TB, duplicate Truc to Machin
launch TB and (ok) with Machin.msf and Machin.sbd

still wondering about this automatic uppercase

but maybe it could help to identify the "particular cases" where you get the
"unable to rename" msg

Comment 10

[Magnus Melin [:mkmelin]]

*** Bug 335672 has been marked as a duplicate of this bug. ***

Comment 11

[Andreas Kleinert]

Just wanted to confirm the case-sensitivity renaming problem problem also for Thunderbird 1.5.0.7 (Windows).

Just wondering why bug 104525 has been marked a duplicate of this one, because the latter deals with IMAP folders. The former just occurs with any kind of folder created in Thunderbird (e.g. if you try to rename "SuSe" to "SuSE").

Comment 12

[Andreas Kleinert]

sorry, I meant bug 335672 (bug 104525 in fact is what you are just reading)

(In reply to comment #11)
> Just wanted to confirm the case-sensitivity renaming problem problem also for
> Thunderbird 1.5.0.7 (Windows).
> 
> Just wondering why bug 104525 has been marked a duplicate of this one, because
> the latter deals with IMAP folders. The former just occurs with any kind of
> folder created in Thunderbird (e.g. if you try to rename "SuSe" to "SuSE").
> 

Comment 14

[realgrouchy]

(In reply to comment #7)
> Bug 92165 is Mozilla mail&news bug for this problem.
> 

Yes. And as with that bug, I don't think it has to do with networking or IMAP, as it applies to local folders as well. Here is the behaviour in Thunderbird 2.0.0.14: (on OSX 10.5.4)

Here's a more recent summary of how Thunderbird behaves with this bug.

- RG>

1. Select folder named "Office Admin".
- Top half of TB window displays messages

2. Right click folder and choose "rename"
- Little box drops down from header bar of window asking for new name of the folder.

3. Rename to "OFFICE ADMIN", click OK
- Box does not go away. Top half of TB window clears.

4. Click "cancel" on dialog box:
- Alert dialog box appears: "Alert / A folder with that name already exists. Please enter a different name."

5. Click "OK" on alert dialog box
- The same dialog appears again

6. Click "OK" on second alert dialog box
- The dialog goes away and the folder view remains empty, even when clicking on the folder. One must click on another folder and then back on "Office Admin" to refresh the view.

Comment 15

[realgrouchy]

Just to elaborate on my previous Comment 14, step 3:
- The top half of the TB window no longer clears (good), but when you rename a folder where only changing its case, the box doesn't go away and gives no other indication. 

If you click the "Rename" button X times, nothing happens until you click "cancel", at which point you'll be presented with a series of X error messages ("Alert / A folder with that name already exists. Please enter a different name.")

In other words, the error should be appearing on top of the rename dialog, not waiting for the rename dialog to clear.

(Well, ideally, this shouldn't produce an error at all, but in the meantime the error handling is off).

- RG>