this post was submitted on 24 Feb 2024
80 points (90.8% liked)
Technology
61227 readers
4324 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
every provider who supports aliases. like foo+baa@bzz.tld where everything after the + is exchangeable. so you can use a 'different' mail for every service you use and just block where spam comes from via the alias.
Not best solution I guess. How about generic sites? Like Git commit mail, my website, Mastodon etc. where I can't add that postfix.
What I do is have some general mailboxes then signed addresses on top of that.
So if you email blog@ or kevincox@ you will get a fairly high level of spam filtering. I also have a few other "memorable" addresses that get reduced spam filtering. If you use the unique signed address that I use for signing up to services, newsletters or whatever where the address is private to a specific service then you basically skip spam filtering. Of course if you abuse that privilege then I will outright block the signed address.
Basically by allowing friends and "trusted" services through the spam filter I can crank up the difficulty for unknown senders.
Why can't you use +-aliases in Git, Mastodon, etc.?
Edit:
git config --local user.email "something+someotherstuff@example.com"shouldn't cause any issues.