I've always had multiple email addresses, right now I have 6:
- One "private": let's say it's the main one, used for everything except for the things I use the other ones for.
- One "dev": for my dev related accounts: GitHub, Dev.to, DigitalOcean, Namecheap, that kind of things.
- Two for work: as a consultant I have an address at my company and one at the client's premises.
- A Gmail address: for Google stuff only.
- A "dirty" address: I don't really use it, but when I need to create an account I'm not sure to keep, I use this address, it allows me to keep the main one clean.
... and I'll probably have a 7th one soon enough (for freelancing, my dev one wont do and I'd like to keep work-related stuff outside the private one).
But I'm starting to think it's too much... hence the question:
How many email addresses do you use? What for?
Oldest comments (49)
What's the point of making so much aliases?
Additionally:
...and it's not just data breaches you need to worry about, it's sites selling your address. When you get an email from the "wrong source" for a given destination, you can send site you actually gave the address to an email asking "did you sell my address or get hacked and not bother to tell me." Either way: a good way to know who you should continue doing business with.
Yeah, all those things made me consider doing the same (if I'm not too lazy to do so, ahah), that's actually pretty awesome, I can't believe I never thought of it.
Makes sense, thanks.
I have a personal one, for general day-to-day things, this is generally as secure as I can make it with a good password, two-factor auth etc. A "professional one", which security isn't as important as it's just for job searching, etc. A private one, which really is just a store of information for myself, I don't email it and to other people from it, just store things in it. This is another secure one.
Aren't there better solutions than a mail account for the last use case?
Quite likely, but I'll be honest I don't care too much about it. It's stuff like passphrases for websites I don't quite care enough about.
I am looking at investing in a Password Manager though, and there are solutions out there like LastPass that may be a better solutions to that.
I started using a password manager recently and that's honestly life changing. You should take a look at Bitwarden: it's free, open-source and self-hostable (but not only, they provide a public instance). You can store passwords/credentials (obviously), credit cards, identity and secured notes (chunks of text, you can put whatever you want in it).
Sounds ideal, I'll give it a look. Cheers for that!
Google mail accounts are great for archiving. Even without buying extra space, you can store years (decades?) worth of content. Can do it with either an auto-forwarding rule or, if you're just setting it up, a simple IMAP-based copy.
The beauty is it's kept in a portable, easy to access structure (its original format) and usually stays accessible via its former methods. Can't really say the same for things like PSTs and some purpose-built mail-archival solutions.
Definitely not enough, that's for sure.
Mine's probably not the recommended way, but I use my main Google account everywhere and use Live whenever I want to make another account on a service, for example, creating another Steam account. But for answering this post, here's a list of my email addresses:
And there are forgotten ones where I have no idea why I signed up in the first place:
My Gmail account used to be my main email... one day I decided I did not want to rely on Google for that kind of things and I switched to GMX (previously know as CaraMail)... dumbest move ever, ahah!
I can totally relate on the "forgotten ones", I have a few too (ProtonMail, Live and Hotmail (ah, the memories...) and probably a few more).
<service_name>@defman.me. It forwards everything to my private Gmail account.For security reasons?
Yeah. I can block services who send too much spam or detect leaks.
One, but I use the built-in aliasing.
GMail for instance you can have an email like myname@gmail.com and when you sign up on a site you can do myname+nameofwebsite@gmail.com
Emails they send you will still go to myname@gmail.com and you can use the +nameofwebsite part to see who it was who maybe sold your email or had a breach. Can also use it for rules and labelling things.
SOME terrible devs out there don't allow + in email addresses even though it is wholly valid to have that character. Lots of devs screw up email name validation. Don't be like those devs if you ever have to validate emails.
GMail also allows for any number of dots in your name. So you can also use my.name@gmail.com or m.y.n.a.m.e@gmail.com if you want. I do this sometimes to re-sign up for trials if the service doesn't allow for the + trick mentioned above.
I always forget about these tricks. Thanks for the reminder!
Yes, not allowing for + in emails is terrible practice. I wish I bookmarked it but I read a great article a few years ago all about email validation and how futile it pretty much is - the conclusion was to just check for the presence of an '@' character. Email validation is best done by sending an email to the address and seeing if the user opens it/goes to some link within it.
Everything before the '@' is entirely ruled by the mailserver, so any validation rules you apply to this are effectively an assumption on the rules your user's mailserver use. I guess you could validate the post-'@' characters but with how many new TLDs are coming out this seems like more hassle than it's worth. Trust your users to know their emails (but make sure you're still encoding the input so as to avoid nasty SQL injection etc!)
Hopefully doing more than just encoding/escaping -- never place user data directly into a SQL statement! Always use placeholders like ? or whatever your flavor of DB allows. And if it doesn't allow for that, really think hard about why you're using that db (or db sdk)!
Fair, I just wanted to throw in something about security after making the questionably phrased statement of 'trust user input' :D
Sadly, spammers and site-attackers know this trick.
Heh... And has been valid for over 20 years — at least that's when Sendmail added it. You'd think over two decades would be enough time for people to get the drift. :p
Sadly, support for that in gSuite seems to be lacking. Probably because they know a lot of companies like to assign .@. So, if you have a legacy Apps account for your personal domain, you can't use that trick to work past the fifty free aliases limit. :(
You can have unlimited temp email addresses with disposable email services.
I use one and see no reason to have multiple email addresses.
One for work, one for personal use. One for gmail because while my personal one used to be a Google Apps account, that had to change so I'm now just redirecting it to a generic gmail address.
For anything else I use services like guerillamail to create throwaway addresses.
I also have the domain notareal.email and use addresses like norepy@ or throwaway@ on that domain when talking to people like recruitment agents, because I am clearly the funniest man alive.
Can't argue with that!
Only 2: personal and work.
Once in a blue moon, I will create an email alias which forwards to my personal account. For example, when I am trying to find out more information about a product and the only facility the site provides is a request form. Which almost certainly adds me to a spam list. Then when I'm done with the alias, I delete it. Spammers deserve bounces.
I actually never thought about using aliases as a security/privacy measure but it seems to be quite common (just had to read the replies here).