Skip to content
meereach

guardrails

Email that won’t let you burn your domain.

MeeReach checks every campaign before it goes, slows a domain down when bounces or complaints climb, and pauses it before the damage is done.

01 · before the send

Five checks, and a reason when one fails.

When you press send, the send doesn’t start until: the from-address is on a verified sending domain; you have a credit for every recipient; the list has members; each A/B variant has at least five people; and the whole send can be delivered before mail waiting in the queue expires. Live

  1. Callout 1: The failing check, by name.
  2. Callout 2: Why, and the most you could send instead.
  3. Callout 3: Nothing sent. Nothing spent.
Spring restockDraft
  • Sending domain verifiednews.northfieldsupply.com
  • Credits for every recipient12,400 needed · 40,000 available
  • List has membersSpring customers · 12,400
  • Can deliver before mail expires

Send not started

This send needs about 57.2h to deliver, but mail expires after 48h and is not refunded. The limit is gmail.com recipients: send at most 9,600 of them per campaign.

Send nowSend testEdit
fig. 03 · The check that stops a send · recreated from the console · sample data

02 · while you write

A score that reads over your shoulder.

As you edit, the spam meter scores the subject line, the content and every link, and says which rule each point came from. Each link is checked against Spamhaus and Google Safe Browsing.1 Live

Account owners can also keep a list of link domains that are always allowed or never allowed, with requests reviewed before a new one is let through. Live

Footnote 1: The meter advises. It doesn’t stop a send; the checks above do that.

Spam guardRisky

A few signals could hurt deliverability. Fix what you can before sending.

SubjectSubject line is mostly capital letters

Subject88
Content71
Links94
fig. 03b · The spam meter · recreated from the console · sample data

03 · while it sends

Slowed, then paused, then held for you.

Each sending domain has its own state. We read its bounces, complaints and deferrals as mail goes out, and move it along the dial when a threshold is crossed. It moves back when the numbers recover, except from Blocked: that one waits for you to look and resume. Live

  1. Healthy

    Under 2% bounces and 0.1% complaints

  2. Slowed

    2% bounces, 0.1% complaints or 30% deferrals

  3. Paused

    5% bounces, 0.3% complaints or 50% deferrals

  4. Blocked

    Paused for 15 minutes without recovering. Waits for you to resume

fig. 04 · The guard on one sending domain · thresholds as shipped
Thresholds per sending domain, as shipped
SignalSlowed atPaused at
Bounces2%5%
Complaints0.1%0.3%
Deferrals30%50%

Warm-up and pacing

A new sending domain starts small and doubles its daily allowance over thirty days. Mail to Gmail, Outlook and Yahoo is paced to each provider’s own limits. Both happen without you scheduling anything. Live

These protections apply to marketing mail. Receipts and account email skip warm-up and the domain guard on purpose, so a password reset is never held back.

04 · setting up a domain

DNS, with a PDF for your IT team.

Add a sending domain and we show the records to create: DKIM by CNAME, so there’s no key for you to rotate; an SPF include; a DMARC check; and an optional bounce subdomain. Hosts are written the way your DNS provider expects them. If someone else runs your DNS, download the whole set as a PDF and send it to them. Live

news.northfieldsupply.comDownload DNS config (PDF)
  • CNAMEmkt._domainkey.newsDKIM · MarketingVerified
  • CNAMEtx1._domainkey.newsDKIM · TransactionalVerified
  • TXTnewsSPFVerified
  • TXT_dmarcDMARCNot found
  • MXbounce.newsBounce processingVerified
fig. 12 · A sending domain’s records · recreated from the console · sample data

05 · the list

Verify before you send, in the same place you send.

Verify a list in bulk, or as you import it. Each address gets a verdict, a score and, for typos, a “did you mean” suggestion. You choose which verdicts to drop for each run. Live

list.csv
  1. 01
    Syntax

    Is it shaped like an address at all?

  2. 02
    Domain & MX

    Does the domain exist, and does it accept mail?

  3. 03
    Provider rules

    What the mailbox provider is known to allow.

  4. 04
    Mailbox

    Ask the receiving server whether the mailbox is there.

  5. 05
    Risk

    A score across everything above.

verdicts →DeliverableRiskyUndeliverableDisposableRole (info@)Accept-all
fig. 05 · One address through five passes · struck-through verdicts are dropped by default; you choose per run

06 · after the send

Suppression, automatically.

Every later send checks the suppression list first. You can review and edit it any time. Live

Hard bounce
The address is suppressed. Nothing goes to it again unless you remove it from the list.
Late bounce
Some servers accept a message and refuse it days later. We catch those too, and treat them the same way.
Complaint
When a spam complaint about a message reaches us, the address is suppressed.
Unsubscribe
One click, from the link or from Gmail’s and Yahoo’s own button (RFC 8058). Suppressed across your account.
Failed verification
Addresses you chose to drop in a verification run are suppressed.

Send us your hardest list.

Request accessor write to hello@meereach.com