> ## 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.

# xorlab Sender Addresses

This page explains how to configure non-standard email addresses that xorlab Security Platform will use in the following situations:

* Receiving reported emails
* Sending feedback emails
* Sending quarantine notifications
* Sending custom bounce messages

The configuration file is  `activeguard/core/active_guard.yml`—open it in the XCC [Expert Editor](/9.0/expert-editor) to make changes.

<Note>
  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 (see step #7 in [*Basic settings*](/9.0/configuration-guide#basic-settings)). For SaaS customers, this domain is provided by xorlab as a part of the onboarding. In case of on-premise xorlab Security Platform, this domain has been setup as a part of the [*xorlab Security Platform VM Setup Guide*](/9.0/vm-setup-guide).
</Note>

## Reporting address

This configuration defines the email address under which xorlab Security Platform will receive the reported emails. All emails sent to this address will be treated as a report.

Reporting works by default and there is no need to change the configuration below, unless you want to use a custom reporting address.

```yaml theme={null}
scanSources:
- smtp
  port: 10025
  handler:
  - smtpReport:
      # Default. <templateDomain> corresponds to the parameter templateDomain in active_guard.yml
      emailAddress: suspicious@<templateDomain>
```

## 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.

Add the following block (if it does not already exist) to the `active_guard.yml` file with `<sender-address>` being the desired sender address:

<Tabs>
  <Tab title="`active_guard.yml` (default)">
    ```yaml theme={null}
    emailReporting:
      # Default. <templateDomain> corresponds to the parameter templateDomain in active_guard.yml
      senderEmail: threatanalyst@<templateDomain>
    ```
  </Tab>

  <Tab title="`active_guard.yml` (custom)">
    ```yaml theme={null}
    emailReporting:
      senderEmail: <sender-address>
    ```
  </Tab>
</Tabs>

### 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*](/9.0/smtp-configuration#smtp-auth-for-specific-email-addresses).

## Quarantine notifications

In order to configure the sender address used for quarantine notifications, open the `activeguard/core/active_guard.yml` file and set `quarantineNotificationAddress`. This is only needed if you use the quarantine notification feature.

```yaml theme={null}
mailDelivery:
  # Default. <templateDomain> corresponds to the parameter templateDomain in active_guard.yml
  quarantineNotificationAddress: quarantine@<templateDomain>
```

## 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`). If this feature is in use, the sender address for those bounce messages can be configured in the `activeguard/core/active_guard.yml` file using `userNotificationAddress`:

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