Native copy or move message/folder function stops at first error
Hello, I am on Thunderbird 128.9.1 ESR, and I've observed that the native options to copy or move messages or folders from one IMAP account to another IMAP account fails when it encounters the first error such as the one mentioned below, and it never proceeds further. The problem is that it copies in some moves/copies the messages in an order that I am unable to comprehend, hence the folder move keeps getting interrupted with the same error. Is there an option in the settings/configurations that can be used to force TB to continue copying/moving even if it encounters an error? I got around this using the ImportExportNG extension, that did not stop the transfer if it encountered an error, but I had to export the folders through the extension before importing them. I'm now working on a nested directory, and I am hesitant to use the export/import option to avoid confusion.
Errors like this appear often: "The current command did not succeed. The mail server for account ProtonMail responded: unexpected char ':', for header field value: failed to parse header."
Thank you!
All Replies (2)
What you say is correct, the process ceases once an error occurs. That is how it works as Thunderbird is a mail client not a file system, resilience against errors was not something the original developers had much need for almost 30 years ago.
The import export tools will export mail to local storage and import it again into a local folder (still local storage). Or individual EML files which have I would guess have their headers parsed in the export process. It does not work with IMAP folders is my experience. But you are talking about IMAP errors generated by a third party product you are paying for in "proton mail" Have you raised your issue with them?
Matt said
Or individual EML files which have I would guess have their headers parsed in the export process.
I get these errors when I export it as EML files as well, but as I mentioned earlier, the import doesn't stop.
Matt said
It does not work with IMAP folders is my experience. But you are talking about IMAP errors generated by a third party product you are paying for in "proton mail" Have you raised your issue with them?
The transfer works for IMAP folders, but there is something that isn't acceptable by my IMAP provider - Proton. They wanted a copy of the message that is generating this error, but I have no idea which one it is since the imported ones appear in no particular order.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.