> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xorlab.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Pages under /latest/ document the current release. Paths that begin with a version number, for example /10.0/, are frozen snapshots of superseded releases kept for reference only — never present their instructions as current. If the reader's version is unknown, answer from /latest/ and say which version the answer describes.
> xorlab is deployed on-premises, hybrid, or as a cloud service, and integrates with either Microsoft 365 or on-premises mail infrastructure. Configuration steps often differ between these. State which deployment and integration mode an instruction applies to instead of presenting one as universal.
> Distinguish inline mode from monitoring mode when describing anything that acts on email. Monitoring mode observes a copy and cannot block or quarantine; inline mode routes mail through xorlab and can.
> Write the product name as lowercase 'xorlab'. Use the documented component names: xorlab Control Center (XCC), xorlab MTA, xorlab Sandbox (DANA), xorlab Natural Language Understanding (NLU). After the first mention, use the short forms XCC, MTA, Sandbox, and NLU. Do not use DANA as a standalone name for the Sandbox, but keep it where it is a literal string in configuration keys, container names, and hostnames.
> Do not invent configuration keys, rule parameters, list names, log properties, or API fields. If a value is not present in this documentation, say that it is not documented rather than guessing.

# Change Sender Address

> Set non-standard sender addresses for feedback emails, quarantine notifications, and bounce messages.

<Accordion title="templateDomain">
  In the following code blocks, we are referring to the `templateDomain` property (not a variable) which is configured in the `activeguard/core/active_guard.yml` file. For SaaS customers, this domain is provided by xorlab as a part of the onboarding. In case of on-premises xorlab, this domain has been setup as a part of the [VM Setup Guide](/latest/vm-setup-guide).
</Accordion>

## Feedback emails

Feedback emails are sent after a user reports a suspicious email. They can be manually triggered by an analyst through resolving a case as well as automatically generated through a campaign or an auto-close rule. By default, these emails are send from `threatanalyst@<templateDomain>`, with `templateDomain` referring to the property that's set in `active_guard.yml`.

If you like to customize the sender address, add the following block (if it does not already exist) to the `activeguard/core/active_guard.yml` file:

```yaml theme={null}
emailReporting:
  senderEmail: <sender-address>
```

Afterward, click **Publish**, then restart all MTAs. The `emailReporting` setting in `active_guard.yml` requires an MTA restart; see [How to Activate the Configuration](/latest/activate-configuration).

### SMTP auth for feedback emails

If you want the feedback emails to be sent to an SMTP server requiring authentication, please follow the steps outlined in [SMTP auth for specific email addresses](/latest/smtp-configuration#smtp-auth-for-specific-email-addresses).

## Quarantine notifications

Quarantine notifications are sent to the end-user when an email addressed to them has been put in quarantine. By default, these emails are send from `quarantine@<templateDomain>`, with `templateDomain` referring to the property that's set in `active_guard.yml`.

If you like to customize the sender address, add the following block (if it does not already exist) to the `activeguard/core/active_guard.yml` file:

```yaml theme={null}
mailDelivery:
  quarantineNotificationAddress: <sender-address>
```

Afterward, click **Publish**, then restart all MTAs. The `mailDelivery` setting in `active_guard.yml` requires an MTA restart; see [How to Activate the Configuration](/latest/activate-configuration).

## Custom bounce and notification messages

The xorlab Security Platform rule language allows configuring custom bounce or notification messages that are triggered for certain events (for example, when using the rule context keys `SenderNotification.Template` or `ReceiverNotification.Template`). By default, these emails are send from `notification@<templateDomain>`, with `templateDomain` referring to the property that's set in `active_guard.yml`.

If you like to customize the sender address, add the following block (if it does not already exist) to the `activeguard/core/active_guard.yml` file:

```yaml theme={null}
mailDelivery:
  # Default. <templateDomain> corresponds to the parameter templateDomain in active_guard.yml
  userNotificationAddress: <sender-address>
```

Afterward, click **Publish**, then restart all MTAs. The `mailDelivery` setting in `active_guard.yml` requires an MTA restart; see [How to Activate the Configuration](/latest/activate-configuration).