> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/administration-and-runtimes/configure-outgoing-notification-email.md).

# Configure outgoing notification email

Choose the notification feature you need before entering mail settings. In the inspected current navigation, operational alerts use Manage → Alert Management, while dashboard reports use Settings → Dashboard Summary Mail. A separate Settings → Mail Server page was not exposed in that navigation; its reference steps below apply only to versions that provide it.

### Current route: operational alert email

Open Manage → Alert Management and select Add Alert Profile. The Create Alert Rule wizard proceeds through Alert Rule → Actioneer Settings → Choose Hyper Flows. Configure delivery in the Email Settings portion of Actioneer Settings, or choose an appropriate existing configuration.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2Frit4Ek1LJY9zTQadJX4n%2Falert-actioneer-email.jpg?alt=media" alt="Current operational-alert Email Settings in Actioneer Settings. This is a feature-specific delivery configuration, not evidence of a global Mail Server page. No profile was saved and no test mail was sent."><figcaption><p>Current operational-alert Email Settings in Actioneer Settings. This is a feature-specific delivery configuration, not evidence of a global Mail Server page. No profile was saved and no test mail was sent.</p></figcaption></figure>

The inspected form requires Host, Port, Sender, To, Subject and Settings Name. Requires Authentication exposes its credential fields; CC, Body and Settings Description are also available. Obtain the exact permitted values from your mail administrator and keep passwords out of screenshots.

Use Test E-Mail Address and Send a test mail only with an approved test recipient. Confirm receipt separately, then test the alert condition and selected Hyperflow scope. A delivery test does not establish that a runtime rule matches.

[Configure operational alerts](/userguide/operate-and-troubleshoot/configure-operational-alerts.md)

[Schedule dashboard summary emails](/userguide/operate-and-troubleshoot/schedule-dashboard-summary-emails.md)

### Before you start

* Have permission to change platform settings.
* Obtain the server hostname, port, SMTP/SMTPS mode, TLS requirement, and authentication details.
* Confirm the permitted sender address and an approved test recipient.
* Confirm any network or mail-server allowlisting required for this environment.

### Version-specific reference: separate Mail Server page

1. If your installed version exposes Settings > Mail Server, open that page. Otherwise use the feature-specific routes above; do not assume a hidden global page is required.
2. Enter **Server Name** and the connection port.
3. Enter the sender name and sender email address.
4. Select the email protocol offered by the form.
5. Set **Enable TLS** according to your mail provider's requirements.
6. If the provider requires authentication, enable **Requires Authentication** and fill in the displayed credential fields.
7. Save the configuration using the page's save control.

Do not copy passwords into screenshots or a troubleshooting email. Share the server and error details separately from the credential.

### Test controls on versions with a separate Mail Server page

1. Enter the agreed test recipient.
2. Select **Send a test mail**.
3. Check the UI response.
4. Confirm receipt, sender identity, and delivery time with the recipient.
5. Check junk/quarantine if the server accepted the message but it is not in the inbox.

### Expected result

The configured server accepts the test and the recipient receives the intended message. Test the alert or reporting workflow separately, because each feature can have its own delivery configuration.

### Troubleshoot

* Connection timeout: check network access and the host/port combination.
* TLS or certificate error: compare the selected protocol and TLS settings with the provider's requirements.
* Authentication failure: check account status, supported authentication, and credential validity.
* Sender rejected: confirm that the configured account may send as the selected address.
* Message not received: inspect the sending server and recipient quarantine before repeating the test.

### Prepare and verify one notification-mail setup

Ask the mail administrator for the exact hostname, port, protocol/TLS combination, sender address and authentication requirements. There is no universal SMTP configuration to copy between providers.

1\. For current operational alerts, open Manage → Alert Management → Add Alert Profile, then Actioneer Settings. Match the approved host, port and sender details to the Email Settings fields.

2\. Complete To, Subject and Settings Name. Enable Requires Authentication only when required by that server and enter the supplied credentials in the form. Keep password values out of screenshots.

3\. Before saving, check the allowed sender identity, network access, intended alert condition and selected Hyperflows.

4\. When an approved test recipient is available, use Test E-Mail Address and Send a test mail in Actioneer Settings once and record the UI result. Confirm receipt, sender and time with that recipient.

5\. If the server accepted the request but the message is absent, inspect delivery/quarantine before sending again. Afterwards test the intended alert or summary separately; its configuration is a different part of the delivery path.