Custom Email Address
We are using AWS SES for email transport which dictates both processes described below. Learn more about both verification processes here.
Domain verification
Tips
We generally recommend domain verification.
In this case we will verify a whole (sub-) domain using DNS records. Afterwards we will be able to send emails from any email address ending with that (sub-) domain.
Process
- You inform us about the address you would like to use (e.g.
noreply@your-domain.com) - We start email domain verification with AWS and provide you with DKIM keys
- You will have 48 hours to complete DNS configuration and add the provided keys to the DNS of
your-domain.com - The domain is verified and can be used for outbound emails
Pros and cons
| Pro | Con |
|---|---|
| DKIM verified, emails are more likely not delivered to spam | DNS configuration required |
| DMARC and SPF compliance possible (please contact us) | |
| Any address that ends with your domain instantly possible |
Single Email verification
In this case we verify a specific email address like noreply@your-domain.com. Afterwards we will only be able to send emails from that specific email address.
Process
- You inform us about the address you would like to use (e.g.
noreply@your-domain.com) - We start email address verification with AWS
- AWS will send a verification email to your chosen email address
- You will have 48 hours to click on the activation link provided by AWS
- The email address is verified and can be used for outbound emails
Pros and cons
| Pro | Con |
|---|---|
| Easier to set up | DMARC, DKIM and SPF not possible |
| Step needs to be repeated if desired address changes | |
| You need to maintain an inbox for the desired address to receive the verification email |