Email Configuration

When retrieving messages from a mail server, this setting may be set to a full path to which attachments should be saved. For example "C:\download\attachments". This setting is valid only when receiving messages, and is supported when using both the IMAP and POP protocols. If a file with the same name as the attachment exists it will be overwritten.

When retrieving messages from the server, this setting specifies whether headers are automatically decoded by the task. When IncludeHeaders is set to True this setting may also be set to False to ensure that the original header values are included without any processing applied. This is helpful in scenarios when further processing of the message is done outside of the task. The default value is True.

When set to 0 (default), the task will use the usual header attributes to determine the filename of the attachment that is saved to disk. If these values are not present, the name attribute from the Content-Type header may be used by setting this configuration setting to 1. Note that use of the name attribute for Content-Type is deprecated, but this configuration setting is present to allow for backward compatibility. Possible value are:

When retrieving non-MIME encoded messages from the server, this setting specifies whether encoded messages (e.g., Base64 encoded message) are automatically decoded by the task. This configuration option is only valid for messages that are not MIME encoded. The default value is False.

If set, the task will move the downloaded messages to the folder specified. This is only applicable when ServerType is set to IMAP. Only successfully downloaded messages will be moved.

This is only applicable when receiving.

Setting this property sets the Return-Path to be used for sending email. If this is not set, the value in From is used.

This is only applicable when sending emails.

If set to true the task will return only the first plain text part of a message. This is false by default. This is only applicable when receiving messages.

When False (default), the IMAP server uses temporary message identifiers that are valid only during the current session. If this configuration setting is True, permanent message identifiers will be used instead.

The IMAP protocol operations where UID mode is used are the following: COPY, FETCH, STORE, SEARCH.

Note: This configuration setting only applies when ServerType is set to IMAP;

This configuration is only used when PersistentConnection has been set to true. Set this to true to tell the task to logoff from the persisted connection once execution completes.

The default for this configuration setting is false.

Used to enable/disable the supported security protocols.

Not all supported protocols are enabled by default (the value of this setting is 240). If you want more granular control over the enabled protocols, you can set this property to the binary 'OR' of one or more of the following values:

TLS 1.1 and TLS1.2 support are only available starting with Windows 7.

If AbsoluteTimeout is set to True, any method which does not complete within Timeout seconds will be aborted. By default, AbsoluteTimeout is False, and the timeout is an inactivity timeout.

The LocalHost configuration contains the name of the local host as obtained by the Gethostname() system call, or if the user has assigned an IP address, the value of that address.

In multihomed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the task initiate connections (or accept in the case of server tasks) only through that interface.

If the task is connected, the LocalHost configuration shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface).

When true, the socket will send all data that is ready to send at once. When false, the socket will send smaller buffered packets of data at small intervals. This is known as the Nagle algorithm.

By default, this config is set to false.

By default the task will use the system security libraries to perform cryptographic functions. This means calls to unmanaged code will be made. In certain environments this is not desirable. To use a completely managed security implementation set this setting to True. Setting this to True tells the task to use the internal managed implementation instead of using the system's security API.

Note that when this value is set the product's system dll is no longer required as a reference, as all unmanaged code is stored in this file.

If persisted connections are enabled and PersistedConnectionTimeout is set to a positive value, the connection will be kept alive for that number of minutes after a message transmission. If no other messages are sent over that connection during the timeout period, the task will disconnect from that server.

Note: the default value is 0. This value means that the connection will be kept alive unless the server disconnects it due to idling.