> 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/products/cc-software/configure/server-configuration/server-enabling-gmail-for-notification.md). # Enabling Gmail for notifications [Server Configuration](/knowledge-hub/products/cc-software/configure/server-configuration.md) › Server - Enabling Gmail For Notifications > 📋 **Prerequisites:** Read [Server - Notifications](/knowledge-hub/products/cc-software/reference/server-notifications.md) first. ## This page answers * Why does Gmail reject Command Centre's outgoing email? * What is an App Password and how do you create one? * How do you configure Command Centre's outgoing and incoming email for Gmail? > ⚠️ **Important:** major SMTP providers (Office 365, Gmail, Yahoo, etc.) have stopped supporting basic authentication and "less secure apps" sign-in for third-party apps and devices. > ⚠️ **Important:** from Command Centre version **9.30**, the modern authentication method (**OAuth 2.0**) is supported with **Microsoft Entra** for Exchange Online email authentication, replacing the deprecated Basic Authentication method. When a Gmail account is used for outgoing email without an app password, Command Centre raises a Notification System Error. The alarm detail shows the SMTP rejection, for example: `535: 5.7.8 Username and Password not accepted`. ![Command Centre Alarm Properties dialog showing a Notification System Error with the SMTP 535 username-and-password-not-accepted message](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-49d3e516808700df613e7cd5e7a8364e4fe74b91%2FSECHUB-CCS-SRV-14-gmail-notification-system-error.png?alt=media) *** ## What is an App Password? An App Password is a unique, randomly generated password used to sign in to an app or device that does not support two-step verification or OAuth 2.0 (modern authentication). It is a **16-digit** passcode that gives a less secure app or device permission to access your Google Account. App passwords can only be used with accounts that have **2-Step Verification** turned on, and you enter the app password once per app or device. > **Important:** app passwords are not recommended and are unnecessary in most cases. Use them only where modern authentication is not available. ### Creating a Google App Password for outgoing email 1. Sign in to your Google Account. 2. Click **Security**. 3. Under **Signing in to Google**, click **App Passwords**. (You may need to sign in. If you do not have this option, it may be because 2-Step Verification is not set up, 2-Step Verification is only set up for security keys, your account is managed by a work/school/other organization, or you turned on Advanced Protection.) 4. Click **Select app** and choose the app. 5. Click **Select device** and pick the device you are using. 6. Click **Generate**. 7. Follow the instructions to enter the app password. The app password is the 16-character code in the yellow bar on your device. 8. Tap **Done**. > **Tip:** most of the time you only enter an app password once per app or device, so there is no need to memorise it. *** ## Command Centre outgoing email settings In Configuration Client, set up **File > Server Properties > Outgoing Email** with the following: 1. Your Gmail username **without** the `@gmail.com`. 2. Copy and paste the App Password into the Password field (**remove the spaces** in the password). 3. The standard SMTP address for Gmail (`smtp.gmail.com`). 4. The port for SMTP SSL (try port **587**), with **Use SSL** ticked. 5. The Sender Address that will indicate where the email came from (e.g. `username@gmail.com`). ![Command Centre Outgoing Email settings tab with the five numbered fields: Account, Password, smtp.gmail.com server, port 587 with Use SSL, and Sender Address](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-20d8fe5038f47c47ea2e48c5ea6544f7777fa7b2%2FSECHUB-CCS-SRV-10-cc-outgoing-email-settings.png?alt=media) ![Detail of the Command Centre Server Properties Outgoing Email configuration for Gmail](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d116f8f73f6b7e5318d8a08022347537c2e77fdc%2FSECHUB-CCS-SRV-15-gmail-test-email-received.png?alt=media) ### Sending a test email > **Note:** the operator account used with the test-notifications option **must** have an email address configured in that user account's Personal Data fields. The system user account will never work, as it cannot have a PDF attached to it. Send the test from the **Notifications** tab (each notification type has its own **Send Test Email** button). When successful, you receive the test email in your inbox. ![Command Centre Notifications tab showing Send Test Email buttons for each notification type and the Broadcast Notification batch-size option](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-5f7401ef446755ad1726ca66c133b5422555c383%2FSECHUB-CCS-SRV-12-cc-notifications-send-test-email.png?alt=media) *** ## Enabling incoming email Incoming email lets an operator acknowledge an alarm by replying to its notification email. > ⚠️ **Important:** the cardholder receiving the email must have an **operator account with the Edit Alarms privilege** to acknowledge an alarm. They must reply to the email with **"Ack"** only. They **cannot** "Process" an alarm from a reply email. Configure incoming email (CC Server Properties > Incoming Email) with: 1. Your full Gmail address. 2. Your Gmail account password (case sensitive). 3. The IMAP address for Gmail (`imap.gmail.com`). 4. The port for IMAP with Gmail (`993`), with **Use SSL** ticked. 5. The interval between checks for new mail (e.g. every 5 seconds). ![Command Centre Incoming Email settings tab with the five numbered fields: IMAP protocol, Account, Password, imap.gmail.com server, port 993, and retrieve-new-email interval](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ea4fbcb2cbf2981dc59de7c13d28ea41d1e96282%2FSECHUB-CCS-SRV-13-gmail-incoming-email-settings.png?alt=media) When set up correctly, you receive an **Incoming Email Connected** event in the Event Viewer ("Incoming Email Notification System successfully connected"). ![Command Centre Event Viewer showing an Incoming Email Connected event confirming the incoming email notification system connected successfully](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-856945467f024746accb607441bee8fd60a95f45%2FSECHUB-CCS-SRV-16-event-viewer-incoming-connected.png?alt=media) *** 🔗 **Related** * [Server - Notifications](/knowledge-hub/products/cc-software/reference/server-notifications.md). The delivery methods and the SMTP path Gmail plugs into. --- # 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/products/cc-software/configure/server-configuration/server-enabling-gmail-for-notification.md?ask=&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.