Mailbase Deliverability Controls
A product guide to the deliverability controls Mailbase exposes across sending, analytics, compliance, and Settings.
Overview
Mailbase deliverability controls span sender-domain verification, suppression enforcement, unsubscribe headers, analytics filtering, bounce and complaint clustering, domain health, webhook debug logs, and safe operational logging.
Compliance Controls
Send-time validation blocks live marketing campaigns that are missing sender, reply-to, compliance footer, unsubscribe URL, or required merge-tag data. One-click unsubscribe headers are added where possible.
Suppression state is enforced across unsubscribed, bounced, complained, and manually suppressed contacts, with admin resubscribe controls and audit logs.
- Sender-domain verification
- Required unsubscribe URL
- List-Unsubscribe headers
- Suppression center
- Audit logs
Analytics Quality
Analytics can filter machine opens and clicks, group bounce and complaint reasons, show deliverability by provider, and compare campaign performance over selectable windows.
Settings includes domain health and UseSend webhook debug surfaces so teams can inspect DNS records, recent payloads, signature errors, and replay outcomes.
- Machine-open/click filtering
- Bounce and complaint clustering
- Provider deliverability
- Domain health dashboard
- Webhook debug and replay
Common Mistakes
- Choosing a tool before deciding who owns deliverability.
- Treating DNS authentication as a one-time checkbox instead of an operating baseline.
- Mixing product-critical transactional email with experimental marketing sends, with no clear boundary.
- Trusting headline metrics (like open rate) that privacy proxies now inflate.
Sources & Further Reading
Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.
Related guides
More on mailbase deliverability controls and the surrounding product workflow:
FAQ
Does Mailbase enforce suppressions at send time?
Yes. Unsubscribed, bounced, complained, and manually suppressed contacts are excluded from future sends.
Can I inspect webhook problems?
Yes. Mailbase stores redacted UseSend webhook debug logs and exposes replay controls.
Does analytics filter bots?
Mailbase classifies machine opens and clicks where possible so analytics can separate scanner activity from human engagement.