Non-Internet email address

A wide variety of non-Internet email address formats were used in early email systems before the ubiquity of the john.smith@example.com form used by Internet mail systems since the 1980s - and a few are still used in specialised contexts.^{[citation needed]}

Single system

The earliest email addresses simply had to identify one user from another on one homogenous system, often a single host minicomputer or mainframe. They were therefore typically the user's login name on that system.

Examples of this style include:

ATS: 123
CompuServe: 432654,6564
MCI Mail: 373-1994
AOL: Steve Case

At a host

As computer systems became networked email addresses needed to be able to identify not only the user, but also which host or mail system they were on. Addresses of this type were used in a number of early email systems, including:

ARPANET: jim@washington
IBM Network Job Entry (NJE)
- TSO/E TRANSMIT: user_id, node.user_id, node/user_id, nickname, distribution list name, (addressee,...)^[1]
- VM SENDFILE: userid, userid AT YOURNODE, userid AT node, nickname^[2]
PROFS: userid@node
DECnet: host::user (e.g. DECWRL::WRL-TECHREPORTS)
cc:Mail: John Alexopoulos at MicroCircuits^[3]
MHS: Barry@MICROSOFT^[4]

Delivery path

Some email address schemes described the path through multiple hosts needed to deliver email. This worked well only if the first host given in the path was sufficiently well known for the sender's system to be able to contact it.

UUCP "bang path": reed!percival!bucket!lisag^[5] (example on a business card)

Hierarchical

Hierarchical addressing schemes are naturally able to expand. The modern Internet email address (e.g. john.smith@example.com), is of this type - but it was also used by a number of early systems, including:

Banyan VINES: Ed Hirsch@Faculty@Univ^[6]^[7]
Grey Book: USERID@UK.AC.CAM.ENG^[8]
FidoNET: lenz @ 2:331/113.1
Lotus Notes: Tyler Hamilton/Sales@Europe

Directory systems

In this type of system, there is no one unique address for a specific user, but instead a series of attributes, not all of which may be needed to identify the user. For convenience however, there may be recommended formats for sharing on business cards and similar contexts, such as:

X.400: C=no;ADMD= ;PRMD=uninett;O=sintef;OU=delab;S=Alvestrand;G=Harald^[a]^[9]

Notes

^ This is the "Labelled format" from RFC 1685.

References

^ "TRANSMIT command operands" (PDF). z/OS 2.5 TSO/E Command Reference (PDF). September 30, 2021. pp. 340–343. SA32-0975-50. Retrieved January 22, 2023.
^ "SENDFILE" (PDF). z/VM 7.2 CMS Commands and Utilities Reference (PDF). April 7, 2022. pp. 893–906. SC24-6260-03. Retrieved January 22, 2023.
^ "Lotus cc:Mail Release 8 Import/Export User's Guide" (PDF). Lotus Development Corporation. 1997.
^ "MHS: Correct Addressing format to DaVinci Email via MHS". Microsoft Support Knowledge Base. Retrieved 2007-01-15.
^ "bang path", The Jargon File
^ ...item@group@organisation...", 18 Sep 1995, p55, Network World
^ "Banyan VINES"
^ "History of Electronic Mail in CUED", University of Cambridge
^ "Short Hand X.400 Address Notation", 1989, RARE/CERN

[9] This is the "Labelled format" from RFC 1685.

[1] "TRANSMIT command operands" (PDF). z/OS 2.5 TSO/E Command Reference (PDF). September 30, 2021. pp. 340–343. SA32-0975-50. Retrieved January 22, 2023.

[2] "SENDFILE" (PDF). z/VM 7.2 CMS Commands and Utilities Reference (PDF). April 7, 2022. pp. 893–906. SC24-6260-03. Retrieved January 22, 2023.

[3] "Lotus cc:Mail Release 8 Import/Export User's Guide" (PDF). Lotus Development Corporation. 1997.

[4] "MHS: Correct Addressing format to DaVinci Email via MHS". Microsoft Support Knowledge Base. Retrieved 2007-01-15.

[5] "bang path", The Jargon File

[6] ...item@group@organisation...", 18 Sep 1995, p55, Network World

[7] "Banyan VINES"

[8] "History of Electronic Mail in CUED", University of Cambridge

[10] "Short Hand X.400 Address Notation", 1989, RARE/CERN

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[a]

[9]