Email address
≈ 7 min read
Names in other languages
No names in other languages are held for this entry yet.
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
An email address identifies a mailbox to which email messages are delivered. While early messaging systems used a variety of address formats, email addresses today follow a specific set of rules originally standardized by the Internet Engineering Task Force (IETF) in the 1980s, and updated by . The term "email address" in this article refers to just the addr-spec in Section 3.4 of . The RFC defines address more broadly as either a mailbox or group. A mailbox value can be either a name-addr, which contains a display-name and addr-spec, or the more common addr-spec alone. An email address, such as jane.smith@example.com, is made up of a local-part, the symbol @, and a domain, which may be either a domain name or an IP address enclosed in brackets. Although the standard stipulates that the local-part is case-sensitive, it also urges that receiving hosts deliver messages in a case-independent manner, e.g., that the mail system in the domain example.com treat Jane.Smith as equivalent to jane.smith. (Some mail systems even treat both as equivalent to jane smith. ) Email systems often limit the user's choice of name to a subset of the characters permitted by the RFCs. With the introduction of internationalized domain names, efforts are progressing to permit non-ASCII characters in email addresses.…
An email address identifies a mailbox to which email messages are delivered. While early messaging systems used a variety of address formats, email addresses today follow a specific set of rules originally standardized by the Internet Engineering Task Force (IETF) in the 1980s, and updated by . The term "email address" in this article refers to just the addr-spec in Section 3.4 of . The RFC defines address more broadly as either a mailbox or group. A mailbox value can be either a name-addr, which contains a display-name and addr-spec, or the more common addr-spec alone. An email address, such as jane.smith@example.com, is made up of a local-part, the symbol @, and a domain, which may be either a domain name or an IP address enclosed in brackets. Although the standard stipulates that the local-part is case-sensitive, it also urges that receiving hosts deliver messages in a case-independent manner, e.g., that the mail system in the domain example.com treat Jane.Smith as equivalent to jane.smith. (Some mail systems even treat both as equivalent to jane smith. ) Email systems often limit the user's choice of name to a subset of the characters permitted by the RFCs. With the introduction of internationalized domain names, efforts are progressing to permit non-ASCII characters in email addresses. Due to the ubiquity of email today, email addresses are used as regular usernames by many websites and services that provide a user profile or account. For example, if a user wants to log in to their Xbox Live video gaming profile, they would use their email address as the username ID of their Microsoft account, even though the service in this case is not email. printable characters !#$%&'*+-/=?^_`{|}~ dot . , provided that it is not the first or last character and provided also that it does not appear consecutively (e.g., Jane..Doe@example.com is not allowed). If quoted, it may contain Space, Horizontal Tab (HT), any ASCII graphic except Backslash and Quote and a quoted-pair consisting of a Backslash followed by HT, Space or any ASCII graphic; it may also be split between lines anywhere that HT or Space appears. In contrast to unquoted local-parts, the addresses ".Jane.Doe"@example.com , "Jane.Doe."@example.com and "Jane..Doe"@example.com are allowed. The maximum total length of the local-part of an email address is 64 octets. Space and special characters "(),:;<>@[\] are allowed with restrictions (they are only allowed inside a quoted string, as described in the paragraph below, and in that quoted string, any backslash or double-quote must be preceded once by a backslash); Comments are allowed with parentheses, either at the start or end of the local-part; e.g., jane.smith(comment)@example.com and (comment)jane.smith@example.com are both equivalent to jane.smith@example.com . In addition to the above ASCII characters, international characters above U+007F, encoded as UTF-8, are permitted by RFC 6531 when the EHLO specifies SMTPUTF8, though even mail systems that support SMTPUTF8 and 8BITMIME may restrict what characters to use when assigning local-parts. A local-part is either a Dot-string or a Quoted-string; it cannot be a combination. Quoted strings and characters, however, are not commonly used. RFC 5321 also warns that "a host that expects to receive mail SHOULD avoid defining mailboxes where the Local-part requires (or uses) the Quoted-string form". The local-part postmaster is treated specially—it is case-insensitive, and should be forwarded to the domain email administrator. Technically all other local-parts are case-sensitive, therefore janes@example.com and JaneS@example.com specify different mailboxes; however, many organizations treat uppercase and lowercase letters as equivalent. Indeed, RFC 5321 warns that "a host that expects to receive mail SHOULD avoid defining mailboxes where ... the Local-part is case-sensitive". Despite the wide range of special characters that are technically valid, organisations, mail services, mail servers, and mail clients in practice often do not accept all of them. For example, Windows Live Hotmail only allows creation of email addresses using alphanumerics, dot ( . ), underscore ( _ ) and hyphen ( - ). Common advice is to avoid using some special characters to avoid the risk of rejected emails. According to RFC 5321 2.3.11 Mailbox and Address, "the local-part MUST be interpreted and assigned semantics only by the host specified in the domain of the address". This means that no assumptions can be made about the meaning of the local-part of another mail server. It is entirely up to the configuration of the mail server. Interpretation of the local-part is dependent on the conventions and policies implemented in the mail server. For example, case sensitivity may distinguish mailboxes differing only in capitalization of characters of the local-part, although this is not very common. For example, Gmail ignores all dots in the local-part of user email address for the purposes of determining account identity.
Text derived from https://en.wikipedia.org/w/index.php?oldid=1374714890 under CC BY-SA 4.0; modifications have been made.