Bulk email rules for campaigns and nonprofits
Sources reviewed . See sources and review
Year-end appeals and post-election updates can push a team's email volume well above its usual level. Gmail, Yahoo and Outlook each publish requirements for domains that send in volume, and mail that misses them can be filtered to spam or rejected.
This checklist covers what those three mailbox providers say on their own pages. It is not legal advice, and it does not cover CAN-SPAM, state law or campaign finance rules. Your email platform's documentation shows where each setting lives.
Check whether you count as a bulk sender
Gmail treats you as a bulk sender when you send close to 5,000 messages or more to personal Gmail accounts within 24 hours. Mail from subdomains counts toward the same primary domain, so 2,500 messages from yourorg.org and 2,500 from news.yourorg.org add up to 5,000.
Microsoft's rules for Outlook.com apply to domains that send more than 5,000 messages a day to its consumer addresses, such as outlook.com, hotmail.com and live.com. Yahoo says a bulk sender sends a significant volume of mail, and that it will not specify a threshold.
Gmail's rules cover personal Gmail accounts. Its FAQ says they do not apply to messages sent to Google Workspace accounts.
Gmail's FAQ says it began ramping up enforcement in November 2025, and that mail missing the requirements can get temporary or permanent rejections. A list that is small most of the year can cross these lines on one large send. If your biggest planned send could reach that volume, meet the bulk sender requirements before that day.
Sources: Google: Email sender guidelines FAQ; Microsoft Tech Community: Outlook requirements for high-volume senders (updated April 29, 2025); Yahoo Sender Hub: FAQs
Authenticate the domain in your From: address
All three providers ask bulk senders for the same three DNS records. The most important detail is alignment: the domain in your From: header must align with the domain that passes SPF or the domain that signs with DKIM. Gmail compares organizational domains, so mail from news.yourorg.org can align with a DKIM signature from yourorg.org. Gmail and Yahoo list alignment as a bulk sender requirement, and Yahoo says relaxed alignment is acceptable. Microsoft asks for alignment with SPF or DKIM, and preferably both.
If an email service sends for you, its setup steps tell you which records to publish. Gmail's guidance is to confirm that the provider authenticates your domain's mail with SPF and DKIM. Gmail also requires valid forward and reverse DNS for sending IP addresses and a TLS connection. Those belong to the sending servers, so confirm them with your provider.
- SPF lists the servers allowed to send as your domain. Include every service that sends as you, such as your email platform, your donation tool and your office mail. Microsoft notes that an SPF record needing more than 10 DNS lookups can fail.
- DKIM adds a signature that shows the message came from your domain and was not changed. Gmail requires a key of at least 1024 bits and recommends 2048. Yahoo also asks for at least 1024 bits.
- DMARC publishes a policy for mail that fails SPF and DKIM. Gmail, Yahoo and Outlook each accept p=none as the minimum policy for bulk senders. DMARC reports show who is sending as your domain.
Sources: Google: Email sender guidelines; Google: Email sender guidelines FAQ; Yahoo Sender Hub: Sender requirements and recommendations; Microsoft Tech Community: Outlook requirements for high-volume senders (updated April 29, 2025)
Add one-click unsubscribe to appeals and newsletters
Gmail and Yahoo require bulk senders to support one-click unsubscribe for marketing and subscribed messages. Gmail's FAQ excludes transactional messages, such as password resets and form submission confirmations. It also says recipients, not Google, decide what kind of message they received.
For a campaign or nonprofit, fundraising appeals, newsletters and action alerts belong on the subscribed side. A donation receipt is closer to a transactional message. Gmail's guidelines say not to mix the two, for example by adding a promotion to a receipt.
Both providers also ask for a clearly visible unsubscribe link in the message body. That link may lead to a preferences page, as long as the headers handle the one-click part.
Process requests quickly. Yahoo asks for 2 days. Gmail recommends 48 hours, and it lists requests not honored within 48 hours among the issues that make a sender ineligible for its delivery support.
One-click unsubscribe removes the person from the list tied to that message, not from everything you send. Decide which list each send belongs to, and make sure an unsubscribe reaches every tool that sends to that list.
What the headers need
RFC 8058 defines the one-click method. Gmail requires it. Yahoo highly recommends it and also accepts a mailto: unsubscribe, so the RFC 8058 setup meets both. If an email platform sends for you, check its output on a test message against this list.
- List-Unsubscribe contains one HTTPS address. It may also contain a mailto: address, but Gmail says mailto alone does not meet its requirement.
- List-Unsubscribe-Post contains exactly List-Unsubscribe=One-Click.
- The HTTPS address removes the recipient when the mailbox provider sends a POST request to it. A link to a landing or preferences page does not count, and the standard says the sender must not answer that POST with a redirect.
- A valid DKIM signature covers both headers.
Sources: Google: Email sender guidelines; Google: Email sender guidelines FAQ; Yahoo Sender Hub: Sender requirements and recommendations; IETF RFC 8058: Signaling One-Click Functionality for List Email Headers
Keep the spam complaint rate under 0.3%
Gmail and Yahoo both set 0.3% as the limit for spam complaints. Gmail recommends staying below 0.1% and never reaching 0.3%, and it measures the rate in Postmaster Tools. Above 0.3%, a bulk sender is not eligible for Gmail's delivery support.
As arithmetic, 0.3% is 3 reports for every 1,000 messages. Each provider measures the rate its own way. Gmail calculates it daily, and Yahoo bases it on mail delivered to the inbox, so a count from your own platform will not match their figures exactly.
Gmail's guidelines say Google does not track open rates, and that low open rates are not necessarily a sign of a delivery problem. Use the spam rate and authentication results in Postmaster Tools instead.
These practices from the providers' pages keep complaints down:
- Send only to people who signed up to hear from you. Gmail says not to buy email addresses.
- Confirm new addresses, and remove addresses that bounce repeatedly.
- Keep the frequency people signed up for. Yahoo says not to start sending daily email to a weekly or monthly list.
- Raise volume in steps, starting with engaged recipients. Gmail warns that suddenly doubling volume can lead to rate limiting or a drop in reputation.
Sources: Google: Email sender guidelines; Google: Email sender guidelines FAQ; Yahoo Sender Hub: Sender requirements and recommendations
Read the bounces that point to setup problems
When a provider rejects mail for a setup reason, the bounce usually says so. These codes come from the providers' own pages. Your email platform's bounce report should show them.
| Code | Provider | What the provider says it means |
|---|---|---|
| 5.7.26 | Gmail | The message was not authenticated with SPF or DKIM as required. |
| 4.7.28 | Gmail | The sending quota was exceeded. Gmail says to stop for at least 10 minutes, then resume on one connection. |
| 550 5.7.515 | Outlook.com | The sending domain does not meet the required authentication level. |
Sources: Google: Email sender guidelines; Microsoft Tech Community: Outlook requirements for high-volume senders (updated April 29, 2025)
Check these before a large send
Go through this list with whoever manages your domain and your email platform. Each line comes from a requirement or recommendation above.
- Every service that sends as your domain is in your SPF record, and the record stays within 10 DNS lookups.
- DKIM signs with your domain, using a key of at least 1024 bits.
- A DMARC record is published with at least p=none, and its reports go to an address someone reads.
- The From: domain aligns with SPF or DKIM.
- Appeals and newsletters carry the List-Unsubscribe and List-Unsubscribe-Post headers that Gmail requires, plus a visible unsubscribe link in the body.
- A test unsubscribe removes the address within 2 days in every tool that sends to that list.
- Postmaster Tools shows a spam rate below 0.1% for recent sends.
- The send goes only to people who signed up, with repeat bounces removed.
- Volume rises in steps instead of doubling overnight.
Sources: Google: Email sender guidelines; Google: Email sender guidelines FAQ; Yahoo Sender Hub: Sender requirements and recommendations; Microsoft Tech Community: Outlook requirements for high-volume senders (updated April 29, 2025); IETF RFC 8058: Signaling One-Click Functionality for List Email Headers
Write down who owns the setup
Record where each DNS record lives, who can change it and which services send as your domain. Keep that note with your other account records, so the next person does not rebuild it the week of a deadline. The staff handoff checklist covers account owners and access when staff change, and the texting guide covers consent and opt-outs for text messages.
Sources and review
Requirements as published by each mailbox provider and the IETF. Providers change these rules, so check their pages before relying on a specific number or date.
Sources checked .
- Google: Email sender guidelines
- Google: Email sender guidelines FAQ
- Yahoo Sender Hub: Sender requirements and recommendations
- Yahoo Sender Hub: FAQs
- Microsoft Tech Community: Outlook requirements for high-volume senders (updated April 29, 2025)
- IETF RFC 8058: Signaling One-Click Functionality for List Email Headers