Deliverability controls
Protect sending reputation with controls that can stop a bad send.
Authenticate owned domains, verify contacts, enforce suppression at send time, cap inbox and domain volume, pause on risk, and keep campaigns away from disconnected or ineligible inboxes.
Send-time suppression·Inbox and domain caps·Health-aware pause controls
Before the send
Make readiness a sequence of explicit checks.
Authenticate the domain
Use the Cloudflare-based setup path to prepare SPF, DKIM, and DMARC, then independently verify the published records.
Connect a business inbox
Send through a connected Google Workspace or Microsoft 365 inbox with usable credentials. Disposable SMTP identities are unsupported.
Verify the contact
Classify addresses through the platform default or a supported customer-owned verification provider before enrollment.
Apply suppression
Honor hard bounces, unsubscribes, complaints, manual suppressions, and matching email or domain block-list entries.
Check capacity
Enforce the lower of the configured inbox limit and its system ceiling, plus the workspace's daily domain limit.
Allocate an eligible sender
Choose only connected, send-ready inboxes from the campaign pool. An empty or ineligible pool pauses the campaign.
Suppression at send time
Recheck consent and risk when it matters.
A contact that was eligible yesterday may unsubscribe, bounce, complain, or be blocked today. MailSequence checks suppression again while preparing the outbound message.
- Hard-bounce and unsubscribe suppression
- Complaint and manual suppression
- Exact-email and whole-domain block lists
- Recent soft-bounce protection
Capacity and intervention
Limits are enforced during sending.
Inbox caps
Atomic send accounting prevents overlapping workers from claiming the same final capacity slot.
Domain caps
Daily domain volume is counted across inboxes so rotating senders does not bypass the shared ceiling.
Risk intervention
Rate-limit violations and complaint thresholds can pause inbox activity and raise an operator-visible alert.
Warmup adaptation
Warmup can cool down or pause on bounce, authentication, provider-limit, DNS, health, or sustained-failure signals.
Reply-aware sending
An associated inbound reply stops remaining sequence follow-up for that enrollment.
Visible outcomes
Track delivery, hard and soft bounces, replies, warmup, inbox health, and domain health without claiming guaranteed placement.
Run the deliverability checklist · Review provider sending limits · Know when to pause
FAQ
Frequently asked questions
Does MailSequence guarantee inbox placement?
No. Authentication, verification, suppression, warmup, limits, and health controls reduce avoidable operational risk, but domain history, list quality, copy, volume, provider policy, and recipient behavior still affect delivery.
When is suppression checked?
Suppression is enforced during enrollment and checked again when the outbound message is prepared. API imports and competitor migrations use the same suppression-aware contact path.
What happens after a hard bounce?
Hard-bounce suppression prevents later sends to the affected address. Reporting distinguishes hard and soft bounce outcomes.
What happens after a soft bounce?
A recent soft bounce makes the contact temporarily ineligible for that inbox. This avoids immediately retrying a recipient with a fresh transient failure.
Can inbox rotation bypass a domain limit?
No. Inbox and domain capacity are separate checks. The domain limit counts outbound messages across inboxes attached to that domain.
What happens when no sending inbox is eligible?
If the campaign pool is empty or contains no connected, SMTP-ready inbox, the campaign pauses instead of silently selecting an unrelated sender.
Build controls into the path of every send.
Authenticate the domain, verify the list, set conservative capacity, and launch one campaign you can inspect.