Connfig

SPF, DKIM and DMARC for Cold Email: A Setup Checklist

Connfig TeamOctober 27, 2026deliverabilitycold-outreachguides
An email envelope passes three checkpoints marked with a server, a signature seal and a shield, then lands in an inbox tray

TL;DR: Mailbox providers check three DNS records before they trust a cold email. SPF says which servers may send your mail, DKIM signs each message, and DMARC decides what happens when those checks fail. Put all three on a separate sending subdomain, start DMARC at p=none and keep your spam complaint rate under 0.3%.

SPF, DKIM and DMARC are DNS records that prove an email really comes from the domain in its From line. SPF (Sender Policy Framework) lists the servers allowed to send for a domain. DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every message. DMARC (Domain-based Message Authentication, Reporting and Conformance) tells the receiving server what to do when SPF or DKIM fails, and sends you reports about it. For cold email, these three records decide whether a message lands in the inbox, in spam or nowhere.

What Gmail and Outlook require in 2026

Google's email sender guidelines have applied since February 2024. Every sender to Gmail needs SPF or DKIM and a spam rate below 0.3% in Postmaster Tools. Anyone sending more than 5,000 messages a day to Gmail accounts needs all three records, with the From domain aligned to SPF or DKIM, and a policy of p=none is enough. In November 2025 Google added that it was ramping up enforcement, with temporary and permanent rejections for mail that breaks these rules (Spam Resource).

Microsoft applies the same idea to Outlook.com, Hotmail and Live addresses. Domains sending more than 5,000 messages a day must pass SPF and DKIM and publish DMARC. Mail that fails goes to Junk and can be rejected with the error 550 5.7.515.

A cold campaign rarely sends 5,000 emails a day from one address. The rules still apply to you in practice, because a new sender has no reputation yet and authentication is the first trust signal a mailbox provider can check.

What each record proves

RecordWhat it provesWhere it livesExample value
SPFThe sending server may send for the domainTXT on the sending domainv=spf1 include:_spf.example.net ~all
DKIMThe domain signed the message and nobody changed it on the wayTXT at selector._domainkey.yourdomainv=DKIM1; k=rsa; p=MIIB…
DMARCWhat to do when SPF or DKIM fails, and where to send reportsTXT at _dmarc.yourdomainv=DMARC1; p=none; rua=mailto:dmarc@yourdomain

Your sending tool generates the SPF include and the DKIM key. Your job is to paste them into your DNS provider exactly as shown.

Why cold email belongs on a subdomain

Your main domain carries invoices, password resets and your team's daily mail. If a cold campaign draws complaints, you want that damage contained. A subdomain such as mail.yourcompany.com still shows your brand to the recipient, and it gives outreach a sending history of its own.

Each subdomain needs its own SPF and DKIM records. The third record behaves differently. Under RFC 7489, a subdomain without its own record falls back to the main domain's policy. If the main domain is already at p=reject, publish a separate _dmarc record for the subdomain while you test it.

How to set up SPF, DKIM and DMARC in seven steps

  1. Choose the sending subdomain. mail., go. and team. are common choices.
  2. Add one SPF record. A domain may publish only one, and SPF allows at most 10 DNS lookups (RFC 7208). Past either limit the check returns a permanent error and fails.
  3. Add the DKIM record exactly as your sending tool shows it, including the selector in the host name.
  4. Add DMARC at _dmarc. with p=none and a rua address for reports. Move to p=quarantine once a few weeks of reports show only your own senders passing.
  5. Send a test to a Gmail address. Open it, choose "Show original" and check that all three say PASS.
  6. Warm up slowly. Start with a few dozen emails a day and raise the volume while replies come in and complaints stay near zero.
  7. Watch the complaint rate in Google Postmaster Tools. Google's limit is 0.3%, so plan to stay well below it.

Mistakes that break authentication

  • Two SPF records on one host. Receivers treat this as a permanent error. Merge them into a single record.
  • Too many includes. Every CRM, help desk and newsletter tool adds lookups. Remove the ones you stopped using.
  • Copying the main domain's policy to a fresh subdomain. A strict policy on day one pushes legitimate mail to spam while you are still fixing records.
  • A From address on another domain than the one in the signature. DMARC passes only when those domains align.

How Connfig sets this up

In Connfig you add a sending domain on the Profile page, and if you type a root domain the form suggests a mail. subdomain. The DNS dialog lists the SPF, DKIM, MX and DMARC records to copy, and campaigns can use it after you press Verify. New domains start at 20 emails a day and move to 50 and then 100 as their total sends grow, with a random 60 to 180 second pause between sends. Every campaign email carries an unsubscribe link, and an address that opts out is suppressed in all of your workspaces. The sending domains guide has the details.

FAQ

Do I need DMARC if I send fewer than 5,000 emails a day?

Google requires only SPF or DKIM below that volume. Publish DMARC anyway. A p=none record only monitors, so it cannot block your own mail, and its reports show who is sending in your name.

How long do DNS changes take?

Often a few minutes and sometimes several hours, depending on your DNS provider's TTL. If verification fails, wait and check again before you edit the records.

Will authentication alone keep me out of spam?

It proves who you are. Your list and your message decide the rest, and our guide to cold emails that get replies covers the writing side.

To get these records generated for you, add a sending domain in Connfig and follow the DNS dialog.

Connfig'i ücretsiz deneyin

Lead bulma, CRM ve e-posta kampanyalarını tek platformda toplayın. Kart bilgisi gerekmez.

Ücretsiz Başla

Related Posts