To use your own email domain for email invites the following instruction below shall be followed. Note that this is an add-on. Request more information via your accountmanager.
Technical detail: we use Amazon Simple Email Service (AWS SES) for this.
Actual DNS records, including the domainkeys, will be generated per case
Please add the following records to your DNS:
| TYPE | NAME | VALUE | NOTES |
| CNAME | ???._domainkey | ???.dkim.amazonses.com | easy DKIM part 1 |
| CNAME | ???._domainkey | ???.dkim.amazonses.com | easy DKIM part 2 |
| CNAME | ???._domainkey | ???.dkim.amazonses.com | easy DKIM part 3 |
| MX | insocial | 10 feedback-smtp.eu-central-1.amazonses.com |
|
| TXT | insocial | "v=spf1 include:amazonses.com ~all" |
|
Definitions
CNAME= A CNAME (Canonical Name) record is a type of DNS record used to map a subdomain to another domain or service. In technical setups, it points a custom domain to a specific destination, such as an AWS SES endpoint for DKIM verification or a Cloudflare instance for white-label surveys.
These records are essential for domain verification and whitelabeling, allowing external services to manage specific functions like email authentication or hosting while using the customer
DKIM= DKIM (DomainKeys Identified Mail) is an email authentication method that adds a public key to a domain's DNS records. This allows email receivers to verify the authenticity of outgoing signed emails.
In technical setups, such as those using AWS SES, DKIM is configured by adding specific CNAME records to the DNS. Once these records are detected and verified, the identity status is updated to successful, ensuring that emails are recognised as legitimate by.
- MX= An MX record is a type of DNS record used to specify the mail server responsible for receiving email messages on behalf of a domain. In the context of white-label email domains, it is often configured on a subdomain to avoid impacting regular mail configurations. While optional, it is highly recommended because it improves email deliverability by resolving FROM alignment issues and ensuring compliance with DMARC standards. This record typically includes a priority value and a mail server address.
- TXT= A TXT record is a type of DNS record used to store text-based information. In the context of white-label email domains, it often functions as an SPF record on a subdomain. While optional, it is highly recommended to improve email deliverability. When combined with an MX record, it helps prevent FROM alignment issues by allowing senders to comply with DMARC standards. Users must ensure their DNS tools do not incorrectly double-
- SPF= SPF (Sender Policy Framework) is a DNS record that advises receivers how to handle emails sent on behalf of a domain. It specifies authorised senders to improve deliverability. Policies include Allow (+all) to accept emails, Soft fail (~all) which may mark messages as spam, and Fail (-all) to reject them. Records can be configured on subdomains to avoid impacting main domain configurations. Using SPF helps prevent FROM alignment issues and supports authentication.
Reply-to not allowed
We do not allow configurations for a custom ‘reply-to’. The same email-address as used for sending the emails is used for replies. Consider using an actual mailbox, or a catch-all to accept inbound traffic.
Security concerns?
Security concerns or practical issues using the main domain? Consider using a subdomain, like ‘@mail.domain.com’. Do let us know, we will regenerate the DNS records for this scenario.
Highly recommended
Optional: The MX and TXT record are optional but highly recommended. Combined with the MX record it is likely to improve deliverability by catching a FROM alignement issue.
Amazon: Messages you send through SES use a subdomain of amazonses.com as the default MAIL FROM domain. Setting the MAIL FROM to a domain you own enables you to comply with Domain-based Message Authentication, Reporting and Conformance (DMARC).
The MAIL FROM domain refers to the domain that appears in the 'From' field of an email message and is recommended for better deliverability, reputation management, and branding purposes. The MAIL FROM domain must be a subdomain of the verified identity from which you’re sending.
Example:
See the "verzonden door" (send by), this is a From misalignment.