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

# How to Activate the Configuration

> Which Expert Editor changes require a component restart to take effect, and which activate automatically within a minute.

All changes outside of the Expert Editor do not require a restart and will get automatically active after one minute.

After making changes in the Expert Editor, click **Publish** to deploy them. Then either wait for automatic activation or restart the component listed below.

## Configuration files

The following table lists all xorlab configuration files from the Expert Editor and how changes to them will get active. More specific entries overwrite the “required action” for wildcard (`*`) entries.

| File                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Required action                                                                                                                                                              |
| :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `activeguard/core/active_guard.yml`: <br />-  `ruleListUpdateCron`<br />- `ruleListUpdateOnStartup`<br />- `ruleListUpdateDisabled`<br />- `scanSources/smtp/handler/*`<br />- `smtpConfiguration`<br /><br />`activeguard/core/logback-audit.xml`<br />`activeguard/core/logback.properties`<br />`activeguard/core/rule_sets/*`<br /><br />`activeguard/rspamd/*`<br /><br />`activeguard/mta/logback-audit.xml`<br />`activeguard/mta/startup_cfg/postfix_custom/*`<br /><br />`auth/auth/*`<br /><br />`shared/*` <br /><br />`xcc/backend/logback-audit.xml`<br />`xcc/backend/logback.properties`<br />`xcc/backend/xcc.yml`:<br />- `misclassificationSubmission`<br />- `roleToPermissionMappings`<br />- `deliveryStatus`<br /><br />`monitored_mta/*`<br />`monitoring/* except grafana.ini` | None, automatically activated after one minute                                                                                                                               |
| `activeguard/core/active_guard.yml`: <br />`all properties not mentioned above, including:`<br /> - `serviceProviders`<br /> - `scanSources`<br /><br />`activeguard/core/startup_cfg/*`<br /><br />`activeguard/db/*`<br />`activeguard/mta/audit/audit.yml`<br /><br />`activeguard/core/startup_cfg/spamhaus_[hbl_]license.txt`                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Restart MTAs. For all MTAs:<br />1. SSH connect to the MTA<br />2. `cd /etc/xorlab/activeguard`<br />3. `docker compose down && docker compose up -d`                        |
| `xcc/backend/xcc.yml`: all properties not mentioned before<br /><br />`xcc/web/*`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | Restart XCC:<br />1. SSH connect to the XCC<br />2. `cd /etc/xorlab/xcc`<br />3. `docker compose down && docker compose up -d`                                               |
| `monitoring/grafana/grafana.ini`                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Restart Monitoring on MTAs. For all MTAs:<br />1. SSH connect to the MTA<br />2. `cd /etc/xorlab/monitored`<br />3. `docker compose down && sleep 2 && docker compose up -d` |

<Warning>
  **xorlab Security Platform (SaaS)**

  Restarting components is only possible for on-premises deployments. If you are using xorlab Security Platform (SaaS), please contact [support@xorlab.com](mailto:support@xorlab.com).
</Warning>