Email Architecture: From MUA to MTA and SMTP Protocols
The email system routes messages through multiple agents and relies on SMTP and DNS records for delivery and verification.
A mail user agent on a user's computer sends messages to a submission agent, which verifies the password before passing the data to a mail transfer agent. The MTA communicates with other servers to reach the receiving MTA, which then hands the message to a local delivery agent for storage. This structure dates back to around 1980, when organizations typically operated a single server. Most MTAs retry failed deliveries for five days using exponential backoff, with some systems increasing intervals from five minutes to one hour during outages.
Communication primarily uses the Simple Mail Transfer Protocol, where the first command is HELO or EHLO followed by the hostname. SMTP responses indicate success, continuation, temporary errors, or undeliverable status. Email uses dedicated MX DNS records, where smaller numbers indicate higher priority. Base SMTP trusts all senders, allowing anyone to impersonate others, which led to the first documented spam in 1978.
Modern security measures include SPF, which verifies the MAIL FROM address via a DNS TXT record. Large providers also require consistent forward and reverse DNS for the HELO hostname. Residential connections generally cannot send mail directly unless the user owns the address block or pays a provider to relay emails.
Sources
Every sentence of this story was checked against facts quoted from these articles. How we make the news
Spotted an error? Tell us
