{"id":31751,"date":"2018-03-27T10:00:22","date_gmt":"2018-03-27T18:00:22","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/import-ingestion\/e-mail-configuration-4050\/email-import\/"},"modified":"2022-03-01T12:12:34","modified_gmt":"2022-03-01T19:12:34","slug":"email-import","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/import-ingestion\/email-configuration\/email-import\/","title":{"rendered":"Email Import"},"content":{"rendered":"
This article describes the types of protocols and security configurations Ephesoft Transact supports to connect with email services. Email import is one of the various ways to provide input files for processing in Ephesoft Transact.<\/p>\n
An administrator can configure an email account for a batch class in Email Import. Ephesoft Transact monitors the configured email folder of that email account to retrieve and process any new mail coming to that folder. Ephesoft Transact marks the email as \u201cread\u201d after it is imported into the system for processing.<\/p>\n
Refer to Email Configuration<\/a> for more information.<\/p>\n Ephesoft Transact supports the following three protocols to connect with email servers:<\/p>\n Post Office Protocol 3 (POP3) is a standard mail protocol used to fetch emails from a remote email server to a local email client. Almost all modern email servers and clients support POP3.<\/p>\n POP3 works by contacting an email service and downloading all new messages from it. Once they are downloaded onto the client machine, they are deleted from the email server automatically. This means that after the email is downloaded, it can only be accessed using the same email client. If you try to access email from a different device, the downloaded messages won\u2019t be visible.<\/p>\n Note: <\/strong>The Folder <\/strong>column is not editable with POP3, as POP3 only supports the Inbox folder.<\/p>\n The following figure is an example of the email configuration fields for POP3.<\/p>\n <\/p>\n Figure 1. Email Import with POP3<\/em><\/p>\n Internet Message Access Protocol (IMAP) is a standard protocol for accessing email on a remote server from a local client. It is an application layer internet protocol using the underlying transport layer protocols to establish host-to-host communication services for applications.<\/p>\n Most modern email servers and clients support IMAP.<\/p>\n Note: <\/strong>IMAP can also be used to connect with a Microsoft Exchange on-premises server. To do so, you will need to enable the IMAP protocol on the Microsoft Exchange server.<\/p>\n Note: <\/strong>With IMAP, messages are not automatically deleted on the server.<\/p>\n The following image is an example of the email configuration fields for IMAP.<\/p>\n <\/p>\n Figure 2. Email Import with IMAP<\/em><\/p>\n Exchange Web Services (EWS) is an application program interface (API) that allows third-party programs access to Microsoft Exchange emails.<\/p>\n Note: With EWS as the server type, Ephesoft Transact does not support attachments in .msg format, and the Email Headers<\/a> feature is not available.<\/p>\n To configure email import with Microsoft Exchange, you will need your EWS URL.<\/p>\n Figure 3. Email Import with EWS<\/em><\/p>\n https:\/\/<ONLINE_URL>\/EWS\/Exchange.asmx<\/p>\n https:\/\/<EXCHANGE_SERVER_HOSTNAME>\/EWS\/Exchange.asmx<\/p>\n Note: <\/strong>Microsoft Exchange servers come with IMAP and POP3 protocols disabled by default. EWS is an alternative email import service for users who do not want to enable IMAP or POP3 on their Microsoft Exchange server.<\/p>\n Ephesoft Transact supports the following security types:<\/p>\n <\/p>\n Figure 4. Email Configuration Security Types<\/em><\/p>\n In this mode, communication between an email server and Ephesoft Transact will be in plain text (not encrypted). This is not a recommended option, as communications will not be secure.<\/p>\n In this mode, communication between an email server and Ephesoft Transact will be encrypted. This method of communication is used for most servers.<\/p>\n Important: <\/strong>If SECURED is selected as the security type and the mail server does not support secure mode, an error will occur at the application end while authenticating the connection.<\/p>\n STARTTLS is an email protocol command which tells an email server that the email client wants to turn an insecure connection into a secure one.<\/p>\n This is done using the first email sent between servers, which acts as a basic setup process (known as a \u201chandshake\u201d). The email client uses Transmission Control Protocol (TCP) via the transport layer to tell the email server which security settings and compression methods it wants to use.<\/p>\n The email server then verifies its identity by sending a certificate to the email client. Once the client knows it can trust the server, they exchange a \u201ckey\u201d, which allows future exchanged messages to be encrypted.<\/p>\n<\/a>Supported Protocols<\/h2>\n
\n
<\/a>Post Office Protocol 3<\/h2>\n
<\/a>POP3 Workflow<\/h3>\n
\n
<\/a>Internet Message Access Protocol<\/h2>\n
<\/a>IMAP Workflow<\/h3>\n
\n
<\/a>Exchange Web Services<\/h2>\n
<\/a>How to Find Your EWS URL<\/h3>\n
\n
\n
<\/a>Security Types<\/h2>\n
\n
<\/a>PLAINTEXT<\/h3>\n
<\/a>SECURED<\/h3>\n
<\/a>STARTTLS<\/h3>\n
<\/a>Server Table Configurations<\/h2>\n