I want to use the data contained in the Thunderbird profile folder of an IMAP account for email backup. Therefor I seek predictability as a precondition for reliability in terms of email restoration. To this end I conducted a restoration test and now find that I have several mails manifold restored in TB.
These are the details of the test in timely order of their occurrence:
I
- in TB subscribed to all folders
- untoggled
- “Keep messages in all folders for this account on this computer”
- “Don´t download messages larger than” (under “Synchronization & Storage > Advanced…”)
- chose all of the desired folders “for offline use” (under “Synchronization & Storage”)
- toggled “Synchronize all messages locally regardless of age”
- shut down TB
- sent a message, labelled
4, from some email account (at mail provider GMX) to the actual email account (different mail provider), using therfor the provider´s front end with a web browser (i.e. not a dedicated mail client) - started TB
- marked the (received) message
4in thejunk or spam suspectfolder in TB as being “not spam” because the message had wound up just there; TB at that automatically moved the message to theInboxfolder - dragged this message
4fromInboxinto a folder namedC(of the same email account) - shut down TB
- sent three messages, labelled
6,7and8(using the same method as before with message4) - on the web interface of the actual email account dragged message
7from theInboxfolder into a folder namedA(obviously of the same email account) - started TB
- dragged message
8in TB from theInboxfolder into a folder namedB(of the same email account) - took notice of all four messages being unique each (i.e. no duplicates anywhere) and still being marked “unread”
- shut down TB
- copied the
mboxfiles of the IMAP account from the profile folder of my working TB installation, once with and once without the corresponding*.msffiles, to folderLocal FoldersAcnt(in “[path of profile folder]Mail”) of a separate TB installation on a virtual machine; I had taken care to delete every file and folder inAcntbefore copying these files - started TB on the virtual machine
The result of the “restoration” of the emails on the virtual machine is (other than the presense of some headers in TB as provided by the *.msf files and the recognition by TB of several folders as being special, like Junk folder e.g., either which is as expected, the result when copying also the *.msf files is the same as when not copying them):
- message
4is trifold present, twice in theInboxfolder and once in folderC(should be inConly) - message
6is double inInbox(should be only once) - message
7is solely present in folderA(as should be) - message
8is double, once inInboxand once in folderB(should reside only in the latter) - none of the hundreds of other messages are manifold present
- the messages
4,6,7and8and all their copies are marked “read” right from the start (which they shouldn´t) - messages
4and6are each stored double in themboxfile corresponding toInboxas well (which is in accordance with the observations described above), while the copies featuring the exact message-ID of their originals and deviating approx. 4 minutes from the time stamp (i.e. “Date:” header) of the originals each - each and every copy and original of the messages
4,6,7and8has “X-Mozilla-Status: 1” in themboxfiles
However, when I
- compact the folders of the IMAP account in TB
- copy the
mboxfiles from the original TB installation to the TB installation on the virtual machine like done before (see above description) - start TB on the virtual machine
the result (on the virtual machine) is
- no more manifold message in TB (as should be)
- the messages
4,6,7and8and all their copies are marked “read” right from the start (which they shouldn´t) - the messages
4,6,7and8reside in their proposed folders each (as should be)
The result from compacting the folders suggests all but one of the copies of the messages 4, 6 and 8 having been marked “deleted”. Telling from the “X-Mozilla-Status” set to 1 however they have been merely “read” but in no way “deleted”, yet they are no longer present in the mbox files after compacting, and they aren´t displayed in the original TB installation. Thus I deduce that TB must store the information about which messages are to be obliterated (and thus not to be displayed but to be removed from the mbox files during the next compacting run) someplace other than in the mbox files and also than in the *.msf files.
Since try compacting IMAP folders after the fact, i.e. under restore conditions (and hence offline), is futile:
What can/must be done to restore the IMAP mails from the profile folder such that at least there is no manifold message occurrence?
As an application example, imagine that some day the connection to the mail server for any reason cannot be established so one has no chance of prior compacting. I´d want to have all emails assigned to synchronization restored from the profile folder, completely, neatly and without excessive effort. And without having the same emails spread over all possible folders.
I have seen a lot of posts dealing with TB backup, I haven´t found one however to dig into how to obtain a sophisticated backup from the profile folder while addressing this issue. I am neither going for a filters-and-Local-Folders nor a use-additional-software solution.
Installation specifics
- TB 140.3.1ESR both with original TB installation and with TB installation on virtual machine (VirtualBox)
- Windows 10 both on corporeal PC and on virtual machine