> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup/system-settings/mailing-server/iis-smtp-exchange-server.md).

# IIS SMTP / Exchange Server

For large email sending requirement you can setup ngSurvey to use an IIS SMTP relay server or using your Microsoft Exchange Server. Instead of connecting to your mail server, which can be an expensive operation, ngSurvey will directly write all outgoing emails directly into the target IIS SMTP / Echange Pickup folder.

## 🔅 IIS / Exchange properties

* **`Pickup directory path`** path to the Pickup directory of your IIS SMTP or Exchange Server. You can use a network path.
* **`Restrict globally to one sender`** if enabled it allow us to specify one email and name that will be used for all email sending processes within ngSurvey. If activated ngSurvey will only use the email specified and will not use anymore the user account email and wont allow the user to enter any email for any of the email features like campaigns, tasks.

{% hint style="info" %}
If you are using a network path make sure to grant access to this path to the user used for your IIS application pool.
{% 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.ngsurvey.com/installation-setup/system-settings/mailing-server/iis-smtp-exchange-server.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.