> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/tech/10.6/using-iis-smtp-gateway.md).

# SMTP Notifications

## Overview

WorkflowGen supports three email delivery methods:

* **SMTP server (Basic Authentication):** Sends messages to the configured SMTP server, which can be an enterprise mail server or an SMTP relay. Configure authentication credentials when required by that server.
* **SMTP server (OAuth 2.0):** Sends messages through Microsoft 365 / Exchange Online using OAuth 2.0 client credentials. This method currently supports Microsoft 365 / Exchange Online only.
* **Pickup directory:** Writes outgoing messages to a local folder for processing by a separately configured SMTP service.

Choose the method that matches your organization’s mail infrastructure and authentication requirements. For configuration settings and test instructions, see [SMTP server](https://docs.workflowgen.com/admin/configuration-panel#smtp-server) in the WorkflowGen Administration Guide.

## Using an IIS SMTP gateway

An IIS SMTP gateway can forward WorkflowGen notifications to an enterprise SMTP gateway, also called a smart host. Depending on its configuration, the relay can provide message queuing, retries and delivery logging. The relay can run on the WorkflowGen server or another server.

{% hint style="warning" %}

### Windows Server compatibility

The built-in SMTP server service is not available on Windows Server 2025. The procedure below applies only to servers where that service is available. WorkflowGen running on Windows Server 2025 can still use an IIS SMTP relay hosted on another compatible server, such as Windows Server 2022, or another SMTP server or relay.

For more information, see [Microsoft’s list of features removed from Windows Server](https://learn.microsoft.com/en-us/windows-server/get-started/removed-deprecated-features-windows-server?tabs=ws25).
{% endhint %}

### Configuring an IIS SMTP gateway

1. Install and configure the SMTP server service on the compatible Windows server that will host the relay.
2. Open IIS 6.0 Manager, and then open the properties of the SMTP virtual server.
3. On the **Access** tab, configure **Connection permissions** to allow only the intended WorkflowGen server addresses.
4. Under **Relay**, select **Only the list below** and add the intended WorkflowGen server addresses. If WorkflowGen runs on the relay server, allow the local address used by WorkflowGen. Review any authenticated relay exception to ensure it does not broaden access beyond the intended senders.
5. Under **Delivery > Advanced**, enter the enterprise SMTP gateway’s hostname or IP address in Smart host.
6. Configure the outbound authentication, TLS, and connection port required by the enterprise SMTP gateway.
7. In WorkflowGen, select **SMTP server (Basic Authentication)** and configure the relay’s hostname, port and applicable authentication and TLS settings (see [SMTP server](https://docs.workflowgen.com/admin/configuration-panel#smtp-server) in the WorkflowGen Administration Guide).
8. Send a test message from WorkflowGen and verify delivery and the relay’s logs.

## Using a pickup directory

With a pickup directory, WorkflowGen writes outgoing email messages to a local folder instead of submitting them over SMTP. A separately configured SMTP service must process that folder and deliver the messages.\
\
Under **SMTP server** on the **General** tab in the Administration Module **Configuration** panel, select **Pickup directory**, and set the folder path. Alternatively, configure `ApplicationSmtpPickupDirectory` in the WorkflowGen `web.config` file.\
\
The default configured path is `C:\inetpub\mailroot\Pickup`. Ensure that the folder exists, that the WorkflowGen application identity has the required write permissions, and that the SMTP service is configured to process it. Setting the path alone does not establish email delivery.

{% hint style="warning" %}
On Windows Server 2025, the built-in IIS SMTP service is unavailable. Use pickup delivery only when another compatible SMTP service processes the configured folder; otherwise, configure SMTP delivery to an appropriate server or relay.
{% 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.workflowgen.com/tech/10.6/using-iis-smtp-gateway.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.
