> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/settings/configuration-du-smtp.md).

# SMTP configuration

## Introduction

By default, Dastra routes a significant number of email notifications for the following services:

* Real time [Notifications](/en/features/settings/notifications.md) (New comments, tasks, ...)
* Email exchanges as part of a rights exercise request
* Invitations to audits for respondents
* Invitations for new users

By default, Dastra uses its own SMTP service.

### How to configure your SMTP sending server?

{% hint style="warning" %}
Customizing SMTP can lead to platform instabilities. Only perform this manipulation if you are certain of the proper functioning and deliverability of your email sending service.
{% endhint %}

### Benefits of customizing SMTP

Dastra strives to ensure maximum availability and security for transactional email delivery. However, depending on your internal security policy, you may need to internalize the routing of transactional emails to control messaging flows.

### Prerequisites

You need to have the configuration details of your SMTP server:

* SMTP Host (e.g., smtp.yourservice.com)
* SMTP Port (default is to use port 25)
* Username
* Password
* A valid sender email address (e.g., <noreply@yourservice.com>): this address must be properly validated by your SMTP provider.

{% hint style="warning" %}
Note that your SMTP server must support a secure connection using SSL.
{% endhint %}

### Configuration

Go to the SMTP [server configuration page](https://app.dastra.eu/general-settings/smtp).

Fill in the form fields using the data requested in the [prerequisites](#prerequisites).

Note that server connectivity is automatically tested to ensure that the server login credentials are correct. A test email will be automatically sent from our servers.

### Testing

Once you have submitted the form, your SMTP server should be operational. You can verify that the notification emails are indeed coming from your SMTP server. To do this, for example, create a comment in a process and see if you receive the notification email in your mailbox.

* **If you do not receive an email**: either you failed to trigger the notification, or there is a problem with your SMTP configuration.
* **If you receive an email**: verify that your SMTP and sender are properly displayed in the email details.

{% hint style="info" %}
[How to view email details in GMAIL](https://doc.dastra.eu/)

[How to view email details in Outlook](https://support.microsoft.com/fr-fr/office/afficher-les-en-t%C3%AAtes-de-message-internet-dans-outlook-cd039382-dc6e-4264-ac74-c048563d212c)
{% 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://doc.dastra.eu/en/features/settings/configuration-du-smtp.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.