Internet Message Format

Internet Message Format
AlexanderVanLoon · CC BY-SA 3.0 · source
Name	Internet Message Format
Caption	Electronic mail header example
Developer	Ray Tomlinson; Paul Mockapetris; Jon Postel
Introduced	1982
Genre	Internet protocol
Standard	RFC 5322; RFC 822; RFC 822bis
Related	Simple Mail Transfer Protocol; Multipurpose Internet Mail Extensions; Domain Name System

Internet Message Format Internet Message Format is the standard defining the syntax and semantics of text messages used for electronic mail and related messaging systems. It evolved from early ARPANET practices and was formalized alongside development efforts involving USENIX, IETF, and researchers such as Ray Tomlinson, Jon Postel, and Paul Mockapetris. The specification underpins interoperability among implementations from vendors like Microsoft and Google and is referenced in standards maintained by organizations including IETF and Internet Society.

Overview and History

The format traces lineage to ARPANET experiments, RFC 822 and the editorial work of Jon Postel, with subsequent revisions captured by RFC 2822 and RFC 5322. Historical milestones include interactions with projects at MIT, Stanford University, and BBN Technologies and influenced messaging systems such as PLATO and Eudora. Standardization occurred amid broader Internet governance debates involving IETF working groups, ISOC advocacy, and vendor engagement from Sun Microsystems, IBM, and Microsoft.

Syntax and Structure

Messages are plain-text objects composed of a header and a body separated by a blank line; formal grammar uses Augmented Backus–Naur Form and ABNF productions first popularized in documents authored by Jon Postel and colleagues. The format specifies line-based rules including CRLF sequences derived from TELNET conventions and conventions that interfaced with systems from DEC, IBM, and Compaq. Parsing behavior affects interoperability among mail transfer agents such as Sendmail, Postfix, Exim, and commercial systems from Google and Microsoft Exchange.

Header Fields

Header fields are name–colon–value pairs; common fields include From, To, Subject, Date, Message-ID and Received, with tracing semantics that informed designs of SMTP and archival systems at institutions like USENIX and Stanford Linear Accelerator Center. Header folding rules and comments follow grammar constraints influenced by RFC 822 authorship and were debated in IETF mailing lists alongside contributors from Mozilla Foundation and Apple Inc.. Mail clients such as Mozilla Thunderbird, Microsoft Outlook, and Apple Mail render header metadata while server software like Sendmail and Postfix record Received entries for diagnostics.

Message Body and Encodings

The body carries the payload and originally assumed 7-bit US-ASCII compatible text, a constraint addressed by MIME (RFC 2045, RFC 2046, RFC 2047) to support UTF-8, attachments, and multipart content. Encoding schemes like Base64 and Quoted-Printable emerged from collaborative work by authors linked to IETF and projects at Hushmail and Procmail; interoperability relies on content-type parameters and charset declarations that interact with implementations from Google, Yahoo!, and Microsoft Exchange Server.

Transmission and Protocols

Internet Message Format is transported by protocols such as Simple Mail Transfer Protocol, with message submission and retrieval handled via Message Submission (RFC 6409), IMAP, and POP3. Gateways between systems required mappings for legacy formats used in X.400 exchanges and enterprise gateways in environments deploying Lotus Notes, Novell NetWare, and Sun Solaris mail solutions. Operational aspects involve DNS records including MX records and interactions with Domain Name System and routing influenced by large providers like Amazon Web Services, Cloudflare, and Akamai.

Security and Privacy Considerations

The format itself lacks built-in confidentiality and authentication, prompting adoption of end-to-end protocols and standards such as S/MIME, OpenPGP, DKIM, DMARC, and SPF. Threat models involving Spamhaus-tracked spam campaigns, phishing incidents against services like Gmail and Outlook.com, and malware distribution led to deployment of filtering systems developed by vendors including Symantec, McAfee, and Trend Micro. Legal and policy responses involved regulators such as the Federal Trade Commission and coordination with industry bodies like ICANN and IETF.

Implementations and Compatibility

Implementations span client software (e.g., Microsoft Outlook, Mozilla Thunderbird, Apple Mail, Evolution), servers (e.g., Sendmail, Postfix, Exim, Microsoft Exchange Server), and cloud services from Google Workspace, Microsoft 365, Yahoo! Mail, and enterprise platforms by IBM Lotus Domino. Compatibility challenges arise with legacy systems including DECnet integrations and archived formats from USENIX and BBN projects; interoperability testing is conducted by IETF working groups and standards organizations like IEEE. Continuous evolution addresses internationalization, mobile ecosystems led by Apple and Google, and compliance demands from institutions such as European Commission and National Institute of Standards and Technology.

Category:Internet standards