OLE embeddings in Outlook Emails sent in Rich Text format

book

Article ID: 100014967

calendar_today

Updated On:

Description

Error Message

  • Text view:
    Viewing an “OLEAttach_” file in Clearwell Text view results in the following error:

    No HTML version of this document is available for display.
    Click on the download link to display the file in native form.

     
  • Native view:
    Viewing an “OLEAttach_” file in Clearwell Native view results in the following error:

    Error preparing document for display.
    [#41057] Content processor error - com.teneo.esa.imaging.ImagingException: [#670200] "Imaging failed: Stellent conversion failed."

     
  • Productions:
    An image production of an “OLEAttach_” file will fail, i.e. it will slipsheet.
     
  • Exports:
    A Clearwell export with natives, with the option “Break out attachments as separate items”, will export these “OLEAttach_” files in their original binary format. These exported “OLEAttach_” files are not given a file extension and are not viewable by any application (Figure 2).

    Figure 2.

     

 

Cause

Clearwell can successfully extract OLE embeddings when an email is sent in “Rich Text” format, but it cannot decode them. Clearwell extracts these embeddings as attachments with names beginning “OLEAttach_”. These files are in a binary format known as “Microsoft OLE Compound File Format”.

This issue most commonly occurs with email signatures that contain an image. However, other OLE embedding types are possible when using the “Insert” menu in Outlook.

Note: This issue only occurs when an email is sent in Rich Text format. This issue does NOT occur in the following situations:

  • When an email is constructed and sent in HTML format.
  • When an email is constructed in Rich Text format and is sent outside of a company network (i.e. sent to the Internet) and the Outlook option “Convert to HTML format” is specified (Figure 3).

    Figure 3.

 

 

Resolution

The only way in Clearwell to view the content of these “OLEAttach_” files is by viewing the parent email in Native view.

When viewing the parent email in Native view, it is usually obvious which parts of the document are likely to correspond to the “OLEAttach_” embeddings. However, if there are multiple “OLEAttach_” files, it is not obvious how to match-up each with the contents of the parent email. If a user cannot identify the contents of each individual “OLEAttach_” files, they will not be able to associate meaningful tags or comments with each item. It is actually possible to identify the contents of each "OLEAttach_" file outside of Clearwell, but the process is manual and time-consuming. Please contact Support for further details.
 

Issue/Introduction

When Clearwell processes an Outlook email that contains OLE embeddings, and the email is sent in Rich Text format, Clearwell extracts the embeddings as attachments with names beginning “OLEAttach_” (Figure 1). These “OLEAttach_” files are in a binary format known as “Microsoft OLE Compound File Format”. Clearwell does not recognise or decode this file format. These “OLEAttach_” files are therefore not individually viewable in either Clearwell Text or Native view. The only way to view these embeddings is by viewing the parent email using Clearwell Native view. Figure 1.


Additional Information

ETrack: 3701507 JIRA: null