RefreshDocsConsole →

Guides

Separate bulk from transactional

Put newsletters on their own subdomain so a bad digest cannot hurt receipts and password resets.

Mailbox providers judge reputation per sending domain (and per IP). One newsletter with a stale list can push the complaint rate of the whole domain over the Gmail line. Then the password resets stop arriving too. The fix is structural:

  1. Add a bulk subdomain — in Domains → Add domain, add news.<your-domain> and publish and verify its records as usual.
  2. Set its stream to Bulk on the domain page, and set the apex domain to Transactional.
  3. Send newsletters from the subdomain — make it the from of broadcasts and of API sends with a bulk kind.
  4. Keep the subdomain warm — it starts at warm-up stage 0 (200 messages a day) and advances on clean days.
  5. Watch both — metrics and alert rules take a domain filter, so you can watch each domain on its own.

Receipts and alerts keep the apex domain. Digests get the subdomain. Each stands or falls on its own.