Chapter 17. Integrating with email

Procedure

1. Go to Platform Configuration Integrations.
2. Under the Notifier Integrations section, select Email.
3. Select New Integration.
4. In the Integration name field, enter a name for your email integration.
5. In the Email server field, enter the address of your email server. The email server address includes fully qualified domain name (FQDN) and the port number; for example, smtp.example.com:465.

6. Optional: If you are using unauthenticated SMTP, select Enable unauthenticated SMTP. This is insecure and not recommended, but might be required for some integrations. For example, you might need to enable this option if you use an internal server for notifications that does not require authentication.

   Note

   You cannot change an existing email integration that uses authentication to enable unauthenticated SMTP. You must delete the existing integration and create a new one with Enable unauthenticated SMTP selected.

7. Enter the user name and password of a service account that is used for authentication.
8. Optional: Enter the name that you want to appear in the FROM header of email notifications in the From field; for example, Security Alerts.
9. Specify the email address that you want to appear in the SENDER header of email notifications in the Sender field.
10. Specify the email address that will receive the notifications in the Default recipient field.

11. Optional: Enter an annotation key in Annotation key for recipient. You can use annotations to dynamically determine an email recipient. To do this:

    1. Add an annotation similar to the following example in your namespace or deployment YAML file, where email is the Annotation key that you specify in your email integration. You can create an annotation for the deployment or the namespace.

       annotations:
         email: <email_address>

    2. Use the annotation key email in the Annotation key for recipient field.

       If you configured the deployment or namespace with an annotation, the RHACS sends the alert to the email specified in the annotation. Otherwise, it sends the alert to the default recipient.

       Note

       The following rules govern how RHACS determines the recipient of an email notification:

       • If the deployment has an annotation key, the annotation’s value overrides the default value.
       • If the namespace has an annotation key, the namespace’s value overrides the default value.
       • If a deployment has an annotation key and a defined audience, RHACS sends an email to the audience specified in the key.
       • If a deployment does not have an annotation key, RHACS checks the namespace for an annotation key and sends an email to the specified audience.
       • If no annotation keys exist, RHACS sends an email to the default recipient.

12. Optional: Select Disable TLS certificate validation (insecure) to send email without TLS. You should not disable TLS unless you are using StartTLS.

    Note

    Use TLS for email notifications. Without TLS, all email is sent unencrypted.

13. Optional: To use StartTLS, select either Login or Plain from the Use STARTTLS (requires TLS to be disabled) drop-down menu.

    Important

    With StartTLS, credentials are passed in plain text to the email server before the session encryption is established.

    • StartTLS with the Login parameter sends authentication credentials in a base64 encoded string.
    • StartTLS with the Plain parameter sends authentication credentials to your mail relay in plain text.

Procedure

1. In the RHACS portal, go to Platform Configuration Policy Management.
2. Select one or more policies for which you want to send alerts.
3. Under Bulk actions, select Enable notification.

4. In the Enable notification window, select the Email notifier.

   Note

   If you have not configured any other integrations, the system displays a message that no notifiers are configured.

5. Click Enable.

Procedure

1. Go to Platform Configuration Integrations.
2. Under the Notifier Integrations section, select RHACS Cloud Service Email.
3. Select New Integration.
4. In the Integration name field, enter a name for your email integration.
5. Specify the email address to which you want to send the email notifications in the Default recipient field.

6. Optional: Enter an annotation key in Annotation key for recipient. You can use annotations to dynamically determine an email recipient. To do this:

   1. Add an annotation similar to the following example in your namespace or deployment YAML file, where email is the Annotation key that you specify in your email integration. You can create an annotation for the deployment or the namespace.

      annotations:
        email: <email_address>

   2. Use the annotation key email in the Annotation key for recipient field.

Procedure

1. In the RHACS portal, go to Platform Configuration Policy Management.
2. Select one or more policies for which you want to send alerts.
3. Under Bulk actions, select Enable notification.

4. In the Enable notification window, select the RHACS Cloud Service Email notifier.

   Note

   If you have not configured any other integrations, the system displays a message that no notifiers are configured.

5. Click Enable.