Closed
Bug 577490
Opened 14 years ago
Closed 12 years ago
Can't delete IMAP folder unless account is set to Remove messages immediately on delete.
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 284933
People
(Reporter: nyle, Unassigned)
Details
(Keywords: imap-interop, Whiteboard: Protocol log attached)
Attachments
(1 file)
21.81 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100611 Firefox/3.6.4 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100608 Lightning/1.0b2 Thunderbird/3.1 I can't delete IMAP folders from our server unless the Server Settings->When I delete a message is set to 'Remove it immediately'. It receives a standard message of 'The current command did not succeed. The mail server for account user@domain.com responded: RENAME failed: 4224.' Reproducible: Always Steps to Reproduce: 1. Click to delete and IMAP folder. (Running on M+Netmail 3.6) 2. Receive error 'The current command did not succeed. The mail server for account user@domain.com responded: RENAME failed: 4224.' 3. Change server setting and you can delete the IMAP folder) Actual Results: No special steps to duplicate, except be using an industry standard IMAP server that follows RFCs. By simply setting the 'Remove it immediately' the IMAP folder will delete. Expected Results: One would think that a simple fix to this bug would be that when the error is returned from the IMAP server, Thunderbird could prompt the user to ask if it should 'Remove it immediately' since it is unable to move it to the trash. Instead it simply throws the error and making the user manually change a setting on the server settings and then change it back which is the typical preferred behavior. No crash, seems to be in the default product without addons other than Lightening. Which should be built into Thunderbird or at least installed by default with an option to remove IMHO.
Reporter | ||
Updated•14 years ago
|
Updated•14 years ago
|
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: folders-message-lists → networking.imap
Version: 3.1 → Trunk
Comment 1•14 years ago
|
||
Nyle, can you attach an imap:5 log to the bug? https://wiki.mozilla.org/MailNews:Logging (only developers set/use bug priority)
Priority: P5 → --
Whiteboard: [needs protocol log]
Reporter | ||
Comment 2•14 years ago
|
||
Sorry for the delay in the requested imap:5 log. My spam filter must be blocking bugzilla emails.
Comment 3•14 years ago
|
||
5376[6ab3e00]: 64c3800:imap.boces.com:A:CreateNewLineFromSocket: 9 NO RENAME failed: 4224 That's not a particularly informative message that your server is giving us; we can't tell if that's going to be something temporary, or if the normal trash works, or what...Do you have messages in the trash folder? Does your server want folders to be under the INBOX, or did you deliberately create folders as sub-folders of the INBOX? I'm wondering if maybe it wants Trash to be under the INBOX as well.
Reporter | ||
Comment 4•14 years ago
|
||
Interesting, I'm running Messaging Architects M+Netmail 3.61. I created the folders under the inbox because I prefer them to be directly under the inbox. I've tried creating them not under the inbox and it still won't let me delete without the error. Messages deleted in Thunderbird go into the trash folder in the email servers web interface as well as the trash folder shown under my Thunderbird mail account. The trash empties properly in both locations from within Thunderbird. Listen I work as a beta tester for M.A., I'm by no means a protocol expert at all but if you can explain to me what details you need - I can likely get them for you.
Whiteboard: [needs protocol log] → Protocol log attached
Comment 5•12 years ago
|
||
I am guessing that with this particular mail server, you cannot have both messages and sub-folders in the same folder, thus marking as DUP. Looking at the log, it appears that the server does not issue mailbox(folder) flags even for the LIST command, which means it is not possible to detect the folder behavior. Using the "Server supports folders that contain sub-folders and messages" setting may also be a workaround.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•