Senderward

Email authentication checklist when adding a new sending service

Updated

Every tool that sends mail with your domain in the From: header needs to be set up for your domain before it goes live: a CRM, a helpdesk, a newsletter tool, invoicing, a survey tool. Done in the right order it takes half an hour and breaks nothing. Skipped, the tool's mail fails DMARC from the first message, and a careless SPF change can break the mail you already send.

1. Before you touch DNS

2. DKIM: the step that makes DMARC pass

In the tool, find "domain authentication", "sender authentication" or "DKIM". It gives you one to three records to publish, usually CNAMEs such as s1._domainkey.example.com pointing at the tool, sometimes a TXT record with the key itself.

DKIM with your domain is enough for DMARC to pass, and it survives forwarding. If the tool cannot sign with your domain, its mail cannot pass DMARC as your domain.

Lookproof has setup notes for common tools, for example HubSpot, Mailchimp, Zendesk and SendGrid; the full list is on its guides page.

3. SPF: only if the tool uses your domain as return-path

SPF checks the return-path (envelope sender) domain, not the From: header. Most tools send with their own return-path, such as bounces.example.org, and their SPF record covers that. Then adding the tool's include: to your record does nothing for DMARC and only uses up lookups.

Add an include: only when the tool tells you to set a custom return-path on your domain, or explicitly asks for it. Then:

4. DMARC: no change

Your DMARC record stays as it is. Relaxed alignment is the default, so a tool signing with d=mail.example.com passes for mail from example.com. Do not lower the policy to p=none "for the launch": a temporary p=none tends to stay, and while it is there anyone can send as you.

5. Check the new tool

  1. Send a real message from the tool (not a "test send" from a preview, which some tools send differently) to a mailbox outside your company.
  2. Open the headers and find Authentication-Results. You want dkim=pass with header.d=example.com (or your subdomain) and dmarc=pass. If DKIM passes for another domain, the tool still signs with its own; go back to step 2.
  3. Over the next days, the tool's IPs should appear in your DMARC aggregate reports as a source that passes. If it shows up failing, see Why DMARC reports show sources you don’t recognise.

6. Check that nothing else broke

The new tool working is half the job. The other half is the mail you already sent before the change:

A full check of the domain covers all four at once; the form below runs one.

When you stop using a tool

Once the tool no longer sends, remove its include: from SPF (it costs lookups) and its DKIM records. Do it after the last message, not before: a tool that still sends a reminder or an invoice fails DMARC the day its DKIM record is gone. For DNS changes like these that break mail without any error, see DNS changes that silently break email.

Check your domain

Free email security check by Lookproof. Opens on lookproof.dev.

Senderward checks your domain's DMARC, SPF, DKIM, MX, MTA-STS and TLS-RPT every day and emails you, with the fix, when something gets worse. $7 per domain per month, 14 days free. See pricing

Sources