Map Extract

A cold email deliverability checklist has four stages, checked in order: the domain (SPF, DKIM and DMARC pass, with the From domain aligned), the mailbox (warmed up, with a real signature and someone reading replies), the list (verified, sourced and screened against suppression) and the campaign (modest volume per mailbox, a clear opt-out and an automatic pause on bounces). If any item fails, fix it before sending; most deliverability problems are visible before the first message goes out.

This is the pillar page for our deliverability posts. It is written for senders using their own mailboxes on Google Workspace, Microsoft 365 or a hosting provider, not a shared sending pool. Copy the checklist, work through it, and follow the links for any item that fails.

How to use this checklist

Each item has a pass criterion you can test, a source where one exists, and a link to the fix. Work top to bottom: there is no point warming a mailbox on a domain whose DKIM fails, or verifying a list you have no lawful basis to email.

Use these tools to test items as you go:

  • dig TXT yourdomain.example (or nslookup -type=TXT) to read SPF and DMARC records.
  • dig TXT selector._domainkey.yourdomain.example for a DKIM key.
  • Send a test message to a personal Gmail account and choose Show original to see SPF, DKIM and DMARC results for that message.
  • Google Postmaster Tools once you send enough to Gmail to generate data.

Stage 1: domain and DNS

#ItemPass criterionFix
1.1Sending domain chosenYou send from a domain you control, ideally a dedicated outreach domain or subdomain that is not your main transactional domainWarm-up schedule for a new domain
1.2SPF recordExactly one TXT record starting v=spf1, listing every service that sends as the domain, ending in ~all or -all, using no more than 10 DNS lookupsSPF too many DNS lookups
1.3DKIMYour mail provider's DKIM signing is turned on; test messages show dkim=pass for your domain, not only the provider'sDKIM checker
1.4DMARCA TXT record at _dmarc.yourdomain.example with at least p=none and an rua reporting addressSee below
1.5AlignmentThe From domain matches (or is a parent of) the SPF domain or the DKIM d= domain on test messagesGmail 550 5.7.26
1.6MXThe sending domain has working MX records, so replies and bounces arriveAdd MX at your DNS host
1.7PTR and TLSYour provider's sending IP has matching forward and reverse DNS, and mail is sent over TLSAutomatic on Workspace and Microsoft 365; ask your host otherwise
1.8Domain age and siteThe domain resolves to a simple website that says who you arePublish one page with your identity and contact

Why these items

Google's email sender guidelines require every sender to set up SPF or DKIM, have valid forward and reverse DNS (PTR) for sending IPs, use TLS, format messages to RFC 5322 and keep the spam rate in Postmaster Tools under 0.3%. Senders of more than 5,000 messages a day to personal Gmail accounts must also have SPF and DKIM, a DMARC record (the policy can be none) and From domain alignment. Yahoo sets the same pattern: SPF or DKIM for all senders, both plus a DMARC policy of at least p=none for bulk senders. Microsoft has required SPF, DKIM and DMARC (at least p=none, aligned with SPF or DKIM) from domains sending over 5,000 messages a day to Outlook.com consumer addresses since 5 May 2025.

A small B2B sender may be below every threshold, but meeting the bulk rules anyway costs nothing and removes a whole category of problem. The Gmail and Yahoo sender rules for B2B and Outlook high-volume sender rules posts explain what applies at which volume.

Example records for a fictional domain

outreach.oakline-joinery.example.  TXT  "v=spf1 include:_spf.google.com ~all"
_dmarc.outreach.oakline-joinery.example.  TXT  "v=DMARC1; p=none; rua=mailto:[email protected]"
google._domainkey.outreach.oakline-joinery.example.  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkq..."

The SPF include shown is the one Google documents for Workspace; Microsoft 365 uses include:spf.protection.outlook.com. Use only the include for the services that actually send as this domain. Under RFC 7208 section 4.5, two SPF records on one name is a permerror, so merge rather than add.

Stage 2: mailbox

#ItemPass criterionFix
2.1Real mailboxA licensed user mailbox (not a group alias) with a person's name in the display nameCreate a named user
2.2Age and historyThe mailbox has sent and received normal, two-way mail for at least two to four weeks before cold volumeWarm-up schedule
2.3Warm-up planA written ramp with daily caps and pause rulesWarm-up schedule
2.4SignatureName, role, business name, a postal or web address, and a way to opt outAdd a plain text signature
2.5Reply handlingSomeone reads replies every working day; out-of-office and bounce messages are processedAssign an owner; filter bounces to a folder
2.6Sending methodSMTP or the provider's API with authentication enabled; app passwords or OAuth as your provider requiresMicrosoft 535 5.7.139
2.7Provider limits knownYou know the daily ceiling for this mailbox type and stay well below itSee below
2.8Number of mailboxesEnough mailboxes that each one sends a modest daily volumeMailboxes calculator

