Open
Bug 894035
Opened 12 years ago
Updated 2 years ago
No error when copying IMAP folders between accounts fails
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: majik, Unassigned)
Details
(Whiteboard: [dupme])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.72 Safari/537.36
Steps to reproduce:
I dragged an imap folder from my Gmail account to my Dreamhost account.
Actual results:
Attempt 1: The folder was copied.
Attempt 2: The folder was copied.
Attempt 3: Nothing (literally).
Expected results:
When copying a folder from one account to another using IMAP the user should be notified when there is a problem and appropriate server error messages, if present, should be provided.
Additionally, no errors are present in the error console.
When I drag the folder and drop it, literally nothing happens.
I have discovered that I can copy one folder each time Thunderbird is restarted.
When I try to copy a folder with subfolders I get:
The current command did not succeed. The mail server for account [account name] responded: [TRYCREATE] Mailbox doesn't exist: INBOX.[folder name]^^[subfolder name].
It looks like the receiving IMAP server is trying to create the folders with the same special characters used by Gmail and failing; that Thunderbird is failing to report this.
I have narrowed down the problem:
Anytime Thunderbird encounters an unhandled error when moving messages in IMAP, it does not present an error and it refuses to process further move commands.
So dragging and dropping a folder after an error occurs means nothing happens when the folder is dropped.
I have around 30GB email to move them from IMAP to Local folder. There is no solution in Thunderbird if this won't be fixed.
Updated•8 years ago
|
Whiteboard: [dupme]
Comment 6•7 years ago
|
||
This is still an issue. I just copied 500 messages to outlook.com and only about 200 made it. No error message.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•