> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/email-configuration/email-from-the-logicnets-cloud.md).

# Email from the LogicNets Cloud

## Description

You can use email functionality when your application is hosted by LogicNets. The LogicNets Cloud uses Amazon AWS Cloud and implements functionality to ensure that email sent from the LogicNets Cloud is not treated as SPAM.

### Amazon SES

In the default setup LogicNets uses the Amazon SES mail service (<https://aws.amazon.com/ses/>) to relay all email traffic. The LogicNets Cloud uses Amazon SES to implement anti-SPAM functionality like SPF, DKIM, and DMARC. To allow Amazon SES to implement these you must make changes to your DNS for the following reasons:

1. Amazon wants to ensure that the sender's domain (the *from* address) is verified by the DNS owner, because this means Amazon will not be blacklisted by anti-spam organizations.
2. DKIM requires changes in the DNS to store the public keys; Amazon uses these private keys to sign the mails.
3. The DNS entry must specify the DMARC settings (<https://docs.aws.amazon.com/ses/latest/DeveloperGuide/easy-dkim.html>).
4. The Amazon server's SPF needs to be listed as valid mail server for sending email (<https://docs.aws.amazon.com/ses/latest/DeveloperGuide/spf.html>).

This setup allows you to use multiple mail addresses as *from* addresses from your domain when your domain is fully verified by Amazon SES.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-be1dbd5acd74b115a586b28143ebcb12718a610b%2F1a3accef-1aa4-4180-9ef4-a781c08e56e1.png?alt=media)

### Central Mail Server

If you have a subscription to a dedicated LogicNets hosted environment you also have a second option, which is that LogicNets relays all email traffic from your hosted environment to your central mail server. The advantage of this setup is that the system uses the SPF, DKIM, and DMARC configuration of your central mail server and you do not need to make changes to your DNS records.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9ccdd8d8ea174078e33f7b0153f391234d356a5d%2F5bd11572-88ae-4748-b81a-50c2f3920371.png?alt=media)

In this setup, all recipients thinks that the mails are sent from **your** trusted central mail server. The communication between the LogicNets local mail server and your central mail server uses the SMTP protocol, which is the same protocol people use at home to send mails through their internet service provider. Your central mail server needs to setup an email account and password, which the LogicNets mail server uses as credentials in the SMTP protocol.

Depending on your central mail server this setup only allows you to use one *from* mail address.


---

# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/email-configuration/email-from-the-logicnets-cloud.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.
