Password resets and newsletters use the same domain, is that a problem?
Transactional mail (invoices, resets) must always land. Marketing mail attracts spam complaints. Mixing on one domain lets marketing poison transactional.
Try this first
- 1Split per subdomain: tx.company.com for transactional, news.company.com for marketing
- 2Separate SPF, DKIM, DMARC per subdomain
- 3Separate ESP or pool per stream
- 4Monitor both subdomains independently
When to bring us in
If marketing pulls many complaints, also separate physically via different sending IP pool.
See also
- Our emails land in spam for some recipientsAlmost always an SPF, DKIM, or DMARC setting that is wrong or missing, or a sender name that mimics a well-known brand.
- Someone reports receiving phishing emails "from us"Read: spoofing. Someone is abusing your sender name, not necessarily your actual mailbox.
- An email bounces (NDR): delivery failedThe NDR text usually states the exact reason. Reading it is step one.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.