Adrian

We use Intella to process and convert large quantities of various government emails to PDF. Since public servants love to book meetings and most governments in Canada use Outlook/Office, the files we process regularly include many Outlook meeting invitations and replies. In Outlook these function as standard emails and save as .msg files. However, when indexed by Intella, they're treated as iCalendar/vCalendar files and thus do not properly export to PDF in native view like other emails. So while we can use Intella to rapidly convert large quantities of .msg email files into sorted PDFs in a way that closely or exactly mirrors the native file (i.e. including all basic metadata like to, from, timestamps, subject, attachments, etc.) it seems we have to manually convert any and all calendar .msg files because Intella only exports the basic text from the body of the invite and can't be calibrated to include the key meeting data (sender/recipient, subject, time/date, etc.). This makes the Intella exports of these files incomplete and unusable. I'm not sure what the best fix is, since I'm sure there are valid reasons for having Intella treat these as iCalendar/vCalendar files, but I would love to have some way to reliably convert these .msg files to PDF directly from within Intella like we can with other .msg files. Thanks!

Thanks Jon, will do. I'll need to find a sample email that replicates the issue but does not include any personal or sensitive information. When I locate I'll open a ticket and include the original email as well as the PDF export and export settings. Thx!

When exporting to PDF, certain text characters (particularly punctuation like apostrophes) consistently appear as non-standard symbols in the resulting PDF, such as in the screenshot below (from a .msg file exported to PDF: The apostrophe displays correctly in the Intella preview window, but in the exported PDF it appears as a series of symbols. My PDF Rendering options include: Content as original view For every email include: Body - Prefer HTML over plain text content (I select this option because I need the PDF to be the truest possible visual representation of the original email) Is this a known issue and is there a resolution? If this topic has been addressed before please direct me to it (I had no luck searching the forum and manual).

I'll second James on this feature. It will be very helpful for our workflows as well