Mail Source provides the ability to specify a file as a source and is accessible via email. This section describes how to create a Mail Source service.

Perform the following steps to create a mail source:

Click Configure > SOURCES > Mail Source.
Click Create Mail Source.

On the Create Mail Source screen, enter the details explained in the table below:

Field Name	Description
Name	Name of the new mail source.
Description	Description of the new mail source.
Protocol	Internet standard protocol to be used for retrieving incoming mails. The available options are POP3, IMAP4 or MAPI. Based on the selected protocol, the default port number for that protocol is displayed in the Port text box. MAPI option will appear for license version. To send an e-mail through Microsoft Exchange Server, select MAPI in Protocol drop down box. To connect Adeptia Suite with Microsoft Exchange Server, you need to buy a third party tool called J-Integra for Exchange. J-Integra for Exchange is a high performance middleware bridge that enables Java Exchange interoperability. If you want to retrieve mails from an Exchange Server using J-Integra, select MAPI in the Protocol drop-down list box. If MAPI is selected in the Protocol drop-down list box: Enter name of the exchange server in Incoming Mail Server text box Enter the domain name in the Domain text box Enter the name of the CDO host machine in CDO host machine text box. CDOConfig.exe is the tool that comes with the J-Integra for Exchange SDK and is used for configuring CDO. Host where CDO is configured is called CDO host machine.
Incoming Mail Server	Incoming mail (SMTP) Server address.
Security Type	Protocol that provide data encryption and authentication between applications and servers in scenarios where that data is being sent across an insecure network. The available options are SSL, TLS, None. This implementation is specific, if and only if, POP3 and IMAP4 Protocol is selected in the Protocol drop-down list box. Supported TLS version is 1.2.
Port	Port number of the Incoming Mail Server.
User Id	Username of the mail server.
Password	Password of the mail server.
Confirm Password	Password to confirm.
Search Criteria	Criteria for the email. The available options are: Sender E-mail, Subject, Mail Content. You can select more than one filter criteria. You can use asterisk and wild cards in the content of the email.
Data Location	Location of the data in the email. The available options are Attachment, Body, and Multipart. Choose Attachment to send the data as an attachment. Choose Body to send the data in the email body. Choose Multipart to send both attachments and email body in the mail source. If you choose MultiPart to send both Attachment and body in the Mail Source, there will be no additional step to send the Body, you just have to pass the stream. However, you have to create a Put-Context Var activity before the mail source and set the variable and Message Body in Variable Value. For example: VariableName: Service.<<MailSourceActivityName>>.MessageBody
Body Content Type	Type of content of the body. The available options are text/html and text/plain.
File Name	Name of the file, if the data is to be sent in the email as an attachment. Mail Source activity does not support more than one file attachment.
Leave Copy on Server	Copy of the email to leave on the server.

Expand Advanced Properties.
Define the required character set encoding code in the Character Set Encoding Used text box.
Select the project from the drop-down list of Project.
Click Save.

Click Test to verify the mail source service at design time. This verifies the values in the Incoming Mail (POP3) Server, Port, User ID and Password text boxes and checks whether the source service actually exists in the specified location or not.

When a mail event triggers process flows, each process flow uses a mail source. At times, when multiple process flows use a mail source, errors can occur. In such case, you can retry the action before exiting the mail source. You can also set the number of retries in the abpm.mailEvent.retry property.

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported