News for hackers. Stuff that matters.
Re:Match.com Used Fake Ads to Swindle Users, F.T.C. Says by newnewpdro on Thursday September 26, 2019 @01:12AM (#21078380)
Unfortunately, being part of the standard, it's become fairly common to strip this from email addresses.

It's more effective to have an entire domain at your disposal and just invent [email protected] whenever an email address is needed. On the server end all you need is a catchall to handle it, and you can blackhole whatever addresses become spam magnets (while also knowing which vendor's responsible).

Re:Match.com Used Fake Ads to Swindle Users, F.T.C. Says by __david__ on Thursday September 26, 2019 @03:04AM (#21078884)
It is not part of any standard. + is a valid email address character and is not special in any way.
Re:Match.com Used Fake Ads to Swindle Users, F.T.C. Says by newnewpdro on Thursday September 26, 2019 @03:23AM (#21078956)
It's specified in RFC5233 [0], by "standard" I meant codified in RFC form, like everything else we treat as open internet "standards".

[0] https://tools.ietf.org/html/rfc5233

Re:Match.com Used Fake Ads to Swindle Users, F.T.C. Says by hdfbdtbcdg on Thursday September 26, 2019 @03:38AM (#21079009)
> On email systems that allow for 'subaddressing' or 'detailed addressing' (e.g., "[email protected]"),

This rfc merely acknowledges that some systems do this. It doesn't say the must or even should.

Re:Match.com Used Fake Ads to Swindle Users, F.T.C. Says by pseudalopex on Thursday September 26, 2019 @03:30AM (#21078980)
RFC 5223 uses + as an example. It doesn't even specify whether the detail part comes before or after the user part.