Overview
This version is for Appian 22.3 and above. Cloud customers on a lower version of Appian that want to install this plugin should open a support case. Self-managed customers can find the latest jar for Appian 22.2 and lower version by downloading from the app market.
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.
Key Features & Functionality
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)
Hi Mike,
i am using Appian Cloud env however, the mailbox i need to configure in on MS Azure Cloud. Will the connection get established using this Plug In?i tried however, I am getting an error "LOGIN failed"
The configurations I made are as below:
protocol: imaps
Port number 993
NOTE: Encryption method is TLS
Java keys: "mail.imap.connectiontimeoutmail.imap.timeoutmail.imaps.fetchsizemail.imaps.auth.plain.disablemail.imaps.auth.ntlm.disablemail.imaps.auth.gssapi.disable"
and have used its related values as mentioned in the documentation
There should not be an issue connecting to Azure Cloud. Can you establish the connection using the details and credentials using a standard email client? If you cannot, I would suggest reviewing permissions in Azure.