Should we stop using a feature because some buggy apps don’t support it?
Other users on my setup can use it, they just have to pick a different "something" if they want to use the same example.com as me.
edit: I was corrected in other comments that the + labeling is optional part of the standard.
Allowing + in emails is not an optional part of the standard.
> you should probably strip the + and everything after before checking for uniqueness.
No, you shouldn't. Different email providers use different characters to allow "subaddressing" or "tagging" and the presence of those characters doesn't mean that any subaddressing will be done.
Also, you'll have to elaborate on how the dot usage actually breaks the RFC. I assume it states that dots are just like any other allowable character, but that's not the same as actually breaking the RFC.
Both of them allow infinite email addresses. The tag feature is not always available because app developers frequently don’t allow the plus character.
I would prefer that (1) a Netflix require email verification and (2) GMail describe in detail all of the email address features so app developers can explore the security issues around them.
I used to work for a company that dealt with these issues almost 10 years ago. It was also fun when Hotmail and Yahoo started recycling unused email addresses after ~6 months.