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,
We are facing an issue with the Mail Poller plugin after upgrading to Appian 25.2. The plugin is no longer working, and our email poller process model is failing.
We suspect this is due to the version upgrade, as it was working fine before. Has anyone else experienced a similar issue with this plugin after upgrading to 25.2?
Appreciate any help or suggestions.
Thanks
Thanks for the update.
May I ask which plugin you're using for the same email polling functionality? It would be helpful to know if it's available on the Appian AppMarket.
turns out our issue was with a different plug-in but the same functionality. Appian Support responded quickly with an updated plug-in to handle the jakarta lib issue and it's working fine now!
Thanks, Matt.
We’re also raised a support case with Appian. Just checking—did you get any update from them or come across any alternative plugin or workaround that works with Appian 25.2?
Let’s stay in touch here in case either of us hears anything from Appian Support or the plugin maintainers.
Having the same issue. We've reached out to Appian Support.