Servd offers a direct integration with ElasticEmail to provide almost-zero-config email deliverability for transactional emails.

We've partnered with ElasticEmail to offer this service for free for all subscribed projects, with optional addons to increase the number of emails that you can send per month.

Once your SMTP account is enabled Servd will automatically begin adding the following environment variables to all of your environments:

`SERVD_SMTP_HOSTNAME`
`SERVD_SMTP_PORT`
`SERVD_SMTP_USERNAME`
`SERVD_SMTP_PASSWORD`

We can use these within Craft's Email settings in order to get everything up and running.

If you're using Craft's 'Project Config' you'll need to perform the following steps in your local development environment:

In order to get emails into your recipient's inboxes, and not flagged as spam, you'll need to set up DKIM, SPF and DMARC, but don't worry! It's simply a case of adding a few DNS records to your sending domain.

The records you need to add can be found in your project's SMTP page. As every DNS provider is a little different, please refer to your DNS provider's documentation for detailed instructions on how to add these records to your account.

Once they have been added, return to the Servd dashboard and click the 'Verify' button next to each of the records to check that they have been set and activate their associated functionality.

If you already have SPF records set

If you're already sending emails from the same domain via another platform, you might already have SPF DNS records defined. If that is the case do not delete the existing ones. Instead you can combine the contents of the existing record with the new value from the Servd Dashboard.

For example, if your domain already has the record: `v=spf1 a mx include:_spf.google.com ~all`, then you would just add: `include:_spf.elasticemail.com`.
​
The final record would look like this: `v=spf1 a mx include:_spf.google.com include:_spf.elasticemail.com ~all`.

When you setup DMARC, you may start receiving emails from external email providers containing reports on what they've received from your domain. This is a key part of DMARC as it allows recipient providers to let you know if they're receiving spam from your domain.
​

Reports are sent to the email address included in the value of your `_dmarc` DNS record, specifically the `ruf` and `rua` keys. By default, Servd includes the email you provided when setting up your ElasticEmail SMTP account, but you are free to change this to a more appropriate address should you prefer.

To help you make sense of the reports, we recommend using Postmark's free DMARC monitoring tool. It generates you a special email address which, when added to your DMARC DNS record, will start receiving and digesting reports from providers. They then deliver the information in a more user-friendly format so you can understand how your domain is being used.
​

If you are seeing an error like this in the project logs when sending an email...

...then there is likely a mismatch between the sender domain that was entered when creating the SMTP account and the "from" email address being used to send the email. The sender domain needs to match the domain of the "from" email address, so to rectify the error, we suggest changing the "from" email address to match it.

If you'd prefer to change the sender domain instead, get in touch via our support and we can update it for you. Alternatively, you can delete the SMTP account in the project's SMTP settings and create a new one with the correct sender domain, and then sync the project to receive the new SMTP credentials in the `SERVD_SMTP` environment variables. Either way you choose, the new domain will require SPF, DKIM and DMARC DNS records to be updated to it to avoid emails being marked as spam.
​