I have pretty much finalized a decision to move from Apple Mail to PostBox, as a result of the Catalina data loss issues long discussed on the blog.
My current situation is that I have two local (On My Mac), multi-level, folder trees.
One that is “active” now in the Apple Mail app, within which there was a loss of ~30 Gb of mail and attachments during the Catalina upgrade. There is a mix of pre-Catalina mail content, and up to date mail content there. Not all pre-Catalina mail content was lost during the upgrade, but a lot of it was.
The other is a complete backup of the Apple Mail folder tree from October of 2019, just prior to the Catalina upgrade. So, everything that I had pre-Catalina is contained there. That backup is in a tar archive. Amazing to think that we have been dealing with this for well over a year…
Thus, my question about best practice for moving both sets of folder trees to PostBox, while taking advantage of the duplicate mail filtering in EF. Ideally, I would like to have the intersection of the two sets of folder trees moved into PostBox, and delete the duplicates that will inevitably result, where some of the pre-Catalina content is in both trees.
I noted that there is a delete duplicate script available, as well as a merge folder function available in EF.
Would the logical steps be along the lines of:
Import the “live” local folder tree from Apple Mail into EF
Import the archive local folder tree into a separate target folder tree in EF
Merge the parallel folders from each tree in EF
Run the delete duplicates script on the merged folders
Import the result into a PostBox local folder tree
Does that make sense or am I missing an easier pathway?
Also, will the merge functionality handle a folder and its sub-folders in one step, or only a single folder at a time?
Lastly, given the substantial space requirements of all of this, I presume that I can use an external HD for the EF Library? I am considering getting a large external SSD to handle all of this for space and speed.