Mail Poller

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

  1. EML with attachments removed
  2. EML with attachments included
  3. Both (2 EMLs of original email) - EML with attachments removed and EML with attachments included

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)

Anonymous
  • Hi Mike,

    Just checking in—any update on the fix for the plugin issue related to the Jakarta library?

    Thanks for your help!

  • 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, appreciate it - looks like we need to update the code for the jakarta lib update.

  • 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.

  • Below is the relevant system log error:

    Caused by: java.lang.IllegalStateException: Error while searching for service [jakarta.activation.spi.MailcapRegistryProvider]
    at jakarta.activation.FactoryFinder$1.createException(FactoryFinder.java:30)
    at jakarta.activation.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:41)
    at jakarta.activation.FactoryFinder.find(FactoryFinder.java:71)
    at jakarta.activation.MailcapCommandMap.getImplementation(MailcapCommandMap.java:703)
    at jakarta.activation.MailcapCommandMap.addMailcap(MailcapCommandMap.java:537)
    at com.appiancs.mail.MailPoller.<clinit>(MailPoller.java:31)
    Caused by: java.util.ServiceConfigurationError: jakarta.activation.spi.MailcapRegistryProvider: Provider org.eclipse.angus.activation.MailcapRegistryProviderImpl not found


    We suspect the plugin is incompatible with recent updates in Appian's runtime environment.

  • 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

  • Hi ,

    Can an oracle version be provided for this plugin?

    We are on an On-prem installation with Oracle DB.

    Thanks in Advance.

    1. If you are using O365, I would recommend using the MSGraph Mail Poller
    2. There usually is a more detailed error in the stdOut log - I would check there first.
    3. If the issue is that the plugin cannot find the host - it may be that your VPN settings need to be adjusted to allow connection to your internal DNS to resolve the address. You could also try using the IP address of the IMAP host directly as a test.