Closed
Bug 101923
Opened 23 years ago
Closed 23 years ago
IMAP Interoperability: Can't delete IMAP folders
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 115988
People
(Reporter: helgedt, Assigned: mscott)
References
Details
(Keywords: imap-interop)
Attachments
(1 file)
6.55 KB,
text/plain
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4+) Gecko/20010926
BuildID: 2001092608
Can't delete IMAP folder; IMAP server says RENAME failed; file exists
Reproducible: Always
Steps to Reproduce:
1.make new IMAP folder "cheese" (yummy)
2.select it
3.right-click on it, choose delete
4."yes" to "do you want to move this folder to Trash" or what-not
Actual Results: I get this error message:
"The current command did not succeed. The mail server responded: RENAME failed:
Can't create mailbox node /home/students/helgedt/Trash/: File exists."
Seems to me like mozilla tries to rename it to Trash in stead of moving it into
Trash? I don't know IMAP and I don't know how Mozilla deals with it so I might
be horribly wrong, but heck. (=
In my home dir at the server, I've got a Trash file and a cheese file.
Both contain a folder-internal message thingie made by the mailer-daemon.
/usr/sbin/imapd output (first lines:)
* PREAUTH [CAPABILITY IMAP4 IMAP4REV1 STARTTLS NAMESPACE IDLE MAILBOX-REFERRALS
SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND]
colargol.tihlde.org IMAP4rev1 2000.287 at Thu, 27 Sep 2001 14:53:59 +0200 (CEST)
Agreed, *kicks himself for not finding that one before posting bug*
But, this is a new aspect of bug 46365 because I have not deleted a folder
called "cheese" before.
Comment 3•23 years ago
|
||
Marking these all WORKSFORME sorry about lack of response but were very
overloaded here. Only reopen the bug if you can reproduce with the following steps:
1) Download the latest nightly (or 0.9.6 which should be out RSN)
2) Create a new profile
3) test the bug again
If it still occurs go ahead and reopen the bug. Again sorry about no response
were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Comment 4•23 years ago
|
||
>this is a new aspect of bug 46365 because I have not deleted a folder
>called "cheese" before.
I am reopening this bug based on above reproter's comments since this is
different as bug 46365.
If reporter cannot find the same existing "cheese" folder name from Trash
Folder, then this should be another bug...
alge. looks like that you are using the IMAP4rev1 2000.287 IMAP server.
Can I know that "is this MS exchange 2000 or UW 2000 IMAP server"?
Can you attach a IMAP log here since we don't have those servers setup from our
lab yet. You can get the IMAP log by setting as following:
For C Shell:
Add a line to ~/.cshrc file of the csh shell as following:
Set NSPR_LOG_MODULES IMAP:5
Set NSPR_LOG_FILE /u/[unix userlogin]/tmp/[filename]
(filename can be defined by you)
Please Note: /u/[unix userlogin] is just Netscape setup UNIX environment for
each user.
It could be /home/[unix userlogin] or /[unix userlogin] depend on how your
users environment setup.
Status: RESOLVED → UNCONFIRMED
Keywords: interop
Resolution: WORKSFORME → ---
Summary: Can't delete IMAP folders → IMAP Interoperability: Can't delete IMAP folders
Bug is still there with 2001111506, blank profile.
And yes, IMAP4rev1 2000.287 (from the log).
The server is running debian so I doubt it's MS-something-something (:
*** Bug 113412 has been marked as a duplicate of this bug. ***
Umm, can somebody change this from unconfirmed to new? Pwetty pwetty pwease?
Updated•23 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 9•23 years ago
|
||
>In my home dir at the server, I've got a Trash file and a cheese file.
.......
>this is a new aspect of bug 46365 because I have not deleted a folder
>called "cheese" before
.....
I am wondering to know why:
From your test description, you mentioned: "In my home dir at the server, I've
got a Trash file and a cheese file"
And later from your comments, you mentioned: "I have not deleted a folder called
'cheese' before"
Can you describe more clear whether you have "cheese" folder under your Trash
folder or not?
Can you provide the exactly steps for us to reproduce this problem?
Also, do you have UW IMAP 2000 test account for me to test?
If yes, would you please send the server and user/passwd info to me? Thanks.
Summary: IMAP Interoperability: Can't delete IMAP folders → UW IMAP 2000: Can't delete IMAP folders
Reporter | ||
Comment 10•23 years ago
|
||
I have a Cheese _file_ and a Trash _file_ on the server. As in:
-rw------- 1 helgedt students 507 Nov 16 18:47 Cheese
-rw------- 1 helgedt students 2890 Nov 21 23:30 Mailbox
-rw------- 1 helgedt students 507 Sep 27 10:42 Trash
drwx------ 2 helgedt students 4096 Sep 12 13:53 mail
To reproduce:
Open Mail/News. Right-click on the account (helgedt@tihlde.org). Select "New
Folder". Type in name "Butter". Press OK for "Make new folder under:
helgedt@tihlde.org". There is now a "Butter" folder for the account. Right-click
on it. Select "Delete folder". Press OK to confirm. Get error message: See bugdesc.
If that's not clear enough, look at the bug that was marked dupe of this one.
It's not my server so getting a testaccount might be not-that-easy. I'll try though.
Summary: UW IMAP 2000: Can't delete IMAP folders → IMAP Interoperability: Can't delete IMAP folders
Comment 11•23 years ago
|
||
Also seeing this bug. Here's the server's banner:
* OK [hostname] IMAP4rev1 v12.264 server ready
It's on a debian machine. APT identifies the package as:
Package: imap
Versions: 4.7c-1
Comment 12•23 years ago
|
||
From the description, the server used is a UW IMAP server or similar. This bug
is duplicate of bug 115988 which has been resolved.
Comment 13•23 years ago
|
||
*** This bug has been marked as a duplicate of 115988 ***
Status: NEW → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•