There are some gotchas in this process where EM Client may be able to assist in.
Firstly, it’s a question of personal preference of storage of messages in folders. Ideally, all saved messages should be stored in local folders, failing that, the Archive folder option looks attractive. So far, so good, and we also know it, and any other standard folders are synced with the mail servers as soon as EM Client starts, and the messages on the server are removed if there be none on the current restore machine.
The only way to prevent this happening on a restore machine, is for EM Client to save a date token on last use of the program, so if it hasn’t been run for some (configurable) time, a popup on launch goes something like:
EM Client has not been run for some [specified] time. If there was a backup made from another source, it must be restored now, or else the mail servers will be syncing with older messages from the current database, and data will be lost.
Continue (Have a backup to restore from)
Continue (No backup to restore from)
This is useful in situations where the EM Client D/B is stored on local machines. Ideally, we’d all want to run the D/B through the cloud, by the looks of it, the way forward is not completely clear yet.
Edit: Also, a “replacing existing” option for Restore to avoid multitudes of duplicates populating the D/B.