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. 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).
Please refer to the attachments included in the download for further documentation and examples.
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 Mike. I'm looking at the MIME encoding in the EML document now.
Takes all unread email from a mailbox and adds entries directly to a database table.
If the attachments aren't saved, there are are a few reasons for it that I can think of:
You can inspect the original email or the saved .eml with attachments to see what the structure looks like.
I was able to poll my test gmail account and retrieve 2 emails each with an attachment.
I noticed the APP_MAIL_POLLER table gets written to and it has the correct appian docid for the attachments.
However, nothing was written to the APP_MAIL_POLLER_DOC table.
Is the plugin suppose to write to that table as well?
It turns out my client does not have a VPN tunnel setup yet for their cloud instances. So, that's not an issue.
The test gmail account I created is set for less secure login and have IMAP enabled. I have used my tablet to connect with an email account using the IMAP settings and it connects fine.
Could outbound network traffic out of my client's Appian Cloud instances be routed only to my client's router/firewall?
I'll check with Appian Support.
Hard to tell why exactly this would be happening. if you do have a VPN, there is a possibility that the traffic is going through it - but it does not have to. Check with Appian Support on the settings and make sure gmail is excluded. Also check that the gmail account has IMAP enabled (IMAP access is disabled by default).
Could this be a firewall issue? If so, at which hop? AWS/Amazon Cloud for my client's Appian Instance, or perhaps VPN tunnel back to the Client's intranet where it can't get out from there? Just a wild guess?
If it is a firewall issue, could we divert gmail server destined network traffic to not go through the to the company vpn tunnel from the Appian cloud instance? Of course, still all other outbound traffic goes through the vpn tunnel.
I'm am having a problem connecting to Gmail and attempting to read emails using the IMAP Mail Poller smart service. We are on the latest version of Appian on the cloud.
I keep getting the error message "Connection dropped by server?" after it times out in about 10 seconds.
Can you help?
We have Re-deployed the plugin, now it was working fine.
Thanks for the Quick Reply.
Any symptoms? Messages from logs? Are you on the latest version that resolves the TLS configuration?
© 2022 Appian. All rights reserved.