> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/incoming-email.md).

# Incoming Email

### Introduction

Completing the details on this tab gives a site the ability to acknowledge alarms through replying to the SMS/email.

**Note:** This tab is only visible if your site is licensed for the Notifications feature.

### Before you begin

Before you begin this procedure, ensure you have enabled and configured the outgoing email notifications on the previous tab. See [Outgoing Email](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/outgoing-email.md) for further detail.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Incoming Email** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-936d2b53f808bceea8f7ec629adea471ce871bb4%2Fincomingemailtab.png?alt=media)
3. Check the **Enable Incoming Email Notifications** checkbox.

   All other fields on this screen become enabled.
4. Configure the following fields as indicated:

   <table><thead><tr><th width="96">Field</th><th>Description</th></tr></thead><tbody><tr><td>Protocol</td><td>Defaults to POP3.</td></tr><tr><td>Account</td><td>An incoming email account (username@domain). Ensure this account is only used by Command Centre as email will be removed once processed.<br><br><strong>Note:</strong> Defaults to the same account as the outgoing account.</td></tr><tr><td>Password</td><td><p>A password is only needed if SSL is required.<br><br><strong>Notes:</strong></p><ul><li>SSL is recommended for incoming email.</li><li>If SSL is required, check the Use SSL checkbox also.</li></ul></td></tr><tr><td>Server</td><td>The email server DNS name or IP address.</td></tr><tr><td>Port</td><td>The port number.</td></tr></tbody></table>

   **Note:** If your site wishes to connect to an SMTP server not supporting authentication, the **Account** and **Password** fields should be left blank.
5. Check the **Validate Server Certificate** checkbox to allow Command Centre to verify the certificate provided to encrypt emails.

   **Note:** The **Use SSL** checkbox must be checked to enable this step.
6. Set how often the Command Centre Server is to **Retrieve new email** from the email server.

   (Default = 5 seconds; Range = 1 -999 seconds)
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/incoming-email.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.
