I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.

  • MeatsOfRage@lemmy.worldEnglish
    41·
    11 months ago

    Exactly. After the @ they should just confirm there’s at least one period. The rest is pretty much up in the air.

    • Trailblazing Braille Taser@lemmy.dbzer0.comEnglish
      22·
      11 months ago

      Even that would be technically incorrect. I believe you could put an A record on a TLD if you wanted. In theory, my email could be me@example.

      Another hole to poke in the single dot regex: I could put in fake@com. with a dot trailing after the TLD, which would satisfy “dot after @” but is not an address to my knowledge.

      • douglasg14b@lemmy.worldEnglish
        12·
        11 months ago

        And this sort of thing is exactly how you end up with bad regex that invalidates valid emails.

        The point isn’t to invalidate all bad emails. It’s to sort out most of them.

      • drathvedro@lemm.eeEnglish
        5·
        11 months ago

        Something something http://[2607:f8b0:4004:c09::8a] and http://3627734062 are valid url’s without a dot, and are probably valid for emails too, but I’m too lazy to actually verify that.

    • restingboredface@sh.itjust.worksEnglish
      13·
      11 months ago

      I’ve had issues with this in using govt emails too. DOD accounts all have multiple dots based on branch and dept. It broke so many systems and emails never went through.

    • Aux@lemmy.worldEnglish
      91·
      11 months ago

      The easiest and most correct check: any character, then @, then any other character.