text:
Email
From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article is about the communications medium. For the former manufacturing conglomerate, see Email Limited.
"Inbox" redirects here. For the Google product, see Inbox by Gmail.
This screenshot shows the "Inbox" page of an email client, where users can see new emails and take actions, such as reading, deleting, saving, or responding to these messages
The at sign, a part of every SMTP email address[1]
Electronic mail (email or e-mail) is a method of exchanging messages ("mail") between people using electronic devices. Email first entered limited use in the 1960s and by the mid-1970s had taken the form now recognized as email. Email operates across computer networks, which today is primarily the Internet. Some early email systems required the author and the recipient to both be online at the same time, in common with instant messaging. Today's email systems are based on a store-and-forward model. Email servers accept, forward, deliver, and store messages. Neither the users nor their computers are required to be online simultaneously; they need to connect only briefly, typically to a mail server or a webmail interface, for as long as it takes to send or receive messages.
Originally an ASCII text-only communications medium, Internet email was extended by Multipurpose Internet Mail Extensions (MIME) to carry text in other character sets and multimedia content attachments. International email, with internationalized email addresses using UTF-8, has been standardized, but as of 2017 it has not been widely adopted.[2]
The history of modern Internet email services reaches back to the early ARPANET, with standards for encoding email messages published as early as 1973 (RFC 561). An email message sent in the early 1970s looks very similar to a basic email sent today. Email had an important role in creating the Internet,[3] and the conversion from ARPANET to the Internet in the early 1980s produced the core of the current services.
Contents
[hide]
1 Terminology
2 Origin
3 Operation
4 Message format
4.1 Message header
4.1.1 Header fields
4.2 Message body
4.2.1 Content encoding
4.2.2 Plain text and HTML
5 Servers and client applications
5.1 Filename extensions
5.2 URI scheme mailto
6 Types
6.1 Web-based email
6.2 POP3 email services
6.3 IMAP email servers
6.4 MAPI email servers
7 Uses
7.1 Business and organizational use
7.1.1 Email marketing
7.2 Personal use
7.2.1 Personal computer
7.2.2 Mobile
7.2.3 Declining use among young people
8 Issues
8.1 Attachment size limitation
8.2 Information overload
8.3 Spam
8.4 Malware
8.5 Email spoofing
8.6 Email bombing
8.7 Privacy concerns
8.8 Flaming
8.9 Email bankruptcy
8.10 Internationalization
8.11 Tracking of sent mail
9 See also
10 References
11 Further reading
12 External links
Terminology[edit]
Historically, the term electronic mail was used generically for any electronic document transmission. For example, several writers in the early 1970s used the term to describe fax document transmission.[4][5] As a result, it is difficult to find the first citation for the use of the term with the more specific meaning it has today.
Electronic mail has been most commonly called email or e-mail since around 1993,[6] but variations of the spelling have been used:
email is the most common form used online, and is required by IETF Requests for Comments (RFC) and working groups[7] and increasingly by style guides.[8][9] This spelling also appears in most dictionaries.[10][11][12][13][14][15][16]
e-mail is the format that sometimes appears in edited, published American English and British English writing as reflected in the Corpus of Contemporary American English data,[17] but is falling out of favor in some style guides.[9][18]
mail was the form used in the original protocol standard, RFC 524.[19] The service is referred to as mail, and a single piece of electronic mail is called a message.[20][21]
EMail is a traditional form that has been used in RFCs for the "Author's Address"[20][21] and is expressly required "for historical reasons".[22]
E-mail is sometimes used, capitalizing the initial E as in similar abbreviations like E-piano, E-guitar, A-bomb, and H-bomb.[23]
An Internet e-mail consists[24] of an envelope and content; the content in turn consists[25] of a header and a body.
Origin[edit]
Main article: History of email
Computer-based mail and messaging became possible with the advent of time-sharing computers in the early 1960s, and informal methods of using shared files to pass messages were soon expanded into the first mail systems. Most developers of early mainframes and minicomputers developed similar, but generally incompatible, mail applications. Over time, a complex web of gateways and routing systems linked many of them. Many US universities were part of the ARPANET (created in the late 1960s), which aimed at software portability between its systems. That portability helped make the Simple Mail Transfer Protocol (SMTP) increasingly influential.
For a time in the late 1980s and early 1990s, it seemed likely that either a proprietary commercial system or the X.400 email system, part of the Government Open Systems Interconnection Profile (GOSIP), would predominate. However, once the final restrictions on carrying commercial traffic over the Internet ended in 1995,[26][27] a combination of factors made the current Internet suite of SMTP, POP3 and IMAP email protocols the standard.
Operation[edit]
The diagram to the right shows a typical sequence of events[28] that takes place when sender Alice transmits a message using a mail user agent (MUA) addressed to the email address of the recipient.
Email operation
The MUA formats the message in email format and uses the submission protocol, a profile of the Simple Mail Transfer Protocol (SMTP), to send the message content to the local mail submission agent (MSA), in this case smtp.a.org.
The MSA determines the destination address provided in the SMTP protocol (not from the message header), in this case bob@b.org. The part before the @ sign is the local part of the address, often the username of the recipient, and the part after the @ sign is a domain name. The MSA resolves a domain name to determine the fully qualified domain name of the mail server in the Domain Name System (DNS).
The DNS server for the domain b.org (ns.b.org) responds with any MX records listing the mail exchange servers for that domain, in this case mx.b.org, a message transfer agent (MTA) server run by the recipient's ISP.[29]
smtp.a.org sends the message to mx.b.org using SMTP. This server may need to forward the message to other MTAs before the message reaches the final message delivery agent (MDA).
The MDA delivers it to the mailbox of user bob.
Bob's MUA picks up the message using either the Post Office Protocol (POP3) or the Internet Message Access Protocol (IMAP).
In addition to this example, alternatives and complications exist in the email system:
Alice or Bob may use a client connected to a corporate email system, such as IBM Lotus Notes or Microsoft Exchange. These systems often have their own internal email format and their clients typically communicate with the email server using a vendor-specific, proprietary protocol. The server sends or receives email via the Internet through the product's Internet mail gateway which also does any necessary reformatting. If Alice and Bob work for the same company, the entire transaction may happen completely within a single corporate email system.
Alice may not have a MUA on her computer but instead may connect to a webmail service.
Alice's computer may run its own MTA, so avoiding the transfer at step 1.
Bob may pick up his email in many ways, for example logging into mx.b.org and reading it directly, or by using a webmail service.
Domains usually have several mail exchange servers so that they can continue to accept mail even if the primary is not available.
Many MTAs used to accept messages for any recipient on the Internet and do their best to deliver them. Such MTAs are called open mail relays. This was very important in the early days of the Internet when network connections were unreliable.[30][31] However, this mechanism proved to be exploitable by originators of unsolicited bulk email and as a consequence open mail relays have become rare,[32] and many MTAs do not accept messages from open mail relays.
Message format [edit]
The Internet email message format is now defined by RFC 5322, with encoding of non-ASCII data and multimedia content attachments being defined in RFC 2045 through RFC 2049, collectively called Multipurpose Internet Mail Extensions or MIME. RFC 5322 replaced the earlier RFC 2822 in 2008, and in turn RFC 2822 in 2001 replaced RFC 822 – which had been the standard for Internet email for nearly 20 years. Published in 1982, RFC 822 was based on the earlier RFC 733 for the ARPANET.[33]
Internet email messages consist of two major sections, the message header and the message body, collectively known as content.[34][35] The header is structured into fields such as From, To, CC, Subject, Date, and other information about the email. In the process of transporting email messages between systems, SMTP communicates delivery parameters and information using message header fields. The body contains the message, as unstructured text, sometimes containing a signature block at the end. The header is separated from the body by a blank line.
Message header[edit]
Each message has exactly one header, which is structured into fields. Each field has a name and a value. RFC 5322 specifies the precise syntax.
Informally, each line of text in the header that begins with a printable character begins a separate field. The field name starts in the first character of the line and ends before the separator character ":". The separator is then followed by the field value (the "body" of the field). The value is continued onto subsequent lines if those lines have a space or tab as their first character. Field names and values are restricted to 7-bit ASCII characters. Some non-ASCII values may be represented using MIME encoded words.
Header fields[edit]
Email header fields can be multi-line, and each line should be at most 78 characters long and in no event more than 998 characters long.[36] Header fields defined by RFC 5322 can only contain US-ASCII characters; for encoding characters in other sets, a syntax specified in RFC 2047 can be used.[37] Recently the IETF EAI working group has defined some standards track extensions,[38][39] replacing previous experimental extensions, to allow UTF-8 encoded Unicode characters to be used within the header. In particular, this allows email addresses to use non-ASCII characters. Such addresses are supported by Google and Microsoft products, and promoted by some governments.[40]
The message header must include at least the following fields:[41][42]
From: The email address, and optionally the name of the author(s). In many email clients not changeable except through changing account settings.
Date: The local time and date when the message was written. Like the From: field, many email clients fill this in automatically when sending. The recipient's client may then display the time in the format and time zone local to them.
RFC 3864 describes registration procedures for message header fields at the IANA; it provides for permanent and provisional field names, including also fields defined for MIME, netnews, and HTTP, and referencing relevant RFCs. Common header fields for email include:[43]
To: The email address(es), and optionally name(s) of the message's recipient(s). Indicates primary recipients (multiple allowed), for secondary recipients see Cc: and Bcc: below.
Subject: A brief summary of the topic of the message. Certain abbreviations are commonly used in the subject, including "RE:" and "FW:".
Cc: Carbon copy; Many email clients will mark email in one's inbox differently depending on whether they are in the To: or Cc: list. (Bcc: Blind carbon copy; addresses are usually only specified during SMTP delivery, and not usually listed in the message header.)
Content-Type: Information about how the message is to be displayed, usually a MIME type.
Precedence: commonly with values "bulk", "junk", or "list"; used to indicate that automated "vacation" or "out of office" responses should not be returned for this mail, e.g. to prevent vacation notices from being sent to all other subscribers of a mailing list. Sendmail uses this field to affect prioritization of queued email, with "Precedence: special-delivery" messages delivered sooner. With modern high-bandwidth networks, delivery priority is less of an issue than it once was. Microsoft Exchange respects a fine-grained automatic response suppression mechanism, the X-Auto-Response-Suppress field.[44]
Message-ID: Also an automatically generated field; used to prevent multiple delivery and for reference in In-Reply-To: (see below).
In-Reply-To: Message-ID of the message that this is a reply to. Used to link related messages together. This field only applies for reply messages.
References: Message-ID of the message that this is a reply to, and the message-id of the message the previous reply was a reply to, etc.
Reply-To: Address that should be used to reply to the message.
Sender: Address of the actual sender acting on behalf of the author listed in the From: field (secretary, list manager, etc.).
Archived-At: A direct link to the archived form of an individual email message.
Note that the To: field is not necessarily related to the addresses to which the message is delivered. The actual delivery list is supplied separately to the transport protocol, SMTP, which may or may not originally have been extracted from the header content. The "To:" field is similar to the addressing at the top of a conventional letter which is delivered according to the address on the outer envelope. In the same way, the "From:" field does not have to be the real sender of the email message. Some mail servers apply email authentication systems to messages being relayed. Data pertaining to server's activity is also part of the header, as defined below.
SMTP defines the trace information of a message, which is also saved in the header using the following two fields:[45]
Received: when an SMTP server accepts a message it inserts this trace record at the top of the header (last to first).
Return-Path: when the delivery SMTP server makes the final delivery of a message, it inserts this field at the top of the header.
Other fields that are added on top of the header by the receiving server may be called trace fields, in a broader sense.[46]
Authentication-Results: when a server carries out authentication checks, it can save the results in this field for consumption by downstream agents.[47]
Received-SPF: stores results of SPF checks in more detail than Authentication-Results.[48]
Auto-Submitted: is used to mark automatically generated messages.[49]
VBR-Info: claims VBR whitelisting[50]
Message body[edit]
Content encoding[edit]
Internet email was originally designed for 7-bit ASCII.[51] Most email software is 8-bit clean but must assume it will communicate with 7-bit servers and mail readers. The MIME standard introduced character set specifiers and two content transfer encodings to enable transmission of non-ASCII data: quoted printable for mostly 7-bit content with a few characters outside that range and base64 for arbitrary binary data. The 8BITMIME and BINARY extensions were introduced to allow transmission of mail without the need for these encodings, but many mail transport agents still do not support them fully. In some countries, several encoding schemes coexist; as the result, by default, the message in a non-Latin alphabet language appears in non-readable form (the only exception is coincidence, when the sender and receiver use the same encoding scheme). Therefore, for international character sets, Unicode is growing in popularity.[citation needed]
Plain text and HTML[edit]
Most modern graphic email clients allow the use of either plain text or HTML for the message body at the option of the user. HTML email messages often include an automatically generated plain text copy as well, for compatibility reasons. Advantages of HTML include the ability to include in-line links and images, set apart previous messages in block quotes, wrap naturally on any display, use emphasis such as underlines and italics, and change font styles. Disadvantages include the increased size of the email, privacy concerns about web bugs, abuse of HTML email as a vector for phishing attacks and the spread of malicious software.[52]
Some web-based mailing lists recommend that all posts be made in plain-text, with 72 or 80 characters per line[53][54] for all the above reasons, but also because they have a significant number of readers using text-based email clients such as Mutt. Some Microsoft email clients allow rich formatting using their proprietary Rich Text Format (RTF), but this should be avoided unless the recipient is guaranteed to have a compatible email client.[55]
Servers and client applications[edit]
The interface of an email client, Thunderbird.
Messages are exchanged between hosts using the Simple Mail Transfer Protocol with software programs called mail transfer agents (MTAs); and delivered to a mail store by programs called mail delivery agents (MDAs, also sometimes called local delivery agents, LDAs). Accepting a message obliges an MTA to deliver it,[56] and when a message cannot be delivered, that MTA must send a bounce message back to the sender, indicating the problem.
Users can retrieve their messages from servers using standard protocols such as POP or IMAP, or, as is more likely in a large corporate environment, with a proprietary protocol specific to Novell Groupwise, Lotus Notes or Microsoft Exchange Servers. Programs used by users for retrieving, reading, and managing email are called mail user agents (MUAs).
Mail can be stored on the client, on the server side, or in both places. Standard formats for mailboxes include Maildir and mbox. Several prominent email clients use their own proprietary format and require conversion software to transfer email between them. Server-side storage is often in a proprietary format but since access is through a standard protocol such as IMAP, moving email from one server to another can be done with any MUA supporting the protocol.
Many current email users do not run MTA, MDA or MUA programs themselves, but use a web-based email platform, such as Gmail, Hotmail, or Yahoo! Mail, that performs the same tasks.[57] Such webmail interfaces allow users to access their mail with any standard web browser, from any computer, rather than relying on an email client.
Filename extensions[edit]
Upon reception of email messages, email client applications save messages in operating system files in the file system. Some clients save individual messages as separate files, while others use various database formats, often proprietary, for collective storage. A historical standard of storage is the mbox format. The specific format used is often indicated by special filename extensions:
eml
Used by many email clients including Novell GroupWise, Microsoft Outlook Express, Lotus notes, Windows Mail, Mozilla Thunderbird, and Postbox. The files contain the email contents as plain text in MIME format, containing the email header and body, including attachments in one or more of several formats.
emlx
Used by Apple Mail.
msg
Used by Microsoft Office Outlook and OfficeLogic Groupware.
mbx
Used by Opera Mail, KMail, and Apple Mail based on the mbox format.
Some applications (like Apple Mail) leave attachments encoded in messages for searching while also saving separate copies of the attachments. Others separate attachments from messages and save them in a specific directory.
URI scheme mailto[edit]
Main article: mailto
The URI scheme, as registered with the IANA, defines the mailto: scheme for SMTP email addresses. Though its use is not strictly defined, URLs of this form are intended to be used to open the new message window of the user's mail client when the URL is activated, with the address as defined by the URL in the To: field.[58]
Types[edit]
Web-based email[edit]
Main article: Webmail
Many email providers have a web-based email client (e.g. AOL Mail, Gmail, Outlook.com, Hotmail and Yahoo! Mail). This allows users to log into the email account by using any compatible web browser to send and receive their email. Mail is typically not downloaded to the client, so can't be read without a current Internet connection.
POP3 email services[edit]
The Post Office Protocol 3 (POP3) is a mail access protocol used by a client application to read messages from the mail server. Received messages are often deleted from the server. POP supports simple download-and-delete requirements for access to remote mailboxes (termed maildrop in the POP RFC's).[59]
IMAP email servers[edit]
The Internet Message Access Protocol (IMAP) provides features to manage a mailbox from multiple devices. Small portable devices like smartphones are increasingly used to check email while travelling, and to make brief replies, larger devices with better keyboard access being used to reply at greater length. IMAP shows the headers of messages, the sender and the subject and the device needs to request to download specific messages. Usually mail is left in folders in the mail server.
MAPI email servers[edit]
Messaging Application Programming Interface (MAPI) is used by Microsoft Outlook to communicate to Microsoft Exchange Server - and to a range of other email server products such as Axigen Mail Server, Kerio Connect, Scalix, Zimbra, HP OpenMail, IBM Lotus Notes, Zarafa, and Bynari where vendors have added MAPI support to allow their products to be accessed directly via Outlook.
Uses[edit]
This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (November 2007) (Learn how and when to remove this template message)
Business and organizational use[edit]
Email has been widely accepted by business, governments and non-governmental organizations in the developed world, and it is one of the key parts of an 'e-revolution' in workplace communication (with the other key plank being widespread adoption of highspeed Internet). A sponsored 2010 study on workplace communication found 83% of U.S. knowledge workers felt email was critical to their success and productivity at work.[60]
It has some key benefits to business and other organizations, including:
Facilitating logistics
Much of the business world relies on communications between people who are not physically in the same building, area, or even country; setting up and attending an in-person meeting, telephone call, or conference call can be inconvenient, time-consuming, and costly. Email provides a method of exchanging information between two or more people with no set-up costs and that is generally far less expensive than a physical meeting or phone call.
Helping with synchronisation
With real time communication by meetings or phone calls, participants must work on the same schedule, and each participant must spend the same amount of time in the meeting or call. Email allows asynchrony: each participant may control their schedule independently.
Reducing cost
Sending an email is much less expensive than sending postal mail, or long distance telephone calls, telex or telegrams.
Increasing speed
Much faster than most of the alternatives.
Creating a "written" record
Unlike a telephone or in-person conversation, email by its nature creates a detailed written record of the communication, the identity of the sender(s) and recipient(s) and the date and time the message was sent. In the event of a contract or legal dispute, saved emails can be used to prove that an individual was advised of certain issues, as each email has the date and time recorded on it.
Email marketing[edit]
Email marketing via "opt-in" is often successfully used to send special sales offerings and new product information.[61] Depending on the recipient's culture,[62] email sent without permission—such as an "opt-in"—is likely to be viewed as unwelcome "email spam".
Personal use[edit]
Personal computer[edit]
Many users access their personal email from friends and family members using a personal computer in their house or apartment.
Mobile[edit]
Email has become used on smartphones and on all types of computers. Mobile "apps" for email increase accessibility to the medium for users who are out of their home. While in the earliest years of email, users could only access email on desktop computers, in the 2010s, it is possible for users to check their email when they are away from home, whether they are across town or across the world. Alerts can also be sent to the smartphone or other device to notify them immediately of new messages. This has given email the ability to be used for more frequent communication between users and allowed them to check their email and write messages throughout the day. As of 2011[update], there were approximately 1.4 billion email users worldwide and 50 billion non-spam emails that were sent daily.[63]
Individuals often check email on smartphones for both personal and work-related messages. It was found that US adults check their email more than they browse the web or check their Facebook accounts, making email the most popular activity for users to do on their smartphones. 78% of the respondents in the study revealed that they check their email on their phone.[64] It was also found that 30% of consumers use only their smartphone to check their email, and 91% were likely to check their email at least once per day on their smartphone. However, the percentage of consumers using email on smartphone ranges and differs dramatically across different countries. For example, in comparison to 75% of those consumers in the US who used it, only 17% in India did.[65]
Declining use among young people[edit]
As of 2010, the number of Americans visiting email web sites had fallen 6 percent after peaking in November 2009. For persons 12 to 17, the number was down 18 percent. Young people preferred instant messaging, texting and social media, and email was not designed for them anyway. Technology writer Matt Richtel said in The New York Times that email was like the VCR, vinyl records and film cameras--no longer cool and something older people do.[66][67]
A 2015 survey of Android users showed that persons 13 to 24 used messaging apps 3.5 times as much as those over 45, and were far less likely to use email.[68]
Issues[edit]
This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (October 2016) (Learn how and when to remove this template message)
Attachment size limitation[edit]
Main article: Email attachment
Email messages may have one or more attachments, which are additional files that are appended to the email. Typical attachments include Microsoft Word documents, pdf documents and scanned images of paper documents. In principle there is no technical restriction on the size or number of attachments, but in practice email clients, servers and Internet service providers implement various limitations on the size of files, or complete email - typically to 25MB or less.[69][70][71] Furthermore, due to technical reasons, attachment sizes as seen by these transport systems can differ to what the user sees,[72] which can be confusing to senders when trying to assess whether they can safely send a file by email. Where larger files need to be shared, file hosting services of various sorts are available; and generally suggested.[73][74] Some large files, such as digital photos, color presentations and video or music files are too large for some email systems.[75]
Information overload[edit]
The ubiquity of email for knowledge workers and "white collar" employees has led to concerns that recipients face an "information overload" in dealing with increasing volumes of email.[76][77] With the growth in mobile devices, by default employees may also receive work-related emails outside of their working day. This can lead to increased stress, decreased satisfaction with work, and some observers even argue it could have a significant negative economic effect,[78] as efforts to read the many emails could reduce productivity.
Spam[edit]
Main article: Email spam
Email "spam" is the term used to describe unsolicited bulk email. The low cost of sending such email meant that by 2003 up to 30% of total email traffic was already spam.[79][80][81] and was threatening the usefulness of email as a practical tool. The US CAN-SPAM Act of 2003 and similar laws elsewhere[82] had some impact, and a number of effective anti-spam techniques now largely mitigate the impact of spam by filtering or rejecting it for most users,[83] but the volume sent is still very high—and increasingly consists not of advertisements for products, but malicious content or links.[84]
Malware[edit]
A range of malicious email types exist. These range from various types of email scams, including "social engineering" scams such as advance-fee scam "Nigerian letters", to phishing, email bombardment and email worms.
Email spoofing[edit]
Main article: Email spoofing
Email spoofing occurs when the email message header is designed to make the message appear to come from a known or trusted source. Email spam and phishing methods typically use spoofing to mislead the recipient about the true message origin. Email spoofing may be done as a prank, or as part of a criminal effort to defraud an individual or organization. An example of a potentially fraudulent email spoofing is if an individual creates an email which appears to be an invoice from a major company, and then sends it to one or more recipients. In some cases, these fraudulent emails incorporate the logo of the purported organization and even the email address may appear legitimate.
Email bombing[edit]
Main article: Email bomb
Email bombing is the intentional sending of large volumes of messages to a target address. The overloading of the target email address can render it unusable and can even cause the mail server to crash.
Privacy concerns[edit]
Main article: Email privacy
Today it can be important to distinguish between Internet and internal email systems. Internet email may travel and be stored on networks and computers without the sender's or the recipient's control. During the transit time it is possible that third parties read or even modify the content. Internal mail systems, in which the information never leaves the organizational network, may be more secure, although information technology personnel and others whose function may involve monitoring or managing may be accessing the email of other employees.
Email privacy, without some security precautions, can be compromised because:
email messages are generally not encrypted.
email messages have to go through intermediate computers before reaching their destination, meaning it is relatively easy for others to intercept and read messages.
many Internet Service Providers (ISP) store copies of email messages on their mail servers before they are delivered. The backups of these can remain for up to several months on their server, despite deletion from the mailbox.
the "Received:"-fields and other information in the email can often identify the sender, preventing anonymous communication.
web bugs invisibly embedded in email content can alert the sender of any email whenever an email is read, or re-read, and from which IP address. It can also reveal whether an email was read on a smartphone or a PC, or Apple Mac device via the user agent string.
There are cryptography applications that can serve as a remedy to one or more of the above. For example, Virtual Private Networks or the Tor anonymity network can be used to encrypt traffic from the user machine to a safer network while GPG, PGP, SMEmail,[85] or S/MIME can be used for end-to-end message encryption, and SMTP STARTTLS or SMTP over Transport Layer Security/Secure Sockets Layer can be used to encrypt communications for a single mail hop between the SMTP client and the SMTP server.
Additionally, many mail user agents do not protect logins and passwords, making them easy to intercept by an attacker. Encrypted authentication schemes such as SASL prevent this. Finally, attached files share many of the same hazards as those found in peer-to-peer filesharing. Attached files may contain trojans or viruses.
Flaming[edit]
Flaming occurs when a person sends a message (or many messages) with angry or antagonistic content. The term is derived from the use of the word "incendiary" to describe particularly heated email discussions. The ease and impersonality of email communications mean that the social norms that encourage civility in person or via telephone do not exist and civility may be forgotten.[86]
Email bankruptcy[edit]
Main article: Email bankruptcy
Also known as "email fatigue", email bankruptcy is when a user ignores a large number of email messages after falling behind in reading and answering them. The reason for falling behind is often due to information overload and a general sense there is so much information that it is not possible to read it all. As a solution, people occasionally send a "boilerplate" message explaining that their email inbox is full, and that they are in the process of clearing out all the messages. Harvard University law professor Lawrence Lessig is credited with coining this term, but he may only have popularized it.[87]
Internationalization[edit]
Originally Internet email was completely ASCII text-based. MIME now allows body content text and some header content text in international character sets, but other headers and email addresses using UTF-8, while standardized[88] have yet to be widely adopted.[2][89]
Further information: International email and Email address § Internationalization
Tracking of sent mail[edit]
The original SMTP mail service provides limited mechanisms for tracking a transmitted message, and none for verifying that it has been delivered or read. It requires that each mail server must either deliver it onward or return a failure notice (bounce message), but both software bugs and system failures can cause messages to be lost. To remedy this, the IETF introduced Delivery Status Notifications (delivery receipts) and Message Disposition Notifications (return receipts); however, these are not universally deployed in production. (A complete Message Tracking mechanism was also defined, but it never gained traction; see RFCs 3885[90] through 3888.[91])
Many ISPs now deliberately disable non-delivery reports (NDRs) and delivery receipts due to the activities of spammers:
Delivery Reports can be used to verify whether an address exists and if so, this indicates to a spammer that it is available to be spammed.
If the spammer uses a forged sender email address (email spoofing), then the innocent email address that was used can be flooded with NDRs from the many invalid email addresses the spammer may have attempted to mail. These NDRs then constitute spam from the ISP to the innocent user.
In the absence of standard methods, a range of system based around the use of web bugs have been developed. However, these are often seen as underhand or raising privacy concerns,[92][93][94] and only work with email clients that support rendering of HTML. Many mail clients now default to not showing "web content".[95] Webmail providers can also disrupt web bugs by pre-caching images.[96]
See also[edit]
Anonymous remailer
Anti-spam techniques
biff
Bounce message
Comparison of email clients
Dark Mail Alliance
Disposable email address
E-card
Electronic mailing list
Email art
Email authentication
Email digest
Email encryption
Email hosting service
Email storm
Email tracking
HTML email
Information overload
Internet fax
Internet mail standards
List of email subject abbreviations
MCI Mail
Netiquette
Posting style
Privacy-enhanced Electronic Mail
Push email
RSS
Telegraphy
Unicode and email
Usenet quoting
Webmail, Comparison of webmail providers
X-Originating-IP
X.400
Yerkish
References[edit]
Jump up ^ "RFC 5321 – Simple Mail Transfer Protocol". Network Working Group. Archived from the original on 16 January 2015. Retrieved 19 January 2015.
^ Jump up to: a b "DataMail: World's first free linguistic email service supports eight India languages". Archived from the original on 2016-10-22.
Jump up ^ (Partridge 2008)
Jump up ^ Ron Brown, Fax invades the mail market, New Scientist Archived 2016-05-09 at the Wayback Machine., Vol. 56, No. 817 (Oct., 26, 1972), pages 218–221.
Jump up ^ Herbert P. Luckett, What's News: Electronic-mail delivery gets started, Popular Science Archived 2016-04-30 at the Wayback Machine., Vol. 202, No. 3 (March 1973); page 85
Jump up ^ Google Ngram Viewer. Books.google.com. Archived from the original on 2013-05-16. Retrieved 2013-04-21.
Jump up ^ "RFC Editor Terms List". IETF. Archived from the original on 2013-12-28. This is suggested by the RFC Document Style Guide Archived 2015-04-24 at the Wayback Machine.
Jump up ^ "Yahoo style guide". Styleguide.yahoo.com. Archived from the original on May 9, 2013. Retrieved 2014-01-09.
^ Jump up to: a b "AP Removes Hyphen From ‘Email’ In Style Guide" Archived 2015-05-12 at the Wayback Machine., 18 March 2011, huffingtonpost.com
Jump up ^ AskOxford Language Query team. "What is the correct way to spell 'e' words such as 'email', 'ecommerce', 'egovernment'?". FAQ. Oxford University Press. Archived from the original on July 1, 2008. Retrieved 4 September 2009. We recommend email, as this is now by far the most common form
Jump up ^ "Reference.com". Dictionary.reference.com. Archived from the original on 2013-12-16. Retrieved 2014-01-09.
Jump up ^ Random House Unabridged Dictionary, 2006
Jump up ^ The American Heritage Dictionary of the English Language, Fourth Edition
Jump up ^ Princeton University WordNet 3.0
Jump up ^ The American Heritage Science Dictionary, 2002
Jump up ^ "Merriam-Webster Dictionary". Merriam-Webster. Archived from the original on 12 May 2014. Retrieved 9 May 2014.
Jump up ^ ""Email" or "e-mail"". English Language & Usage – Stack Exchange. August 25, 2010. Archived from the original on August 31, 2010. Retrieved September 26, 2010.
Jump up ^ Gerri Berendzen; Daniel Hunt. "AP changes e-mail to email". 15th National Conference of the American Copy Editors Society (2011, Phoenix). ACES. Archived from the original on 22 March 2011. Retrieved 23 March 2011.
Jump up ^ "RFC 524 (rfc524) – A Proposed Mail Protocol". Faqs.org. 1973-06-13. Archived from the original on 2016-04-03. Retrieved 2016-11-18.
^ Jump up to: a b "RFC 1939 (rfc1939) – Post Office Protocol – Version 3". Faqs.org. Archived from the original on 2014-01-07. Retrieved 2014-01-09.
^ Jump up to: a b "RFC 3501 (rfc3501) – Internet Message Access Protocol – version 4rev1". Faqs.org. Archived from the original on 2014-01-07. Retrieved 2014-01-09.
Jump up ^ "''"RFC Style Guide"'', Table of decisions on consistent usage in RFC". Archived from the original on 2013-12-28. Retrieved 2014-01-09.
Jump up ^ "Excerpt from the FAQ list of the Usenet newsgroup alt.usage.english". Alt-usage-english.org. Archived from the original on 2012-04-03. Retrieved 2014-01-09.
Jump up ^ "Mail Objects". Simple Mail Transfer Protocol. IETF. sec. 2.3.1. doi:10.17487/RFC5321. RFC 5321. https://tools.ietf.org/html/rfc5321#section-2.3.1. "SMTP transports a mail object. A mail object contains an envelope and content."
Jump up ^ "Mail Objects". Simple Mail Transfer Protocol. IETF. sec. 2.3.1. doi:10.17487/RFC5321. RFC 5321. https://tools.ietf.org/html/rfc5321#section-2.3.1. "The SMTP content is sent in the SMTP DATA protocol unit and has two parts: the header section and the body. If the content conforms to other contemporary standards, the header section consists of a collection of header fields, each consisting of a header name, a colon, and data, structured as in the message format specification"
Jump up ^ "Retiring the NSFNET Backbone Service: Chronicling the End of an Era" Archived 2016-01-01 at the Wayback Machine., Susan R. Harris, Ph.D., and Elise Gerich, ConneXions, Vol. 10, No. 4, April 1996
Jump up ^ "A Brief History of the Internet". Archived from the original on 2015-08-11.
Jump up ^ How E-mail Works. howstuffworks.com. 2008. Archived from the original on 2017-06-11.
Jump up ^ "MX Record Explanation" Archived 2015-01-17 at the Wayback Machine., it.cornell.edu
Jump up ^ "What is open relay?". WhatIs.com. Indiana University. 2004-07-19. Archived from the original on 2007-08-24. Retrieved 2008-04-07.
Jump up ^ Ch Seetha Ram (2010). Information Technology for Management. Deep & Deep Publications. p. 164. ISBN 978-81-8450-267-1.
Jump up ^ Hoffman, Paul (2002-08-20). "Allowing Relaying in SMTP: A Series of Surveys". IMC Reports. Internet Mail Consortium. Archived from the original on 2007-01-18. Retrieved 2008-04-13.
Jump up ^ Simpson, Ken (October 3, 2008). "An update to the email standards". MailChannels Blog Entry. Archived from the original on October 6, 2008.
Jump up ^ J. Klensin (October 2008). "Mail Objects". Simple Mail Transfer Protocol. sec. 2.3.1.. doi:10.17487/RFC5321. RFC 5321. https://tools.ietf.org/html/rfc5321#section-2.3.1. "SMTP transports a mail object. A mail object contains an envelope and content. ... The SMTP content is sent in the SMTP DATA protocol unit and has two parts: the header section and the body."
Jump up ^ D. Crocker (July 2009). "Message Data". Internet Mail Architecture. sec. 4.1.. doi:10.17487/RFC5598. RFC 5598. https://tools.ietf.org/html/rfc5598#section-4.1. "A message comprises a transit-handling envelope and the message content. The envelope contains information used by the MHS. The content is divided into a structured header and the body."
Jump up ^ P. Resnick, Ed. (October 2008). "RFC 5322, Internet Message Format". IETF. Archived from the original on 2015-02-22.
Jump up ^ Moore, K (November 1996). "MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text". IETF. Archived from the original on 2012-01-14. Retrieved 2012-01-21.
Jump up ^ A Yang, Ed. (February 2012). "RFC 6532, Internationalized Email Headers". IETF. ISSN 2070-1721. Archived from the original on 2015-02-18.
Jump up ^ J. Yao, Ed., W. Mao, Ed. (February 2012). "RFC 6531, SMTP Extension for Internationalized Email Addresses". IETF. ISSN 2070-1721. Archived from the original on 2015-02-18. CS1 maint: Multiple names: authors list (link)
Jump up ^ "Now, get your email address in Hindi - The Economic Times". The Economic Times. Archived from the original on 2016-08-28. Retrieved 2016-10-17.
Jump up ^ "RFC 5322, 3.6. Field Definitions". Tools.ietf.org. October 2008. Archived from the original on 2013-12-30. Retrieved 2014-01-09.
Jump up ^ "RFC 5322, 3.6.4. Identification Fields". Tools.ietf.org. October 2008. Archived from the original on 2013-12-30. Retrieved 2014-01-09.
Jump up ^ "RFC 5064". Tools.ietf.org. December 2007. Archived from the original on 2014-07-25. Retrieved 2014-01-09.
Jump up ^ Microsoft, Auto Response Suppress, 2010, microsoft reference Archived 2011-04-07 at the Wayback Machine., 2010 Sep 22
Jump up ^ John Klensin (October 2008). "Trace Information". Simple Mail Transfer Protocol. IETF. sec. 4.4. doi:10.17487/RFC5321. RFC 5321. https://tools.ietf.org/html/rfc5321#section-4.4.
Jump up ^ John Levine (14 January 2012). "Trace headers". email message. IETF. Archived from the original on 11 August 2012. Retrieved 16 January 2012. there are many more trace fields than those two
Jump up ^ This extensible field is defined by RFC 7001, that also defines an IANA registry of Email Authentication Parameters.
Jump up ^ RFC 7208.
Jump up ^ Defined in RFC 3834, and updated by RFC 5436.
Jump up ^ RFC 5518.
Jump up ^ Craig Hunt (2002). TCP/IP Network Administration. O'Reilly Media. p. 70. ISBN 978-0-596-00297-8.
Jump up ^ "Email policies that prevent viruses". Archived from the original on 2007-05-12. CS1 maint: BOT: original-url status unknown (link)
Jump up ^ "When posting to a RootsWeb mailing list..." Helpdesk.rootsweb.com. Archived from the original on 2014-02-19. Retrieved 2014-01-09.
Jump up ^ "...Plain text, 72 characters per line..." Openbsd.org. Archived from the original on 2014-02-08. Retrieved 2014-01-09.
Jump up ^ "How to Prevent the Winmail.dat File from Being Sent to Internet Users". Support.microsoft.com. 2010-07-02. Archived from the original on 2014-01-09. Retrieved 2014-01-09.
Jump up ^ In practice, some accepted messages may nowadays not be delivered to the recipient's InBox, but instead to a Spam or Junk folder which, especially in a corporate environment, may be inaccessible to the recipient
Jump up ^ "Free Email Providers in the Yahoo! Directory". dir.yahoo.com. Archived from the original on 2014-07-04.
Jump up ^ RFC 2368 section 3 : by Paul Hoffman in 1998 discusses operation of the "mailto" URL.
Jump up ^ Allen, David (2004). Windows to Linux. Prentice Hall. p. 192. Archived from the original on 2016-12-26.
Jump up ^ By Om Malik, GigaOm. "Is Email a Curse or a Boon? Archived 2010-12-04 at the Wayback Machine." September 22, 2010. Retrieved October 11, 2010.
Jump up ^ Martin, Brett A. S.; Van Durme, Joel; Raulas, Mika; Merisavo, Marko (2003). "E-mail Marketing: Exploratory Insights from Finland" (PDF). Journal of Advertising Research. 43 (3): 293–300. doi:10.1017/s0021849903030265. Archived (PDF) from the original on 2012-10-21.
Jump up ^ Lev, Amir. "Spam culture, part 1: China". Archived from the original on 2016-11-10.
Jump up ^ Hansen, Derek; Smith, Marc A.; Heer, Jeffrey (2011). "E-Mail". In Barnett, George A. Encyclopedia of social networks. Thousand Oaks, Calif: Sage. p. 245. ISBN 9781412994170. OCLC 959670912.
Jump up ^ "Email Is Top Activity On Smartphones, Ahead Of Web Browsing & Facebook [Study]". 28 March 2013. Archived from the original on 29 April 2014.
Jump up ^ "The ultimate mobile email statistics overview". Archived from the original on 2014-07-11.
Jump up ^ Richtel, Matt (2010-12-20). "E-Mail Gets an Instant Makeover". The New York Times. Retrieved 2018-04-04.
Jump up ^ Gustini, Ray (2010-12-21). "Why Are Young People Abandoning Email?". The Atlantic. Retrieved 2018-04-04.
Jump up ^ Perez, Sarah (2016-03-24). "Email is dying among mobile's youngest users". techcrunch.com. Retrieved 2018-04-04.
Jump up ^ "Setting Message Size Limits in Exchange 2010 and Exchange 2007" Archived 2013-02-12 at the Wayback Machine..
Jump up ^ "Google updates file size limits for Gmail and YouTube", geek.com Archived 2011-12-19 at the Wayback Machine..
Jump up ^ "Maximum attachment size", mail.google,com.
Jump up ^ "Exchange 2007: Attachment Size Increase,..." TechNet Magazine, Microsoft.com US. 2010-03-25. Archived from the original on 2016-08-25.
Jump up ^ "Send large files to other people" Archived 2016-08-07 at the Wayback Machine., Microsoft.com
Jump up ^ "8 ways to email large attachments" Archived 2016-07-02 at the Wayback Machine., Chris Hoffman, December 21, 2012, makeuseof.com
Jump up ^ Bunin, Rachel Biheller (2012-08-01). Microsoft Outlook 2010: Essentials. Cengage Learning. ISBN 1133418201. Archived from the original on 2018-01-02.
Jump up ^ Radicati, Sara. "Email Statistics Report, 2010" (PDF). Archived (PDF) from the original on 2011-09-01.
Jump up ^ Gross, Doug (July 26, 2011). "Happy Information Overload Day!". CNN. Archived from the original on January 21, 2012.
Jump up ^ Stross, Randall (2008-04-20). "Struggling to Evade the E-Mail Tsunami". The New York Times. Archived from the original on April 17, 2009. Retrieved May 1, 2010.
Jump up ^ "Seeing Spam? How To Take Care of Your Google Analytics Data". sitepronews.com. Archived from the original on 7 November 2017. Retrieved 5 September 2017.
Jump up ^ Rich Kawanagh. The top ten email spam list of 2005. ITVibe news, 2006, January 02, ITvibe.com Archived 2008-07-20 at the Wayback Machine.
Jump up ^ How Microsoft is losing the war on spam Salon.com Archived 2008-06-29 at the Wayback Machine.
Jump up ^ Spam Bill 2003 (PDF Archived 2006-09-11 at the Wayback Machine.)
Jump up ^ "Google Says Its AI Catches 99.9 Percent of Gmail Spam" Archived 2016-09-16 at the Wayback Machine., Cade Metz, July 09 2015, wired.com
Jump up ^ "Spam and phishing in Q1 2016" Archived 2016-08-09 at the Wayback Machine., May 12, 2016, securelist.com
Jump up ^ SMEmail – A New Protocol for the Secure E-mail in Mobile Environments, Proceedings of the Australian Telecommunications Networks and Applications Conference (ATNAC'08), pp. 39–44, Adelaide, Australia, Dec. 2008.
Jump up ^ S. Kiesler; D. Zubrow; A.M. Moses; V. Geller (1985). "Affect in computer-mediated communication: an experiment in synchronous terminal-to-terminal discussion". Human-Computer Interaction. 1: 77–104. doi:10.1207/s15327051hci0101_3.
Jump up ^ Barrett, Grant (December 23, 2007). "All We Are Saying". The New York Times. Archived from the original on April 17, 2009. Retrieved 2007-12-24.
Jump up ^ "Internationalized Domain Names (IDNs) | Registry.In". registry.in. Archived from the original on 2016-05-13. Retrieved 2016-10-17.
Jump up ^ "Made In India 'Datamail' Empowers Russia With Email Address In Russian Language - Digital Conqueror". 7 December 2016. Archived from the original on 5 March 2017.
Jump up ^ RFC 3885, SMTP Service Extension for Message Tracking
Jump up ^ RFC 3888, Message Tracking Model and Requirements
Jump up ^ Amy Harmon (2000-11-22). "Software That Tracks E-Mail Is Raising Privacy Concerns". The New York Times. Retrieved 2012-01-13.
Jump up ^ "About.com". Email.about.com. 2013-12-19. Archived from the original on 2018-01-02. Retrieved 2014-01-09.
Jump up ^ "Webdevelopersnotes.com". Webdevelopersnotes.com. Archived from the original on 2014-01-09. Retrieved 2014-01-09.
Jump up ^ "Outlook: Web Bugs & Blocked HTML Images" Archived 2015-02-18 at the Wayback Machine., slipstick.com
Jump up ^ "Gmail blows up e-mail marketing..." Archived 2017-06-07 at the Wayback Machine., Ron Amadeo, Dec 13 2013, Ars Technica
Further reading[edit]
Cemil Betanov, Introduction to X.400, Artech House, ISBN 0-89006-597-7.
Marsha Egan, "Inbox Detox and The Habit of Email Excellence", Acanthus Publishing ISBN 978-0-9815589-8-1
Lawrence Hughes, Internet e-mail Protocols, Standards and Implementation, Artech House Publishers, ISBN 0-89006-939-5.
Kevin Johnson, Internet Email Protocols: A Developer's Guide, Addison-Wesley Professional, ISBN 0-201-43288-9.
Pete Loshin, Essential Email Standards: RFCs and Protocols Made Practical, John Wiley & Sons, ISBN 0-471-34597-0.
Partridge, Craig (April–June 2008). "The Technical Development of Internet Email" (PDF). IEEE Annals of the History of Computing. Berlin: IEEE Computer Society. 30 (2): 3–29. doi:10.1109/mahc.2008.32. ISSN 1934-1547. Archived from the original (PDF) on 2016-06-02
Sara Radicati, Electronic Mail: An Introduction to the X.400 Message Handling Standards, Mcgraw-Hill, ISBN 0-07-051104-7.
John Rhoton, Programmer's Guide to Internet Mail: SMTP, POP, IMAP, and LDAP, Elsevier, ISBN 1-55558-212-5.
John Rhoton, X.400 and SMTP: Battle of the E-mail Protocols, Elsevier, ISBN 1-55558-165-X.
David Wood, Programming Internet Mail, O'Reilly, ISBN 1-56592-479-7.
External links[edit]
Look up email or outbox in Wiktionary, the free dictionary.
IANA's list of standard header fields
The History of Email is Dave Crocker's attempt at capturing the sequence of 'significant' occurrences in the evolution of email; a collaborative effort that also cites this page.
The History of Electronic Mail is a personal memoir by the implementer of an early email system
A Look at the Origins of Network Email is a short, yet vivid recap of the key historical facts
Business E-Mail Compromise - An Emerging Global Threat, FBI
[show]
v
t
e
Computer-mediated communication
Online chat
Online discussion
Communication software
Collaborative software
Social network service
Virtual learning environment
Asynchronous conferencing
Email
Electronic mailing list
FidoNet
Usenet
Internet forum
Textboard
Imageboard
Shoutbox
Bulletin board system
Online guestbook
Synchronous conferencing
Data conferencing
Instant messaging
Internet Relay Chat
LAN messenger
Talker
Videoconferencing
Voice over IP
Voice chat in online gaming
Web chat
Web conferencing
Publishing
Blog
Microblogging
Wiki
[show]
v
t
e
Email clients
Free software
Alpine
Balsa
Citadel/UX
Classilla
Claws Mail
Columba
Cone
Elm
Evolution
fetchmail
Geary
getmail
GNUMail
Gnus
Gnuzilla
IMP
KMail
Mahogany
Mailpile
Mailx
Mailx (Heirloom Project)
Modest
Mozilla Thunderbird
Mulberry
Mutt
nmh / MH
Nylas N1
OfflineIMAP
Roundcube
SeaMonkey
SquirrelMail
Sylpheed
Trojitá
YAM
Zimbra
Freeware
eM Client
EmailTray
Foxmail
i.Scribe
Mailbird
Opera Mail
Spark
TouchMail
Retail
Hiri
Bloomba/WordPerfect Mail
Newton
IBM Notes
InScribe
Mail (Apple)
Mail (Windows)
Microsoft Outlook
Novell GroupWise
Shareware
Becky!
Eureka Email
Forté Agent
GyazMail
Pocomail
The Bat!
Donationware
Pegasus Mail
Discontinued
Arachne
Beonex Communicator
BlitzMail
cc:Mail
Claris Emailer
Columbia MM
Courier
Cyberdog
Cyberjack
Embrowser
Eudora
FossaMail
Hula
Mailbox
Mailody
Microsoft Entourage
Microsoft Internet Mail and News
MINUET
Mozilla Mail & Newsgroups
Netscape Mail
Netscape Messenger 9
NeXTMail
Outlook Express
Pine
POPmail
Sparrow
Spicebird
Turnpike
WebSpyder
Windows Live Mail
Windows Mail
Windows Messaging
Related technologies
Extended SMTP
LMTP
IMAP
POP
Push-IMAP
SMAP
SMTP
UUCP
Related topics
Email
Unicode and email
Category
Comparison
Authority control
GND: 4191427-2
NARA: 10636085
NDL: 00576450
Retrieved from "https://en.wikipedia.org/w/index.php?title=Email&oldid=843387842"
Categories:
Email
Internet terminology
Electronic documents
History of the Internet
Computer-related introductions in 1971
Hidden categories:
Webarchive template wayback links
CS1 maint: Multiple names: authors list
CS1 maint: BOT: original-url status unknown
Pages using RFC magic links
All articles with unsourced statements
Articles with unsourced statements from September 2014
Articles needing additional references from November 2007
All articles needing additional references
Articles containing potentially dated statements from 2011
All articles containing potentially dated statements
Articles needing additional references from October 2016
Articles with inconsistent citation formats
Wikipedia articles with GND identifiers
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
Afrikaans
Alemannisch
العربية
Aragonés
অসমীয়া
Asturianu
Azərbaycanca
বাংলা
Bân-lâm-gú
Башҡортса
Беларуская
Беларуская (тарашкевіца)
भोजपुरी
Български
Boarisch
བོད་ཡིག
Bosanski
Brezhoneg
Català
Чӑвашла
Čeština
Cymraeg
Dansk
Deutsch
Eesti
Ελληνικά
Español
Esperanto
Euskara
فارسی
Føroyskt
Français
Frysk
Furlan
Gaeilge
Galego
贛語
گیلکی
ગુજરાતી
한국어
Հայերեն
हिन्दी
Hrvatski
Bahasa Indonesia
Interlingua
IsiXhosa
Íslenska
Italiano
עברית
Basa Jawa
ಕನ್ನಡ
ქართული
Қазақша
Kiswahili
Kurdî
ລາວ
Latina
Latviešu
Lëtzebuergesch
Lietuvių
Limburgs
Lingála
Lumbaart
Magyar
Македонски
Malagasy
മലയാളം
मराठी
Bahasa Melayu
Mìng-dĕ̤ng-ngṳ̄
Монгол
မြန်မာဘာသာ
Nāhuatl
Nederlands
Nedersaksies
नेपाली
日本語
Norsk
Norsk nynorsk
Occitan
Олык марий
ଓଡ଼ିଆ
Oʻzbekcha/ўзбекча
ਪੰਜਾਬੀ
پنجابی
پښتو
Patois
Piemontèis
Tok Pisin
Plattdüütsch
Polski
Português
Română
Rumantsch
Runa Simi
Русиньскый
Русский
Саха тыла
Scots
Shqip
Sicilianu
සිංහල
Simple English
سنڌي
Slovenčina
Slovenščina
Soomaaliga
کوردی
Српски / srpski
Srpskohrvatski / српскохрватски
Basa Sunda
Suomi
Svenska
Tagalog
தமிழ்
తెలుగు
ไทย
ᏣᎳᎩ
Türkçe
Українська
اردو
Vèneto
Tiếng Việt
Võro
Walon
Winaray
吴语
ייִדיש
粵語
Zazaki
Žemaitėška
中文
123 more
Edit links
This page was last edited on 28 May 2018, at 20:38.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

attrs: role class

values:
note
hatnote navigation-not-searchable

values: /wiki/File:(at).svg internal Enlarge

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc561

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc524

values: Government Open Systems Interconnection Profile

values:
/wiki/Placeholder_names_in_cryptography
mw-redirect
Placeholder names in cryptography

values:
/wiki/E-mail_client
mw-redirect
E-mail client

values:
/wiki/Mail_submission_agent
mw-redirect
Mail submission agent

values:
/wiki/Message_delivery_agent
mw-redirect
Message delivery agent

values:
/wiki/Email_Mailbox
mw-redirect
Email Mailbox

values:
/wiki/Lotus_Notes
mw-redirect
Lotus Notes

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc5322

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc2045

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc2049

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc2822

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc822

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc733

values:
/wiki/Printable_characters
mw-redirect
Printable characters

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc2047

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc3864

values:
/wiki/E-mail_subject_abbreviations
mw-redirect
E-mail subject abbreviations

values:
/wiki/Quoted_printable
mw-redirect
Quoted printable

values:
/wiki/Mail_transport_agent
mw-redirect
Mail transport agent

values:
/wiki/Character_set
mw-redirect
Character set

values: This claim needs references to reliable sources. (September 2014)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Block_quote
mw-redirect
Block quote

values:
/wiki/List_of_email_clients#Text-based
mw-redirect
List of email clients

values: Edit section: Servers and client applications

values:
/wiki/Mail_transfer_agent
mw-redirect
Mail transfer agent

values:
/wiki/Novell_Groupwise
mw-redirect
Novell Groupwise

values:
/wiki/Mail_user_agent
mw-redirect
Mail user agent

values:
/wiki/Novell_GroupWise
mw-redirect
Novell GroupWise

values:
/wiki/Microsoft_Outlook_Express
mw-redirect
Microsoft Outlook Express

values:
/wiki/Lotus_notes
mw-redirect
Lotus notes

values:
/wiki/Windows_Mail
mw-redirect
Windows Mail

values:
/wiki/Kerio_Connect
mw-redirect
Kerio Connect

values:
/wiki/IBM_Lotus_Notes
mw-redirect
IBM Lotus Notes

values: Help:Introduction to referencing with Wiki Markup/1

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values: Edit section: Business and organizational use

values:
/wiki/Long_distance_telephone_call
mw-redirect
Long distance telephone call

values: plainlinks noexcerpt noprint asof-tag update

values: Edit section: Declining use among young people

values:
/wiki/Vinyl_record
mw-redirect
Vinyl record

values: Edit section: Attachment size limitation

values:
/wiki/Anti-spam_techniques_(email)
mw-redirect
Anti-spam techniques (email)

values:
/wiki/User_agent_string
mw-redirect
User agent string

values:
/wiki/Virtual_Private_Network
mw-redirect
Virtual Private Network

values: Simple Authentication and Security Layer

values:
/wiki/Social_norms
mw-redirect
Social norms

values:
/wiki/Delivery_Status_Notification
mw-redirect
Delivery Status Notification

values: -moz-column-width: 22em; -webkit-column-width: 22em; column-width: 22em;

values:
nofollow
external text
http://styleguide.yahoo.com/word-list/e

values: AP Stylebook editors share big changes (page does not exist)

values:
nofollow
external text
http://www.faqs.org/rfcs/rfc524.html

values:
nofollow
external text
http://www.faqs.org/rfcs/rfc1939.html

values:
nofollow
external text
http://www.faqs.org/rfcs/rfc3501.html

values:
nofollow
external text
https://tools.ietf.org/html/rfc5321

values:
nofollow
external text
http://dx.doi.org/10.17487%2FRFC5321

values:
nofollow
external text
http://www.imc.org/ube-relay.html

values:
nofollow
external text
https://tools.ietf.org/html/rfc5598

values:
nofollow
external text
http://dx.doi.org/10.17487%2FRFC5598

values:
nofollow
external text
https://tools.ietf.org/html/rfc5322

values:
nofollow
external text
https://tools.ietf.org/html/rfc2047

values:
nofollow
external text
https://tools.ietf.org/html/rfc6532

values:
nofollow
external text
//www.worldcat.org/issn/2070-1721

values:
nofollow
external text
https://tools.ietf.org/html/rfc6531

values: Category:CS1 maint: Multiple names: authors list

values:
nofollow
external text
https://tools.ietf.org/html/rfc5064

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc7001

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc7208

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc3834

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc5436

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc5518

values: Category:CS1 maint: BOT: original-url status unknown

values:
nofollow
external text
http://www.openbsd.org/mail.html

values:
nofollow
external text
http://support.microsoft.com/kb/138053

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc2368

values:
nofollow
external text
//www.worldcat.org/oclc/959670912

values:
nofollow
http://itvibe.com/news/3837/
external text

values:
nofollow
external text
http://www.arxiv.org/pdf/1002.3176

values:
nofollow
external text
//doi.org/10.1207%2Fs15327051hci0101_3

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc3885

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc3888

values:
nofollow
external text
http://www.inboxdetox.com

values:
nofollow
external text
//doi.org/10.1109%2Fmahc.2008.32

values:
nofollow
external text
//www.worldcat.org/issn/1934-1547

values:
nofollow
http://emailhistory.org/
external text

values:
/wiki/Online_discussion
mw-redirect
Online discussion

values:
/wiki/Social_network_service
mw-redirect
Social network service

values: nowraplinks hlist collapsible autocollapse navbox-inner

values:
/wiki/Microsoft_Internet_Mail_and_News
mw-redirect
Microsoft Internet Mail and News

values:
nofollow
external text
https://d-nb.info/gnd/4191427-2

values: National Archives and Records Administration

values: Category:Computer-related introductions in 1971

values: Category:Webarchive template wayback links

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from September 2014

values: Category:Articles needing additional references from November 2007

values: Category:All articles needing additional references

values: Category:Articles containing potentially dated statements from 2011

values: Category:All articles containing potentially dated statements

values: Category:Articles needing additional references from October 2016

values: Category:Articles with inconsistent citation formats

values: Category:Wikipedia articles with GND identifiers

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Email
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values:
/w/index.php?title=Email&action=edit
Edit this page [ctrl-alt-e]
e

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values:
https://af.wikipedia.org/wiki/E-pos
E-pos – Afrikaans
af
af
interlanguage-link-target

values:
interlanguage-link interwiki-af
display: none;

values:
https://als.wikipedia.org/wiki/E-Mail
E-Mail – Alemannisch
als
als
interlanguage-link-target

values:
interlanguage-link interwiki-als
display: none;

values: بريد إلكتروني – Arabic

values:
interlanguage-link interwiki-an
display: none;

values:
interlanguage-link interwiki-as
display: none;

values:
interlanguage-link interwiki-ast
display: none;

values:
interlanguage-link interwiki-az
display: none;

values:
interlanguage-link interwiki-bn
display: none;

values:
interlanguage-link interwiki-zh-min-nan
display: none;

values: Электрон почта – Bashkir

values:
interlanguage-link interwiki-ba
display: none;

values: Электронная пошта – Belarusian

values:
interlanguage-link interwiki-be
display: none;

values: Электронная пошта – Belarusian (Taraškievica orthography)

values:
interlanguage-link interwiki-be-x-old
display: none;

values:
interlanguage-link interwiki-bh
display: none;

values: Електронна поща – Bulgarian

values:
interlanguage-link interwiki-bg
display: none;

values:
https://bar.wikipedia.org/wiki/E-Mail
E-Mail – Bavarian
bar
bar
interlanguage-link-target

values:
interlanguage-link interwiki-bar
display: none;

values: གློག་རྡུལ་འཕྲིན་སྒམ། – Tibetan

values:
interlanguage-link interwiki-bo
display: none;

values:
https://bs.wikipedia.org/wiki/E-mail
E-mail – Bosnian
bs
bs
interlanguage-link-target

values:
interlanguage-link interwiki-bs
display: none;

values:
interlanguage-link interwiki-br
display: none;

values:
interlanguage-link interwiki-ca
display: none;

values: Электронлă почта – Chuvash

values:
interlanguage-link interwiki-cv
display: none;

values:
https://cs.wikipedia.org/wiki/E-mail
E-mail – Czech
cs
cs
interlanguage-link-target

values:
interlanguage-link interwiki-cs
display: none;

values:
https://cy.wikipedia.org/wiki/E-bost
E-bost – Welsh
cy
cy
interlanguage-link-target

values:
interlanguage-link interwiki-cy
display: none;

values:
https://da.wikipedia.org/wiki/E-mail
E-mail – Danish
da
da
interlanguage-link-target

values:
interlanguage-link interwiki-da
display: none;

values:
https://de.wikipedia.org/wiki/E-Mail
E-Mail – German
de
de
interlanguage-link-target

values:
interlanguage-link interwiki-de
display: none;

values:
https://et.wikipedia.org/wiki/E-kiri
E-kiri – Estonian
et
et
interlanguage-link-target

values:
interlanguage-link interwiki-et
display: none;

values: Ηλεκτρονικό ταχυδρομείο – Greek

values:
interlanguage-link interwiki-el
display: none;

values:
interlanguage-link interwiki-eo
display: none;

values:
interlanguage-link interwiki-eu
display: none;

values:
interlanguage-link interwiki-fa
display: none;

values:
interlanguage-link interwiki-fo
display: none;

values:
interlanguage-link interwiki-fr
display: none;

values:
https://fy.wikipedia.org/wiki/E-mail
E-mail – Western Frisian
fy
fy
interlanguage-link-target

values:
interlanguage-link interwiki-fy
display: none;

values:
interlanguage-link interwiki-fur
display: none;

values:
interlanguage-link interwiki-ga
display: none;

values:
interlanguage-link interwiki-gl
display: none;

values:
interlanguage-link interwiki-gan
display: none;

values: ايميل – Gilaki

values:
interlanguage-link interwiki-glk
display: none;

values:
interlanguage-link interwiki-gu
display: none;

values:
interlanguage-link interwiki-ko
display: none;

values: Էլեկտրոնային փոստ – Armenian

values:
interlanguage-link interwiki-hy
display: none;

values: प-पत्र – Hindi

values:
interlanguage-link interwiki-hr
display: none;

values:
interlanguage-link interwiki-ia
display: none;

values:
https://xh.wikipedia.org/wiki/I-e-mail
I-e-mail – Xhosa
xh
xh
interlanguage-link-target

values:
interlanguage-link interwiki-xh
display: none;

values:
interlanguage-link interwiki-is
display: none;

values:
interlanguage-link interwiki-it
display: none;

values: דואר אלקטרוני – Hebrew

values:
interlanguage-link interwiki-he
display: none;

values:
interlanguage-link interwiki-jv
display: none;

values:
interlanguage-link interwiki-kn
display: none;

values: ელექტრონული ფოსტა – Georgian

values:
interlanguage-link interwiki-ka
display: none;

values: Электронды пошта – Kazakh

values:
interlanguage-link interwiki-kk
display: none;

values:
interlanguage-link interwiki-sw
display: none;

values:
https://ku.wikipedia.org/wiki/E-peyam
E-peyam – Kurdish
ku
ku
interlanguage-link-target

values:
interlanguage-link interwiki-ku
display: none;

values:
interlanguage-link interwiki-lo
display: none;

values:
interlanguage-link interwiki-la
display: none;

values:
https://lv.wikipedia.org/wiki/E-pasts
E-pasts – Latvian
lv
lv
interlanguage-link-target

values:
interlanguage-link interwiki-lv
display: none;

values:
https://lb.wikipedia.org/wiki/E-Mail
E-Mail – Luxembourgish
lb
lb
interlanguage-link-target

values:
interlanguage-link interwiki-lb
display: none;

values:
interlanguage-link interwiki-lt
display: none;

values:
https://li.wikipedia.org/wiki/E-mail
E-mail – Limburgish
li
li
interlanguage-link-target

values:
interlanguage-link interwiki-li
display: none;

values:
interlanguage-link interwiki-ln
display: none;

values:
https://lmo.wikipedia.org/wiki/E-mail
E-mail – Lombard
lmo
lmo
interlanguage-link-target

values:
interlanguage-link interwiki-lmo
display: none;

values:
https://hu.wikipedia.org/wiki/E-mail
E-mail – Hungarian
hu
hu
interlanguage-link-target

values:
interlanguage-link interwiki-hu
display: none;

values: Електронско писмо – Macedonian

values:
interlanguage-link interwiki-mk
display: none;

values:
https://mg.wikipedia.org/wiki/Mailaka
Mailaka – Malagasy
mg
mg
interlanguage-link-target

values:
interlanguage-link interwiki-mg
display: none;

values:
interlanguage-link interwiki-ml
display: none;

values:
interlanguage-link interwiki-mr
display: none;

values:
interlanguage-link interwiki-cdo
display: none;

values: Цахим шуудан – Mongolian

values:
interlanguage-link interwiki-mn
display: none;

values: အီးမေးလ် – Burmese

values:
interlanguage-link interwiki-my
display: none;

values:
https://nah.wikipedia.org/wiki/E-mail
E-mail – Nāhuatl
nah
nah
interlanguage-link-target

values:
interlanguage-link interwiki-nah
display: none;

values:
https://nl.wikipedia.org/wiki/E-mail
E-mail – Dutch
nl
nl
interlanguage-link-target

values:
interlanguage-link interwiki-nl
display: none;

values:
interlanguage-link interwiki-nds-nl
display: none;

values:
interlanguage-link interwiki-ne
display: none;

values:
interlanguage-link interwiki-ja
display: none;

values:
https://no.wikipedia.org/wiki/E-post
E-post – Norwegian
no
no
interlanguage-link-target

values:
interlanguage-link interwiki-no
display: none;

values:
https://nn.wikipedia.org/wiki/E-post
E-post – Norwegian Nynorsk
nn
nn
interlanguage-link-target

values:
interlanguage-link interwiki-nn
display: none;

values:
interlanguage-link interwiki-oc
display: none;

values: Электрон почто – Eastern Mari

values:
interlanguage-link interwiki-mhr
display: none;

values:
interlanguage-link interwiki-or
display: none;

values:
https://uz.wikipedia.org/wiki/E-Mail
E-Mail – Uzbek
uz
uz
interlanguage-link-target

values:
interlanguage-link interwiki-uz
display: none;

values:
interlanguage-link interwiki-pa
display: none;

values:
interlanguage-link interwiki-pnb
display: none;

values: برېښليک – Pashto

values:
interlanguage-link interwiki-ps
display: none;

values:
https://jam.wikipedia.org/wiki/Iimiel
Iimiel – Jamaican Creole English
jam
jam
interlanguage-link-target

values:
interlanguage-link interwiki-jam
display: none;

values:
interlanguage-link interwiki-pms
display: none;

values:
https://tpi.wikipedia.org/wiki/Imel
Imel – Tok Pisin
tpi
tpi
interlanguage-link-target

values:
interlanguage-link interwiki-tpi
display: none;

values:
interlanguage-link interwiki-nds
display: none;

values:
interlanguage-link interwiki-pl
display: none;

values:
https://pt.wikipedia.org/wiki/E-mail
E-mail – Portuguese
pt
pt
interlanguage-link-target

values:
https://ro.wikipedia.org/wiki/E-mail
E-mail – Romanian
ro
ro
interlanguage-link-target

values:
interlanguage-link interwiki-ro
display: none;

values:
https://rm.wikipedia.org/wiki/E-mail
E-mail – Romansh
rm
rm
interlanguage-link-target

values:
interlanguage-link interwiki-rm
display: none;

values:
https://qu.wikipedia.org/wiki/E-chaski
E-chaski – Quechua
qu
qu
interlanguage-link-target

values:
interlanguage-link interwiki-qu
display: none;

values: Електронічна пошта – Rusyn

values:
interlanguage-link interwiki-rue
display: none;

values: Электронная почта – Russian

values:
https://sah.wikipedia.org/wiki/E-mail
E-mail – Sakha
sah
sah
interlanguage-link-target

values:
interlanguage-link interwiki-sah
display: none;

values:
https://sco.wikipedia.org/wiki/Email
Email – Scots
sco
sco
interlanguage-link-target

values:
interlanguage-link interwiki-sco
display: none;

values:
interlanguage-link interwiki-sq
display: none;

values:
https://scn.wikipedia.org/wiki/E-mail
E-mail – Sicilian
scn
scn
interlanguage-link-target

values:
interlanguage-link interwiki-scn
display: none;

values: විද්‍යුත් තැපෑල – Sinhala

values:
interlanguage-link interwiki-si
display: none;

values:
interlanguage-link interwiki-simple
display: none;

values: اي ميل – Sindhi

values:
interlanguage-link interwiki-sd
display: none;

values:
https://sk.wikipedia.org/wiki/E-mail
E-mail – Slovak
sk
sk
interlanguage-link-target

values:
interlanguage-link interwiki-sk
display: none;

values:
interlanguage-link interwiki-sl
display: none;

values:
https://so.wikipedia.org/wiki/Email
Email – Somali
so
so
interlanguage-link-target

values:
interlanguage-link interwiki-so
display: none;

values: پۆستی ئەلەکترۆنی – Central Kurdish

values:
interlanguage-link interwiki-ckb
display: none;

values: Електронска пошта – Serbian

values:
interlanguage-link interwiki-sr
display: none;

values:
https://sh.wikipedia.org/wiki/E-mail
E-mail – Serbo-Croatian
sh
sh
interlanguage-link-target

values:
interlanguage-link interwiki-sh
display: none;

values:
interlanguage-link interwiki-su
display: none;

values:
interlanguage-link interwiki-fi
display: none;

values:
https://sv.wikipedia.org/wiki/E-post
E-post – Swedish
sv
sv
interlanguage-link-target

values:
interlanguage-link interwiki-sv
display: none;

values:
interlanguage-link interwiki-tl
display: none;

values: மின்னஞ்சல் – Tamil

values:
interlanguage-link interwiki-ta
display: none;

values: ఈ-మెయిల్ – Telugu

values:
interlanguage-link interwiki-te
display: none;

values: อีเมล – Thai

values:
interlanguage-link interwiki-th
display: none;

values: ᎠᎾᎦᎵᏍᎩ ᎪᏪᎵ – Cherokee

values:
interlanguage-link interwiki-chr
display: none;

values:
https://tr.wikipedia.org/wiki/E-posta
E-posta – Turkish
tr
tr
interlanguage-link-target

values:
interlanguage-link interwiki-tr
display: none;

values: Електронна пошта – Ukrainian

values:
interlanguage-link interwiki-uk
display: none;

values: برقی ڈاک – Urdu

values:
interlanguage-link interwiki-vec
display: none;

values:
interlanguage-link interwiki-vi
display: none;

values:
interlanguage-link interwiki-fiu-vro
display: none;

values:
https://wa.wikipedia.org/wiki/Emile
Emile – Walloon
wa
wa
interlanguage-link-target

values:
interlanguage-link interwiki-wa
display: none;

values:
https://war.wikipedia.org/wiki/Email
Email – Waray
war
war
interlanguage-link-target

values:
interlanguage-link interwiki-war
display: none;

values:
interlanguage-link interwiki-wuu
display: none;

values: בליצפאסט – Yiddish

values:
interlanguage-link interwiki-yi
display: none;

values:
interlanguage-link interwiki-zh-yue
display: none;

values:
https://diq.wikipedia.org/wiki/E-mail
E-mail – Zazaki
diq
diq
interlanguage-link-target

values:
interlanguage-link interwiki-diq
display: none;

values:
interlanguage-link interwiki-bat-smg
display: none;

values: All languages (initial selection from common choices by you and others)

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Email rootpage-Email skin-vector action-view