This Plug-in contains Functions and Smart Services that allow users to create and read email files containing all e-mail attributes, i.e. to, cc, bcc, from, subject, body, content type, and attachments. The generated file can be read by any email client that support EML files, such as Outlook Express and Windows Live Mail. The Plug-in and a help guide are provided with this listing.
This version is for Appian 25.2 and above. Customers on a lower version of Appian that want to install this plugin can find the latest jar for Appian 25.1 and earlier version by downloading from the AppMarket.
Smart Services:
Features:
The EML Utility plug-in does not correctly process EML files that contain nested MSG attachments.
In our current process, we use the EML Utility plug-in to read EML files and return a list of attachments. In version 2.2.5 of the plug-in, the nested MSG attachment was detected and converted to a TXT file. However, the actual content of the MSG file was not read; it always returned the value "jakarta.mail.internet.MimeMultipart".
After upgrading the plug-in (3.0.0, the latest), attachments are no longer returned at all. Neither the nested MSG attachment nor other attachments (for example, PNG files) are detected.
Thank you!
Hi,We are facing an issue in reademlfile(). When an email document containing one or more link address is used such as 'Click here: eur01.safelinks.protection.outlook.com/' in below image, the output body is returned as empty by the function.Below shared are the EML document screenshot that was used for processing and expression rule output -
THe plugin contains several bugs to distinct between HTML attachments and HTML as the body and not be able to detect the proper characterset. That is probably of the reason what is happening in your case. We fixed this but we only use it as a private plugin on our cloud instance now and didn't made those fixes public available.
We've been encountering an issue when reading eml files that are in html format. The eml files themselves can be downloaded and viewed in outlook without any formatting issues, but when we use readEmlFile() to extract the body of the email for display on an interface, the HTML doesn't come through properly and we get a lot of randomly broken characters.
Example 1 (apostrophe):
Example 2 (emoji):
Hi Mohammed
do you solve this issue ?
we have the same issue
UPDATE: It only occurs when the attachment is an HTM/HTML. Do you have any idea?
Hi,
We are using this plugin to read an email and display the body in an interface. This works fine when the email does not have an attachment, however, when it does, it is displaying the attachment information instead of the email body (what I mean is that the body parameter has the attachment information instead of the email body).
Is anyone else having the same issue? Thank you.
Is The current version compatible with Appian version 25.3?.