DMARC for nonprofits: SPF, DKIM, and the Gmail and Yahoo rules
November 3, 2026 · 7 min read
The year-end appeal went out on time, and a week later a board member mentioned she'd found it in her spam folder. Or someone at a conference said Gmail and Yahoo "require DMARC now," and you wrote it down to look up later. Most of what's written about DMARC for nonprofits assumes you have an IT department. You probably have a website someone built a few years ago, an email platform for appeals, and a domain registered under somebody's personal account.
What SPF, DKIM, and DMARC actually do
All three are short lines of text published in your domain's DNS settings, the same place that points your web address at your website. Receiving mail servers look them up when a message arrives claiming to be from you.
SPF is a list of who is allowed to send email as your domain: your staff mailboxes, your email platform, your donation software. Mail from a server that isn't on the list looks suspicious.
DKIM is a signature. The service sending your mail signs each message, and the key to check that signature is published in your DNS, so the receiving server can confirm the message came from someone you authorized.
DMARC is the instruction for what to do when a message fails. It tells the receiving server whether to deliver it anyway, send it to spam, or refuse it, and where to send reports about what it saw. It sits on top of the other two and checks one thing they don't: that the domain in the From line, the one your donors actually see, matches the domain that passed SPF or DKIM.
That last check is the one to watch with appeals. An appeal sent through an email platform can pass SPF and DKIM on the platform's own domain while saying it's from yours. It may still be delivered, but nothing in it proves it came from you.
What Google and Yahoo started requiring
Google's email sender guidelines set two tiers, in effect since February 2024. Everyone sending to personal Gmail addresses has to set up SPF or DKIM, send over an encrypted connection, have valid DNS records for their sending servers, and keep the spam rate shown in Google's Postmaster Tools under 0.3 percent.
Senders who reach about 5,000 messages to personal Gmail accounts in a 24-hour period have to do more: both SPF and DKIM, a DMARC record (Google says its policy can be none), a From domain that lines up with one of them, and one-click unsubscribe on marketing mail. Google's FAQ adds two details that catch small senders out. Mail from the same primary domain counts together, and a sender who crosses the line once is "permanently considered" a bulk sender. Since November 2025, Google says, it has been ramping up enforcement, including rejecting mail that doesn't comply.
Yahoo's sender requirements follow the same shape. All senders need SPF or DKIM at a minimum and a spam rate under 0.3 percent. Bulk senders need both, plus a DMARC policy of at least p=none that passes, and they have to honor unsubscribes within two days. What Yahoo won't give is a number. Its FAQ says, "We will not specify a volume threshold."
DMARC for nonprofits that aren't bulk senders
Most small nonprofits will never send 5,000 messages to Gmail in a day. That doesn't put you outside the rules. You're already held to SPF or DKIM, and you can't know you're under Yahoo's bulk line when Yahoo won't say where it is.
Your busiest day also isn't your typical one. Invented example: a land trust with 6,000 personal Gmail addresses on its list sends its December 31 appeal in one batch. By Google's definition it became a bulk sender that afternoon, and it stays one.
The best reason has nothing to do with volume. The scams that reach small organizations are ordinary ones: an email "from" the executive director asking the bookkeeper to pay an invoice today, or a fake appeal to your donors with a different donate link. Without DMARC, inboxes have no instruction from you about mail that uses your domain and didn't come from you. A policy of none won't stop it, but the reports show it's happening, and none is the setting you later tighten to quarantine or reject, which is what Yahoo tells a spoofed domain to do.
For a sense of where other organizations are, the email benchmarks track how many nonprofits in the gallery have their DMARC policy turned on, meaning set past none.
How to check what you have
You don't need to read DNS records to get a first answer. Send an appeal from your email platform to a personal Gmail address, open it, and click the small arrow under the sender's name. Google says an authenticated message shows a "mailed by" line and a "signed by" line with the sending domain. If "signed by" shows your own domain, DKIM is working for that platform. If it shows the platform's domain, or isn't there at all, it isn't.
Do the same with a donation receipt and a message from a staff mailbox, since each goes out through a different service. Then find the domain authentication page in your email platform's settings and see whether it calls your domain verified.
Getting set up, step by step
You'll need someone with admin access to your email platform and someone who can edit your domain's DNS. At a small organization that's often the same person.
- List everything that sends email as your domain. An invented but typical list: Google Workspace for staff, a newsletter platform, a donation form that sends receipts, and an event tool somebody signed up for two years ago.
- Find out who controls your DNS. It lives wherever your domain is registered or hosted. If the login belongs to a former volunteer or a web designer you no longer work with, fix that first and put the account in the organization's name. If nobody nearby has done this before, the National Council of Nonprofits' page on cybersecurity for nonprofits notes that your state association of nonprofits may offer workshops and know people who can help.
- Turn on domain authentication in each sending service. The platform will give you a few records to add. Your DNS person adds them, and the platform tells you when it can see them.
- Keep SPF to one record. Google's troubleshooting guide says "each domain can have only one SPF record," and that a second one can land your mail in spam. When a service asks you to add SPF, add it to the record you already have.
- Wait two days. Google suggests allowing 48 hours after setting up SPF and DKIM before adding DMARC.
- Publish DMARC at p=none. It's one TXT record at
_dmarcin front of your domain, along the lines ofv=DMARC1; p=none; rua=mailto:dmarc@yourdomain.org. Google describes none as "take no action on the message and deliver it to the intended recipient," so DMARC itself won't block anything you send. The rua address is where reports go. Google recommends a dedicated mailbox, not a person's inbox. - Read the reports, then tighten. They're machine-generated, and there are services that turn them into a readable summary. You're looking for every legitimate sender on your list passing. Once they do, move to p=quarantine, which sends failing mail to spam, and later to p=reject. Google sets no timetable. Moving too soon sends your own receipts to spam. Never moving leaves the spoofing problem where it was.
If you'd like the outside view first, the website scan looks up your domain's public records and reports whether you have an SPF record, whether you have a DMARC record and what its policy is, and, when it can tell, who hosts your mailboxes. It doesn't check DKIM, which can't be reliably found from outside, so the Gmail check above is still how you confirm that one. It's free, with nothing to set up.
None of this guarantees an appeal reaches the inbox. Plenty else goes into that, including how many people mark your mail as spam. What it settles is whether your domain says, in public, who is allowed to speak for it. Usually that comes down to a handful of records and a login nobody has looked at in years.