You just gave me a good idea. I have my own domain and my main email address is [email protected] . Whenever I register to any websites now I'll start using [email protected] and I'll configure my mail server to forward me anything that arrives to [email protected] and drop all mail to [email protected] .

Don't run my own domain, but I'm thinking of creating a second gmail address for this:

* [email protected]

* use [email protected] per site

* use a filter to forward to [email protected] everything BUT messages to: [email protected]

Many sign up forms disallow the use of '+' in email addresses, either to prevent this, or more likely because the programmer wasn't aware it was a valid character for an email address in the first place.

If you're not going to verify that the email address they're giving you is real, why restrict them to your idea of what goes in an address? I often fill in my email address as [email protected] . It's pretty easy to see that that's invalid -- to the best of my knowledge, there is no .fake TLD, and there certainly wasn't when I started doing it. But, I've never seen a form reject it.

You validate email addresses by sending confirmation emails. What's the thinking behind pretending you're doing it in the form?

I agree with you, it'd be the obvious thing to do if you're going to buy some emails from the black market. I'm not going to name any names, but you'd be surprised how much spam I've tracked down by using subaddressing.

I use subaddressing to keep track of my email subscriptions and who is selling them to 3rd parties

Three ways to work around this if you actually suspect it:

1) Instead of using + (which some sites incorrectly reject as invalid), don't use a separator at all. For instance, [email protected] . (This assumes you have a bit more control over email aliases.)

2) Don't use a modification of your standard email address; make the version without the site name still different than your standard email address. For instance, if your usual email is [email protected], then instead of using [email protected], use [email protected].

3) If you run your own domain, don't bother including a unique component before the @ at all. Just use [email protected].

Clever. Proper email validation can be tricky at the edge cases, but parsing out sub-addresses shouldn't be too hard.

I'm curious as to why the OP disclosed this hack - given there are surely more contests to win. I wonder if the target companies have gotten savvy to this technique and it suddenly became ineffective.

OP probably revealed it to encourage others to replicate it, given the last paragraph. It might not be the best decision in the long term but in the long term there are other ways to have more than one email address.