In this article, we will show you how to create a custom email as the sender for your event.
This option is only available for Professional and Enterprise customers.
To do this, go to an event of your choice and click on “Messages” → “Email sender”
(Once an email sender has been activated, it can be used for all events in your account).
If you have not yet created your own sender, an empty window will open with the option "Add new sender". Click on this once.
A window will now open in which you can enter your desired e-mail.
As soon as you click on "Create", a confirmation email will be sent to this email address.
The link in it is active for 24 hours. After you have clicked on the link in this email, the email address is confirmed and receives a green tick in the system.
The last step involves entering certain DNS entries to enable our emails to be sent via the specified email.
To do this, click on the email in the sender overview to open the detailed view. (The detailed view can only be opened once the email has been verified)
You will now see a table with various DNS entries.
All entries marked with "(required)" must be entered for the sender domain via your IT department or hosting provider.
We also recommend entering the entries marked "(recommended)", but they are not mandatory.
Once the entries have been entered, everything is done, but it may take a few hours before you can use the e-mail address.
Our system checks every 60 minutes whether the entries have been set. As soon as the domain has been successfully verified, a green tick appears next to "Domain verified" and the email sender is now available for selection in your email templates.
See also the article "Customised domain for the landing page (incl. wildcard)".
You also have these options with our quick menu:
- Resend the verification email
- Manually verify the sender domain
- Delete the sender
General information on DNS records for sending emails
DNS records play a central role in improving the deliverability and security of your emails. These records help to identify your emails as legitimate and confirm the authenticity of your messages.
Here are the most important DNS records required for secure email delivery:
MX-records (Mail Exchange):
The MX record shows which mail server is responsible for receiving emails for your domain. It is particularly important for receiving replies and server messages. The MX record entry is optional and is recognised as positive by the recipient server if it contains the same domain as the sender address. If the MX entry is not set, an MX server from our service provider Amazon Webservices is automatically used to process the responses.
TXT-records for SPF (Sender Policy Framework):
An SPF entry confirms that the mail servers that send emails on behalf of your domain are authorised to do so. A typical SPF record for use with AWS SES could be: v=spf1 include:amazonses.com ~all. This indicates that emails sent via AWS SES are authorised and emails that do not match should be treated as suspicious. If an SPF entry already exists, please add ‘include:amazonses.com’. These entries are mandatory in order to be able to use your own sender domain.
CNAME-records for DKIM (DomainKeys Identified Mail):
In contrast to a TXT entry, DKIM entries for AWS SES are stored as CNAME entries. These CNAME records refer to the DKIM keys generated by AWS SES. Adding DKIM as a CNAME record makes it possible to verify the authenticity of your emails and ensure that they have not been altered on their way to the recipient. These entries are mandatory in order to be able to use your own sender domain.
TXT-records for DMARC (Domain-based Message Authentication, Reporting, and Conformance):
A DMARC entry uses SPF and DKIM to determine how email recipients should handle messages that fail authentication checks. A typical DMARC entry could look like this: _dmarc.example.com v=DMARC1; p=quarantine; pct=100, which indicates that all emails that fail authentication checks should be moved to quarantine. This entry is recommended.
Summary:
- MX-records are crucial for receiving server responses and improve trust in the sender domain.
- SPF-records confirm that senders who send emails on behalf of your domain are authorised to do so.
- CNAME-records for DKIM are required to ensure the integrity and authenticity of your emails.
- DMARC-records define how to deal with emails that do not pass the authentication checks.
You can find out more about SPF, DMARC and DKIM here: SPF, DKIM und DMARC: Sicherheit beim E-Mail-Versand mit AirLST über AWS