>[...] so that some unsuspecting third party isn't suddenly subject to your emails
why not something like byfmupajzmvdaxef@{gmail.com,outlook.com,yahoo.com}? I doubt that large email providers are going to be inconvenienced by the spam. Your solution is likely to get rejected by overzealous form validation (for good reason!).
Nah, it will pass many validators even with semicolons (like http://emailregex.com, which yours would fail btw). You are right though about better leaving spaces verbatim and adding the hyphens.
The standard is followed so infrequently that quoting it is basically an exercise in needless pedantic detail mongering. It's just not very relevant, probably because the rules to check valid email are so ridiculously complex (how long was that regex, 200+ characters?).
The email address standard is hilarious and should be made fun of at every opportunity.
The whole quoted-string commented multiline business (seriously, why?) is rightfully ignored by anyone who's ever made or used a mailserver, but it's still there.
why not something like byfmupajzmvdaxef@{gmail.com,outlook.com,yahoo.com}? I doubt that large email providers are going to be inconvenienced by the spam. Your solution is likely to get rejected by overzealous form validation (for good reason!).