POP/SMTP: Sends and receives emails via SMTP (Simple Mails Transfer Protocol) or POP3 (Post Office Protocol v3). The adapter supports multiple file attachments and MIME type definitions for the email body e.g. for sending HTML emails. In addition, the sending and receiving of S/MIME encoded and/or signed email messages is supported.
Former name until version 5.5.4: POP/SMTP Connector
Properties
|
|
Data handling mode Possible values:
|
|
|
Name of the file attachment to be sent (if Please note: If you want to parameterize this property dynamically, use its technical name in the corresponding XSL mapping. The technical name may differ from the displayed name. Example: XML
|
|
|
Delete email message after the successful reception from the POP3 server (if property |
|
|
Defines which operation will be executed for the specified file(s). Depending on the value in Possible values:
|
Parameters
|
|
Email address of the email sender; If required, with specification of a display name Possible values: Any valid email address (e.g. |
|
|
Technical sender agent (if different from parameter Possible values: Any valid email address (e.g. |
|
|
Email address(es), to which the email shall be sent; If required, with specification of a display name Possible values: Any valid email address; in case of multiple addresses separated by semicolon (e.g. |
|
|
Email address(es) to which the email will be sent as carbon copy; If required, with specification of a display name Possible values: Any valid email address; in case of multiple addresses separated by semicolon (e.g. |
|
|
Email address(es) to which the email will be sent as blind carbon copy; If required, with specification of a display name Possible values: Any valid email address; in case of multiple addresses separated by semicolon (e.g. |
|
|
Email address to which the reply shall be sent Possible values: Any valid email address (e.g. |
|
|
Subject of the email to be sent |
|
|
Message body that represents the email's content (if the input document of the adapter is an HTML document, it will be used as HTML message body) Possible values: Any string |
|
|
MIME type of the email body (allows to display HTML emails or multiple attachments) Possible values: Valid MIME type (e.g. |
|
|
Encoding of the email body Possible values: Valid encoding/charset (e.g. |
|
|
IP address or host name of the SMTP server to send emails Possible values: Any valid string (e.g. |
|
|
Port of the SMTP server to send emails Possible values: Any positive integer number, e.g. |
|
|
SMTP security protocol to be used Possible values:
|
|
|
Allow all hosts for SMTP Please note that hosts without a valid certificate will also be allowed. (information) This parameter is only valid, if SSL is used as security protocol. |
|
|
IP address or host name of the POP3 server to receive emails Possible values: Any valid string (e.g. |
|
|
Port of the POP3 server to receive emails Possible values: Any positive integer number |
|
|
POP3 security protocol to be used Possible values:
|
|
|
Allow all hosts for POP3 Please note that hosts without a valid certificate will also be allowed. (information) This parameter is only valid, if SSL is used as security protocol. |
|
|
User name for the POP3 server (when receiving email) or for the SMTP server (when sending an email) Possible values: Any valid string (e.g. |
|
|
Password for the POP3 server (when receiving email) or for the SMTP server (when sending an email) |
|
|
Defines if the OAuth 2.0 protocol is used for log-in. Possible values:
If the OAuth 2.0 protocol is used,
|
|
|
Activates the POP3 protocol for Microsoft 365. Needs to be activated in addition to Possible values:
|
|
|
Limit the number of attachments to be sent (if Possible values:
|
|
|
Local directory on the X4 Server e.g. in the X4 Repository that contains files to be sent as email attachments (if Possible values: Any string (e.g. |
|
|
Filter files to be send as attachments by their name using the placeholders Possible values:
|
|
|
Send a message in EML format (this requires an EML message as adapter input) or receive a message in EML format Possible values:
|
|
|
Encode attachments (multipart content) always as base64 (if the property Possible values:
|
|
|
Encrypt the message with S/MIME (Multipart/Encrypted) Possible values:
|
|
|
Sign the message with S/MIME (Multipart/Signed) Possible values:
|
|
|
Path to a valid key/certificate in the PKCS#12 format Possible values: Any valid path in the local file system of the X4 Server (e.g. |
|
|
Password/passphrase to the key/certificate file in PKCS#12 format that has been specified within the parameter Possible values: Any valid string |
|
|
Date format for a properties file which can be used to define further JavaMail properties Possible values:
|
|
|
As of version 6.2.0 of the X4 BPMS, the security protocol to be used can be set via the parameters If using the now deprecated parameter URL to a properties file which can be used to define further JavaMail properties, see https://javamail.java.net/nonav/docs/api/com/sun/mail/smtp/package-summary.html. The linked file must be available in the format defined within parameter (information) If the Possible values: Any valid URL, e.g. |
Which e-mail addresses are formally valid can be found in the guidelines RFC 5321 and RFC 5322.