> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemmodeler/project-settings/smtp-settings.md).

# SMTP Settings

{% hint style="info" %}
Using your own (corporate) mail server for handling emails has the additional advantage of logging and providing information: 

* when your messages cannot be delivered to recipients, the Non-Delivery-Reports will be available on your own mail server, so you can act on that information.
* Also, all sent items can be found in the mailbox of the used sender – available for review, follow-up, or just evidence that a message has indeed been sent.
  {% endhint %}

{% hint style="warning" %}
The sender you set on the e-mail process node (from-parameter) must have the same domain as the SMTP server, or the SMTP server must be allowed to send mails on behalf of the sender in the from-parameter. 
{% endhint %}

Per portal you can select which SMTP Server you want to use to send e-mail messages from.

The list of available SMTP Servers was previously managed on Workspace Level (or in DevOps portal for Kubernetes Runtimes). This has changed since 2024-12-12, you can now manage the profiles directly from the Portal Settings, via button `[Manage project SMTP servers]`:

<figure><img src="/files/cxH7XNskBhl3Zw7hywQb" alt=""><figcaption><p>manage SMTP server profiles</p></figcaption></figure>

* On the overlay for SMTP Servers, add or edit an entry.

<figure><img src="/files/GhrUYhbUTz3BTU1vs7Mb" alt=""><figcaption></figcaption></figure>

* Parameters to set, are:
  * Host (smtp server hostname, like smtp.gmail.com or smtp.office365.com).
  * Port (587 is the standard for secure SMTP via TLS).
  * Username (the account that can connect to the server and has sufficient rights to send messages on behalf of the from-address you want to use in your project's emails).
  * Password for that username to access the SMTP server.

After one or more SMTP server profiles have been set up, you can pick one on the Portal Settings to be used specifically for sending out E-mail messages using the Email Process Node.

{% hint style="info" %}
It is possible to use a (free) Gmail account that you own, as SMTP server.

<https://support.google.com/a/answer/176600?hl=en>

<img src="/files/waQQHgiYU4uRndeyeqSc" alt="" data-size="original">
{% endhint %}

{% hint style="info" %}
If you want to use **IP-whitelisting** on your SMTP-server, or use an **Exchange Connector** to allow incoming SMTP traffic from your WEM Application, you may need to know the IP-address for the WEM Server that sends out the SMTP traffic.

For portals running in **EUR** zone, use **\[185.3.209.154]** as the IP-address from which WEM is sending the emails.

For portals running in **APAC** zone, the outbound mail will come from **\[52.189.211.222]**.
{% endhint %}

### **Office 365 Account Settings**

#### If you are using an Office365 account, **following info is very important**:

* The account-username to be used in the WEM SMTP Profile must be an **active account in Office365** - you may need to **specifically login** to Office365 with this account as Microsoft may require this for accounts to be activated and checked with additional information - also check **Multi-Factor** settings that may cause issues when an application acts as non-interactive-user. This account may be setup as a non-personal account (like <smtpsender@yourdomain.com>).
* The Office365 Account must have a **valid office license with a mailbox** (so you can also see the Sent Items there and useful info like non-delivery-reports).
* The Office365 Account has **permissions or aliases** to **send on behalf of** all the addresses used in the FROM parameter of the email nodes in your application (like <noreply@yourdomain.com>).
* The Office365 Account **must be setup using MFA and an App Password must be created. This App Password must be used in the WEM SMTP Profile Settings.** This is necessary to work around the required Multi Factor Authentication and to enable another application like your WEM Runtime Portal to login to Office365 bypassing the MFA.

[**Read this link from Microsoft**](https://support.microsoft.com/en-us/account-billing/using-app-passwords-with-apps-that-don-t-support-two-step-verification-5896ed9b-4263-e681-128a-a6f2979a7944) about how to set up App Password.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wem.io/platform/wemmodeler/project-settings/smtp-settings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.