Modify an SMTP (embedded) transport

After you create an embedded SMTP pickup, you can view and modify the fields that define the object.

This topic provides information for completing fields in the maintenance pages.

SMTP (embedded) settings tab (pickup only)

  • Embedded SMTP server – A link is provided to view the settings for a particular embedded server or for the global embedded server.
  • Host – The fully qualified domain name of the computer on which the embedded SMTP server runs. This field cannot be changed.
  • Host used by partners – The email address that partners should use to access your embedded SMTP server. Activator maps this email address to the correct delivery exchange.
  • While this field is visible on the delivery exchange maintenance page, you can only edit it on the embedded server maintenance page. See Modify a global embedded SMTP server or SMTP (embedded) configuration.
  • Email address – The email address that the remote partner uses to send messages to your local community.

Accounts tab (pickup only)

Select an option for authorizing the reception of email from a sender:

  • Identify the sender using partner delivery defined e-mail addresses - (Default) When you select this option, Activator consumes email on this transport only if the sender email address is well-defined and configured in a partner SMTP delivery.
  • Identify the sender using partner associated e-mail accounts – Select this option if you want to create a list of authorized sending-partner email accounts. Use this feature, for example, if you want this pickup to allow multiple members of a remote partner organization to send email, without a validation of the complete sender email address.
  • You can create the list of authorized senders by selecting accounts that already exist on pre-existing partners, or you can enter accounts directly to the list for this pickup.
  • The local element of the email address is case sensitive. For example, myaccount@organization.com is evaluated as a different address than MyAccount@oragnization.com.
  • See the rules sections below, for additional configuration details.

Rules for the use of wildcard characters

The list of authorized senders can include entries composed with wild-card characters.

  • "*" may be substituted for zero or more characters
  • "?" may be substituted for any one of the 36 characters, "A" through "Z" and "0" through "9

Examples of accounts using wildcards:

  • *@domain.com
  • *@*.*

When Activator parses the user account name, it ranks specific characters over wildcard characters. For example, "partner1@domain1" is selected over "partner?@domain1".

Rules for sender identification on a single pickup

If a single pickup consumes email from an external POP3 server, the Activator partner (from the list of authorized partners) with the most specific rule is selected first.

Example – We define the following addresses on an email trading pickup:

  • Partner1 = partner1@myPartner.com
  • Partner2 = @myPartner.com
  • Partner3 = *@*

When receiving a message from partner1@myPartner.com, Activator identifies the sending partner as Partner1.

Rules that apply on multiple trading pickups

When two or more email trading pickups point to the same external POP3 server, the same email account or pattern can be associated with different Activator Partners. For example, one pickup may indicate that the a@a.com email account resolves to PartnerA, while another may specify that the same email address resolves to PartnerB.

In this case, the trading pickup that consumes the message determines the partner with whom the user account is associated, based on the accounts specified in its Accounts tab.

Advanced (pickup only)

  • Sequence consumed messages based on their delivery exchange – Select this option if you want messages that are consumed by this pickup to be delivered in their original consumption order per resolved destination delivery. When Activator consumes messages on this pickup that are delivered over multiple delivery exchanges, the messages are filtered and ordered in their consumed sequence for each delivery, and processed in parallel per delivery. For details about this functionality, see Sequential message delivery.
    • Timeout to apply for out of sequence messages (seconds) – Default = 60 seconds. Enter a time limit for Activator to wait for missing messages of a sequence before taking the appropriate action. This feature avoids the blocking of processing when a sequenced message is not available.
  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it consumes from back-end applications or from partners.
  • Backing up files is strongly recommended. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server or a processing node stops or restarts. Backups also are needed if you want the ability to resubmit messages to back-end applications or resend messages to partners. Backup files are stored in \<Activator_common_directory>\data\backup, unless you specify otherwise.
  • Restrict maximum file size for this transport – Use this option to specify the maximum size of files a transport can handle.
  • If the pickup consumes a file larger than the specified maximum, the file is rejected and a message is written to the events log.
  • Express the maximum size in bytes. Do not use commas. For example, a kilobyte is 1024 bytes, a megabyte is 1048576 bytes, a gigabyte is 1073741824 bytes. The smallest maximum allowed is 1000 bytes. On the opposite extreme, you can enter the largest number the field can accommodate.