Google documents a limit of 2,000 messages a day per paid Workspace user and 500 for trial accounts, applied over a rolling 24 hours, with sending blocked for up to 24 hours when exceeded (Gmail sending limits in Google Workspace). These are ceilings for normal business use. Cold email reputation fails long before you reach them, so plan in tens per mailbox per day, not hundreds.

Stage 3: list

#ItemPass criterionFix
3.1Sourcing recordEvery address has a source (page URL or record), a date collected and a business it belongs toFind emails from a domain
3.2Lawful basisFor each recipient you have recorded why you may email them (corporate subscriber, consent, soft opt-in)UK cold email law
3.3Subscriber typeSole traders and some partnerships are identified and excluded unless you have consent or soft opt-inCorporate subscriber or sole trader
3.4VerificationEvery address has a recent verdict; invalid removed; catch-all and unknown in separate segmentsVerification results explained
3.5Inbox purposeprivacy@, abuse@, noreply@, unsubscribe@ and recruitment inboxes removed; role addresses kept only where the purpose fitsVerification results explained
3.6SuppressionThe list is screened against every past opt-out, hard bounce and complaint, across all your mailboxesSuppression list merger
3.7DuplicatesOne primary address per business per campaignDeduplicate by domain
3.8Personalisation fieldsEvery merge field is filled or has a fallback; no {first_name} reaching a recipientPreview every row

The ICO's business-to-business guidance says PECR's email marketing rule does not apply to corporate subscribers, but you must identify yourself and give a valid opt-out address, and you should keep a do-not-email list to screen new lists against. Sole traders and some partnerships are individual subscribers and need consent or the soft opt-in. Named addresses are personal data under UK GDPR: you need a lawful basis such as legitimate interests (after the three-part test), privacy information and respect for objections. Other countries differ: Germany generally needs prior consent for advertising email, including B2B, and the US has CAN-SPAM. This is general information, not legal advice.

Stage 4: campaign

#ItemPass criterionFix
4.1Daily volume per mailboxWithin your warm-up stage; a few dozen new cold messages a day at most once warmMailboxes calculator
4.2Sending patternMessages spread through working hours with a minimum gap, not in one burstSet hourly caps and delays
4.3Per-domain throttleNo more than a handful of messages to the same recipient domain per hour; one contact per businessCap per business
4.4IdentityThe From name, sender business and a contact address are in every messageEdit the template
4.5Opt-out wordingEvery message has a plain sentence offering an opt-out ("Reply 'no thanks' and I will not contact you again")Edit the template
4.6One-click unsubscribeIf you meet the Gmail or Yahoo bulk sender definition and send marketing, List-Unsubscribe and List-Unsubscribe-Post headers per RFC 8058List-Unsubscribe header generator
4.7Links and trackingFew links, all to your own domain; no URL shorteners; open tracking off or on a custom domainRemove extra links
4.8Content checkPlain text or light HTML, no attachments on first contact, subject line matches the bodyRewrite
4.9Test sendThe rendered message to Gmail and Outlook test accounts shows pass for SPF, DKIM and DMARC and lands in the inboxFix stage 1

On item 4.6: RFC 8058 requires the List-Unsubscribe header to contain one HTTPS URI, a List-Unsubscribe-Post: List-Unsubscribe=One-Click header, and a DKIM signature that covers both. Google says one-click unsubscribe is required only for marketing and promotional messages from bulk senders, and recommends processing unsubscribe requests within 48 hours (sender guidelines FAQ). Yahoo asks bulk senders to honour unsubscribes within 2 days. A low-volume sender using an ordinary mailbox usually cannot add these headers; the plain opt-out sentence in item 4.5 is then the essential part, and it is what UK law asks for.

Stage 5: monitoring and stop rules

#ItemPass criterionFix
5.1Bounce limitAn automatic pause at a set hard bounce rate per campaign, well below 5%Warm-up schedule and pause rules
5.2Complaint rateGmail spam rate in Postmaster Tools below 0.1%, never reaching 0.3%Gmail and Yahoo sender requirements
5.3Bounce readingEvery bounce is read for its code; 5.1.1 addresses suppressed; 5.7.x policy blocks investigatedSMTP error codes
5.4Opt-out processingOpt-outs added to suppression the same working dayDaily routine
5.5Reply rateTracked per campaign; a sudden drop to zero investigated as a placement problemEmail deliverability checker
5.6DMARC reportsAggregate reports reviewed weekly for unknown senders and failuresUse a free report reader

Google's FAQ sets the targets for item 5.2: "keep your user-reported spam rate below 0.1% and prevent it from reaching 0.3% or higher", and bulk senders above 0.3% are ineligible for mitigation until they stay below it for 7 consecutive days. Yahoo's threshold is also 0.3%. Cold email recipients did not ask for your message, so complaints come faster than with newsletters; volume and targeting are your main controls.

Printable summary

DOMAIN    [ ] one SPF record, <=10 lookups   [ ] DKIM pass on own domain
          [ ] DMARC p=none or stricter, rua   [ ] From aligned   [ ] MX, PTR, TLS
