{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihfvyw3irhb2l27rbkdvpi2u6mhthdbriujpmn46eeoqtjow74y4i",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mf2bb4jtici2"
  },
  "path": "/t/checking-email-from-addresses/35563#post_4",
  "publishedAt": "2026-02-17T08:51:33.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "[1]",
    "mmonium.purity671+store=fancy.com",
    "mmonium.purity671+store=fancy.com",
    "(click for more details)",
    "layers of complexity if you use **Proton aliases**",
    "↩︎"
  ],
  "textContent": "Grapeg:\n\n> I haven’t configured the system to recognise\n\nWhat do you mean here?\nConfigured what?\n\nOnce you have an alias service in place, you don’t really need to do anything when it comes down to **a reply** , it will forward it for you without any possible mistakes.\n\nThe danger is when you want to write an email to someone **first** , there you need to be careful of not using your email provider and typing in the place you want to reach in the input field but rather: go into your alias service, type the email of the person there, then use that as your starting point in your email client.\n\n* * *\n\nLet’s take a quick example with Proton + Addy combo[1] with the following specs:\n\n  * your personal private email is `grapeg@proton.me`\n  * you want to buy something from `store@fancy.com`\n\n\n\nHence, it shouldn’t be\n\n> From: grapeg@proton.me\n>  To: store@fancy.com\n\nand on the reply side\n\n> From: store@fancy.com\n>  To: grapeg@proton.me\n\n* * *\n\nbut rather\n\n> From: grapeg@proton.me\n>  To: mmonium.purity671+store=fancy.com@addy.to\n\nand the reply you’ll get back is as following\n\n> From: mmonium.purity671+store=fancy.com@addy.to\n>  To: mmonium.purity671@addy.to\n\nthen of course, Addy will forward the email received\n\nmmonium.purity671@addy.to → grapeg@proton.me\n\nHence, only Addy will know where you’re sending your emails from (your Proton) and to (the fancy store).\n\nThis is the step to not miss **if you’re the one initiating** the email.\n\n\n\nIn practice, it’s not that bad because Addy will do the concatenation of strings and once done for that specific company, it will then be transparent and you can reply further without needing those steps no more.\n\nGroup discussion side quest (click for more details)\n\n* * *\n\nThe flow of just receiving first is overall “less dangerous” because you just paste the freshly created alias into a text input rather than doing the entire danse with your alias + email.\nBut overall, the tools still kinda make it easy enough by forwarding/copying/opening the apps for you. Still, might be a head scratcher, scary and confusing at first.\nYou might also make a few mistakes figuring all of that out in the first place, hopefully you realize the damage early on and can minimize the spread of your personal email.\n\n* * *\n\nThere are definitely layers of complexity if you use **Proton aliases**.\nThose are not aliases in the sense of **alias service** like Addy/SimpleLogin but those are additional Proton email addresses, hence something like:\n\n  * grapeg@proton.me\n  * super.graaaap@proton.me\n\n\n\nAs seen here\n\n\n\n\n\nHence both `grapeg` and `super.graaaap` are “hosted” under the same paid Proton email account and can be accessed with either on the login page.\n\nFor those use cases (and if you have a custom domain for example), you could then maybe look into adding some rules to not make mistakes while initiating an email?\n\nNot sure it’s the email service’s job to do that.\nGood news is: both Addy and SimpleLogin allow you to kinda allow/block-list those based on their own ways.\n\nAddy’s rules look like that\n\n\n\nNow, I myself never had to use such a thing because as said above, it’s not needed to have a workflow of:\n\n  * receiving from a company first\n  * sending an email first to a company\n\n\n\nThose are more of where should I forward from the alias to which inbox as in the example above\n`mmonium.purity671@addy.to → grapeg@proton.me`\nwhere you could be a power user and have some fancy rules if you’re running an empire of fast paced emails sent from anonymous aliases.\n\n* * *\n\nI meanwhile do strongly recommend using your own personal email’s capabilities to sort/filter/move some emails into dedicated folders so that (for example):\n\n  * you know where your expenses are located when receiving a receipt you care about\n  * don’t get notified from endless stuff like hourly notifications about services that insist sending you 10 emails for each action\n  * have that annoying website that you don’t want to disable the alias for those rare times you need an info from them, yet don’t want to hear about their constant yapping about their latest and greatest products\n\n\n\n* * *\n\nI know it’s a lot to wrap your head around but I hope that the explanations + screenshots helped.\n\n* * *\n\n  1. it can of course be done with SimpleLogin and Tuta etc, mix and match your favorites here  ↩︎\n\n\n",
  "title": "Checking email from addresses"
}