Enhancement to the plug-in to enable the selection of whether or not to include the email attachments as part of the EML document. Previously, the plug-in would create an EML document with the attachments stripped out. Our client needs to preserve the original e-mail as it was sent (for auditing purposes), so the EML must include the attachments as part of it. This update extends the functionality to allow the user to select whether they want an EML with the attachments removed (original functionality), an EML with attachments included, or both (2 EMLS of original email - one without the attachments included and one with the attachments included). Any e-mail attachments will continue to be saved separately. Takes all unread email from a mailbox and adds entries directly to a database table.
The original email is saved as an EML based on three attachment type options
Each email attachment is saved as its own document. The database tables store the Appian document ids, email recipients, subject and body (text and HTML).
Please refer to the attachments included in the download for further documentation and examples.
This an older update we did a couple years ago to allow saving different types of eml, -1 just states that the id is not available.
The CDT is updated to add the DOC_ID_WITH_ATTACHMENTS column. That is working fine. Just wanted to understand what is it representing the value update as -1 in the same field.
Thank you for the update.
Yes we have TLS1.2 connection set up.
Yes, the version that was just published (1.1.6) is compatible with the latest update to Java and 21.3.
Please be mindful that the plugin will no longer work with TLS 1.0 or 1.1, so make sure your mail servers have the right support.
The new version of the service which is compatible with 21.3 is available for user?
Any update on the availability of above mentioned issue fixed version?
Thanks for the update. Will wait for the fix to be available.
We just found about this yesterday - it is actually the Java upgrade that likely coincided with your Appian upgrade that breaks the plugin. We have identified a fix and should have it available by the end of the week.
This plugin is giving an error "No appropriate protocol (Protocol is disabled or cipher suites are inappropriate) " .
The plugin was working fine until now.
But this behavior is encountered post the 21.3 upgrade(Not sure if this is the cause and also there is no changes to the shared mailbox). Any help or suggestions?
© 2021 Appian. All rights reserved.