Archiving and HTML-to-MHT conversion

If your EngageOne Deliver application is configured to send outbound HTML email messages and opts to archive these outbound messages in their original (parts) format then it will generally not suffice to only archive the HTML of the message. Otherwise HTML retrieved from the archive may not display properly and it will be difficult to manage the images that the archived HTML references.

EngageOne Deliver converts such messages to an HTML archive format (.MHT) which stores the HTML together with referenced images embedded in a single file.

If EngageOne Deliver is configured to convert HTML to PDF or PDF/a for archiving and the email contains embedded images, the images are extracted and HTML is rewritten to reference the location of the extracted images, prior to calling the Open Office conversion routine. This ensures that HTML email content with embedded images is converted to PDF correctly.

If the email contains referenced images, EngageOne Deliver checks for the value of the Referenced Images checkbox in Inbound Profile. If it is enabled, the external images are downloaded and HTML is rewritten to reference the location of the extracted images prior to conversion to HTML archive format (.MHT) or PDF format as described above. If the Referenced Images checkbox is not enabled, EngageOne Deliver ignores them.

Note: For referenced images, the full path of the source must be in the email (in HTML format) and/or the attached HTML file. If referenced images do not exist and the Referenced Images checkbox is enabled, an exception will be generated and a workflow item will be created.