Infrastructure
Domains, DNS, MTAs, sending platforms, and the operational systems that move email at scale.
Definition
Email infrastructure is the operational stack that makes sending possible at scale: domains and DNS, IPs, MTAs or ESPs, feedback loops, and the monitoring that keeps the system honest.
Why it matters
Authentication and reputation assume a coherent infrastructure. Shared vs dedicated IPs, subdomain strategy, and DNS ownership determine how hard warmup and recovery will be when something goes wrong.
Core building blocks
Treat infrastructure as a designed system, not a pile of vendor defaults.
- Domains and subdomains that separate transactional, marketing, and corporate mail when needed.
- DNS zones you can change safely — MX, TXT, CNAME, and PTR where relevant.
- Sending platforms or MTAs with clear responsibility for queues, retries, and TLS.
- Observability: bounce classes, complaints, deferrals, and authentication failures.
Where to go from here
Revisit DNS and Warmup if you are standing up a new sender. Use Solve when a live symptom appears, and open a step-by-step workflow when you need an operational sequence. Return to the Learn hub anytime to restart the journey from Foundations.