How do you handle email for prof and private uses?
-
I was using protonmail for my custom domain for work and private emails but now I think mailbox has better options, providing way more custom domain emails. Wondering what the best use case is? Thinking of using my own domains instead of proton. I have this one and my name.
Using [email protected] or [email protected] is fun and easy but is it private? These companies already know my name so is using my work website domain okay?
Current emails
- [email protected] for prof
- [email protected] example for money
- [email protected] example for legal torrenting
- No idea what I will use this domain for
Well, it's not like email is a particularly private protocol to begin with. Proton has PGP encryption under the hood for proton to proton communication. But proton to whatever is not more private than using your hosters mail service.
-
Well, it's not like email is a particularly private protocol to begin with. Proton has PGP encryption under the hood for proton to proton communication. But proton to whatever is not more private than using your hosters mail service.
True, hence another reason I switched to mailbox.
I guess my question is more email naming and domain.
-
I was using protonmail for my custom domain for work and private emails but now I think mailbox has better options, providing way more custom domain emails. Wondering what the best use case is? Thinking of using my own domains instead of proton. I have this one and my name.
Using [email protected] or [email protected] is fun and easy but is it private? These companies already know my name so is using my work website domain okay?
Current emails
- [email protected] for prof
- [email protected] example for money
- [email protected] example for legal torrenting
- No idea what I will use this domain for
I’m not familiar with Mailbox, but I’ve recently switched to Proton with custom domains, and I’ve made use of their partnership with Simple Login for semi-custom domains and aliases on them. The rest is about that.
I think if you know you need more than 3 unique domains (that being the number offered in the Proton Unlimited plan), then maybe Mailbox is the move?
On security, I’m also a beginner, but from what I’ve read, I’ve decided to setup my addresses so that I’m never handing out an address that includes a stock Proton domain (e.g. @proton.me or @pm.me). I’m basically only using a Proton domain address to login to my Proton account, which collects emails from my custom domain addresses and Simple Login aliases.
Another thing. Setting up a catch-all email in Proton, which you seem to have done, allows any [email protected] address to login to your Proton account. If that is a security concern for you, then I recommend exploring the Simple Login partnership. My threat model has me generally creating one email address for each service I use. This allows me to maintain a single address for professional stuff and other addresses for everything else.
While your custom domain @name reveals your name, like you said, you’ll use it to engage with entities that expect you to relinquish some privacy. I recommend WHOIS protections for you domain if you’re not already doing that though.
I hope this is helpful for understanding your possible options with Proton, at least somewhat! Still on a learning journey myself
-
I was using protonmail for my custom domain for work and private emails but now I think mailbox has better options, providing way more custom domain emails. Wondering what the best use case is? Thinking of using my own domains instead of proton. I have this one and my name.
Using [email protected] or [email protected] is fun and easy but is it private? These companies already know my name so is using my work website domain okay?
Current emails
- [email protected] for prof
- [email protected] example for money
- [email protected] example for legal torrenting
- No idea what I will use this domain for
Use a custom domain with proton simple login. I set a wildcard regex and just allow <nameofservice>@customdomain.com. I can make up an email on the spot and when they inevitably add me to some annoying mailing list, I can just disable it in simple login.
-
Use a custom domain with proton simple login. I set a wildcard regex and just allow <nameofservice>@customdomain.com. I can make up an email on the spot and when they inevitably add me to some annoying mailing list, I can just disable it in simple login.
Thanks! What’s a proton simple login? In this use case could I use my name.com domain? I think mailbox can do this!
-
I was using protonmail for my custom domain for work and private emails but now I think mailbox has better options, providing way more custom domain emails. Wondering what the best use case is? Thinking of using my own domains instead of proton. I have this one and my name.
Using [email protected] or [email protected] is fun and easy but is it private? These companies already know my name so is using my work website domain okay?
Current emails
- [email protected] for prof
- [email protected] example for money
- [email protected] example for legal torrenting
- No idea what I will use this domain for
If you have a custom domain Tuta is way better than Proton. It's unlimited addresses.
-
If you have a custom domain Tuta is way better than Proton. It's unlimited addresses.
I quickly quit them because they don't do IMAP for "security" reasons, ie walled garden, and their support requires you paying. After canceling my membership I literally couldn't contact support unless I paid again.
-
Thanks! What’s a proton simple login? In this use case could I use my name.com domain? I think mailbox can do this!
proton owns a service called SimpleLogin, you can use it to setup and manage email aliases.
-
proton owns a service called SimpleLogin, you can use it to setup and manage email aliases.
Thanks!
Mailbox.org is a commonly recommended service beside Tuta and Proton. I was going to switch from Proton to Tuta to have more custom domain emails but it doesn’t allow service outside of its apps. Mailbox.org is cheaper and allows 50 custom domains
-
I quickly quit them because they don't do IMAP for "security" reasons, ie walled garden, and their support requires you paying. After canceling my membership I literally couldn't contact support unless I paid again.
They're open source, so for technical issues you can open an issue on GitHub
-
They're open source, so for technical issues you can open an issue on GitHub
I searched and searched about this and every response of theirs I found gave the same speech about IMAP not being as safe as their apps.
-
System shared this topic on
