Infrastructure
Separating marketing and transactional email streams
24 September 2025 · 7 min read
Transactional mail is expected, opened almost universally, and complained about almost never. Marketing mail is unsolicited in the moment, opened sometimes, and complained about occasionally. Sending both from the same identity averages those reputations — and the direction of the averaging is never in your favour.
Separation is a one-time piece of DNS and configuration work that protects the messages you cannot afford to lose.
Why sharing an identity is risky
If a promotional send collects complaints, the reputation damage attaches to the sending domain — the same domain carrying password resets, order confirmations and security alerts. A filtering decision made because of a campaign can prevent a customer logging in.
The reverse also holds: excellent transactional engagement masks a deteriorating marketing programme until the problem is large.
A subdomain structure that works
| Stream | Subdomain | Examples |
|---|---|---|
| Marketing | mail.example.com | Newsletters, campaigns, promotions |
| Transactional | notify.example.com | Receipts, resets, alerts, confirmations |
| Corporate | example.com | Human correspondence from staff |
What to configure for each
- Separate SPF and DKIM records per sending subdomain.
- A DMARC record at the organisational domain, with relaxed alignment so subdomains align.
- Separate suppression handling: unsubscribes apply to marketing, never to security or receipt mail.
- One-click unsubscribe headers on marketing mail only — transactional mail is exempt and should not carry them.
- Separate monitoring in Postmaster Tools, so each stream's reputation is read independently.
Keep the brand recognisable
Subdomain separation does not mean unfamiliar senders. Keep the From name consistent, keep the visible domain a recognisable subdomain of the brand, and keep the template identity shared. Recipients read the From name; providers read the domain.
Key takeaways
- Never let a marketing complaint rate endanger password resets.
- Use distinct subdomains with their own SPF and DKIM records.
- Unsubscribes apply to marketing streams only.
- Monitor each stream's reputation separately.
Sources
Put this into practice with HTsend
Everything in this guide is built into the platform: authenticate a sending domain, clean your list before you send, and watch inbox placement in real time.
