Skip to content
meereach

Know where every email went.

MeeReach sends your newsletters and account email on mail servers we run ourselves, and itemises every message that didn’t make it. Bots and link scanners are counted separately, not as readers.

Request accessSee how we count
fig. 01 · A campaign, itemised · sample campaign · figures illustrative
Stage or leakMessages
Active recipients12,400
Leak: never sent310
Sent12,090
Leak: bounced214
Leak: retries exhausted21
Delivered11,855
Opened by people3,920
Leak: excluded as automation (Apple Mail privacy prefetch 2,184; Security / link scanner 351; Every link in the message fetched at once 75)2,610
Clicked by people610
fig. 01 · A campaign, itemised · sample campaign · figures illustrative

For marketing teams, and agencies that send for their clients.

Most email reports flatter you. Mail privacy features open every message they receive. Security scanners click every link. We count those separately, show you how many there were, and tell you which of your messages never left, and why.1

Footnote 1: Our open rates will look lower than your last provider’s. That’s the point. How we count

the tally

Every message, and every message that didn’t.

One campaign, from the list to the click. Each leak has a name, a number and a reason, in the same words the console uses. Here’s what each leak in the figure above means.

never sent
Stopped before it left us: a suppressed or unverified address, or a check that failed at send time. Not charged.
bounced
Refused by the receiving server and classified. Hard bounces suppress the address; policy and authentication failures don’t.
retries exhausted
Deferred by the receiving server, retried, and still not accepted when the retry window closed.
excluded as automation
Opens and clicks that no person made. Counted, shown to you, and left out of every rate.

before you press send

We’d rather stop a send than apologise for it.

Before a campaign goes, we check that your sending domain is verified, that you have the credits, that the list isn’t empty, and that the send can finish before mail in the queue expires. If any of those fail, the send doesn’t start, and the screen tells you which one. Live

While you write, a live score reads your subject line, your content and every link, including a check of each URL against Spamhaus and Google Safe Browsing.2 Live

  1. Callout 1: The check that failed is named, not hidden behind “something went wrong”.
  2. Callout 2: The reason, with the numbers behind it and what to do instead.
  3. Callout 3: Nothing has been sent and no credits were spent.

Footnote 2: The score advises; it never blocks. You’re the editor.

Read the guardrails
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
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 while you write · recreated from the console · sample data

while it sends

A domain that’s struggling gets slowed down, not burned. Live

We watch each sending domain’s bounces, complaints and deferrals as the send runs. At 2% bounces or 0.1% complaints we slow it down. At 5% or 0.3% we pause it, and if it hasn’t recovered fifteen minutes later it stops and waits for you.

New domains warm up over thirty days. Gmail, Outlook and Yahoo each get their own pace. You don’t schedule any of it.

  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
2%

Bounce rate at which a domain is slowed

with 0.1% complaints

0.3%

Complaint rate at which a domain is paused

with 5% bounces

30days

Warm-up for a new sending domain

on a doubling curve

clean the list first

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

Upload a list and we check every address in five passes. You decide what to drop: undeliverable, risky, disposable, role addresses like info@. Anything you drop is suppressed automatically, so it can’t slip back into a send.

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

make it

A drag-and-drop editor. Journeys that branch.

Spring restock · templateVisualHTML
NORTHFIELD SUPPLY CO.

Hi {{ first_name }},

The spring stock is in. Your usual order is ready to reorder in one click.

Reorder
DesktopMobile
fig. 07 · The visual editor · recreated from the console · sample data

Build emails visually, or paste your own HTML. Personalise with {{ first_name }} or any field you imported. Live

Welcome seriesDraft
Trigger
Added to list
New customers
Send email
Welcome
Wait
2 days
Branch
Opened “Welcome”?
yes
End
Done
no
Send email
A second hello
fig. 08 · The journey builder · recreated from the console · sample data

Someone joins a list, you wait, you send, you branch on whether they opened or clicked. Live

Not yet event triggers · splits inside journeys

Test up to four subject lines.

We pick the winner on opens or clicks by people, with bots excluded, and send it to the rest of the list. Live

A/B test · winner on opensPick winner now
  • ASpring stock is in31.4%
  • BYour usual, restocked28.9%
  • CNew season, same prices24.2%

Opens by people only · automation excluded

fig. 09 · The A/B race · recreated from the console · sample data

two lanes

Your password resets don’t wait behind your newsletter.

Receipts and account email run in their own queue on their own IP pool. Newsletters and promotions run on theirs. Every marketing message carries one-click unsubscribe, as Gmail and Yahoo require.3

Receipts and account email

No warm-up throttle, so a password reset is never held back

  1. Its own queue
  2. Transactional IP pool
Newsletters and promotions

Warm-up, per-provider pacing and the domain guard apply

  1. Its own queue
  2. Marketing IP pools
Receiving serversGmail, Outlook, Yahoo and the rest
fig. 06 · Two lanes, from your account to the receiving server

Footnote 3: Pools are shared between customers by type of mail. Dedicated IPs: Not yet

under the hood

The parts list.

What does the work, in plain terms. The mechanisms behind every claim on this page.

Read about security
Mail servers
Run by us, with sending pace tuned separately for each big mailbox provider
Unsubscribe
One-click (RFC 8058) on every marketing message, as Gmail and Yahoo require
Bounces
Caught when they happen and when they arrive days later; classified; only hard bounces suppress
Authentication
DKIM by CNAME, an SPF include, DMARC checked, an optional bounce subdomain
Blocklists
Every sending IP checked against 5 major blocklists every 15 minutes
Isolation
Row-level security in the database on every customer table
Credits
Reserved when you send; not charged if the message never leaves
API
Idempotency keys, scoped keys, signed webhooks Pilot

who runs your mail

We run the servers that send your email. We watch the queues, the blocklists and the bounce codes every day, because we’d rather see a problem before you do. When something’s wrong, a person on our side knows, not a ticket in someone else’s.

The MeeReach team, Teknomee

for agencies

Run email for your clients, under your own name.

Create a client account. Fund it from your credit balance. Pause its sending, suspend it, reset a password. Live

Your name and your own domain on the page your clients sign in to. Pilot

Not yet your logo · your own prices · full theming

What agencies get today
CustomersNew customer
CustomerCreditsActions
Harbour & Pine DentalActive18,000Fund
Kestrel OutdoorActive42,500Fund
Mill Lane BakerySending paused3,200Fund
Orchard PhysioSuspended0Fund
fig. 10 · Your customers · recreated from the reseller console · sample data

pricing

Pay for what you send.

MEEREACHPRICING
1 credit
1 accepted message
Never sent
not charged
Contact fees
0
Seat fees
0
Deliverability add-ons
0
Volume pricingtalk to us

Change due:
0 contact fees

MeeReach

One credit per accepted message. A message that never leaves isn’t charged. We’re in early access, so pricing is by conversation. There’s no card to enter, because there’s no checkout yet.

How credits work

What we don’t do yet

So you don’t find out from a sales call.

Not yetSMTP relay
Sending is through the console, or the API while it's in pilot.
Not yetAttachments through the API
Not yetSingle sign-on and two-factor sign-in
Not yetJourneys triggered by product events
Today a journey starts when someone is added to a list.
Not yetDedicated IPs
IP pools are shared between customers, separated by type of mail.
Not yetSelf-serve sign-up and card payments
Accounts are set up with you, by a person.

Send us your hardest list.

Request accessor write to hello@meereach.com