Frank
My feedback
11 results found
-
12 votes
An error occurred while saving the comment Frank supported this idea · -
6,492 votesFrank supported this idea ·
-
794 votesFrank supported this idea ·
-
454 votesFrank supported this idea ·
-
35 votesFrank supported this idea ·
-
23 votesFrank supported this idea ·
-
204 votesFrank supported this idea ·
-
256 votesFrank supported this idea ·
-
56 votesFrank supported this idea ·
-
418 votesFrank supported this idea ·
-
123 votes
An error occurred while saving the comment Frank commentedI create unique aliases for every service and do not wish to use, nor can I always rely on my ability to use ProtonPass' browser extension to generate email addresses.
I think it's more than generous to allow any aliases at all with proton's own domains, and honestly don't think that should even be available.
For custom domains, there should be no limit whatsoever. This feature alone is literally prohibiting me from migrating from my existing email service into Proton where I'd prefer to be. I was super disappointed to discover that even a custom domain counted against the 15-alias limit.
Frank supported this idea ·
There are several services I've found which have blocked my SimpleLogin email address (GitHub) or straight up deleted my entire account after changing to a SimpleLogin address (Yelp).
Proton's known as a legitimate email service. It's not difficult for services like the above to do a quick MX record lookup and block any addresses that resolve to mx1.simplelogin.co.
Can we please get SimpleLogin integrated fully into Proton, and using Proton's native MX, and the alias system built-into Proton Mail directly?