this post was submitted on 15 Oct 2024
26 points (96.4% liked)

Privacy

31991 readers
693 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 1 month ago (1 children)

I believe because any site that has an extension with more than four characters is detected as invalid.

Usually it's just badly coded apps/websites that only whitelisted some of the main domains e.g. most vanity domains don't make it through. Or sometimes there are apps/websites that purposely block your domain if the admins think it's too spammy or whatever.

If your current email provider allows you to use their own domains as an alias that's one way to sidestep the issue e.g. you'd end up with [something]@[youremailprovider].com --> [name]@[name].rocks

I have Fastmail & they have a ton of their own internal domains so that's one way I sidestep that issue. It's pretty common among most/all email providers when you bring your own domain e.g. pretty sure Proton can do the same thing. Once you have your own domain you can make up any [alias]@[yourdomain] you like or just use the provider's as a front facing alias [alias]@[youremailprovider] --> [anything]@[yourdomain].

[–] [email protected] 1 points 1 month ago

Thanks everyone! I think this will be the solution I go with.