Skip to content

Email deliverability for online stores: SPF, DKIM, DMARC and the spam-rate line

email marketingdeliverabilitywoocommerce

You send the season's first big newsletter to 8,000 customers. The next morning, orders look like any other Tuesday, and a friend with a Gmail address finds your email in Spam. The offer was fine. What failed was trust: the mailbox providers couldn't confirm the email really came from your shop, some addresses were years old and bounced, and a few people who had forgotten signing up pressed "Report spam".

Email deliverability is whether your email reaches the inbox, not just the server. For an online store it comes down to three things you control: proving the email is yours (SPF, DKIM and DMARC), keeping complaints under the line Gmail and Yahoo draw, and keeping your list clean. This guide covers each with a shop example, then how to warm up a new sending domain and what to measure now that open rates mean little.

If you'd rather have the sending side handled for you, MailPilot is our email marketing for WooCommerce; the last section shows what it does.

SPF, DKIM and DMARC for a shop domain

Three DNS records tell mailbox providers that an email from news@example.com really comes from you. Here they are for a shop at example.com that sends its newsletters through an email service:

example.com.                TXT  "v=spf1 mx include:spf.mailservice.example ~all"
s1._domainkey.example.com.  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh...IDAQAB"
_dmarc.example.com.         TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
  • SPF (RFC 7208) lists the servers allowed to send mail for the domain: here your own mail servers (mx) and your email service (include:). ~all says anything else is probably not you (a "softfail"), -all that it definitely isn't. A domain may publish only one SPF record, since a second one makes the check fail, and the record may cause at most 10 DNS lookups.
  • DKIM (RFC 6376) signs every message. Your email service signs with a private key; the public key sits in DNS under a selector (s1._domainkey), and the receiver checks that the message wasn't altered and which domain signed it.
  • DMARC (RFC 9989, which replaced RFC 7489 in May 2026) tells receivers what to do with mail that fails, and where to send reports. p=none changes nothing and collects reports; p=quarantine marks failing mail as suspicious and p=reject as not valid, and receivers that honour either keep that mail out of the inbox.

Alignment: where shops get caught

DMARC passes only when SPF or DKIM passes for the domain the customer sees in the From line. That's alignment. In the default "relaxed" mode the two must share the same organisational domain, so bounce.example.com aligns with example.com. Two common failures:

  • Your email service signs with its own domain (d=mailservice.example). DKIM passes, but for their domain, so it doesn't count for yours.
  • SPF checks the envelope sender, the return path where bounces go, not the From line. If that address is on the service's domain, SPF passes for them, not for you.

The fix: have the service sign with your domain, and ideally use a return-path subdomain of yours, such as bounce.example.com. Then start DMARC at p=none, read the reports for a few weeks, and move to quarantine and reject once all your real mail passes. Microsoft's sender FAQ recommends the same order.

Gmail, Yahoo and Outlook.com rules

Since February 2024, Gmail and Yahoo require every sender to authenticate, and bulk senders to do more. Outlook.com followed in May 2025 for domains sending more than 5,000 emails a day.

GmailYahooOutlook.com
Stricter rules apply toSenders of about 5,000+ messages a day to personal Gmail accountsBulk sendersDomains sending over 5,000 a day
SPF and DKIMBothBothBoth must pass
DMARCPublished, p=none is enough, aligned with SPF or DKIMAt least p=none, must pass; relaxed alignment is fineAt least p=none, aligned with SPF or DKIM
UnsubscribeOne-click (RFC 8058) plus a visible link; honour within 48 hoursList-Unsubscribe header, RFC 8058 recommended; honour within 2 daysA working, visible link recommended
Spam rateBelow 0.3%, ideally below 0.1%Below 0.3%—

Below the bulk line, Gmail still asks every sender for SPF or DKIM, valid forward and reverse DNS for the sending servers, TLS, and a spam rate below 0.3%. Google counts everything sent from the same primary domain, and a sender that crosses the bulk line once stays a bulk sender for good. Since November 2025 Gmail has been stepping up enforcement, with temporary and permanent rejections for mail that doesn't comply. Outlook.com rejects failing mail with the error "550 5.7.515".

Sources: Google's Email sender guidelines and FAQ, Yahoo's Sender Best Practices, and Microsoft's requirements for high-volume senders.

A small shop should meet the bulk rules from the start anyway: one Black Friday campaign can cross the line.

The spam-rate line

In Postmaster Tools, Gmail's spam rate is the share of your messages delivered to the inbox that recipients then mark as spam (dashboards). 0.3% is three complaints per 1,000 delivered; 0.1% is one. Google asks you to stay below 0.1% and never reach 0.3%.

Complaints are harder to see than they sound:

  • Gmail doesn't tell you who complained. Its feedback loop gives aggregate rates per campaign identifier. Yahoo's Complaint Feedback Loop and Outlook.com's Junk Mail Reporting Program, by contrast, send reports back to the sender.
  • Your email service counts only what it hears. Amazon SES, for example, calculates the complaint rate only on mail sent to providers that report complaints, reviews an account from 0.1% and may pause its sending at 0.5% (SES FAQ).

