Databases
StackOverflow2013
Postsdbo
POWhat's the current state of RFC 822/3696 etc. (email addresses) in practical, real world use?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat's the current state of RFC 822/3696 etc. (email addresses) in practical, real world use?
    primarykey
    data
    text
    <p><a href="http://tools.ietf.org/html/rfc822" rel="nofollow">RFC 822</a>, <a href="http://tools.ietf.org/html/rfc3696" rel="nofollow">3696</a> and others specify email address formats and how those should be validated by applications. Unfortunately in practice virtually nobody adheres to them, with most developers tending to invent a regex on the fly or copy-n-paste one from dubious sources to validate their user's email addresses. This in practice leads to many web services requiring email addresses, often as the primary identity of their users, yet only accepting a very limited subset of addresses that the RFCs actually allow.</p> <p>So, can anything be said about the current state of what is generally considered a "web safe" email address? Is there some common subset that has crystalized over time that's accepted by most services? What's the standard for the HTML 5 <code>email</code> input type, which will hopefully eventually emerge as the default quick front-end validity check for emails?</p> <hr> <p>Please note that I'm not asking what <em>should</em> be done to validate email addresses. Ideally validation should consist of light front-end validation which allows every possible address and possibly some false-positives, followed by a callback validation with the actual email server on the backend. I'm asking instead whether there is any sort of consensus on what the current implementations in the wild regard as valid. If I were to create a regex to validate email addresses (which I'm not, but humor me), what should that be to roughly match what everyone else does? If I were to create a new email address for myself on my own server, what safe subset should I stick to in order to be able to use that address at most web sites?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdeceze
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat's the current state of RFC 822/3696 etc. (email addresses) in practical, real world use?
      1. USGryphius
      1. VTFavorite
    2. VO
      singulars
      1. POWhat's the current state of RFC 822/3696 etc. (email addresses) in practical, real world use?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat's the current state of RFC 822/3696 etc. (email addresses) in practical, real world use?
      1. USMillie Smith
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload