Campaign-specific external accounts external-account
Follow the steps below to configure the account settings based on the type of external account you selected.
Bounce mails (POP3) bounce
The Bounce mails external account specifies the external POP3 account used to connect to the email service. All servers configured for POP3 access can receive return mail.
To configure the Bounce mails (POP3) external account, fill in the following fields:
-
Server - URL of the POP3 server.
-
Port - POP3 connection port number (default port is 110).
-
Account - Name of the user.
-
Password - User account password.
-
Encryption - Type of chosen encryption, including:
- By default (POP3 if port 110, POP3S if port 995).
- POP3 that switches to SSL after sending a STARTTLS.
- POP3 non-secure (port 110 by default).
- POP3 secure above SSL (port 995 by default).
-
Function - Select Inbound email to configure the account for receiving incoming emails or SOAP router to handle SOAP requests.
To configure a POP3 external using Microsoft OAuth 2.0, check the Microsoft OAuth 2.0 option and fill in the following fields:
-
Azure Tenant
Azure ID (or Directory (tenant) ID) can be found in the Essentials drop-down of your application overview in the Azure portal.
-
Azure Client ID
Client ID (or Application (client) ID) can be found in the Essentials drop-down of your application overview in the Azure portal.
-
Azure Client Secret
Client secret ID can be found in the Client secrets column from the Certificates & secrets menu of your application in the Azure portal.
-
Azure Redirect URL
Redirect URL can be found in the Authentication menu of your application in the Azure portal. It should end with the following syntax nl/jsp/oauth.jsp, e.g.
https://redirect.adobe.net/nl/jsp/oauth.jsp.
Internet access is needed for setup and to use the Test Connection button in the client console. After setup, the inMail process can communicate with Microsoft servers without internet.
After entering your different credentials, you can click Setup the connection to finish your external account configuration.
Routing routing
To configure a specific external account for external deliveries, follow the steps below.
-
Create an external account. Learn more
-
Select the Routing type.
-
Select the desired channel and click Create.
-
In the external account Details section, External is selected by default as the Delivery mode.
note note NOTE Currently, External is the only available mode. -
To handle the process after delivery execution, externalize this to a post-processing workflow. Create a workflow with an External signal activity and select it from the Post-processing field.
-
In the Activity field, edit the name of the post-processing workflow activity displayed in the logs.
Execution instance instance-exec
If you have a segmented architecture, identify the execution instances associated with the control instance and establish connections between them. Transactional message templates are deployed on the execution instance.
To configure the Execution instance external account:
-
URL - URL of the server where the execution instance is installed.
-
Account - Name of the account, matching the Message Center Agent as defined in the operator folder.
-
Password - Password of the account as defined in the operator folder.
-
Method - Choose between Web service or Federated Data Access (FDA).
For FDA, select your FDA account. Note that Campaign connection to external systems is restricted to advanced users and only available from the client console. Learn more
-
Create archiving workflow - For each execution instance registered in the Message Center, regardless of whether you have one or multiple instances, create a separate archiving workflow for each external account associated with the execution instance.