whenever I enter a folder containing *.eml files (email data), DO seems to touch all of these files.
After entering the folder and 2 seconds later all the modified timestamps are set to the current date.
You can actually watch the modified timestamps changing.
I have no script columns activated (folder format: default)
this also happens for DO v10
DO spins its blue circle while that happens
it happens on Win7 and Server2008R2 (where definetly no office or something is installed)
eml files are associated with "emClient", not Outlook or something on the Win7 machine
it does not happen when using Explorer
Any idea why that is and how to stop it?
Thanks! o)
I have encountered an .eml timestamp problem for the first time since installing DO on a new laptop under Windows 10. I save emails in .eml format with their original timestamp, then when I right click on one its "modified" timestamp changes to the current time. I have turned off indexing for .eml and .msg files but it doesn't solve the problem.
I can copy and paste the file with Ctrl-C / Ctrl-V and the original timestamp is retained in the copy and the original, but recurs when I right click the files. I can rename the file (by left clicking the filename) to .txt, open it in Notepad with a right click, close it, and the original timestamp is retained. But if I then rename the file from .txt to .eml and right click to open it I am back to square one - the timestamp changes immediately (before the file is opened).
Is DO doing something that it didn't under Windows 7 and is there something I can do to work around it?
It has nothing to do with Opus. It's a bug in the EML shell extension by Microsoft which has been unfixed for many years, and which also affects File Explorer and anything else which triggers the shell extension.
(I'm not sure why the other thread linked above is deleted. Looks like the person who posted it deleted it, but it had useful information. Will try to restore it later on.)
(The summary remains the same: It's a bug in a Microsoft component that dates back at least 12 years now and affects lots of software. You can disable the component as a workaround if the timestamps are more important than the information it provides.)