Connection Profiles (connections) manage the way an SMTP conversation is established and authenticated. Using the Manage Connections page, you can:
The Manage Connections page displays the list of configured Connection Profiles.
Do one of the following:
Enter the IP address of the server (or range of servers) or the host fully qualified domain name (FQDN) to which this Connection Profile applies. You can use a wildcard (*) to specify a host on a Connection Profile, which allows the profile to match anything that doesn't match another profile.
You can specify the host name, a wildcarded host name, an IP address, or a wildcarded IP address. Wildcarded IP addresses only support trailing wildcards for whole terms, for example, 1.2.3.* or 1.2.*. You cannot insert wildcards in the middle of the IP address, for example 1.2.3* or 1.*.3.4. |
If mandatory inbound TLS is configured on this profile, this takes precedence over the global opportunistic setting. However, if mandatory inbound TLS is not configured on this profile, the global opportunistic setting is used.
For an inbound connection, the |
Click Close.
Enter the sender domain name to which this Connection Profile applies.
If mandatory inbound TLS is configured on this profile, this takes precedence over the global opportunistic setting. However, if mandatory inbound TLS is not configured on this profile, the global opportunistic setting is used.
Click Close.
Click the Relay tab.
Change the settings in the Inbound Relay Control section.
Select the type of Relay Control you require for your configured Hosts.
Inbound Relay Control | Description |
---|---|
None | No relay control configured for this Connection profile. |
Full | This Connection profile represents internal corporate mail servers. Connection Hosts can send mail to any domain. |
Restricted External | This Connection Profile represents hosts that may send mail to any configured Hosted Domain. |
Restricted Internal | This Connection Profile represents hosts that may send mail to any configured Hosted Domain. |
Blocked |
No messages are accepted from this Connection Profile. Note: Mail that is sent and received inside your Hosted Domain is not blocked, unless Spoof Detection is enabled. See Configuring spoof detection settings for more information. |
*Messages will be checked for spam if the spam checks on outbound messages option in SpamLogic Settings is enabled. |
Click the TLS Settings tab.
Configure Inbound (When Acting as a Server).
Edit the settings used
when the
Area | Setting | Description |
---|---|---|
Default | Use Mandatory TLS for this connection profile | If enabled, the |
Encryption strength | Encryption should meet or exceed | Enter the minimum number of bits to use for encryption, in the range 40-256. This is in addition to the global cipher strength setting. Any incoming connection must meet both the global cipher strength and the number of bits criteria. |
Client certificate validation | Require valid client certificate |
Select this option if you want the certificates of connecting clients and servers to validate successfully for the communication to continue. A successful validation requires a valid CA signing certificate to be present in the certificate
store. If you enable this but don't want Common Name (CN) checking to be enabled, the |
CN of the certificate must match | The Common Name (CN) of the certificate must match what you enter in the text box. If you select this option but do not specify a CN, the host name of the client is used. You can use a wildcard (*) to match the CN to the host name but if the host name cannot be determined, a match is not attempted. | |
CN of the certificate issuer must match | The Common Name (CN) of the certificate issuer must match what you enter in the text box. |
The client certificate validation can be made to match the client host name or a specified value.
If the host name from a reverse-lookup is host.domain.com, a match occurs if the CN is formatted as *.domain.com or *.host.domain.com. It does not match for simply domain.com.
If validation of the CN should match a specified value, for example *.domain.com, a match occurs on values formatted as domain.com, *.domain.com, and sub.domain.com. It does not match abcdomain.com.
Click the TLS Settings tab.
Edit the settings used
when the
Area | Setting | Description |
---|---|---|
Default | Use Mandatory TLS for this connection profile | If enabled, the |
Supported protocols | TLS versions in use for this connection | Select the version(s) of TLS required for this connection or use the global settings. |
Encryption Strength | Minimum Cipher Strength | Select the encryption strength (high, medium, any) required for this connection, or use the global settings. |
Certificate Issuer Validation | Server certificate validation |
Select the SAN/CN matching criteria. Subject Alternate Names (SANs) are checked first. You can also add a recipient domain to the SAN/CN field. If you select the option Validate the receiving server SAN/CN, you may encounter difficulties using a fixed IP address for routing. You need to either retrieve the host name of the server or use the DNS in order to avoid issues using this setting. |
Enter the SMTP Authentication credentials required to complete the connection. Confirm your password.
When setting up the user name and password on a Connection Profile, be aware that the user names apply across all Connection Profiles and can, therefore, only be used once.
You can apply SMTP authentication credentials to outgoing mail, provided you know the appropriate user name and password. See Specifying Routing of Email for more information.
© 1995–2018 Clearswift Ltd.