Open roberts1000 opened 2 months ago
@roberts1000 Thank you for the detailed report. I have not looked into the compact issue yet, however, I had a fundamental error in the EML import on Thunderbird v128. Messages were corrupted on import. If you can try b3 beta it may well solve this. If not I will investigate. https://github.com/thunderbird/import-export-tools-ng/blob/v14.1.3/xpi/beta/import-export-tools-ng-14.1.3-b3-tb.xpi @cleidigh
@cleidigh Thanks for the suggestion. I gave 14.1.3-b3 a shot and it does seem to fix the issue! I'm able to import, detach, trigger the compact process and the imported emails continue to render correctly. It appears the error you found/fix was the culprit.
The only issue remaining is, I now have several emails that are corrupted. I tried to export and re-import one email that was clearly having problems, and one that was still rendering correctly (but was imported using an older version ImportExportTools NG, so it likely has issues). They look the same after the re-import, and, when I run Thunderbird's Repair tool on them, Thunderbird still discards them. So it doesn't look like an export and re-import helps get them back on track. I also tried to export, and then import them back into the original email service, but the service thinks both email files have errors in them.
@roberts1000 Great, I was hoping b3 would address your issue ! I think without actually having your mbox and investigating it I could not tell you what to look for unfortunately. @cleidigh
@cleidigh When multiple EML files are imported, The symptom that the raw data of the first imported email is added to the end of the next email to be processed has been improved. Thank you.
I recently started exporting emails in .eml format from my provider, then importing them into Local Folders. The process appeared to work fine at first, but after a few days, I started noticing issues with the imported emails:
Symptoms/Issues
I think I've traced this back to the compaction process that Thunderbird uses. I can't say for sure that ImportExportTools NG is involved, but the corrupted .eml's are only the ones I imported using ImportExportTools NG.
To Reproduce the Error
Other considerations