28
If using custom domain e-mails, to prevent spam, is it necessary to make addresses unpredictable (e.g.: stem-chaos-stricken@domain), or is servicename@domain good enough? (lemmy.sdf.org)
submitted 2 weeks ago by to c/privacy@lemmy.dbzer0.com
19 comments fedilink hide all child comments
 

Assuming a password manager is used, even jfav0ohjau4gvncgan19@domain should be OK.

On the other hand, I might just be overthinking it. It could even look suspicious to customer support, or is that again just overthinking?

Also, there already will necessarily be some predictable ones, such as work@domain, although servicename@domain would provide even more possible matches.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 weeks ago* (last edited 2 weeks ago)

I’ve been hacked before, luckily nothing severe happened but ever since then I’ve taken stuff like this a lot more seriously.

Let’s say I use a self hosted Addy instance, a bad actor knowing that my email is for email forwarding could assume I’m running Addy, which uses PHP, try the recent php2shell vulnerability and potentially execute commands on my server.

I was thinking of a data breach where it may not be obvious or mentioned which service it’s for, but I’m not sure how realistic that is. 🤔

Maybe I’m a bit overly paranoid, but In this day and age of LLMs I don’t think that’s a bad thing.

Edit: rewording

  • permalink
  • fedilink
  • source
  • parent