How we send
Every author sends as themselves
Mail goes out from a domain the author has proven they own — verified with DKIM through a guided setup that checks each DNS record individually and tells you exactly what to fix. There is no shared blast domain: a new account cannot send from our domain, so one careless sender can never poison the reputation your mail rides on. Your sending reputation is yours — built by you, owned by you, portable with you.
If a domain verification stalls, we notice on our own — the platform re-checks unverified domains and alerts the author (in-app and by email) instead of letting the problem sit silent.
Honest numbers, even when flattering ones would sell better
Apple’s Mail Privacy Protection opens emails by machine, which inflates open rates on every platform. We label open rates as the estimates they are, and we rank reader engagement by clicks first— the signal a machine doesn’t fake. When you migrate a list here, imported engagement is scored the same honest way, so your warm-up plan is built on real readers, not on Apple’s robots.
Unsubscribes are forever
One click unsubscribes a reader — no login, no “are you sure.” Every email carries the one-click unsubscribe headers inbox providers use for their own unsubscribe buttons. A suppressed address stays suppressed: no import, signup, or automation can quietly start emailing someone who opted out. When you import a list, we ask you to bring the unsubscribes too — their choice is a promise you made, and we keep enforcing it here.
Consent travels with the reader
Imports preserve opt-in evidence — when, where, and what a reader agreed to — and never invent it where it doesn’t exist. Every email footer states why the reader is receiving it, alongside the sender’s real mailing address (required by anti-spam law; sending is blocked until it’s set).
Clean, letter-shaped email
The composer produces light, semantic HTML with a genuine plain-text twin — email that looks like a letter to inbox filters because it is one. No design-tool markup soup, no oversized payloads for Gmail to clip. Layout features (wrapped covers, image rows, galleries) compile to the boring, bulletproof markup every email client renders — that restraint is deliberate, and it’s a large part of why author mail from here lands in inboxes.
Volume that looks human
Big sends can be spread across a delivery window instead of hitting inbox providers as one spike — the shape providers expect from a real newsletter, and the tool that makes warming up a migrated list practical. Per-campaign complaint rates are monitored, and an account that crosses the line is stopped from sending entirely — every author here is protected from every other author’s mistakes.
The boring foundations
Delivery runs on Amazon SES — the same infrastructure behind much of the mail you already receive — with bounce and complaint feedback processed in real time. Hard bounces are suppressed automatically. We bill by mailable readers only: unsubscribed and bounced contacts stay safely on your list for your records, free.
Questions about any of this — or a deliverability puzzle of your own? Write to support@newsletterscriv.com; a human who works on this pipeline reads it.