I’ve recently been working on de-Googling and part of that has been setting up an email with my custom domain. This mostly works great, but one issue I’ve noticed is email validation on some websites detect this email address as invalid. For instance, if I have the domain [name].rocks with the email [name]@[name].rocks (with [name] being a placeholder for my name) my email cannot be used to register with the Ventra app (for getting mobile train tickets) I believe because any site that has an extension with more than four characters is detected as invalid.

I understand this is a validation issue on the end of the app dev / website, but I was wondering if people had suggestions for workarounds when they encounter this? Setting up other custom emails with forwarding? Thanks!

  • miau@lemmy.sdf.org
    link
    fedilink
    arrow-up
    4
    ·
    17 days ago

    I have a domain with one of the new TLD which I used for my emails.

    Most services worked fine with it, but there were a few cases where my email was flagged as fraudulent and I had to call, explain it was legit and provide with another email.

    There was one service I registered which explicitly said they oy accept gmail addresses.

    Roughly one year ago I acquired a new domain using the .org extension, I am migrating my accounts to this one, and I havent had any problems so far.

    So overall my conclusion is that most services are fine with custom emails, a few of them block based on TLD and an even smaller subset will allow only specific providers. Since I am moving alway from big corp, having a widely used TLD that seems to be accepted in most cases is my personal sweet spot.