Key facts
- SPF says which servers may send as your domain.
- DKIM adds a signature that proves the message was not changed.
- Start with p=none so nothing is blocked while you check the reports, then move to quarantine once every service you send from passes.
- Buzz Send sends from sending domains and mailboxes set up in Buzzlist.
What does each record do?
SPF says which servers may send as your domain. Source: RFC 7208 DKIM adds a signature that proves the message was not changed. Source: Microsoft DMARC ties them together, tells inboxes whether to accept, quarantine or reject failures, and can send you reports. Source: RFC 7489
What DMARC policy should I start with?
Start with p=none so nothing is blocked while you check the reports, then move to quarantine once every service you send from passes. Source: RFC 7489
How does Buzzlist handle this?
Buzz Send sends from sending domains and mailboxes set up in Buzzlist. They are a separate recurring purchase on every plan, so the domain, the mailboxes and the sending live in one place.
| Record | What it does | Where it lives |
|---|---|---|
| SPF | Lists who may send for the domain | TXT record on the domain |
| DKIM | Signs each email | TXT record at a selector |
| DMARC | Sets the policy for failures | TXT record at _dmarc |
How to add the records yourself
- Find your sending service's values
Each provider publishes its SPF include and DKIM key.
- Add one SPF record
Only one per domain. Combine every sender into it.
- Add DKIM
Paste the key your provider gives you at the selector it names.
- Add DMARC
Start with p=none and a reporting address, then tighten.
When does Buzzlist fit, and when does it not?
It fits when
- You want sending domains and mailboxes set up in the same tool that sends.
- You want sending limits enforced for you.
It does not fit when
- You must send cold email from your main company domain. A separate sending domain is the safer choice.
Questions people ask next
Can I have two SPF records?
No. Two SPF records on one domain make SPF fail. Source: RFC 7208 Merge them into one.
Do these records stop spam folder placement on their own?
No. You need all three before you send. Volume, bounces and the email itself still matter.
Do I need these on a separate sending domain too?
Yes. Every domain you send from needs its own records. Source: Microsoft
Sources
- Google Workspace Admin Help: Email sender guidelines
- Yahoo Sender Hub: Sender best practices
- Outlook.com Postmaster: high-volume sender requirements
- RFC 7208: Sender Policy Framework (SPF)
- Microsoft Learn: How email authentication works
- RFC 7489: DMARC
Checked October 9, 2026. Rules change, so read the source before you rely on it. This is general information, not legal advice.