mailinapp
Documentation menu

Multiple domains & sender identities

Most accounts only ever verify one domain, but Settings supports more — a good fit if you send on behalf of several brands, or want a dedicated subdomain for transactional mail separate from marketing.

Multiple sending domains

The Settings → Domains page shows a list, not a single card: every verified (or in-progress) domain, with a default badge on whichever one new sends fall back to. Each entry expands into its own detail panel — DNS records, verification status, from-address, native-vs-SMTP toggle, and inbound receiving — completely independent of any other domain on the account. Set default switches which domain a send uses when nothing more specific applies; Disconnect removes a domain (refused if an enabled recurring schedule still depends on it as its only verified domain).

Your plan caps how many sending domains you can verify at once — see pricing.

Sender identities

A sender identity is a named {name, email, reply-to} scoped to one of your verified domains — Brevo calls the same concept "Senders." Create one from the Sender identities card once you have at least one verified domain: [email protected] for receipts, [email protected] for newsletters, both verified by the same underlying domain but showing a different name and address to recipients.

Where a sender identity applies

Four places resolve which identity (and therefore which domain) a send uses, in this order:

  1. A schedule's own sender, if the recurring send's creation form has one picked.
  2. A project's own sender, set in the Send panel's "Sender identity" picker.
  3. The audience list's default sender, set once on a contacts list under its settings — useful when every send to that list should come from the same identity without picking it per project.
  4. The account's default sending domain, if nothing more specific is set — unchanged, single-domain behavior.

The Send API accepts an explicit senderId the same way, or an ad-hoc from address (validated against any of the account's verified domains, not just the default one) for full per-call control.

Deleting a sender identity is never blocked — anything still referencing it just falls back to its domain's own default from-address, the same graceful-degrade behavior as a deleted lifecycle binding elsewhere in the product.