News for hackers. Stuff that matters.
Re:How to get gmail.com banned (2011) by nkassis on Tuesday August 04, 2015 @12:29PM (#10004436)
Could use + in the first part of email such as: [email protected] to create throwaways. most sites consider those to be different email address then [email protected] for account purposes but email service, who respect the rfc, will threat them as the same.
Re:How to get gmail.com banned (2011) by paulmd on Tuesday August 04, 2015 @12:47PM (#10004541)
Many sites won't accept email addresses with + in them, because many devs have extremely wrongheaded ideas about validation.

I used to have a [email protected] address and that one was touch-and-go as well due to the fact that the mailbox had two .'s in it. I actually had to file a support request to get Amazon Student to accept it, even. Nobody from a university with that scheme ever registered before?

For the record, the gold standard for email validation is "send a confirmation link and see if they click it". Don't try and get fancy.

One other trick is that Gmail ignores .'s in addresses entirely. [email protected] is the same as firstlast or f.irstlast.

Re:How to get gmail.com banned (2011) by michaelhoffman on Tuesday August 04, 2015 @02:02PM (#10005097)
What's worse: some sites accept email addresses with + in them and then years later, they stop working, and you can't log in to fix your email address.

Ask me how I know this.

Re:How to get gmail.com banned (2011) by cosmotron on Tuesday August 04, 2015 @03:29PM (#10005654)
Hah, this happened to me once. Turns out the email validation was occurring client-side though... so a quick edit later and the server still gladly accepted my '+'-enabled email address. :-)
Re:How to get gmail.com banned (2011) by mintplant on Tuesday August 04, 2015 @03:10PM (#10005544)
>For the record, the gold standard for email validation is "send a confirmation link and see if they click it". Don't try and get fancy.

But make sure you have some sort of rate limiting set up, so malicious users can't take advantage to spam someone's mailbox (and get your server blacklisted).

Re:How to get gmail.com banned (2011) by GauntletWizard on Tuesday August 04, 2015 @01:15PM (#10004775)
My favorite is e-mails with three dots in them. Which is actually not a valid address - the RFC specifies that you must have a valid textual character between dots[1]. However, because of poor decisions by Japanese telcoms, a substantial chunk of their users have 'e-mails' associated with their mobile phones with three dots, breaking goddamn every sensible validation script.

[1] https://tools.ietf.org/html/rfc2822#section-3.2.4

Re:How to get gmail.com banned (2011) by driverdan on Tuesday August 04, 2015 @04:36PM (#10006118)
> Which is actually not a valid address

That means validation was working correctly. The email addresses are invalid even if the server will accept email for them.

Re:How to get gmail.com banned (2011) by ori_b on Tuesday August 04, 2015 @01:51PM (#10005007)
There's only one sensible validation script: "Send an email with a confirm link".
Re:How to get gmail.com banned (2011) by sk5t on Tuesday August 04, 2015 @11:33PM (#10007910)
Taking action with side-effects on entirely unvalidated user input is usually a pretty bad idea.
Re:How to get gmail.com banned (2011) by GauntletWizard on Tuesday August 04, 2015 @02:07PM (#10005129)
Sadly, if you're sending e-mail sanely, your mail provider likely validates recipients, and will be annoyed at you if you send them recipients they think are bogus.
Re:How to get gmail.com banned (2011) by belovedeagle on Tuesday August 04, 2015 @11:36PM (#10007915)
The relevant rfc (on mobile; don't remember which) specifically states that intermediate servers must not validate mailboxes (local parts). And honestly the domain should be "validated" by the server doing an mx lookup; let dns handle it.
Re:How to get gmail.com banned (2011) by paulmd on Tuesday August 04, 2015 @10:56PM (#10007801)
So wait, what now? So you can have an email address like [email protected]? Can you give me a generic example?

Yeah, I'm with the other guy, regardless of whether or not it's a good idea to do validation (it's not), that's not an address that should pass validation because it's not a valid domain or hostname.

I could see it being less of a big deal in the mailbox portion given that it's now kinda kosher to ignore dots there.

Re:How to get gmail.com banned (2011) by Steko on Wednesday August 05, 2015 @01:24AM (#10008143)
Yep, for some reason my wife's emails to her sister[1] always bounce unless she uses the desktop, it's madness.

[1] docomo customer with two dots in email

Re:How to get gmail.com banned (2011) by brongondwana on Tuesday August 04, 2015 @10:00PM (#10007647)
This is why we allow subdomain magic at FastMail, so that if you wanted to use [email protected] you can use [email protected] as well, and it works fine. Everyone accepts that form.
Re:How to get gmail.com banned (2011) by aidenn0 on Tuesday August 04, 2015 @12:58PM (#10004637)
I had a [email protected] (though I have a really common name so it was actually [email protected]), but fortunately they also gave us 8 character usernames (which were also our login to our shared hosting on the Sun E6500 machine), but I never used the long form since it was rejected nearly everywhere.
Re:How to get gmail.com banned (2011) by PebblesHD on Wednesday August 05, 2015 @12:19AM (#10008000)
My university address at the moment causes similar issues, it follows the [email protected] form which throws off lots of input validators.
Re:How to get gmail.com banned (2011) by giancarlostoro on Tuesday August 04, 2015 @03:06PM (#10005522)
All this time I've been telling people my email has a . in it, I had no idea I could remove it and still login.
Re:How to get gmail.com banned (2011) by graywh on Tuesday August 04, 2015 @04:14PM (#10005972)
In the early days, you had to use the username as it was registered to log in.
Re:How to get gmail.com banned (2011) by dragonwriter on Tuesday August 04, 2015 @06:35PM (#10006712)
> Could use + in the first part of email such as: [email protected] to create throwaways. most sites consider those to be different email address then [email protected] for account purposes but email service, who respect the rfc, will threat them as the same.

There is no RFC that requires this behavior. Subaddressing within the local part is recognized as a common practice (e.g., in RFC 5233), but nothing requires a system to support subaddressing, or requires a system that does to support a particular separator character or character sequence (e.g., "+") for subaddressing. Email systems are free to implement or not implement subaddressing, and to use any character sequence they want as the separator.

Re:How to get gmail.com banned (2011) by cdubzzz on Tuesday August 04, 2015 @12:43PM (#10004517)
I've always found this to be such an odd option. If the concern is people spamming you or selling your email address, how does this really help? Anyone intentionally doing nefarious things can just add a simple regex to strip the garbage.
Re:How to get gmail.com banned (2011) by kpcyrd on Tuesday August 04, 2015 @02:01PM (#10005096)
The parent mentioned QA, it would work for that. For antispam you could add a filter for emails to the direct address without suffix. Personally I prefer aliases, but I think they are very rare on freemailers.
Re:How to get gmail.com banned (2011) by matt_kantor on Tuesday August 04, 2015 @03:14PM (#10005564)
> Could use + in the first part of email [...] email service, who respect the rfc, will threat them as the same.

I'm not aware of any RFC that says that mail sent to [email protected] should go to the same mailbox as mail sent to [email protected] (nor am I aware of any RFC that forbids this). I thought that GMail made up that feature and other vendors followed suit since users find it handy.

Re:How to get gmail.com banned (2011) by aaronbasssett on Tuesday August 04, 2015 @03:35PM (#10005696)
Re:How to get gmail.com banned (2011) by TimWolla on Tuesday August 04, 2015 @06:25PM (#10006674)

    > Subaddressing is the practice of augmenting the local-part of an
    > [RFC2822] address with some 'detail' information in order to give
    > some extra meaning to that address.  One common way of encoding
    > 'detail' information into the local-part is to add a 'separator
    > character sequence', such as "+", to form a boundary between the
                           ^^^^^^^^^^^
    > 'user' (original local-part) and 'detail' sub-parts of the address,
    > much like the "@" character forms the boundary between the local-part
    > and domain.
(Highlighting by me)

The RFC even gives an example using the hash:

    > o  A message addressed to "5551212#[email protected]" is delivered to
         the voice mailbox number "123" at phone number "5551212".
Re:How to get gmail.com banned (2011) by redthrowaway on Tuesday August 04, 2015 @01:12PM (#10004750)
This is how we do it, with a predefined string after the first plus. Makes it easy to prune test accounts from the members db.