I’d like to offload my years of legacy email into EagleFiler. To test the process, I used the F1 capture key to import one folder (and its many subfolders) of messages from Mail.app. The Errors log showed many entries that looked like:
Missing Apple Mail Message Attachment
Question 1: Is there a way for me to use the info in the error message (“100610”) to figure out which email message triggered the error message?
To investigate these error messages, I looked at some messages in EagleFiler that had attachments (using the “#” column), and tried to open those attachments by double-clicking that record. In some cases that worked (i.e., Mail.app opened EagleFiler’s copy of the message and then I could open the attachment).
However, in other cases when Mail.app opened EagleFiler’s copy of the message, the attachment showed up as an icon with a downward-pointing arrow, indicating I needed to download the attachment from the server.
- When I clicked on the downward-pointing arrow, the icon changed to have a progress bar, and blue text “Downloading…”.
- The “Downloading…” indicator never went away: EF never successfully downloaded the attachment. This despite the fact that:
- When I located the original message in Mail.app, it DID have a fully downloaded and available and openable attachment.
Question 2: What can I do about these attachments that (a) aren’t being correctly imported by EF even though (b) they are fully downloaded and openable from my original emails?
I note that my problem sounds like it might be related to a thread “Mail macOSX Sierra Import messages script problem?” from September 2016. That problem was supposed to have been fixed by EagleFiler 1.7.2. (I’m running EF 1.76.)
I’m running macOS Sierra 10.12.5.