Transactional vs marketing email: why they must be kept apart

Two kinds of mail, two sets of rules

Transactional mail is triggered by something the recipient did and exists to complete it: receipts, password resets, shipping notices, security alerts. Marketing mail is sent on your initiative to advance your goals: newsletters, promotions, announcements.

The line matters because everything downstream differs. Commercial-email law generally requires unsubscribe mechanisms for marketing but not for transactional mail — an unsubscribable password reset would be absurd. Readers hold them to different standards too: a promotion can be ignored for a day; a reset that takes ten minutes is an outage.

Content decides the category — not your intent

A receipt with a promotional paragraph in it is, in the eyes of most regulators and every mailbox provider, marketing mail — which means the unsubscribe rules apply to it, and means the person who opted out of your newsletter arguably should not receive it. The label in your codebase does not transfer.

The practical rule: transactional mail carries the information the recipient's action requires, and nothing else. The moment an upsell block creeps into the receipt template, you have converted your most-trusted mail stream into your least-trusted one.

Separate them at the subdomain

Reputation attaches to sending domains. Send receipts from mail.example.com and campaigns from news.example.com and each stream builds its own standing — a campaign that goes badly cannot drag the password resets into the spam folder with it. On one shared domain, it can and does.

The same isolation applies to suppression logic: an unsubscribe applies to the marketing stream, a hard bounce applies to both, and a spam complaint should stop everything to that address. Three different scopes — which only work if the streams are distinguishable in the first place.

What this looks like in practice

• Two subdomains, both fully authenticated. SPF, DKIM and DMARC on each. The isolation only exists if each stream carries its own aligned identity.
• Transactional never throttled behind bulk. Queueing must let a reset overtake a million-recipient campaign. If your platform cannot promise that, the streams are separate in name only.
• Different alerting. A 2% dip in campaign opens is Tuesday; a 2% failure rate on password resets is an incident. Monitor them as the different things they are.
• One shared complaint suppression. Category separation is about content and reputation — not a licence to keep mailing someone who reported you from the other stream.

Common questions

Keep reading

• SMTP relay or email API — which should you use?
• How to reduce spam complaints
• SPF, DKIM and DMARC, explained in plain English