[vinay427]

I've started doing this and have ended up depending on my password manager to track which emails I need for logging in to a service, which is a bit of a hassle although I think it's still worth it for the reasons you outlined. For example, did I use [service]@domain.com or [abbreviated-service]@domain.com, or was it [service.com]@domain.com...?

[kalleboo]

The only service I have that problem with is Microsoft since it's a merge of like three different accounts (MSN messenger, Skype, and Office365) so I can never remember which is the right one.

Otherwise my rule is to use the central part of the domain name (no www or TLD), or it's easy enough to just search my email archive for messages from whatever service.

[sdflhasjd]

I also find that some services don't let you use their name in your email address.

Samsung is one I remember which wouldn't let me use [e-mail], I managed to get by with [e-mail]. Definitely one for the password.

Then again, we should be using unique passwords for everything anyway, so a password manage is a must regardless of how you handle emails.

[throw_away]

This also happens to some extent in real life. Often when I say that my email is "[e-mail]" it's met with a "well, if you're just going to give me a fake address…". At which point I have to explain 1) catch-all email addresses, and 2) yes, you can own your own entire domain name.

[Normal_gaussian]

Near enough everything is in my password manager. I use <service>.<month>.<year>.<nonce>@domain so I have to so to speak.

Using keepassxc + its browser and mobile extensions make this easier than typing the address in myself. I was astounded at how bad the ux the paid pw mamagers I've used is