Bounce rate and spam rate limits: what Gmail and Yahoo require

Mailbox providers now publish rules for people who send in volume. This guide separates what the official pages say from folklore, explains how bounces and complaints differ, and shows where list verification helps.

CheckMX guide · Published October 27, 2026 · Requirements change, so confirm them on the official pages linked below.

What the official pages say

Google publishes its email sender guidelines and a sender FAQ. Yahoo publishes its sender best practices. Those pages are the source of truth. Here is what we take from Google’s pages, kept to what they state:

• Bulk senders are defined by volume. Google treats a sender as a bulk sender when it sends about 5,000 or more messages a day to Gmail addresses.
• Authentication is required. Bulk senders need SPF, DKIM and DMARC set up for the sending domain.
• One-click unsubscribe. Marketing and subscribed messages need one-click unsubscribe, following RFC 8058, and unsubscribe requests should be processed within two days.
• Keep the spam rate low. Google asks senders to keep the spam rate reported in Postmaster Tools below 0.3%, and to aim for under 0.1%.

For Yahoo we point you to its best-practices page instead of paraphrasing numbers. Do not assume Yahoo’s requirements match Google’s line for line, and read both. Either provider can change its rules, and your own sending platform may impose stricter limits of its own.

Bounce rate and spam rate are different things

People often use “bounce rate limits” and “spam rate limits” as if they were one thing. They measure different problems.

• A bounce means a message was refused. A hard bounce is a permanent failure, for example an address that does not exist. A soft bounce is temporary, such as a full mailbox or a server that is down. Hard bounces tell you the address was bad.
• A spam complaint means a recipient who did receive your message marked it as spam. That is the signal Google’s 0.3% figure describes, measured through Postmaster Tools.

The pages we cite give a spam-rate figure. We have not taken a bounce-rate target from them, so we will not invent one. Many sending platforms set their own bounce thresholds and may pause an account that exceeds them, so read your platform’s policy. A bounce still matters because it is a visible sign that you are sending to addresses you did not check. Receiving servers notice patterns of sending to nonexistent recipients, and your sender reputation can suffer.

Why a clean list protects your reputation

Verification cannot remove complaints, but it removes one source of damage: sending to addresses that cannot receive mail. Before a campaign, a verifier can check syntax, look up mail records and ask the receiving server whether it accepts the recipient. Addresses that fail those checks should not go into a send.

Be realistic about what it cannot do. A server may accept an address and still bounce, filter or discard your real message later. Catch-all domains accept everything, so the verifier can only mark them risky (see catch-all emails). And verification says nothing about whether the person wants to hear from you. Complaints come from the message and the audience, so a perfectly valid address can still produce a spam report.

A pre-send checklist

1. Authenticate the domain. Check your records with the SPF checker, DKIM checker and DMARC checker. Authentication is required for bulk senders and is good practice at any volume.
2. Verify the list. Run the whole list through verification and separate confirmed, risky, invalid and unknown results. Drop the invalid ones and handle risky ones separately.
3. Make unsubscribing easy. Provide an unsubscribe method that works, and honor requests promptly. Google asks for one-click unsubscribe and processing within two days for subscribed messages.
4. Watch the signals. If you send to Gmail users, use Google Postmaster Tools to see your reported spam rate, and compare it with the 0.3% limit and the 0.1% aim.
5. Check blocklists when something goes wrong. The blacklist checker helps you investigate a listing, but a clean result is not a guarantee of inbox placement.
6. Send in steps. Start small and increase volume only while bounces and complaints stay low.

What to do if your numbers rise

If bounces climb, pause and look at where the list came from. Old lists, purchased lists and addresses guessed from name patterns are the usual causes. Re-verify, remove the failures and resume with a smaller batch. If the spam rate climbs, the problem is relevance and expectation: check who you are sending to, what you promised them, whether your subject line matches the message and whether the unsubscribe link is easy to find. Do not hide the unsubscribe option; that tends to turn opt-outs into spam reports.

Only email people where you have a valid basis to do so. Laws such as CAN-SPAM in the United States set their own requirements, including a way to opt out, and other countries differ. The sending setup guide covers the basics and links to the FTC’s guidance. This page is educational information, not legal advice or a deliverability guarantee.

Where CheckMX fits

CheckMX checks single addresses and bulk CSV files of up to 10,000 unique addresses and gives each a verdict and reason. You can reach it through API keys, the CLI, MCP and webhooks. Every plan, including the free Sandbox, comes with email checks. Next, read the cold email domain setup checklist.

Frequently asked questions