Posthaste

Deliverability

Reputation is the product.

We run our own mail servers, so the reputation your email travels on is one we protect on purpose. Here’s exactly how, and what we can’t promise.

The one rule

If it risks the inbox, we don’t do it.

However convenient it would be. We never send to an address on your suppression list, never let volume jump past what your reputation has earned, and never send from a domain whose ownership we haven’t checked in DNS.

Signing

We sign as you. One record does it.

Every message carries your domain’s DKIM signature, so inbox providers credit the mail to you. You add one TXT record. We never ask you to change your SPF.

Add this to your DNS
Type
TXT
Name
s1._domainkey.yourdomain.com
Value
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…
Checked as you go

Warmup

Volume ramps, whether you want it to or not.

A new sender who blasts 100,000 emails on day one gets filtered. So every account starts at 50 a day and earns its way up.

  1. 50Tier 0
  2. 200Tier 1
  3. 500Tier 2
  4. 1kTier 3
  5. 2.5kTier 4
  6. 5kTier 5
  7. 10kTier 6
  8. 25kTier 7
  9. 50kTier 8
  10. 100kTier 9

Up one rung

After a day that used at least 80% of the cap, with complaints at or under 0.1% and bounces at or under 5%.

Down one rung

When complaints pass 0.3% or bounces pass 10%. The 0.3% line is Gmail’s, not ours.

One step a day

At most one rung a day, and quiet days move nothing. Nobody can pay to skip it, including us.

Every message ends somewhere definite.

Not “sent”. One of four outcomes, with the receiving server’s own words.

Delivered250 2.0.0The inbox provider took it. We keep its exact reply.
Bounced550 5.1.1The address doesn’t exist. It joins your suppression list at once.
Deferred451 4.7.1“Try later.” We retry with backoff, and never suppress for it.
Suppressedon listWe refused before sending, and say which entry stopped it.

Why we refuse marketing mail.

Newsletters and campaigns draw far more complaints than receipts and sign-in codes. Mixing them on one set of servers would drag down every customer’s password resets. So we don’t accept them, on any plan.

Announcements to your own users.

An outage notice or a change to your terms is different, and welcome. Broadcasts travel on their own stream, stop themselves for good once 200 of their messages have settled with more than 5% bouncing or 0.1% complaining, and an account’s first broadcast to more than 1,000 people is read by a person first.

What we can’t promise.

Inbox placement is decided by Gmail, Outlook and the rest, not by us. Our IP is young, and today we are not better at deliverability than Postmark. What we can promise is to deliver correctly and tell you truthfully what happened to every message.

What we ask of you.

  • Send only to people who expect to hear from you.
  • Set List-Unsubscribe on anything that isn’t strictly transactional.
  • Treat a bounce as final. We will.
  • Keep codes, receipts and resets apart from announcements.

See where every email ended up.

Free to start, with the full record on every plan.