SMTP settings tab (delivery only)

  • Email address – The email address for sending messages to a partner.
  • Use the global external SMTP server – Selecting this means the system’s external SMTP server is used to send messages to the partner. A link is provided to configure the system’s external SMTP server. See Configure the global external SMTP/SMTPS server.
  • Use a partner-specific SMTP server – Selecting this means you can specify an external SMTP server to send messages to the partner that is different from the system’s external SMTP server.
  • SMTP server – Enter an SMTP server for sending messages only to this partner. Enter a fully-qualified domain name or IP address for the server. If you leave this field blank, the system inserts its external SMTP server.
  • Port – The default port for sending mail is 25.
  • This server requires a user name and password – Select this if a user name and password are required to connect to the server and then complete the name and password fields. SMTP servers usually do not require user names and passwords for sending. The Password, Confirm password, and User name field descriptions are limited to 128 characters.

Advanced tab (delivery only)

  • Retries – This is the number of times Activator retries connecting to the partner’s transport if the initial attempt to connect and send the message failed. The following are common reasons for triggering retries.
    • The connection attempt failed immediately for a reason such as host not found.
    • The host was found, but the connection process took longer than the connect timeout interval specified on the Advanced tab.
    • The connection was successful, but the partner’s HTTP server took longer than the response timeout interval to return a 200 OK response indicating the message was successfully received. A 200 OK response is a transport response, separate from a message protocol response such as an AS2 receipt.
  • Note that in the last case, the 200 OK response also will include the receipt if synchronous receipts were requested. Otherwise, it will be a simple 200 OK response with no payload. And if an asynchronous receipt was requested, the partner will connect later to send it.
  • Retries occur according to an algorithm that starts at 5 minutes. The interval between retries increases with each subsequent retry in this pattern: 10 minutes, 15 minutes, 30 minutes, 60 minutes. The interval plateaus at 60 minutes. This means if the retry value is greater than 5, the fifth and each subsequent retry occurs at 60 minute intervals.
  • For example, if retries is 3, the system will try connecting again in 5 minutes if the initial connection attempt fails. If this retry attempt also fails, the system attempts a second retry in 10 minutes. The third retry attempt is made 15 minutes later. If the third retry attempt fails, the message is given a failed status. So after four attempts (the first attempt plus 3 retries), the message fails. You can search for and manually resubmit failed messages in Message Tracker.
  • Retries do not occur precisely at these intervals because each connection attempt takes some seconds, which varies by computer. So retries actually occur after the connection attempt time plus the interval.
  • This control applies only to retrying to send messages, not receiving. It applies only to retrying to send related to transport issues. It does not apply to successfully sent messages for which receipts have not been received as expected. Another control, resends, determines how many times the system will resend a message when a receipt is not received from the partner. For information about resends, see reliable messaging in the collaboration settings chapter.
  • Connect timeout (seconds) – Time in seconds Activator waits for a connection to the delivery exchange before the attempt times out. Although the default value is 30 seconds, this may be longer than the interval allowed by your operating system (OS). For example, Windows XP by default allows a maximum timeout of 20 seconds. The actual connect timeout interval is the lesser of the OS timeout and the value set in Activator.
  • Read timeout (seconds) – Time in seconds Activator waits to read data from the delivery exchange before terminating the connection.
  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it retrieves from back-end applications or from partners.
  • Backing up files is strongly recommended. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server or a processing node stops or restarts. Backups also are needed if you want the ability to resubmit messages to back-end applications or resend messages to partners.
  • Backup files are stored in \<Activator_common_directory>\data\backup, unless you specify otherwise.
  • Post-processing script – The full path to an executable file that contains post-processing commands. This field is available for both application and partner delivery exchanges.
  • See Post-processing of consumed messages.

Related topics

Related Links