MAILBOX   [ ] named user   [ ] 2-4 weeks history   [ ] warm-up plan
          [ ] signature with identity   [ ] replies read daily   [ ] limits known
LIST      [ ] source + date per address   [ ] lawful basis recorded
          [ ] sole traders handled   [ ] verified, catch-all/unknown segmented
          [ ] privacy/noreply removed   [ ] suppression screened   [ ] deduped
CAMPAIGN  [ ] volume within ramp   [ ] spread with delays   [ ] one per business
          [ ] identity + opt-out line   [ ] one-click headers if bulk marketing
          [ ] few links, own domain   [ ] test send passes auth, inbox
MONITOR   [ ] bounce auto-pause   [ ] spam rate < 0.1%   [ ] bounces read
          [ ] opt-outs same day   [ ] DMARC reports weekly

How Map Extract helps

The bulk email sender in Map Extract covers several items in stages 3 to 5 for campaigns sent through your own SMTP mailboxes:

  • Permission gate (3.2, 3.3). Every outbox item is held as "Needs review" unless a permission record exists for that recipient, sender and channel, with a documentary reference, a recorded lawful basis and a working opt-out route. UK rules are encoded so that corporate status alone is not treated as approval.
  • Suppression (3.6). Suppression is applied to the audience and again to queued items before each send.
  • Verification policy (3.4). Settings decide whether catch-all and unknown verdicts from the email verifier may be sent.
  • Opt-out requirement (4.5). A message cannot be sent unless its plain text contains opt-out wording, and only approved links may appear.
  • Volume controls (4.1 to 4.3). Caps per hour, day and month, a minimum delay, route ceilings per hour and day, a per-business cap and an optional warm-up ramp that starts low and increases by a set amount at set intervals.
  • Stop rules (5.1, 5.3). Replies and bounces are read by IMAP, and a campaign pauses itself with an emergency stop when bounces reach the threshold (5% by default; set it lower if you prefer). Ambiguous failures are marked "Uncertain" and not blindly retried.

What it does not do: it does not check or fix your SPF, DKIM or DMARC records, it does not add one-click List-Unsubscribe headers for you, it does not warm mailboxes through a network, and it cannot guarantee inbox placement. Stage 1 and stage 2 are yours to complete with your DNS host and mail provider.

Key takeaways

  • Check in order: domain, mailbox, list, campaign, then monitoring.
  • Meet the bulk sender authentication rules even at low volume: SPF, DKIM, DMARC p=none, aligned From.
  • Provider sending limits are ceilings, not targets; scale with mailboxes, not volume per mailbox.
  • A list item without a source, a lawful basis and a verdict is not ready to send.
  • Every message needs your identity and a plain opt-out; add one-click headers when you are a bulk marketing sender.
  • Decide your stop rules before the first send and let the software enforce them.

Frequently asked questions

What should I check before sending a cold email campaign?

Check four things in order. The domain: SPF, DKIM and DMARC pass and the From domain aligns. The mailbox: it has a history of normal mail and handles replies. The list: every address is verified, sourced and screened against your suppression list. The campaign: daily volume per mailbox is modest, there is a clear opt-out, and a bounce limit will pause sending automatically.

Do I need DMARC for cold email?

If you send more than about 5,000 messages a day to personal Gmail accounts, or to Outlook.com consumer addresses, DMARC is required, and p=none is enough to start. Below that it is not mandatory, but publishing a DMARC record is cheap, gives you aggregate reports showing who sends as your domain, and is part of what receiving servers expect from a legitimate sender.

What bounce rate is too high for cold email?

No provider publishes a single bounce limit for cold email, so set your own. Many practitioners aim to keep hard bounces under about 2 per cent of a send and pause well before 5 per cent. A high bounce rate usually means the list was not verified or contains guessed addresses on catch-all domains. Stop, find the segment responsible and fix the source.

Do cold emails need an unsubscribe link?

In the UK every marketing email must identify the sender and give a valid way to opt out, including emails to companies. One-click List-Unsubscribe headers are required by Gmail and Yahoo for bulk marketing mail, but a plain sentence offering an easy opt-out by reply is the minimum for any cold email. Honour every opt-out quickly and keep a suppression list.

How many cold emails can I send per mailbox per day?

Provider limits, such as 2,000 messages a day for a paid Google Workspace user, are ceilings for ordinary use, not targets for cold email. Most experienced senders keep new cold messages per mailbox to a few dozen a day after warm-up, because complaints and bounces, not raw limits, are what damage reputation. Scale with more mailboxes rather than more volume per mailbox.

Sources

  1. Google Postmaster Tools
  2. Google: Email sender guidelines
  3. Google: Email sender guidelines FAQ
  4. Yahoo Sender Hub: Sender best practices
  5. Microsoft: Outlook's new requirements for high-volume senders
  6. RFC 8058: Signaling One-Click Functionality for List Email Headers
  7. RFC 7208: Sender Policy Framework (SPF)
  8. Google Workspace: Gmail sending limits
  9. ICO: Business-to-business marketing

Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top