How to set up SPF, DKIM and DMARC for your newsletter
The three DNS records that decide whether your chamber or association newsletter reaches the inbox, explained in plain English, with the exact steps to add them.
By Mike Andersen · Updated October 2026
SPF, DKIM and DMARC are three short text records you add to your domain’s DNS settings. Together they prove to Gmail, Yahoo and Outlook that your newsletter really came from your organization. Without them, a chamber or association newsletter is far more likely to land in spam, or not arrive at all. Setting them up takes about half an hour, once, and mostly means copying values from your email provider into your domain settings.
Mike Andersen, who builds every Purple Pushpin site, sets these records up for organizations that send email from their own domain. Here’s the plain-English version.
What each record does
| Record | What it says | Plain-English version |
|---|---|---|
| SPF | Which services are allowed to send email for your domain | The guest list |
| DKIM | A digital signature on every message, checked against a key in your DNS | The wax seal on the envelope |
| DMARC | What inboxes should do with mail that fails SPF and DKIM, and where to send reports | The instructions for the doorman |
Why this matters now
Since February 2024, Google requires everyone sending to Gmail addresses to set up SPF or DKIM. Anyone sending more than 5,000 messages a day to Gmail addresses must have SPF, DKIM and DMARC, keep spam complaints below 0.3%, and offer one-click unsubscribe. Yahoo introduced similar rules at the same time, and since May 2025 Outlook sends mail from high-volume domains without these records to the junk folder.
A chamber with 9,000 contacts sending one newsletter can cross the 5,000-a-day line in a single send. Even below it, authenticated mail is simply more trusted.
Before you start
- Find where your DNS lives. Usually your domain registrar (GoDaddy, Namecheap, Squarespace Domains and so on) or your web host. That’s where you’ll paste the records.
- List everything that sends email as your domain. Your Google Workspace or Microsoft 365 mailbox, your newsletter tool, your website’s confirmation emails, your invoicing tool. Each one needs to be covered.
- Get the values from each provider. Every email service has a “domain authentication” or “verify your domain” page that gives you the exact records to add.
Step 1: Set up SPF
SPF is one TXT record on your main domain. It lists the services allowed to send for you. An organization that uses Google Workspace for mailboxes might have:
v=spf1 include:_spf.google.com ~all
If you add a newsletter service, its include goes in the same record, before the ending:
v=spf1 include:_spf.google.com include:your-newsletter-provider ~all
- Only one SPF record per domain. Two separate SPF records is a common mistake and breaks both. Combine them into one.
- Use the exact include your provider gives you. Don’t guess.
- Keep it short. SPF allows only 10 lookups, so remove services you no longer use.
Step 2: Set up DKIM
Each sending service gives you its own DKIM record, usually a TXT or CNAME record with a name like selector._domainkey. You add one for each service. Then turn on signing inside the service if it asks you to. Google recommends a 2048-bit key where you have the choice.
Step 3: Set up DMARC
DMARC is one TXT record named _dmarc. Start in monitoring mode:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.org
- p=none means “don’t block anything yet, just report.” It meets Google’s requirement for bulk senders.
- rua is where daily reports go. Use a mailbox someone checks, or a free DMARC report reader.
- After a few weeks of clean reports, move to
p=quarantine, which sends failing mail to spam. That’s what protects your members from people pretending to be you.
Step 4: Check your work
- Wait an hour or so for DNS changes to spread.
- Send a test newsletter to a Gmail address. Open it, choose “Show original,” and look for SPF, DKIM and DMARC all marked PASS.
- Check your newsletter tool’s domain page shows the domain as verified.
Common mistakes
- Sending from a free Gmail or Yahoo address through a newsletter tool. You can’t authenticate a domain you don’t own, so send from your organization’s domain.
- Two SPF records instead of one.
- Forgetting a sender, such as the website’s registration confirmations.
- Jumping straight to
p=rejectbefore you know everything that sends for you. - Deleting records during a website or email move. Write them down before you change anything.
Frequently asked questions
Do I need SPF, DKIM and DMARC for a small newsletter?
Google requires SPF or DKIM from every sender, and all three once you send more than 5,000 messages a day to Gmail addresses. Even for a small list, all three improve delivery and stop others from sending email that looks like it came from you.
Where do I add SPF and DKIM records?
In the DNS settings wherever your domain is managed, usually your registrar or web host.
What is the difference between SPF and DKIM?
SPF lists which services may send for your domain. DKIM signs each message so the receiver can check it wasn’t changed and really came from you.
What DMARC policy should I start with?
Start with p=none to collect reports, then move to p=quarantine once you’re confident every legitimate sender passes.
Where Purple Pushpin fits
Purple Pushpin email sends newsletters and registration confirmations from your organization’s own domain and address, not ours. We add these records for you when we connect email to your site, so there’s nothing for your board to set up and your newsletter arrives where it should.
See it for yourself
Click around a real one.
The Purple Pushpin demo is a complete fictional chamber and association. Log in to the admin side your board would use, no sales call needed.