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

# Upgrading to Version 9.0.X

xorlab follows semantic versioning using the `Major.Minor.Patch` format. For example, `9.X.2` means patch no. 2 to the Xth minor release of the 9th major version of the software.

This guide supports system administrators in upgrading XSP to a new minor or major release while ensuring minimal disruption.

Before proceeding, ensure that you have a recent backup in place. Refer to *[Manual backup](backup-recovery.md/#manual-backup)* and *[Patch Rollback](backup-recovery.md/#patch-rollback)* for detailed instructions.

## Release support lifecycle

xorlab follows a time-based release support lifecycle. Each major release is supported for 9 months after its initial public release. Customers are expected to upgrade xorlab at least twice per year to remain within a supported release.

Please refer to the *[Release Lifecycle Support](https://docs.xorlab.com/9.0/release-lifecycle-support.md)* page to verify support timelines and end-of-support dates.

## Release notes

Below is a summary of major changes in version 9.0.X. For a complete list of changes, refer to the *[Changelog](https://docs.xorlab.com/changelog.md)*.

* **New SSQ release feature**: End-users can now request the release of quarantined emails directly via their SSQ. The feature can be enabled individually per quarantine, and is per default deactivated.
* **Hot-reload for authentication settings**: Configuration changes to LDAP, SAML, and other authentication integrations no longer require a service restart.
* **Enhanced email authentication insights**: SPF, DKIM, and DMARC alignment results are now summarized in the message detail view.
* **Improved multi-tenant support**: SSQ configuration and data retention settings are now fully multi-tenant capable and can be managed separately for each domain.

### Breaking changes

* \[SA-14037] Rules: The following MTA trust lists were removed:

  * `MTA EHLO trust list for guarded (regex)`
  * `MTA EHLO trust list for partner (regex)`
  * `MTA RDNS trust list for guarded (regex)`
  * `MTA RDNS trust list for partner (regex)`

  If you're using any of these lists and want to keep these MTA entries trusted, make sure to manually migrate them to the `trustedMTAProfiles` in `active_guard.yml`. See more information here: [https://docs.xorlab.com/9.0/trusted-mtas/](https://docs.xorlab.com/9.0/trusted-mtas.md).

  Also removed are the following rule templates: `sender_is_trusted_ehlo_for_guarded.xml`, `sender_is_trusted_ehlo_for_partner.xml`, `sender_is_trusted_reverse_dns_for_guarded.xml` and `sender_is_trusted_reverse_dns_for_partner.xml`

  If any custom rule exists that relies on these templates (e.g., if it uses `<template name="sender_is_trusted_ehlo_for_guarded"/>` anywhere), the rule will stop working.

* \[SA-14284] XCC: All configuration parameters related to data retention were moved from `xcc.yml` to `guarded_tenants.yml`, see [Data Retention](https://docs.xorlab.com/9.0/data-retention.md?h=reten#configuration). Additionally, all SSQ related configuration parameters were also moved from `xcc.yml` to `guarded_tenants.yml`, see [SSQ](https://docs.xorlab.com/9.0/ssq-self-service-quarantine.md). No action is required from your side.

* \[SA-14354] MTA: Only consider `TXT` DNS records when verifying SPF, ignore `SPF` DNS records. **Please ensure all your guarded domains have valid SPF entries in their `TXT` DNS records.**

## Upgrade Process

### Order of Process

Upgrade XSP Services in the following order:

1. Sandbox (for an on-premises instance)
2. XCC
3. MTA

If multiple services run on the same host, the migration script ensures the correct order automatically.

### Execute the Script

Run the following command as the `admin` user on each host, following the upgrade order above:

```shell theme={null}
# Replace X.Y.Z with the version number you would like to upgrade to, e.g. 9.0.2
xorlab-upgrade X.Y.Z
```

**After you ran the script on every host, the process of upgrading XSP to the new release is finished.**

## Post-upgrade actions

During the migration period, it’s important to check the migration logs for any warnings or errors that may occur. To do this, use the following link (be sure to replace `<xcc_domain:xcc.customer.tld>` with your actual XCC domain in the browser):

```html theme={null}
https://<xcc_domain:xcc.customer.tld>/monitoring/explore?panes=%7B%22ZU4%22:%7B%22datasource%22:%22loki_monitoring_cbef60b6%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Blevel%3D~%5C%22WARN%7CERROR%5C%22,%20container_name%3D%5C%22xcc_backend%5C%22%7D%20%7C%3D%20%60MigrationLogger%60%22,%22queryType%22:%22range%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22loki_monitoring_cbef60b6%22%7D,%22editorMode%22:%22builder%22%7D%5D,%22range%22:%7B%22from%22:%22now-24h%22,%22to%22:%22now%22%7D%7D%7D&schemaVersion=1&orgId=1
```

We recommend reviewing the warnings carefully to ensure a successful migration. If you have any questions or issues, please do not hesitate to contact us at [support@xorlab.com](mailto:support@xorlab.com).

## New features configuration

After upgrading, review the documentation pages below for new features introduced in version 9.0.X and apply configurations as needed.

* [Request-release feature](https://docs.xorlab.com/9.0/request-release.md)
* [Email authentication insights](https://docs.xorlab.com/9.0/email-authentication.md)
* [Improved multi-tenancy support](https://docs.xorlab.com/9.0/multi-tenancy-configuration.md#config-sets)

## Troubleshooting

If you experience issues or have questions, refer to the support documentation or contact our support team at [support@xorlab.com](mailto:support@xorlab.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.