Mailbase
Start free
DeliverabilityUpdated 2026-05-25

Sender Domains And Verification

Connect sender domains, understand hosted versus BYO useSend sending, and keep SPF, DKIM, and DMARC status visible in Mailbase.

Canonical: /docs/sender-domains

Delivery Modes

  • Hosted Mailbase plans use Mailbase-managed sending after sender-domain verification.
  • The BYO useSend plan connects a user-managed useSend instance, API URL, API key, default sender, and webhook secret.
  • A workspace slug address can help onboarding, but production campaigns should use a verified sender domain.

Verify A Domain

  • Add and verify the domain in the active useSend provider first.
  • Publish the provider's SPF, DKIM, and DMARC DNS records at your DNS host.
  • Open Settings, then Sender emails, and refresh domain health.
  • Add a sender address using any local part on a connected verified domain.

Workspace Safety

Mailbase lists only provider domains already connected to sender emails in the current workspace. When adding a sender, the selected provider domain must match the email domain and must belong to the workspace.

If the workspace cannot be resolved, Mailbase fails instead of guessing a workspace or falling back to a first database row.

Domain Health

  • Settings shows provider verification state and DNS record details when useSend returns them.
  • Cached sender status keeps the UI useful if the provider is temporarily unavailable.
  • Delivery analytics also surface provider health rates, bounce clusters, and complaint clusters for follow-up.

Related Docs

OperationsUpdated 2026-05-25
Cron setup
Configure the recurring Mailbase cron endpoints that enqueue scheduled campaigns, process durable send-job batches, and run due workflow steps.
ComplianceUpdated 2026-05-25
Unsubscribe compliance
How Mailbase signs unsubscribe links, enforces suppression states, adds List-Unsubscribe headers, and keeps marketing sends compliant.
Developer APIUpdated 2026-05-25
API tokens
Create, scope, rotate, and verify Mailbase API tokens for workspace-safe backend integrations.
MCPUpdated 2026-05-25
MCP OAuth
Connect Claude, Cursor, Codex, or another MCP client to Mailbase with OAuth-scoped workspace access.
IntegrationsUpdated 2026-05-25
No-code integrations
Connect Mailbase to Zapier, Make, or n8n with REST Hooks: subscribe a callback URL to an event, sample real payloads while you build, and unsubscribe when the automation is turned off.