I’ve recently signed up for an email forwarding service w/ aliases so that I can keep my true email address private when I sign up for new websites and services. I should clarify that I’m less concerned about concealing my identity as I am about protecting my real email address, identifying who leaked my info when my email address is compromised, and being able to stop the spam by turning off that alias.

While updating my existing profiles to point to aliases instead of my real address, I’ve hit a snag - some sites (Steam, Slack, etc) won’t allow me to update my email address to any known domains from my email forwarding service.

On these sites that block email forwarding addresses, for now I’m either updating my existing email address w/ a plus sign if the website allows it, otherwise I’m just leaving my existing email address unchanged. It’s not the end of the world, they already have my real email address, and I can probably go a Very Long Time without needing to check those inboxes anyway, but I’m still miffed that I can’t completely migrate my existing accounts to my new scheme.

I’ve read numerous posts about the benefits of custom domains to enable portability of email service providers, and I’m wondering if custom domains are the answer to these sites that disallow forwarding addresses, but I have questions:

  • How do other people deal with this situation?
  • Do these websites that block known email forwarding domains typically work on a whitelist or blacklist model? If the former (whitelist), then I’m thinking a custom domain will have the same problem, but if the latter (blacklist), then I reckon a custom domain with catchall might work.
  • Particularly owners of custom domains, do you find your custom domain is allowed more often than not or do you run into the same problem?

EDIT: Clarified my objectives.

  • [email protected]@lemmy.zipEnglish
    1·
    6 hours ago

    I also use an email alias service and have dealt with this a handful of times. Here’s how I’ve been able to address most of them, in order of what I tried which worked, meaning that items lower on the list were more rarely required but also more likely to work than items higher on the list:

    1. Instead of using the free-tier alias domain names (like freealiasservice.com), I used the paid-tier ones (like paidaliasservice.com).
    2. Instead of the common domain names shared by everyone (like aliasservice.com), I used a custom subdomain, (like cricket.aliasservice.com).
    3. Instead of either of the above, I used a custom domain name.

    So the above is the answer to your first question. The answer to your second is that in my experience the majority of sites that block certain email domains are using a deny-list instead of an allow-list. The answer to your third is that custom domains should work for the vast majority of sites. I think it would be silly for sites to use allow-lists for this, but I’ve heard of some doing it.

    One other thing to keep in mind about my list is that it’s also more or less in order of most private/anonymous to least private/anonymous. Item 1 hides you in the crowd, while 2 and 3 can be more easy to associate with you if you have enough of them for someone interested in finding this out to do some matching to determine if you use services a, b, and c, for example.

    I hope this helps.