3 ms·
The problem with aliases is that it's effectively a way to ensure vendor lock-in even for people with custom email domains. If one of the reasons to use a custo
by solatic 7y ago
The problem with aliases is that it's effectively a way to ensure vendor lock-in even for people with custom email domains. If one of the reasons to use a custom email domain is to preserve flexibility in choosing an email provider, good luck switching providers when you have hundreds of aliases set up in the hands of hundreds if not thousands of third-parties and your strategy for managing your inbox depends on these aliases continuing to function.
It may not be nearly as strong of a lock-in as a @gmail.com address, but I'd be curious to hear how many heavy alias users are paying Fastmail on a month-to-month basis.
- pheug 7y agoFastmail makes it very easy (unlike many others) to send emails from any *@yourdomain.com email as a sender. But if you only need to receive email, then almost any paid email service I know supports such catch-all addresses, even gmail/gsuite, there's no lock in.
- inapis 7y agoIt’s not an issue if your email is primarily for newsletters, bills and other one way updates (where you are not frequently conversing back). You’ll rarely have to create an actual functioning alias in those cases because a catch-all would do reasonably well. If you are conversing with people it’s unlikely you are going to create an alias for each person specifically, that’ll come across as super shady TBH. So it’s not a major issue for most people because most services support 30-50 aliases easily.
- glofish 7y agonot sure I follow, the mail handling is set at domain DNS level - one may choose to handle their custom domain with another provider at any time it is zero lock-in, I can read my custom domain email with them with minimal fuss, or I could handle it myself in any other manner if I choose so.