Closed Bug 59441 Opened 25 years ago Closed 25 years ago

IMAP: Empty trash command leads to an error

Categories

(MailNews Core :: Backend, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 56826

People

(Reporter: momoi, Assigned: mscott)

Details

** 11/6/2000 Win32 Branch build ** I have my options set to "expunge" Inbox and empty Trash folder upon exit from my IMAP server (nsmail-2). When I log out of my account, I always get an error message on a warning dialog window saying that the "The comman did not succeed because the mailbox does not exist.) In fact I get the same message when I try to empty the Trash folder manually. I'm getting the same error message on another IMAP server I use for Intl group. putterman reports that he is able to empty the Trash folder without this warning. So this is not universally experienced. I have been getting this message for some time now, however. The good news is that the trash folder actually gets emptied even though the error message shows up.
By using the same build and same server (netscape messaging server: nsmail-2), I got the same results as Scott -- I didn't get this Alert.
I am pursuing some hunch right now on this but this will take some time. Will report back later.
it's just because you have some sub-folders of the trash that have modified utf-7 names that are different from their actual names- you're probably unsubscribed to them, but we try to delete them anyway. It's a known bug, I believe.
There turns out to be a prior bug on this. David's right. This was a case of IMAP Trash folder containing folders with non-ASCII or special characters. Marking it as a duplicate of Bug 56826. *** This bug has been marked as a duplicate of 56826 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Thanks for finding that duplicate. Verified as duplicate then.
Status: RESOLVED → VERIFIED
QA Contact: esther → huang
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.