Suppress anyone who complains at once, then look for the cause: a sign-up that promised one thing and emails that deliver another, too many emails, or an unsubscribe link that's hard to find. The one-click unsubscribe standard (RFC 8058) says it plainly: when unsubscribing is too difficult, people report the mail as junk instead.

Bounces: hard, soft, and why to suppress

A hard bounce is a permanent failure: the address doesn't exist or the domain takes no mail. In SMTP these are 5xx replies, which the sender should not simply repeat (RFC 5321). A soft bounce is temporary (4xx): a full mailbox, a busy server.

  • Suppress a hard bounce after the first one. Sending to it again only raises your bounce rate.
  • Retry soft bounces, and stop when the same address keeps failing.

Bounce rates are watched too. Amazon SES recommends staying below 2% hard bounces, reviews accounts at 5% and may pause them at 10%. And addresses left bouncing for a long time can be turned into spam traps, which providers and anti-spam organisations use to spot questionable senders.

List hygiene for an online store

  • Email only people who may be emailed: explicit consent or a valid soft opt-in. Our guide to soft opt-in and email consent explains who qualifies.
  • Never email made-up addresses. Phone and point-of-sale (POS) orders can carry placeholders typed by staff. They bounce, or land on someone who never bought. If your POS and online store share one system (see syncing stock with a physical store), keep those orders out of your marketing list.
  • Sunset unengaged contacts. Pick a window, for example no click and no order in 12 months, and stop sending. Amazon's advice is similar: consider removing people who haven't engaged in several months.
  • Confirm new sign-ups. A confirmation email keeps typos and fake addresses out.
  • Make leaving easy: one-click unsubscribe in the header and a visible link in the footer.

Warming up a new sending domain

A domain or tool with no sending history has no reputation yet. Google's guidelines say to increase volume slowly, starting with a low volume to engaged users and avoiding sudden spikes. For a shop moving to a new tool:

  1. Send first to the people most likely to want your email: recent buyers and recent clickers.
  2. Widen the audience step by step over a few weeks, older contacts last.
  3. After each step, check bounces, complaints and Postmaster Tools; hold back if they rise.

Don't start a new domain with your biggest campaign of the year.

Why open rates stopped meaning much

Since iOS 15 in September 2021, Apple's Mail Privacy Protection "prevents senders from learning whether an email has been opened" (Apple). For people who use it, Apple Mail downloads remote content in the background, whether or not they read the email (Apple), so a tracking pixel can load for an email nobody opened. Open rates are inflated by an amount you can't know, and anything built on opens (A/B winners, "engaged" segments, sunset rules) inherits the error.

Watch what people do instead:

  • Clicks, minus the ones machines make: anti-spam software fetches some links on its own, which is partly why RFC 8058 exists.
  • Orders placed after a click.
  • Unsubscribes, complaints and bounces per campaign.
  • Gmail's spam rate in Postmaster Tools.

How MailPilot handles deliverability

MailPilot is the email marketing module of RetailPilot, for WooCommerce shops. It runs as a pilot, by invitation, and our team sets up each shop's sending domain with them. Then:

  • Your own domain, signed with DKIM. Email goes out from an address at your shop's domain through Amazon SES in Frankfurt (eu-central-1). Amazon SES is listed among our sub-processors on the GDPR page.
  • One-click unsubscribe from Gmail's or Yahoo's own button. The link in the email asks first, so link scanners can't unsubscribe anyone.
  • Hard bounces and spam complaints suppress the address automatically, and suppressions are checked again right before every email leaves.
  • Brakes. Campaigns, automations and the shop's email as a whole pause themselves when bounces or complaints near the limits Amazon SES enforces.
  • Gmail's spam rate on your dashboard, read daily from Postmaster Tools once you connect it.
  • No open tracking, by design. MailPilot counts clicks, deliveries, bounces, complaints, unsubscribes and orders after a click.

Your DMARC record stays your own: MailPilot doesn't create it, so publish one if you haven't.

Frequently asked questions

Do I need DMARC if I send fewer than 5,000 emails a day?

Gmail and Yahoo require it only from bulk senders, but publish one anyway: a p=none record changes nothing for your mail, its reports show who sends as your domain, and one big campaign can make you a bulk sender for good.

What spam rate is too high?

Gmail and Yahoo draw the line at 0.3%, and Google asks you to stay below 0.1%: one complaint per 1,000 emails delivered.

Why do my emails go to spam even with SPF and DKIM?

Usually because they pass for your email service's domain rather than yours (no alignment), or because of complaints, old addresses that bounce, or a sudden jump in volume from a new domain.

What's the difference between a hard and a soft bounce?

A hard bounce is permanent, such as an address that doesn't exist: remove it after the first one. A soft bounce is temporary, such as a full mailbox: retry, and stop if it keeps failing.

Should I still track open rates?

Not for decisions. Since Apple's Mail Privacy Protection, opens are inflated by an unknown amount; judge emails by clicks and orders.