Unfortunately, Mail did not say why it couldn’t import the “Test 1” e-mail. Perhaps there is something wrong with the mbox file or perhaps there’s a bug in Mail. If you would like to send me (off forum) the mbox file I can take a look at it, or you could try importing into a different mail client (such as Thunderbird) and see whether that works better.
Thank you very much for your answer. The directory was previously recreated in Apple Mail. Subsequently, the 5 test mails were sent to my e-mail address and moved to the mail directory/mailbox. Test mail 5 contains a file attachment.
I will send you the test data by mail or download link.
MacBook Pro, M1, 2020
macOS: Version 11.6.2 (20G314)
Mail: Version 14.0 (3654.120.0.1.13)
EagleFiler: Version 1.9.6
Sorry, but I’m not sure what this means. Which directory? Previous, meaning before importing from EagleFiler? If it was recreated, does that mean that at some point you had deleted it?
Thanks. It looks like Mail is getting confused because the first test message had an empty body.
In Apple Mail, 5 test emails were created and moved to a mailbox in the left sidebar of Apple Mail. I’ll send you a short video about this in a moment.
Thanks. It looks like Mail is getting confused because the first test message had an empty body.
Yes, there seems to be a problem with this if the email body is empty. Since I often send myself mails as notes that only consist of a subject line without an email body, this can happen.
The behaviour is reproducible, see
2021-12-30-EagleFiler-Test-1.mp4 (e-mails with subject and body)
2021-12-30-EagleFiler-Test-2.mp4 (e-mails with subject, without body)
Can the problem be solved with the help of EagleFiler?
For the next version of EagleFiler, I’ll look into whether it can “repair” such messages on import or export so that Mail will be able to import the mbox file properly.