Give options to use features that are in simplelogin because many sites block simplelogin as it is primarily a disposable mail service.

I seriously question why simplelogin has unlimited alias and proton has only 15 when simplelogin is hosted on proton (or are they not). (I also have a custom domain btw). With reverse-aliasing and unnecessary extra step of forwarding to my actual mailbox, I can only imagine simplelogin as being more computationally intensive on the backend then an actual alias would be.

I'd personally be fine though with simple login if integration was better (like the same level as alias, where you can send from with pgp key attatched and see icons for the sender). Currently using SL for everything with my proton email just being the mailbox and domain I login to and tell no one about.

I honestly expected this would be a feature when I signed up. Where is the 15 limit from?

I will pay for more than 15 addresses! Please! Why did you remove the 50 address limit. Even that isn't enough. Doesn't this incentives people to create multiple accounts?

At least allow us to have unlimited aliases for our own domains. You have acquired Simplelogin, but I have set my domain up with Proton and would like to keep it that way and continue to use simplelogin with their standard domains, which do not point to my domain. 15 aliases incl. for my domain is simply not enough, especially when I cannot get back any of the aliases by deleting old aliases, which I have no intention of using anymore.

I mean we can already use any alias with our e-mail address, e.g: username+alias@example.org. This would be great to keep track of those.

I kind of agree with it too (as long as it does not take too much ressources on the backend, but it could be done as alias).

Catch all emails are not a solution, it's in the name, they are catch all, not send all.

Simple login is an option but then the domain wouldn't be counted as proton mail and so not encryption by default between proton users on them.

So For custom domains (and so paid customers), having 1 free address per domain name at a minimum, and multiple identities/alias for the custom domain names would be a good solution.

Absolutely agree when it comes to our own domains. I have a domain and find there is no excuse to not be able to use as many aliases as I need/want for it. These should not count against your in-house aliases (protonmail.com, pm.me, etc). I tend to agree that proton is not a valid service when they restrict your own domain this way. We already pay for the service, let us use it.

Catch-all is not an option for many people. Spammers do these dictionary type spams that basically, pick a domain and send spam to thousands of popular names to see if they can find a valid one that didn't bounce. When you turn on catch-all, nothing bounces again. Catch-all is a spam magnet. I've deleted email addresses to see in the logs that it is still getting spammed decades later. I will never use catch-all because, long term, it's just evil.

@Eléanor ⋙

Yes. But you can’t send mail with… and there’s no "Reply-to" field. So catch-all is not enough.

It is possible to use the 'catch-all' feature with a custom domain to emulate this feature

Hello,
This is a must-have for me for paid accounts and clearly what's today prevents me from subscribing.
I understand you need to limit the email accounts but I see no reason why you should limit the aliases, especially when we use a custom domain where we don't "burn" any proton.me addresses.

we can no use proton mail without it