I was running into a problem with my Trim 22.214.171.12455 installation where it wouldn't preview catalogged emails properly, instead showing the message as being blank. Relaunching the Trim client fixed the issue, so it looks like there is some sort of condition where the client corrupts its memory or something.
Oddly, whenever we try to view such EML files in Outlook 2010, they are displayed as gibberish. Is this email format expected to work in Outlook?
I've attached a screen shot showing what I get when I try to view Trim's EML messages in Outlook 2010 x64. After messing with it some more, I noticed that if I supercopied the file and renamed its extension to .MSG, it opened properly. I think there are some instances where the Trim client malfunctioned and saved files with the wrong extension.
Edit: Trim doesn't allow cataloged emails to be checked out or have a new revision added. Short of destroying the record and recreating it with a properly-named file, is the only way to resolve this to edit the name of the document in the database and then rename the file in the document store to match?
Edit 2: This may have been user error, it doesn't seem like Trim caused this. Is there any way to use the Trim integration to create an EML file short of catalogging the message into Trim?
Trims EML displayed in Outlook.jpg, description:Trims EML displayed in Outlook.jpg
As I mentioned, I determined that this was user error. There was a malfunction of a SAN volume and we had to manually recover some files that had been entered between backups of the document store. Somehow messages that had originally been catalogged via the Outlook integration (EML format) had been restored to the document store by taking an MSG file and renaming it to EML so that it simply matched the original file name. Since I wanted to resolve it quickly I took the MSG files, put them into my mailbox, entered them into our development dataset via the TiO integration, super copied them to get EML files and put those EML files back into the production document store.
It doesn't seem that you're aware of a way to have the Outlook integration create an EML file any other way, so it seems this is generally the process I would have had to use anyways. I tried your theory about the extensions, but Outlook 2010 will not open an EML file renamed with an MSG extension or vice-versa.