Skip to content

The checks between Send and the inbox.

Drin refuses mail that can only bounce, remembers every bounce and slows a sender down before it hurts anyone else. We publish no inbox percentage: yours depends on your mail and your list.

Every send takes the same route.

The API and SMTP go through these checks. List mail is checked again when it goes out.

  1. Recipient check

    No MX, null MX, disposable domains, our block list and farm mail hosts are refused before anything is sent.

    422 recipient_rejected
  2. Suppression

    Bounces and complaints go on the project's list. A hard bounce also blocks that address for every sender on Drin.

    409 suppressed
  3. Limits

    New accounts, agent keys, inboxes and your plan each have a line. Over it, the send is refused until the reset.

    429 with Retry-After
  4. Paced

    Sends are paced to the live sending quota, so a burst queues rather than bouncing off a rate limit.

    202 queued

Your domain, your own key.

Every domain gets a fresh 2048-bit DKIM key, and we don't keep the private half.

  • A selector of its own

    A domain that moved from another account can't collide with its old key.
  • Checked live

    Each record shows ok, missing or wrong, read from public DNS, with GET /v1/domains/:id/records.
  • DMARC is yours to tighten

    Drin starts you at p=none, and you choose how strict to make it.
The records for acme.com
drin-<12 hex>._domainkey  TXT
  v=DKIM1; k=rsa; p=…

send  MX
  feedback-smtp.<region>.amazonses.com
send  TXT
  v=spf1 include:amazonses.com ~all

_dmarc  TXT
  v=DMARC1; p=none;

@  MX
  10 inbound.drin.run

New accounts start quiet.

Abuse tends to come from brand-new accounts, and it hurts everyone on the same servers. So a new workspace grows into its volume.

  • 50new people a day for the first 7 days. Replies to people who wrote first don't count.
  • 200people at most in one list send that first week.
  • 200a day from the shared drin.run domain, per workspace.
  • 20,000a day is where the largest paid plan starts on its own domain. Plans start from 200, and even proven senders warm up.

When rates climb, sending stops at the smallest ring.

One sender's bad week stays theirs. See your own numbers with GET /v1/domains/:id/health.

Bounce and complaint lines
LineBouncesComplaintsWhat happens
A list send8%0.5%Pauses that send, judged after 50 sent
A project: warning2.5%0.05%A reputation.warning event, at most once a day
A project: pause5%0.1%Stops that project alone, measured over 7 days from 100 people. It resumes once rates fall
A workspace: slow5%0.1%100 a day, and the owner gets an email
A workspace: suspend10%0.5%Refused for at least 24 hours, and the owner gets an email
All of Drin4%0.08%The breaker pauses all sending and alerts us

Mail to a list plays by stricter rules.

Marketing mail is where reputations get burned, so it carries the most checks.

  • Opted-in contacts only

    A list send goes only to subscribed contacts. An imported contact isn't opted in unless the row says so.
  • Imports are checked

    Bad syntax, no MX, disposable domains, the block list and known hard bounces are left out, and each comes back with the reason.
  • One-click unsubscribe

    The headers Gmail and Yahoo ask for, signed for each reader. Opening the link changes nothing, so link scanners can't opt anyone out.

Send from your own domain.

Add your domain, publish the records and watch each one turn ok.