The SMTP server must be configured to enable email and SMS notifications and digests to be sent by the Controller.
Configure the SMTP server
- While logged in as an administrator, click Alert & Respond from the top navigation menu bar and then Email/ SMS Configuration.
Provide the connection information for the SMTP host and port.
A SaaS Controller should be preconfigured with the appropriate settings, but verify the settings as the following:
- SMTP Host: localhost
- SMTP Port: 25
No authentication is needed.
For an on-premise controller, use a host and port settings for an SMTP server available in the controller deployment environment.
- Customize the sent from address in notifications emails in the From Address field. By default, emails are sent by the root Controller user.
- If the SMTP host requires authentication, configure the credentials in the Authentication settings.
- If you want to add any text to the beginning of the notification, enter it in the Notification Header Text field.
If you are using SMS do one of the following:
- Select Default and choose one of the available carriers from the pulldown menu.
- Select Custom and enter the phone number receving the message as <phone number>@<sms gateway>.
For example, a mobile phone in the United States serviced by AT&T might be:
A mobile phone in the United Kingdom serviced by Textlocal might be:
See SMS gateway by country for information on most common SMS gateways.
- Test the configuration by sending an email.
- Save the settings.
If you do not receive notifications for health rule violations, it could be because the SMTP server timeout is set too short a period of time. To troubleshoot this problem:
- Log in to the Administration Console.
- Select the Controller Settings option.
- Increase the mail.smtp.socketiotimeout global configuration property. The default setting is 30 seconds.