Monday, May 24, 2010

Can an email address include Arabic letters, i.e., 賵丨賷丿@hotmail.com?

The format of Internet e-mail addresses is defined in RFC 2822, which permits them to consist of only a subset of ASCII characters.





As defined in RFC 2821, the local-part of an e-mail address has a maximum of 64 characters (although servers are encouraged to not limit themselves to accepting only 64 characters) and the domain name a maximum of 255 characters. Unlike everything else in the header, the local-part "MUST BE treated as case sensitive. [...] However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged."





Local part is the portion of a mail address before the @ character. This normally identifies a particular mailbox within a site mail system so is not usually of interest to other mail systems.





According to RFC 2822, the local-part of the address may use any of these ASCII characters:





* Uppercase and lowercase letters (case sensitive)


* The digits 0 through 9


* The characters ! # $ % %26amp; ' * + - / = ? ^ _ ` { | } ~


* The character . provided that it is not the first or last character in the local-part.





Additionally, RFC 2821 and RFC 2822 allow the local-part to be a quoted-string, as in "John Doe"@example.com, thus allowing characters in the local-part that would otherwise be prohibited. However, RFC 2821 warns: "a host that expects to receive mail SHOULD avoid defining mailboxes where the Local-part requires (or uses) the Quoted-string form".





Notwithstanding the addresses permitted by these standards, some systems impose more restrictions on email addresses, both in email addresses created on the system and in email addresses to which messages can be sent. Hotmail, for example, only allows creation of email addresses using alphanumerics and . _ - and will not allow sending mail to any email address containing ! # $ % * + / ? | ^ { } ` ~.

Can an email address include Arabic letters, i.e., 賵丨賷丿@hotmail.com?
Not as far as i know


No comments:

Post a Comment