Timestamp on email files keeps changing
I have a program that syncs files between two different PCs. This software checks every two hours to make sure all of the files are in sync.
I have some emails that I saved and they will be in the files that are in sync between the two PCs. Thunderbird keeps updating the timestamp on the files. This causes the program to think that the file has been updated and it is in the list to be updated.
I am assuming that Thunderbird is updating the timestamp since only Thunderbird email files get updated.
Why does Thunderbird keep updating the files?
Can it be configured not to update the timestamp unless something changes.
Chosen solution
Once you save messages as eml files, they are stored outside of the TB profile folder and are not affected by TB. Only an external program or process could be affecting the timestamp, which seems to be what you have found.
Read this answer in context 👍 0All Replies (3)
TB stores messages in one file per folder by default (mbox format), so every time a message is added or deleted, or the folder syncs with the mail server, the time stamp may change. Even if messages are deleted, the mbox size may not change until the folder is compacted and deleted messages are permanently removed.
To sync mail between devices, the usual approach is to have all accounts set up as IMAP.
Let me make sure you understand.
I have an email, I right click on the email, I select Save Selected Message / EML Format. The email is saved.
EML file extensions are associated with TB. Something is updating the timestamp on these .eml files. I am assuming it is TB since these .eml files are the only ones doing this.
I may have resolved the problem, only time will tell. I found a problem on Microsoft. They had the same complaint. The suggestion was to turn off indexing on .eml files. I did that and it appears the problem stopped.
I will let you know.
Chosen Solution
Once you save messages as eml files, they are stored outside of the TB profile folder and are not affected by TB. Only an external program or process could be affecting the timestamp, which seems to be what you have found.