Label*

Default Value: None
Example: IMAP Account

String

None

Enter a unique label for the account.

Email ID

Default Value: None
Example: john@abcd.com

String

None

Enter the email ID to use for this account.

Password

Default Value: None
Example: o8jkll0#

String

None

Enter the the password for the account.

Server domain*

Default Value: None
Example: imap.example.com

String

None

Enter the name of the server domain. 

Port*

Default Value: None
Example: 993

Integer

None

Enter the port number of the email server. This will vary depending on your mail provider and the Secure connection selected.

Secure connection*

Default Value: None
Example: SSL

String

None

Select how the secure connection to the email server should be initiated. Options available include:

• STARTTLS: Connects to the regular SMTP/IMAP/POP3 port and then upgrades the connection to TLS.

• SSL: If enabled on your server domain, creates a secure connection.

• NONE: Used if a secure connection is not configured.

Attachment password

Default Value: None
Example: o8jkll0#

String

None

Enter the password for attachment URL.

Connection timeout

Default Value: 60000
Example: 50000

Integer

None

Enter the time duration in milliseconds, in the event of a connection error, after which the server will not try reconnecting. 

Read Timeout

Default Value: 60000
Example: 50000

Integer

None

Enter the time duration in milliseconds, in the event of a read error, after which the server will not try to read the data. 

Write Timeout

Default Value: 60000
Example: 50000

Integer

None

Enter the time duration in milliseconds, in the event of a write error, after which the server will not try to write the data. 

Mail properties

<Need information about it>

Specify advanced parameters that you want to include in the request.

This fieldset consists of the following fields:

• Mail property name

• Mail property value

Mail property name

Default Value: 
Example: 

String

None

Mail property value

Default Value: 
Example: 

String

None

If using Gmail, you may need to turn on the option to allow less secure apps to access your account within Gmail. See https://support.google.com/accounts/answer/6010255?hl=en  for more information.

Due to the anti-email-hijacking policies of webmail servers, the Email Snaps often fail to perform as expected.

It is a trend for webmail servers (e.g. gmail, yahoo, hotmail, etc.) to enforce their security policy increasingly against all email client applications which access email accounts through email API (SMTP, IMAP, etc), other than web browsers, if the client applications access from a geographical location far from usual locations of the web browser logins. The Email Snaps are often classified as suspicious email hijacker since the Snaps try to access the email server from AWS, a location different from usual web browser logins of users. Sometimes, users can find additional information in the emails from the mail servers or in the security page of the account. The Email Snaps function well as expected if their accounts are not from webmail servers.

If you are using Standard Encryption, the High sensitivity settings under Enhanced Encryption are followed.

If you have the Enhanced Account Encryption feature, the following describes which fields are encrypted for each sensitivity level selected per each account.

Account: Email - IMAP

• High: Password

• Medium + High: Email ID, Password

• Low + Medium + High: Email ID, Password, Server domain

Account validation failed.

The Pipeline ended before the batch could complete execution due to a connection error.

Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.