That should work, right? Assuming EagleFiler continues to work as it has.Collect notes, e-mails, and Web pages on your Mac, and search them instantly. Much smaller than having to continue to live with a badly broken Apple Mail (maybe broken, from what I read, by my keeping so much mail that it overwhelms Apple's bizarre structure for storing messages). I expect that (now that I know what works and what does not) I can 1) select the remaining 20 or so Apple Mail folders, hit the EF grab key, F1 2) one by one, import the resulting mbox files and then nest them by drag and drop. I now understand that I must do this the longer way. Of course, the reason for that was to reduce the work of importing many folders from Apple Mail.
Looking at the result with both EF and Finder, the structure was as expected, two level "folders," some with a single mbox. (Did not check to see if all were there, trusting Tsai and yourself.) Then tried a nested structure by asking EF to take it in. Did that a couple of more times with larger mboxes. What I did with EagleFiler is first ask it to take in (into EF) a single Apple Mail folder, then used IET to import that as an mbox. That is quick and would help slow persons such as myself. At the multiple import entry, you might want to add this after 'EML' : '(only)'. (I see now at the top of Help, that it is listed as a format. (That is, I did not know there was a format with that name. I do see the string 'EML' in the text, but I had no idea what that might mean, unless it meant e-mail message. This was quick, does it describe things enough? as I dictate, I take some shortcuts! just for reference the EML import is the only way to maintain structure currently. I think that is the closest thing to use. The names of the imported mailboxes folders will be that of the actual mbox filename, not the containing folderĬhoosing the last important option will traverse the subdirectories but import at the same level. The problem is that the extension does not currently support importing a structure with mboxįormat, although it will traverse a structure and import all m boxes at the same level. The radio button dialogue that comes up after choosing Import mbox gives you four options.Īs I understand it your file structure does not utilize 'sbd' names for subfolders. From the help you can see Import Messages is for EML files and not relevant for you. The menu item import mbox is the option you want to use. The extension as I took it over has some quirks regarding structured e-mail folders.įirst, we are clearly talking about importing mboxes, not EML. I took a quick look at EgaleFiler but did not see the exact file name/file structure of an export. I am curious if you looked at that.Ĭouple of things, I think you may have seen some of the other posts regarding Apple Mail based on your first comment. What I did add is a good start at internal help pages, but I do make it clear what the menu options are. I am hoping to do this in the next revision. The menu structure has to be made clearer. !( for the post and especially the donation! Could that be why the selection dialog goes down the directory hierarchy, instead of importing the selected directory with its subdirectories and mbox files? Now: Eagle Filer has not added the string '.sbd' to the subdirectory names. Instead the selection window changes to show the subdirectories, apparently wanting me to select one (the button does not change. ImportExportTools NG does not then import that directory and its subdirectories and messages. I select the folder created by EagleFiler (which has the structure of subdirectories with mbox files. When I make that choice, the selection window comes up, showing, as with single mail boxes, the EagleFiler directory EagleFiler is using. I see from the ImportExportTools NG Help that the correct choice might be Menu>Tools>ImportExportTools NG>Import all messages from a directory>also from its subdirectories. When I select in Apple Mail a folder with subfolders, EagleFiler creates a directory with subdirectories and an mbox file wherever there are messages. When I export a folder with only messages-no subfolders-and then import the file created by EagleFiles using ImportExportTools NG by selecting the file that EagleFiler generated, it is imported as expected: that is, a folder is created in Thunderbird with the same name, and it contains the messages. To avoid any problems from using Apple Mail export, I am exporting the mail folders using EagleFiler. I am switching from Apple Mail to Thunderbird.
0 kommentar(er)
