I have been making different tests with email import and archiving from Apple Mail to DT3 lately, to gain familiarity with the different ways to import, archive, and in general deal with email using DT3.
I am in the process of dealing with a multi-year backlog of old emails which I’d like to keep in a searchable database on DT3, while at the same time implement new workflows to keep Mail.app, DT3 and OmniFocus working nicely as a team. So far so good.
The only blocking issue I have is with the pesky UUID issue with email that I have already imported sometimes in the past, something which is preventing me from finalizing the import of a long MBOX file with the old Archive mailbox.
Since the Archive is some 18G large, with little more than 73k messages, I tried to import it in a single shot but the import failed around 35% or so.
Now I have split th MBOX file in 3 chunks (very easy to do on the CLI, thanks to awk!) and, even after creating an entirely new database the import reaches the end but gives the pesky “10130 previously imported“ message in the log.
Effectively, it looks like some 10k messages have their UUIDs already somewhere within the guts of my test DT3 setup.
Why does this happen with a brand new database, to begin with? Shouldn’t it be the case that UUIDs are only kept for documents which are in the open database? Maybe they had been imported in the Global Inbox and deleted, granted, so this might be the answer.
Thus the question now becomes, how can I fix this issue? Can the UUID “database“ hidden somewhere in the guts of DT3 be purged altogether?
This is a different test machine that I am using, so I would not have a problem in clearing up my DT3 installation and starting from a clean slate. Can I do this with some CLI commands or do I need to completely uninstall and reinstall DT3?
I am quite good with the Unix CLI so I don’t have any issue in “going under the hood“ if needed.
I very much look forward to using DT3 as a working repository for email moving forward!