Created
April 17, 2018 18:58
-
-
Save neilstuartcraig/d4fd833c51f2a54c2f9e36ab5b25f9cf to your computer and use it in GitHub Desktop.
Email address format - template to request corrections as per RFC 2822
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Hello | |
| I’d be grateful if you could forward this email to your technical folk for their consideration please: | |
| I just used your website contact form and I noticed that the email address validation doesn’t allow “+" in the “locally interpreted string” (the part of the email address before the “@"). A “+" (along with a number of other characters) is a valid character in this part of the address (as per the relevant standard, RFC 2822: https://tools.ietf.org/html/rfc2822#section-3.2.4). If you’re unfamiliar with the email address format/spec, this blog post does a good job of explaining it: https://haacked.com/archive/2007/08/21/i-knew-how-to-validate-an-email-address-until-i.aspx/. | |
| Like many others, I use a specific “+ alias” for each account I sign up for, this allows me to filter any resulting spam and more importantly, means that it is more difficult for malicious people and unwanted advertisers to link two or more leaked sets of account details of mine together (see https://fieldguide.gizmodo.com/how-to-use-the-infinite-number-of-email-addresses-gmail-1609458192 for more info). | |
| It would be great if you could amend the email address validation you use to allow all the relevant characters as per RFC 2822 so we can use “+ aliases” and all other valid forms of email address. | |
| Kind regards |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment