> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/message.md).

# Message section of Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

The **Message** section on the **Email Alerts** tab of Patch My PC (PMPC) Publisher allows you to configure who to send email notifications to and how they are addressed when specific publishing events occur.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2Fm4DA0its1S8BWIrAMaDT%2Fimage.png?alt=media&amp;token=84a00b0e-a595-4188-b253-2309db9673bb" alt=""><figcaption></figcaption></figure>

## **Sender** (*required*)

Enter the email address you want the alerts to come *from*. e.g. `alerts@yourdomain.com`

## **Recipients (*****required*****)**

Enter the email address(es) that should *receive* the alerts. You can enter multiple addresses separated by a semicolon. e.g. `alerts@yourdomain.com; security@yourdomain.com`

## **CC recipients (*****optional*****)**

Add any additional recipients if needed. You can enter multiple addresses separated by a semicolon. e.g. `alerts@yourdomain.com; security@yourdomain.com`

## Email subject (*required*)

The default subject of the email is `Report from Patch My PC Publishing Service`. You can change this if required.

## Additional text **(*****optional*****)**

Enter any additional text you want included at the top of the email report, such as notes or context for your recipients.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/message.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
