Deliver
Deliverability basics: bulk-sender rules, warming up, list hygiene and bounces
The Gmail and Yahoo bulk-sender rules, one-click unsubscribe, spam complaint rates, warming up a new domain and keeping your list clean.
Updated 7 min read
Deliverability is whether your email reaches the inbox, rather than the spam folder or nowhere at all. It depends partly on technical setup and mostly on behaviour: who you send to, whether they asked for it, and how they react when it arrives. Mailbox providers such as Gmail, Yahoo and Outlook.com watch those reactions closely and adjust where your future mail goes.
In February 2024, Gmail and Yahoo began enforcing a clearer set of rules for senders, with the strictest applying to bulk senders. Most small lists will never reach the bulk threshold, but the rules are a good description of what any responsible sender should be doing anyway. This guide covers those rules, then the everyday habits that keep you out of trouble: warming up, list hygiene and handling bounces.
The 2024 Gmail and Yahoo sender rules
Google publishes its requirements in its email sender guidelines, and Yahoo in its sender best practices. The two are closely aligned. Check the originals from time to time, because both providers update them.
Rules for everyone sending to personal accounts
- Authenticate with SPF or DKIM. At least one must pass for your domain. See SPF, DKIM and DMARC explained.
- Valid forward and reverse DNS for your sending servers. If you use a hosted email service, it handles this. If you send from your own server, the server’s IP address needs a PTR record that matches its hostname.
- Use TLS to encrypt the connection when sending. Again, reputable services do this already.
- Keep spam complaints low. Google asks senders to keep the spam rate reported in Postmaster Tools below 0.1% and to avoid ever reaching 0.3% or higher. Yahoo uses the same 0.3% ceiling.
- Format messages properly, following the internet message standard, and don’t impersonate other domains in the From header.
Extra rules for bulk senders
Google defines a bulk sender as one that sends close to 5,000 or more messages to personal Gmail accounts within 24 hours. Messages from the same primary domain count together, and once you have been treated as a bulk sender, Google says that status is permanent. Bulk senders must also:
- Set up SPF and DKIM, not just one of them.
- Publish a DMARC record, with a policy of at least
p=none. - Align the From domain with either the SPF or DKIM domain, so DMARC passes.
- Offer one-click unsubscribe in marketing and subscribed messages, and process unsubscribes within two days.
- Include a clearly visible unsubscribe link in the message body as well.
Microsoft announced broadly similar requirements for high-volume senders to Outlook.com and its other consumer addresses in 2025. If a meaningful share of your list uses Hotmail, Live or Outlook.com addresses, check Microsoft’s current guidance too.
One-click unsubscribe (RFC 8058)
One-click unsubscribe lets a mail app show its own “Unsubscribe” button next to your message, which removes the reader in a single action without visiting a web page or logging in. It works through two email headers defined in RFC 8058:
List-Unsubscribe: <https://example.co.uk/unsubscribe?u=8f3a2c&l=news>, <mailto:unsubscribe@example.co.uk?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
When the reader presses the button, their mail provider sends an HTTPS POST request to the web address in List-Unsubscribe, with the body List-Unsubscribe=One-Click. Your system must unsubscribe that person on receipt of the request, without asking them to confirm on a page. The URL needs to identify the subscriber (the token in the example), and both headers must be covered by your DKIM signature so they can’t be tampered with.
Hosted email services add these headers for you; check your provider’s documentation to confirm. If you run self-hosted software, check that your version supports RFC 8058 and that your unsubscribe endpoint accepts POST requests. Don’t treat the header as a replacement for the visible link: you need both.
Watching your spam complaint rate
Gmail’s spam rate is the share of your mail to Gmail inboxes that recipients mark as spam. You can see it, along with your domain’s authentication results, in Google Postmaster Tools. Sign in with a Google account, add your sending domain and verify it with a DNS TXT record. Data only appears once you send enough daily volume to Gmail users, so small senders may see little or nothing.
Whatever your size, keep complaints down with the same habits:
- Only email people who signed up, and remind them why they are hearing from you.
- Use a recognisable From name, the same one every time.
- Send at the frequency you promised on the sign-up form.
- Make unsubscribing easy and immediate.
- Stop mailing people who have shown no interest for a long time.
Warming up a new domain or IP
Mailbox providers are wary of a domain they have never seen before that suddenly sends thousands of messages. Warming up means building volume gradually so they can see that recipients welcome your mail.
- Start with your most engaged people: recent sign-ups, recent customers, people who have clicked or replied lately.
- Send small batches first, then increase volume over a few weeks, rather than sending to the whole list on day one.
- Watch bounces, complaints and unsubscribes after each send. If anything spikes, pause and find out why before sending more.
- Keep sending regularly. Long gaps followed by a big send look the same as starting from cold.
On a hosted service you usually share IP addresses with other customers, and the provider manages IP reputation. Your domain reputation is still yours, so a gentle start still matters. If you move to a dedicated IP or run your own server, warming up becomes essential.
Example
A hypothetical craft shop is moving 3,000 subscribers to a new email service on a new sending subdomain. For the first send it mails the 600 people who bought or clicked in the past three months. A few days later it adds the next most recent group, and so on, reaching the whole list after several sends while checking bounce and complaint figures each time.
List hygiene
A clean list is one where nearly everyone is real, reachable and still interested. Untidy lists produce bounces, complaints and spam traps (addresses that mailbox providers use to spot poor list practices).
- Never buy, rent or scrape lists. Apart from the legal problems under PECR and UK GDPR, bought lists are full of stale addresses and people who will report you. See growing a list legally.
- Use double opt-in where you can, so typos and fake addresses never join.
- Catch obvious typos such as
gmial.comorhotmial.co.ukat the form, or fix them on import only with the person’s confirmation. - Be careful with role addresses like
info@,sales@oradmin@. They are often read by several people, none of whom signed up. - Sunset unengaged subscribers. Decide a period after which someone who hasn’t clicked, replied or bought gets a re-engagement email, and stop mailing them if they still don’t respond. The automations guide covers how.
Bounces and suppression
A bounce is a message the receiving server refused or couldn’t deliver. There are two kinds, and they need different treatment.
| Type | Typical causes | What to do |
|---|---|---|
| Hard bounce | The address doesn’t exist, the domain doesn’t exist, or the address has been closed | Stop sending to it immediately and permanently |
| Soft bounce | Mailbox full, server temporarily unavailable, message too large | Retry later; suppress the address if it keeps soft-bouncing over several sends |
Hosted email services suppress hard bounces automatically and usually suppress repeated soft bounces too. Suppression means the address stays in a “do not send” list rather than being deleted, so it can’t be accidentally re-imported. Keep unsubscribes and complaints on that suppression list as well. If you self-host, you need to set up bounce and complaint handling yourself, for example by connecting your sending provider’s notifications to your software. Skipping this is one of the commonest ways self-hosted senders damage their reputation.
A quick deliverability checklist
- SPF and DKIM pass for your domain; DMARC is published and passing.
- One-click unsubscribe headers are present, plus a visible unsubscribe link.
- Your From name and address are consistent and recognisable.
- Everyone on the list signed up, and you can show when and how.
- Hard bounces, complaints and unsubscribes are suppressed automatically.
- Long-term unengaged subscribers are re-engaged or removed.
- You check bounces and complaints after every campaign.
Our pre-send checklist includes these checks alongside the content ones.