In this article
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
You can use this account type to connect Email Snaps with data sources that use IMAP account.
Prerequisites
<To be verified with QA>
Limitations
<To be verified with QA>
Known Issues
<To be verified with QA>
Account Settings
<Temporary image, will be replaced once the values for the Mail properties fieldset are known>
Appsplus panel macro confluence macro | ||
---|---|---|
| ||
**Delete Before Publishing** Choose from the following sentences to document specific field types. Drop-down lists/Option Buttons (radio buttons): You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.
Check boxes:
Text Fields
Numeric Text Fields
Notes in field descriptions
|
Email Reader, Email Delete, and Email Archive Snaps use this account type.
Limitations
Note |
---|
If using Gmail, you may need to turn on the option to allow less secure apps to access your account within Gmail. See Less secure apps & your Google Account - Google Account Help 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. |
Known Issues
None.
Account Settings
...
Info |
---|
|
Field Name | Field Type | Field Dependency | Description | |||
---|---|---|---|---|---|---|
Label* Default Value: None | String | None | Enter Specify a unique label for the account.
| |||
Email ID Default Value: None | String | None | Enter Specify the email ID to use for this account. | |||
Password Default Value: None | String | None | Enter Specify the the password for the account. | |||
Server domain* Default Value: None | String | None | Enter Specify the name of the server domain. | |||
Port* Default Value: None | Integer | None | Enter Specify the port number of the email server. This will vary depending on your mail provider and the Secure connection selected. The default port for IMAP is 993. | |||
Secure connection* Default Value: None | String | None | Select how the secure connection to the email server should be initiated. Options available include:
| |||
Attachment password Default Value: None | String | None | Enter Specify the password for attachment URL. | |||
Connection timeout Default Value: 60000 | Integer | None | Enter Specify 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 | 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 | 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. | |||||
Mail property name | Mail property valueMail property name Default Value: None | StringNone | Specify the name of the mail property. | |||
Mail property value Default Value: None | String | None |
Note |
---|
Note |
...
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.
Troubleshooting
<To be checked with QA>
...
Error
...
Reason
...
Resolution
...
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.
...
Binary | String | Specify the mail property value associated with the mail property name. |
Snap Pack History
Multiexcerpt include macro | ||||
---|---|---|---|---|
|
Related Links
...