{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibxtwn2f5un6g6bg3nic55afouvrw5hpzfy5vv7w2wki5m5ev5ttq",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3ml2qvfi6ll62"
  },
  "path": "/t/email-aliases-via-proton-or-tuta-paid-using-custom-domain-from-cloudflare-following-bazzell-ebook/37602#post_7",
  "publishedAt": "2026-05-04T21:13:00.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "I’ve set up custom domains with both Proton and SimpleLogin. Both were straight forward.\n\nI have a custom domain(s) purely for aliasing which I originally set up with SimpleLogin but decided to integrate directly with Proton instead. Too much of a pain to create reverse aliases in SL for sending outgoing mail. Easier for me to just add the specific aliases in ProtonMail that I need to be able to send from, that way I can easily select which email I’m sending from in the dropdown, and less likely to make mistakes. Still I have the domain set as “catch all\" in Proton so all mail comes through. The downside is the limited number of aliases allowed in Proton but not an issue since I have catch-all enabled and just rotate out the aliases I don’t actively need to be able to send from.\n\nSorry that was kind of a tangent. Point is both Proton and SL are easy to set up with custom domain, and they both have guides that walk you through it (I’m not sure if they have ones specifically for Cloudflare)",
  "title": "Email aliases via proton or tuta paid - using custom domain from cloudflare, following bazzell ebook"
}