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,

    Yes we have verified the credentials and they are working fine and we are able to login to outlook mailbox.

    Both Version - Version 1.1.6 and New verion with support to Jakarta library (Got installed via ticket on 22.2 version).

    We are getting below error -

    528 : UnattendedJavaActivityRequest] ERROR com.appiancs.mail.MailPollerSmartService - Error during mail polling

    javax.mail.AuthenticationFailedException: LOGIN failed.

    at com.sun.mail.imap.IMAPStore.protocolConnect(IMAPStore.java:661)

  • Do you have the stack trace or any additional detail? Not much to go on otherwise.

    What do you mean by "both versions"?

    How have you verified the credentials?

  • Hi Mike,

    We are seeing one strange behavior where Plugin has started giving us LOGIN Failed error even when mailbox credentials are correct and working perfectly fine.

    We are on 22.2 and tried for both the version of plugins 1.1.6 and by deploying the Plugin as mentioned in release notes but getting same error in all the env

  • Yes, it is a clean break. 1.1.7 works with 22.2 and below, 2.0 works with 22.3 and above.

  • Hi Mike, does the above mean the version 2.0.0 is not backward compatible (Appian v21.4, on-premise, in our case) and must have Appian v22.2+ to work ? Will current version (1.1.7) stop working once Appian version is upgraded to 22.2/ 22.3? 

  • Release Notes - v2.0.0
    • Updated to support the jakarta mail library introduced in Appian 22.3. 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.
  • Hi Mike,

    With the 22.3 Appian version, the plugin no longer works, since the library javax.mail is no longer supported. Are there plans to update the plugin to the new Jakarta Mail library?

    We were using the plugin without any issues, and now with the update it stopped working, so we're in a bit of a situation.

    Thanks!

  • Hi Mike,

    I'm doing some research to see what options are available, if any, for polling multiple configurable Gmail inboxes.

    I see that there's a lot of emphasis in the documentation that this plug-in is meant to support polling for only one inbox, but just to make sure: when you say there should be "only one instance of this node is running at one time", is that across all process instances in an environment, or just within one instance?

    Thanks.

  • Thanks Mike.  I'm looking at the MIME encoding in the EML document now.

  • Yes.

    Per docs: 

    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
      • EML with attachments removed
      • EML with attachments included
      • 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)

    If the attachments aren't saved, there are are a few reasons for it that I can think of:

    1. They are inline attachments
    2. They are a part inside a part

    You can inspect the original email or the saved .eml with attachments to see what the structure looks like.