Jump to content

Talk:Email address

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Status of RFC 5322

[edit]

RFC 5322 is not outdated per the [IETF]; if a PHP validator fails on a quoted local part containing a space then the validator is broken. Shmuel (Seymour J.) Metz Username:Chatul (talk) 22:38, 13 December 2020 (UTC)[reply]

One thing this article seems to be very strict on is, "this is what the RFCs say", but seem to lack practical warnings against doing what is "technically allowed". One can certainly set up a server and allow someone the mail address of "technically allowed"@example.com, but a huge number of users on the internet will simply not be able to send e-mail to that address (because it is a post year 2000 extension that many providers simply will not deal with). Today, one cannot sent such an outbound e-mail via Google's email services, for one example that I'm able to test right now. (( Even though the allowance is much newer, Internationalized (UTF8) local parts are much more accepted )). Vollink (talk) 19:30, 27 September 2022 (UTC)[reply]
I agree that adding a list of technically valid but problematic addresses would be useful, and that Despite the wide range of special characters which 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 (-).[1] Common advice is to avoid using some special characters to avoid the risk of rejected emails.[2] could well be expanded --Shmuel (Seymour J.) Metz Username:Chatul (talk) 15:34, 28 September 2022 (UTC)[reply]
I agree,Mark Branch, 50.215.55.253 (talk) 03:09, 10 April 2025 (UTC)[reply]
A quoted-string as a local-part has been a valid email address since RFC-821 from 1982. I can send email to and receive email from such addresses using both Gmail and Outlook (using a work around for a Gmail bug) and I suspect most other email providers. Quoted-string is not a post year 2000 extension.
Quoted-strings have generally worked in major MTA software for over forty years; since well before the World Wide Web was conceived.
UTF-8 support is comparatively new, only standardized in 2012, but advertised by both Gmail and Outlook. Gene.hightower (talk) 17:25, 19 May 2024 (UTC)[reply]
While RFC 6530, 6531, 6532, 6533 are 2012, RFC 5335, 5336 are 2008. BTW, none of those supersede RFC 5321, 5322, which are still current. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 06:17, 20 May 2024 (UTC)[reply]
RFC-5335 was EXPERIMENTAL, not a standard or proposed standard. And RFC-5335/RFC-6531 didn't change anything related to quoted-strings; UTF-8 support is a different issue. Gene.hightower (talk) 14:26, 20 May 2024 (UTC)[reply]
Obrigado pelo renovação 2804:389:C019:F85F:8083:76A2:E345:52C0 (talk) 07:40, 10 March 2025 (UTC)[reply]


References

  1. ^ "Sign up for Windows Live". Retrieved 2008-07-26.. However, the phrase is hidden, thus one has to either check the availability of an invalid ID, e.g., me#1, or resort to alternative displaying, e.g., no-style or source view, in order to read it.
  2. ^ "Characters in the local part of an email address". Retrieved 2016-03-30.

Abbreviation for the term "email address"?

[edit]

Is there an abbreviation for the term "email address", like e.g. "ema"? Google had no answer.
Steue (talk) 14:21, 11 August 2024 (UTC)[reply]

WP:NOTFORUMkashmīrī TALK 19:24, 22 August 2024 (UTC)[reply]