Email deliverability is the share of the mail you send that lands in the recipient's inbox instead of the spam folder, a quarantine queue, or a silent drop at the mailbox provider's edge. In 2026 it is not a reputation score a platform assigns to you once; it is a per-recipient-domain verdict recalculated on every message from your authentication records, your recent bounce and complaint rates, and the sending pattern your domain has built over time. Mailbox providers treat alignment of SPF, DKIM, and DMARC as a baseline expectation rather than a bonus, and a transactional sender that fails those checks or carries unresolved hard-bounce traffic gets filtered no matter how clean the content is. This playbook defines the four levers you control, walks a concrete setup checklist, and shows where the controls sit in Devotel Orbit as tenant-side choices you own.
The four levers you control
Deliverability turns on four knobs, and every one of them is set by the sender, not by the email platform.
1. SPF, DKIM, and DMARC alignment. SPF declares which hosts may send for your domain; DKIM signs the message with a key your domain publishes; DMARC tells a receiver how to treat a message when those checks fail, and whether the domain in the From header is the one that authenticated. Receivers in 2026 expect all three to pass and to relate to the same domain. A passing DKIM signature over a domain unrelated to your From domain counts as unaligned, and unaligned mail is the realistic failure point today: nothing looks broken on your side, but the receiver's policy already filed you lower.
2. Sender and domain reputation. Reputation is receiver-side history: per-domain complaint rates, hard-bounce rates, spam-trap hits, and how recipients interact with what you send. Transactional senders have an advantage — receipts and resets get opened, not complained about — but one bad import or one compromised API key posting junk through your domain recolors that history within days, and the recovery is measured in weeks.
3. IP and domain warmup. A new sending domain has no history, so receivers treat its early traffic with suspicion. Warmup means starting at a modest volume, growing by small increments, and watching complaint and bounce rates at each step instead of announcing a new domain by blasting a full list on day one. Sudden volume spikes from a young domain behave the way spam looks.
4. Bounce handling. A hard bounce is a permanent failure — a nonexistent recipient — and hard bounces sent repeatedly are the single clearest reputation poison. They need to stop reaching your sends, automatically. Soft bounces (a full mailbox, a temporary block) deserve retries for a bounded window and then suppression. Spam complaints need the same automatic treatment; continuing to mail a complainer is how a reputation slips from healthy to filtered.
How the levers surface in Orbit's email API
In Orbit, each lever maps to a control on the account rather than a promise in the marketing copy. When you register a sending domain, Orbit publishes the SPF and DKIM records for it and re-checks them against a live authentication grid, so you see at a glance whether receivers currently see an authenticated sender. The deliverability health view runs a spam-score test send and ingests DMARC aggregate (RUA) reports, which catch an alignment drift — a DNS change by another team, a lapsed key — before it shows up as an inbox-placement drop. Hard bounces, spam complaints, and List-Unsubscribe clicks go straight to the account's suppression list automatically, so list hygiene does not depend on someone remembering to run a cleanup.
You operate those controls from the same account that runs your other channels; the feature surface covers the way email sits alongside SMS, WhatsApp, RCS, voice, and the rest on one bill. For a buyer still deciding whose email API to run on top of, the best email API providers 2026 buyer's guide compares Orbit against SendGrid, Mailgun, and Amazon SES on exactly these axes.
The checklist, step by step
Here is the order a transactional-email operator works through, whether the sending platform is Orbit or one of the specialists.
- Pick a sending subdomain. Send from a dedicated subdomain of your main domain (for example the
mailsubdomain) so transactional traffic builds its own reputation and is insulated from whatever your marketing domain is doing. - Publish SPF for the sending domain. One
TXTrecord naming the hosts allowed to send for it. Keep to a single SPF record; two SPF records on one domain is a permanent soft-fail. - Publish the DKIM key. The platform's public key goes in as a DNS record; the private half signs outbound mail. Verify a test send actually produces a passing signature.
- Set a DMARC policy and a reporting address. Start with a monitoring policy pointed at an RUA address, read the aggregate reports for a couple of weeks, then tighten to quarantine or reject once alignment stays clean. Skipping the monitoring phase is how a strict policy breaks legitimate forwarding and nobody notices.
- Check alignment explicitly. Run a test message or ingested RUA report and confirm that both SPF and DKIM pass and that at least one of them aligns with the
Fromdomain. Passing-but-unaligned is the trap. - Warm up. Start at a fraction of your steady volume, increase in steps, and watch the complaint and hard-bounce rates at each step before the next. Any step that moves those rates the wrong way deserves a pause, not bigger volume.
- Wire bounces and complaints to suppression before the first real send. Hard bounces and complaints must stop re-entering the send path on their own; soft bounces retry for a bounded window and then suppress. Doing this after the first bounce storm is too late.
- Watch one dashboard, not three. Pick the single place that shows you authentication status, bounce and complaint rates, and test-send results, and check it on the same schedule you check revenue — drift in deliverability is early and quiet.
Scope: tenant-owned controls, not platform claims
This post deliberately documents only the controls a sending tenant owns with any competent email platform: the DNS records under your domain, the volume ramp you choose, the suppression rules for your sends, and the health signals you read. It makes no claim that Devotel Orbit — or any platform — can move a recipient's verdict for you, promise an inbox-placement rate, or override a mailbox provider's filtering. In Orbit those controls are exposed on your account as settings and views; the reputation they operate on is yours, and the discipline that keeps it healthy is yours.
Frequently asked questions
What is email deliverability, in one sentence?
Email deliverability is the share of the mail you send that reaches recipients' inboxes rather than the spam folder, a quarantine, or a silent drop — a per-recipient verdict computed from your authentication records, your bounce and complaint history, and your sending pattern.
Are SPF, DKIM, and DMARC all still required in 2026?
Yes. Receivers treat passing, aligned SPF/DKIM/DMARC as the baseline expectation for a trustworthy sender rather than a differentiator, and transactional mail that fails or sends unaligned gets filtered regardless of content quality. Alignment — the checks relating to the domain in the From header — is the piece senders most often get wrong while everything looks green on their own side.
How long should warmup take for a new sending domain?
Warmup is about the pattern, not a fixed number of days: start at a modest fraction of steady volume, step the volume up slowly, and gate each step on stable bounce and complaint rates. A young domain announcing itself with a full-volume blast reads as spam-pattern behavior to receivers, whatever the content.
What is the difference between a hard and a soft bounce?
A hard bounce is a permanent failure — typically a nonexistent recipient — and it should suppress the address from future sends immediately, because resending hard bounces is the clearest reputation poison. A soft bounce is a temporary failure (a full mailbox, a transient block) that deserves a bounded retry window and then suppression if it keeps failing.
What does Orbit automate, and what stays mine to run?
Orbit publishes and re-checks your SPF and DKIM records, shows authentication health with spam-score test sends and DMARC aggregate-report ingest, and suppresses hard bounces, complaints, and unsubscribes automatically. The DNS records on your domain, the DMARC policy posture, the warmup ramp, and the decision to act on a drifting health signal stay with you — they are tenant-owned controls, not platform-mandated claims.