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
[–] 4 points 2 weeks ago (1 child)

Compactflax.myfitnesspal@domain gets a TON of spam.

other than that it’s actually surprising how little I get.

But damn that leak went far

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 weeks ago

    Spam is thankfully pretty much a thing of the past. I had to stop using a couple of my primary emails because they were just getting drowned in spam, like a hundred messages a day if not more.

    Then Sender Policy Framework came out, which went a long way to reducing spam, then came DKIM and DMARC and it's now really down to very manageable levels, and I've been able to start using both those email addresses again. They do still get some spam, but no more than 1-3 a day now.

  • permalink
  • fedilink
  • source
  • parent