> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes/mail-sender-configuration.md).

# Mail Sender Configuration

Cortex XSOAR 8 provides a built-in mail sender integration. It is installed out-of-the-box and does not require you to set up an SMTP server or provide credentials. Emails sent via the built-in mail sender integration have a watermark that specifies the FQDN and mentions that the mail was sent via Cortex XSOAR. This provides protection against possible abuse of the built-in mail sender.

{% hint style="info" %}

### Tip

We recommend using the built-in mail sender for all tenants, as it impacts sending emails from the child tenants.
{% endhint %}

By default, the built-in mail sender is disabled and your mail sender from Cortex XSOAR 6 is used. You have the option to enable the built-in mail sender and disable your previous mail server integration.

During the User Acceptance Testing (UAT) phase, mail sender integrations are disabled by default. To test the built-in mail sender or your mail sender integration, enable the relevant integration instance. To temporarily enable a mail sender, go to **Settings & Info** → **Settings** → **Integrations** → **Instances**, click on the arrow next to your mail sender integration (or the built-in **Mail Sender** integration) and **Enable** the integration instance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes/mail-sender-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.