Simple Mail Transfer Protocol

Simple Mail Transfer Protocol
Name	Simple Mail Transfer Protocol
Introduced	1982
Developer	Jonathan B. Postel
Status	Active
Type	Application layer protocol
Ports	25, 587, 465

Simple Mail Transfer Protocol is an Internet protocol used for the transmission of electronic mail between mail servers and from mail clients to mail servers. It originated in the early ARPANET era and has evolved through successive Request for Comments documents to support modern Internet messaging needs. Implementations interoperate across diverse operating systems and network architectures to deliver messages worldwide.

History

SMTP traces to the experimental mail systems of the ARPANET and formalization by Jonathan B. Postel in the early 1980s via RFC 821 and later revisions such as RFC 5321. Early usage overlapped with systems like Sendmail and UUCP gateways, influencing deployments at institutions such as MIT, Stanford University, and NASA. Subsequent milestones include the introduction of extended SMTP in RFC 1869, adoption of MIME standards from IETF working groups, and security-related enhancements prompted by incidents involving spam and phishing that affected providers like Yahoo! and Microsoft. Standards evolution has been driven by organizations including the Internet Engineering Task Force and archived through the RFC Editor.

Protocol Overview

The protocol operates as an application layer service in the TCP/IP suite, traditionally using Transmission Control Protocol sessions on port 25, with message submission and submission over TLS on ports 587 and 465 respectively. SMTP defines commands such as HELO, EHLO, MAIL FROM, RCPT TO, DATA and QUIT, enabling exchange between Postfix, Exim, Microsoft Exchange Server, and other mail transfer agent implementations. Extended SMTP mechanisms allow capability advertising and negotiation between peers such as Gmail and enterprise Exchange Online systems.

Architecture and Components

An SMTP deployment typically consists of mail transfer agents, mail delivery agents, and user agents. Common MTA software includes Sendmail, Postfix, and Exim, while delivery and storage are handled by systems like Dovecot and Courier Mail Server. SMTP relays route messages through network topologies involving autonomous systemes and rely on DNS components such as MX record entries and PTR records for routing and anti-abuse measures. Gateways interconnect with legacy systems including UUCP and with cloud providers such as Amazon Web Services and Google Cloud Platform.

Message Formats and Extensions

SMTP transmits messages encoded in ASCII command streams and carries payloads formatted per MIME to support attachments, multimedia, and character sets. Extensions standardized in RFC 5321 and RFC 5322 and later documents include SIZE, 8BITMIME, PIPELINING, STARTTLS, and SMTPUTF8 to handle larger messages, non-ASCII text, and encrypted sessions. Header fields such as From, To, Subject, Date, and Message-ID conform to syntax harmonized with IETF mailing list practices and interoperable with clients like Mozilla Thunderbird and Microsoft Outlook.

Security and Authentication

Security evolved with STARTTLS for opportunistic encryption and with mandatory TLS in many provider policies enacted by organizations like Google and Microsoft. Authentication mechanisms include SMTP AUTH methods like PLAIN, LOGIN, and CRAM-MD5, often integrated with SASL frameworks used by Cyrus SASL and Dovecot SASL. Anti-spam and anti-forgery measures encompass SPF, DKIM, and DMARC records deployed via Domain Name System to mitigate spoofing exploited in campaigns linked to groups exposed in cybersecurity incident reports. Rate limiting, greylisting, and reputation services provided by vendors such as Cisco and Cloudflare further reduce abuse.

Implementation and Operation

Deployments configure MTAs to accept submission on port 587 for authenticated clients and to relay between peering MTAs on port 25, using queuing, retry logic, and bounce handling implemented in Postfix and Exim. Operational considerations include log analysis with tools like Splunk and ELK Stack, certificate management from authorities including Let's Encrypt and DigiCert, and compliance with privacy regulations influenced by laws such as GDPR in the European Union. High-volume providers operate geographically distributed clusters and use techniques from content delivery network architectures to optimize delivery.

Standards and Development

Standards are maintained through the Internet Engineering Task Force and documented in Request for Comments publications; key RFCs span from early documents by Jonathan B. Postel to modern updates issued by working groups like MAIL and OPS. Open-source communities around projects such as Sendmail and Postfix contribute implementations and guidance, while commercial vendors and academic institutions participate in interoperability testing events and standards discussions hosted at IETF meetings and regional conferences.

Category:Internet protocols