Updated mbox file import crashes DT

Hi Folks:

I’ve been experimenting with archiving emails via the mbox import facility. I have assumed that I would be able to import a ‘later’ version of the mbox into my DT archive, rely on message id uniqueness to prevent duplicate entries, and capture the difference between the previous import and the new one.

So far I find that this doesn’t work and results in a reproducible crash.

If the source mbox has the same name as the originally imported mbox a new import will start with a new group nested in the original group with the same name. It will crash DEVONthink in short order. If the name is changed then a new group is created and the system crashes as well. This occurs whether or not I have enabled the ‘Previously imported messages will become replicants’ option.

My constraint is that I can only generate full mbox archives from my provider. Am I wrong in expecting to be able to do this type of operation?

Thanks

Crashes should be reported to our support ticket system.

1 Like