15

How is this not a valid address!

Comments
  • 2
    They scan for know domain classifiers or profanity for some reason. According to the email spec, t@t is a valid email.
  • 0
    @molaram
    Obv. My statement was just that whatever they are doing is superfluous, app specific use case. The email portion of the address specification is clear, anything else is fluff.

    https://tools.ietf.org/html/...
  • 1
    Bad regex
  • 4
    Wow, is the whole band at your ass?
  • 5
    @Matthewb there are no good regex for email verifications, only bad and worse.
  • 0
    their artificial intelligence robot said ass kissing is only available in Sweden
  • 0
    @FrodoSwaggins you meant Mexican ?
  • 2
    some devs will go to the extent of doing a MX lookup to verify the domain will accept emails.

    for example:

    my.ass
    https://mxtoolbox.com/SuperTool.asp...

    vs

    devrant.com
    https://mxtoolbox.com/SuperTool.asp...
  • 1
    @molaram i know, these guys have an api to do such lookups too through https://mojodns.com/ for small scale applications.
  • 1
  • 0
    Is .ass a legit top level domain?
  • 0
    @SortOfTested well, the email spec also has to work for the intranet, hence t@t is valid. But in the common Internet, everything (?) works through domains, so it is valid to check those.

    No need to allow 'a@b' if the dns of the service has no way to get the address of 'b' oO Or am I wrong here? I'm open to input :)
  • 0
    In a word, yes.

    0: you're conflating technologies. The standards define how the "common internet works," not the other way around
    1: TLDs are themselves valid domain names (hence why your computer doesn't choke on localhost)
    2: SMTP is an application layer protocol, as is DNS. Neither has contextual awareness of the other, email works fine on IP addresses, as does the internet. DNS is a convenience.
    3: if your business logic has a rule that says only employees.example.com account holders can register, that's a separate validation rule from "is this even a valid email."
    3.5: it's also a separate error message
    4: your computer is a capable nameserver without any additional software or even being online

    Bonus: what if I were to tell you that intranets aren't special in regards to protocols and standards. I mean, wouldn't it be cool if there were a way to connect a whole bunch of intranets together that didn't need a bunch of incompatible technologies? Whatever would we call that 😝
Add Comment