{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiccjtokplrpyxjhrvfmrbzsnqip4ixvr5qe4cp2lyd2bshpfk2gpu",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mkksjm4t2uu2"
  },
  "path": "/t/email-aliases-pgp-and-e2ee/37050#post_7",
  "publishedAt": "2026-04-28T14:07:39.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "That sounds like a misunderstanding.\n\nA PGP/GPG-Key is bound to an email address. Part of it’s purpose is to prove an email is actually written by the owner of that address.\n\nIf you have an PGP/GPG-Key for myrealidentity@emailprovider.com then you should use it only for email communication for this address.\n\nIf you are using an alias like myalias@emailprovider.com then you have to create a PGP/GPG-Key for that alias and use it for all communication using that alias.\n\nUsing myrealidentity@emailprovider.com PGP/GPG-Key for myalias@emailprovider.com would do two bad things:\n\n  * It would reveal that myrealidentity is most likely behind myalias.\n  * It would not ensure that myalias is actually myalias.\n\n",
  "title": "Email aliases , pgp and e2ee"
}