Skip to content
MeeReach

Email that protects your reputation.

For marketing teams and agencies who can’t afford a burned sending domain.

  1. 01

    Verified on the way in

    Every address is checked as it enters your account. The ones that fail are suppressed before a single message goes out.

  2. 02

    Three IP pools

    Transactional, newsletter and promotional mail leave on separate pools. A promotional blast never shares addresses, or a queue, with your password resets.

  3. 03

    Counted by people

    Opens and clicks made by privacy features and link scanners are set aside, and you see exactly how many there were.

Request accessSee the guardrails
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

honest numbers

Two people clicked. Machines clicked 165 times.

That was one week of a customer’s sending: 197 opens and 2 clicks by people, and another 265 opens and 165 clicks by machines. Most email reports would have counted them all as readers.

Here’s where the extra came from. Company security filters fetch every link in a message at once, to test it before anyone reads it. Some mail systems open a message seconds after it arrives, faster than a person could. Apple Mail downloads every message to protect its readers’ privacy. All of it looks like engagement, and none of it is.

MeeReach sets those aside and shows you how many there were, so the numbers you act on were made by people.1

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

265 opens and 165 clicks were excluded as automation. Every link in the message fetched at once: 246. Fetched too soon after sending: 112. Security or link scanner: 71. Malformed user agent: 1.
fig. 02 · The dashboard, one week of a customer’s sending · real data, anonymised

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.

verified on the way in

Bad addresses are stopped at the door. Live

Verification isn’t a separate tool you remember to run. Every address is checked as it enters your account: in a CSV import, added by hand, or through the API. The ones that fail your policy are suppressed on the spot, and every send skips them.

That matters because bounces are what burn a sending domain. We slow a domain down at 2% bounces and pause it at 5%. In the run on the right, 977 of 20,000 addresses were undeliverable: nearly 5%, and none of them were mailed.

You choose what to drop for each run: undeliverable, risky, disposable, unknown, role addresses.

Email verification, done. 18,969 deliverable, 977 undeliverable, 54 risky, 0 unknown, 1,031 opted out, 20,000 total. Opt-out policy: risky, unknown, disposable, undeliverable.
fig. 04 · A real verification run, 20,000 addresses · anonymised
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. 04b · One address through five passes · struck-through verdicts are dropped by default; you choose per run

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. 05 · The check that stops a send · recreated from the console · sample data
Step 4, Will this land in inbox? Spam guard: Inbox-ready, 100 out of 100. Subject 100, content 100, links 100. No issues found.
fig. 05b · Spam guard, step 4 of a new campaign · from the console

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. 06 · 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

make it

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

The template editor in Visual mode, with elements such as columns, text, button, image, add to calendar and unsubscribe link, and desktop, tablet and mobile previews.
fig. 07 · The visual editor · from the console

Build emails from blocks, or switch to code and paste your own HTML. Personalise with {{ first_name }} or any field you imported. Live

A journey branch: Did they open? Opened leads to one email, didn't open leads to another, then both end.
fig. 08 · A journey in the builder · anonymised

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.

Send each to a slice of the list, and after the wait we pick the winner on opens or clicks by people, with bots excluded, then send it to everyone else. Live

Step 3, What does it say? A/B test: try 2 to 4 subjects and auto-pick the winner. Test audience 20%, pick winner after 4 hours, winner metric open rate or click rate.
fig. 09 · Setting up an A/B test · from the console

three pools

A big promotion can’t hold up your password resets.

MeeReach sends on three IP pools, one for each kind of mail. Receipts and account email also get their own queue, so they never wait behind a blast. Newsletters and promotions are kept on separate addresses from each other, and every marketing message carries one-click unsubscribe, as Gmail and Yahoo require.3

TransactionalReceipts, password resets, account email

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

  1. Its own queue
  2. Transactional IP pool
NewsletterRegular updates to people who subscribed

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

  1. Marketing queue
  2. Newsletter IP pool
PromotionalOffers, launches and one-off blasts

Same guardrails, on addresses kept apart from your newsletter

  1. Marketing queue
  2. Promotional IP pool
Receiving serversGmail, Outlook, Yahoo and the rest
fig. 10 · Three pools, from your account to the receiving server

Footnote 3: Pools are shared between customers by kind 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
IP pools
Three, by kind of mail: transactional, newsletter and promotional
Verification
Five passes on every address, at import, on single adds and in bulk
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. 11 · 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