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)
Mike Cichy To add to (Sonakshid874) the below error we are seeing in PROD. So we have few mailboxes that are to be monitored. If I enable one, the process ran fine without any errors. I enable the second mailbox, the process failed with error "Mail poller already running -- mailbox 2". It keeps on repeating that same error for every run. Ran out of ideas and can't figure whats going on. Any help or input is appreciated. Please let us know.
You can only have one instance of mail poller running at any point in time. You need to configure the node either to poll mailboxes in sequence, or for mailboxes to forward all mail to a single mailbox.
How much unread mail are in each of the new boxes that you are adding in? At a high level it sounds like the backlog of unread items is either high in quantity or size (or both)
Kenneth Chen We have marked all mailboxes to inactive. Mark, enabled one mailbox and cancelled all active instances, ran the inbound process manually. It succeeded without any error. Next we enabled another mailbox, then it failed giving error message that the first mailbox is already running. After 15-20 mins, both of them ran successfully. Again Mark enabled 5 mailboxes, we got the same errors, after few runs all 5 ran successfully. Now we enabled all and the errors are random. Sometimes all run successfully and the next run will fail....so on. The only change we did was downloaded the new plugin after Mike's changes. Just checked and we are still receiving the "already running errors". Any pointers on what we might be missing to look for since we have ~19 active mailboxes.