Email Accounts - IMAP, POP3, and SMTP
In this article
Overview
You can use the account type to connect Email Snaps with data sources that use IMAP, POP3, and SMTP accounts. The different account types and the supported Email Snaps are listed below:
IMAP - Email Reader, Email Delete, and Email Archive Snaps.
POP3 - Email Reader and Email Delete.Â
SMTP - Email Sender.
Ask your email administrator which option is best for you to use. Account settings are common for all the three accounts.
Limitations
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, such as Gmail, Yahoo, Hotmail, and so on to enforce their security policy increasingly against all email client applications which access email accounts through email API (SMTP, IMAP), 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
Asterisk (*): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon (): Indicates whether the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon (): Indicates that you can add fields in the field set.
Remove icon (): Indicates that you can remove fields from the field set.
The fields available for all the account configurations are the same.
SMTP accounts cannot be validated before sending any email due to the nature of the SMTP Servers. Therefore, no Validate button is provided in SMTP accounts.
Field Name | Field Type | Description | |
---|---|---|---|
Label* Default Value:Â None | String | Specify a unique label for the account. | |
Email ID Default Value:Â None | String | Specify the email ID to use for this account. | |
Password Default Value:Â None | String | Specify the the password for the account. | |
Server domain* Default Value: None | String | Specify the name of the server domain. | |
Port* Default Value: None | Integer | 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 | Dropdown list | Select how the secure connection to the email server should be initiated. Options available include:
| |
Attachment password Default Value:Â None | String | Specify the password for attachment URL. | |
Connection timeout Default Value: 60000 | Integer | 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 | Specify 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 | Specify 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 | Use this field set to configure advanced parameters that you want to include in the request. | ||
Mail property name Default Value:Â None | String | Specify the name of the mail property. Â | |
Mail property value Default Value:Â None | String | Specify the mail property value associated with the mail property name. |
Snap Pack History
Related Links
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.