Email Configuration: Configure the Software to Send Emails
Configuration :: Email Address
If an appliance is designated as a backup appliance or a traffic node, the email configuration for that appliance will be overwritten with the email configuration defined on the primary master appliance.
Set the email address from which automatic messages from your BeyondTrust Appliance will be sent.
Configuration :: SMTP Relay Server
Configure your BeyondTrust Appliance to work with your SMTP relay server in order to send automatic email notifications of certain events.
SMTP Relay Server
Enter the hostname or IP address of your SMTP relay server.
Set the SMTP port to contact this server on.
If your SMTP server supports SSL encryption, choose SSL or TLS. Otherwise, select None.
If your SMTP server requires authentication, enter a username.
If your SMTP server requires authentication, enter a password.
Configuration :: Admin Contact
Default Admin Contact Email Addresses
Enter one or more email addresses to which emails should be sent. Separate addresses with a space.
Send a test email when the settings are saved
If you wish to receive an immediate test email to verify that your SMTP settings are accurately configured, check this option before clicking the Save Changes button.
Send Daily Communication Notice
You can have the BeyondTrust Appliance send a daily notification to ensure that alert communication is working correctly.
In addition to the test email and daily communication notices that can be configured above, emails are sent for the following events:
- During any failover operation, the product version on the primary node does not match the product version on the backup node.
- During a failover status check, any of the following problems are detected.
- The current appliance is the primary node and a shared IP address is configured in /login, but its network interface is not enabled.
- A shared IP address is configured in /login but is not listed as an IP address in /appliance.
- The backup node could not contact the primary node, and it also could not contact any of the test IP addresses configured on the Management > Failover page.
- The backup node could not contact any of the test IP addresses configured on the Management > Failover page.
- The backup node's backup operations are disabled on the Management > Failover page.
- The backup node unexpectedly failed to perform a probe of itself, indicating that it is malfunctioning.
- The backup node failed to contact the primary node using the primary node's hostname.
- Automatic failover is disabled, and the backup node failed to probe the primary node.
- Automatic failover is enabled, and the backup node failed to probe the primary node. The backup node will automatically become the primary node if the primary node remains unresponsive.
- Automatic failover is enabled, and the backup node is automatically becoming the primary node because the primary node was down for too long.
- The primary node failed to perform a data sync with the backup node sometime in the past 24 hours.