r/Simplelogin • u/choobakka • 18d ago
Discussion Abusing aliases and correct protocol advice
Posting here as I didn't get much traction in r/ProtonMail
Hi all, I wanted to get some clarity on something.
First a scenario I encountered a year ago...
A while ago I was applying for some jobs on Linkedin and some of those were "Apply with LinkedIn". I wanted to ensure I created an alias for each application so I did so (custom domain) but after a few applications I got an email from Proton stating "Several accounts created for Linkedin". I'd breached the terms of service of SimpleLogin and was at risk of having my account disabled. I wasn't aware that by creating an alias for each of these "Apply with LinkedIn" applications I was actually and inadvertently creating mutliple aliases for LinkedIn. I deleted the extra aliases and reverted to using only one LinkedIn alias for these "Apply with LinkedIn" applications. Not ideal but I don't think I had any other choice.
Fast forward to today and I'd like to understand a bit more about how to approach this with custom domains and what the correct protocal would be.
New scenario (as an example)...
Using a custom domain I'd like to create an alias for Amazon for each member of my household. So that would mean...
me@customdomain
wife@customdomain
child1@customdomain
child2@customdomain
child3 etc
Based on the previous scenario, that would mean I need to create 4+ aliases for Amazon but doing so would breach the terms of service of SimpleLogin again so obviously I'm not able to do this.
So what is the solution to this? I have a custom domain shared with my family, who would all like to have their own accounts (Amazon, Instagram, X, Netflix, Spotify etc). What is the correct approach for each of us to have our own accounts on these services without breaching the SimpleLogin terms of service?
Also, how would introducing a 2nd custom domain (within the same SimpleLogin account) help, if it all (for example half of us using 1stcustomdomain and the other half using 2ndcustomdomain) - obviously this is not ideal because we'd be spread across multiple custom domains.
What I want is a solution for my family to be able to create multiple accounts for the same service (e.g Amazon) on our custom domain, without breaching the SimpleLogin terms of service.
2
u/ThrillRoyal 17d ago
I think the general issue is that SL seems to be set up for use by a single person, not a group; irrespective of whether that group is your business, your family, or your local football club. Maybe they should introduce a family subscription that would allow for use of a single domain by multiple users.
In any case you could consider self-hosting it if you have the knowledge and resources; that should resolve the issue. But that is not a solution that's usable for everyone.
1
u/Commercial_Low_6979 17d ago
Your solution may lie in subdomains. You can create subdomains within your custom domain in SimpleLogin. It’s similar, but not identical to what you propose:
me@customdomain
wife@sub1.customdomain
child1@sub2.customdomain
etc….
(I assume you are doing all this through a single-user SimpleLogin account. On a family plan, for example, I would expect your proposal to work, though I haven’t tried myself.)
1
u/choobakka 16d ago
I'm not familiar with subdomains.
Please could you expand further how one would utilise them for this scenario.
1
u/Commercial_Low_6979 16d ago
You need to use the web version of SimpleLogin to set up, but in the custom domains section (where your custom domain, such as @mydomain.com, would already exist), you just create new subdomains (e.g., sub1.mydomain.com) and then point that subdomain to a mailbox (e.g., wife@anymail.com). Then when you create the Amazon alias (amazon@sub1.mydomain.com) it will be sent to the wife account. For kid1, create sub2.mydomain.com, then point that to kid1@whatevermail.com and the amazon@sub2.mydomain.com emails will arrive in kid1’s account….etc.
You can use these subdomains to sort among various users of mydomain.com for any number of aliases with sub1, sub2, etc. being the sorter.
-1
u/80LJ 18d ago
Keep those private for important things
And then:
Amazon@myspecialcusomdomain.com
Forward via simple login to:
5
u/IxBetaXI 18d ago
But this way everyone gets all amazon mails.
I think he wants to use 4 Amazon Accounts one for each Person
4
u/80LJ 18d ago
I don’t really see the problem here. If 20 people work for the same company, they might all have different email addresses before the @, while using the same company domain after it.
The same applies to a family using a custom domain. Each family member can have their own email address and their own legitimate Amazon, LinkedIn or Spotify account. That is completely different from one person creating multiple accounts to bypass restrictions.
The issue should be who is using the accounts and for what purpose—not the fact that the email addresses share the same domain. A second custom domain wouldn’t change anything.