trustyourinbox

Emarsys SPF and DKIM setup

The SPF, DKIM, and bounce records to publish for SAP Emarsys, why the sending domain is always a subdomain, and why both key5 and key6 have to exist.

Verified 2026-08-30 against the official SAP Emarsys documentation.

What you are setting up

SAP Emarsys sends your marketing and triggered email from a dedicated subdomain of your brand, something like email.yourdomain.com, never the apex. You publish an SPF record and two DKIM CNAMEs on that subdomain, plus a CNAME for a bounces subdomain beneath it, so Emarsys signs as you and both SPF and DKIM align. Emarsys can also host the subdomain for you if you delegate it with NS records to its nameservers (such as ns1.emarsys.net); this guide covers the self-managed records, which is what the validation tool checks.

Publish SPF and DKIM

In Emarsys, go to Management > Email Domain Validation, click Add Domain, and enter your sending subdomain and link domain. The DNS Settings step lists the records for your exact names (there is an Export DNS table button). Using email.yourdomain.com as the example, they are:

Type:  TXT     (SPF)
Host:  email.yourdomain.com
Value: v=spf1 include:spf.emarsys.net ~all

Type:  CNAME   (DKIM, first key)
Host:  key5._domainkey.email.yourdomain.com
Value: key5.dkim.emarsys.net

Type:  CNAME   (DKIM, second key)
Host:  key6._domainkey.email.yourdomain.com
Value: key6.dkim.emarsys.net

Type:  CNAME   (bounce / return-path domain)
Host:  bounces.email.yourdomain.com
Value: bounces.emarsys.net

The DKIM records are CNAMEs to keys Emarsys hosts, which is how it rotates 2048-bit keys for you without a DNS change on your side; the validator expects both key5 and key6. The SPF include costs two lookups, because spf.emarsys.net itself includes s.emarsys.net. If you use Emarsys Reply Management to receive replies, add an MX record on the sending subdomain pointing at mx.eemms.net; if you host replies yourself, use your own MX and make sure the mailbox exists and receives every reply. Then click Start validation. For a brand-new sending or link domain, Emarsys enables sending on it only after validation passes, so expect a support step before the first send.

Add DMARC

Emarsys treats DKIM alignment as mandatory and SPF alignment as optional, but start in monitor-only mode and ramp up once your reports are clean. Publish it on the sending subdomain (and on your apex, which covers every subdomain without its own record):

Type:  TXT
Host:  _dmarc.email.yourdomain.com
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Build it with our DMARC builder and progress past p=none when you are ready. Because Emarsys mail aligns on DKIM at the sending subdomain, p=reject is a safe destination for this sender once the reports confirm it; treat it as the destination, not the first step.

The Emarsys gotcha

The bounce domain decides whether SPF aligns. If your account still uses a shared Emarsys bounce domain (a generic name like xpressus.emsmtp.us), SPF passes for Emarsys but does not align to your domain, so only DKIM carries DMARC, and a shared return-path pools your sending reputation with every other sender on it. Publish the bounces.email.yourdomain.com CNAME so the return-path is yours. The second trap is legacy records: setups from before 2022 published a static DKIM TXT key you generated yourself rather than the CNAME pair, and may carry older SPF and MX values. Add the new records alongside the old ones, do not delete the old DKIM record until Emarsys support confirms the switch, and only then remove it. And never put any of this on the apex; Emarsys sends from the subdomain, so the records live there.

Confirm it worked

  • Validate in Emarsys. Each domain on the Email Domain Validation page should show Success, and the Domain and DNS Information view shows BOUNCE, SPF, MX, DKIM, DMARC, and CNAME each as valid.
  • Send a test and read the headers. Send a test campaign to a Gmail address, open Show original, and confirm the DKIM signature shows d=email.yourdomain.com, the return-path is on your bounces subdomain, and you see dmarc=pass. Our header analyzer reads it back plainly.
  • Watch the reports. Emarsys should appear as an aligned, passing source in your DMARC aggregate reports, labeled as a known sender in trustyourinbox, with the subdomain it sends from broken out in the subdomain view.

Let trustyourinbox publish Emarsys for you.

Connect Cloudflare or AWS Route 53 once and the Emarsys records are one click. We email you the exact record, wait five minutes, write it, and read it back from public DNS. Then we keep watching this sender in your DMARC reports and alert you when Emarsys mail starts failing.

Was this page helpful?

Keep reading.

Start with one domain. See it with your own data.

Free for one domain, no card. Add one DNS record and the first reports usually arrive within a day.

  1. Monitoring
  2. Quarantine
  3. Reject