tmailrGuides
Use a subdomain, unless you really mean it
23 July 2026 · 2 min read · TMailr
Whether to send from example.com or mail.example.com sounds like a naming preference. It decides what happens to the rest of your mail when one campaign goes wrong, and it is much easier to choose now than to change later.
The bare domain is the thing you cannot replace
Reputation attaches to the sending domain, and the bare domain is the one your people use for their own addresses, the one on your invoices, the one in every contract. If it acquires a bad reputation you cannot rotate away from it, and repairing domain reputation takes weeks.
Everything else can be abandoned. A subdomain is a DNS record, and if news.example.com becomes a liability you can stop using it. That optionality is the entire argument.
Split by consequence, not by department
The useful division is what happens if this stops arriving, not who owns the sending tool.
- Transactional: password resets, receipts, verification codes. If these stop, people cannot use your product.
- Notifications: alerts, digests, activity mail. Annoying to lose, not fatal.
- Marketing: campaigns, newsletters, anything with an unsubscribe link and a complaint rate.
Marketing generates the complaints, so marketing gets its own subdomain. Everything else can share, and if you only make one split, make that one.
Naming
Short and boring. mail, send, e, notify, news. It appears in the Return-Path, in DKIM signatures, and in the bounce addresses your recipients occasionally see, so it should look like infrastructure rather than a campaign name that will be stale in a year.
Avoid anything that reads like a redirect service or a tracking domain. Filters are suspicious of names that look disposable, which is unfair and true.
What each subdomain needs
- Its own DKIM key, so a compromise or a bad platform is contained.
- Its own SPF record, which keeps each one well under the ten-lookup limit rather than stacking every supplier on the parent.
- A DMARC record, or the parent policy applies to it, which is usually right but should be a decision rather than an accident.
- A reason to exist. Three subdomains for three tools is administration; two for two risk levels is architecture.
The From address still says your name
None of this changes what a reader sees, as long as the visible From: uses the subdomain and DKIM signs with it. billing@mail.example.com reads as you. What you have bought is the ability to lose mail.example.com without losing example.com, and that is worth the ten minutes it takes to set up.
More on guides
