> 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/authentication.md).

# Authentication section of Patch My PC Publisher

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

The **Authentication** section on the **Email Alerts** tab of Patch My PC (PMPC) Publisher configures how Publisher signs in to the mail server to be able to send email alerts.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FaHevPjcqNpykUG1qLRKz%2Fimage.png?alt=media&amp;token=a4132ed6-127d-4b25-98f8-d9a832b3cd05" alt="&#x27;Authentication&#x27; section" width="563"><figcaption></figcaption></figure>

When choosing an authentication method, select the option that aligns with how your mail system accepts SMTP connections.

For internal or on-premises mail servers, [Specific user](#specific-user) is commonly used when the relay supports authenticated SMTP connections.

For cloud-based email services such as Microsoft 365 (Exchange Online) and Google Workspace, [OAuth2 (App Auth)](#oauth2-app-auth) is recommended, as modern cloud providers increasingly restrict or deprecate username and password–based SMTP authentication.

Ultimately, the appropriate option depends on the authentication methods supported by your SMTP server.

You can choose from the following authentication methods:

* [Anonymous](#anonymous)
* [System account](#system-account)
* [Specific user](#specific-user)
* [OAuth2 (App Auth)](#oauth2-app-auth)

## **Anonymous**

Use the **Anonymous** option only if your SMTP relay explicitly allows unauthenticated sending. Most cloud providers, including Exchange Online, do not support anonymous SMTP. This option typically works only with on-premises SMTP relays configured to accept unauthenticated traffic from trusted internal IP addresses.

{% hint style="info" %}
**Note**

When you select **Anonymous**, the **Login** and **Password** fields do not appear, as no credentials are required for authentication. See [Server Configuration for Anonymous](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/server.md#server-configuration-for-anonymous) for details on how you should configure the settings in the **Server** section.
{% endhint %}

## **System account**

Use the **System account** option to authenticate to the SMTP server using the Windows account under which the Publisher service is running.

Choose this option only if your SMTP relay supports integrated Windows authentication using NTLM or Kerberos. This is typically limited to on-premises Microsoft Exchange servers or internal SMTP relays within the same Active Directory domain.

By default, the Publisher service runs under the local **SYSTEM** account.

{% hint style="info" %}
**Note**

When you select **System account**, the **Login** and **Password** fields do not appear, as no credentials are required for authentication. See [Server Configuration for System account](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/server.md#server-configuration-for-system-account) for details on how you should configure the settings in the **Server** section.
{% endhint %}

## **Specific user**

Use the **Specific user** option when your SMTP server requires authentication with a dedicated username and password. This is the most common configuration and is recommended for most environments, including Exchange Online, Google Workspace, and authenticated SMTP relays.

{% hint style="danger" %}
**Important**

Microsoft Exchange Online has deprecated Basic SMTP authentication and does not support username/password–based SMTP authentication by default. For Exchange Online, OAuth2 (App Authentication) is recommended.

Some providers, such as Google Workspace, may still allow authenticated SMTP using a username and password, but this typically requires additional configuration and may be restricted by tenant security policies.
{% endhint %}

If you choose to use the **Specific user** option, configure the following settings:

<table><thead><tr><th width="101.77777099609375" valign="top">Field</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Login</td><td valign="top">Enter the username used to authenticate to the SMTP server. This is often a full email address but may vary depending on your mail provider or relay configuration.</td></tr><tr><td valign="top">Password</td><td valign="top">Enter the password associated with the specified SMTP account.</td></tr></tbody></table>

{% hint style="info" %}
**Note**

See [Server Configuration for Specific user](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/server.md#server-configuration-for-specific-user) for details on how you should configure the settings in the **Server** section.
{% endhint %}

### OAuth2 (App Auth)

Use the **OAuth2 (App Auth)** option to send email using OAuth 2.0 instead of a mailbox username and password. OAuth2 authenticates using a Microsoft Entra ID app registration and is the recommended approach for modern cloud email services.

{% hint style="info" %}
**Note**

See [OAuth2 (App Auth) Configuration](https://docs.patchmypc.com/patch-my-pc-publisher/manage/alerts-tab/email-alerts-tab/authentication/configure-oauth2.md) for detailed guidance on how to configure OAuth 2.0 authentication for email notifications.
{% endhint %}


---

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