{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihqgjcpzk3ege2omf744a6gom4feyzsuoxgdwicrkw7jtgyyhlfqe",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mf5g2i2zuy32"
  },
  "path": "/t/checking-email-from-addresses/35563#post_9",
  "publishedAt": "2026-02-18T14:50:57.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "fancy.com",
    "http://mmonium.purity671+store=fancy.com@addy.to",
    "mycustomdomain.com",
    "Addy.io",
    "fancy.com",
    "fancy.com",
    "like Porkbun",
    "mmonium.purity671+store=fancy.com"
  ],
  "textContent": "Grapeg:\n\n> I get an email from store@fancy.com addressed to fancyalias@mycustomdomain.com. When I reply I don’t want it to be sent from any address other than fancyalias@mycustomdomain.com\n\nIf you input that specific alias on the website fancy.com, you will receive it in your main email.\nYou can only reply to that email as shown by this part above\n\n> From: http://mmonium.purity671+store=fancy.com@addy.to\n>  To: mmonium.purity671@addy.to\n\nThere is no possible mistake and it’s the default behavior.\n\nIt being addy.to or mycustomdomain.com, doesn’t really matter a lot.\n\nMeanwhile, you don’t really have anonymity in that case because the domain will be tied to you, most registrars do quite their fare share of KYC.\n\nGrapeg:\n\n> I don’t want to look like a fool\n\nIf you properly create the email from your service (Addy or SimpleLogin), there is no possible error then.\n\nGrapeg:\n\n> my mailbox will be untidied by the encoding\n\nIt doesn’t really matter IMO because you do not need to do that yourself, it’s handled for you.\n\nGrapeg:\n\n> It will also mean my emails are passing unnecessarily through Addy.io\n\nThat’s kinda the point of having a 3rd party alias service yes.\nI’m not sure to understand if you want anonymity or just an email server at this point because if you host your own server + have your own name, then there is literally no anonymity.\n\nGrapeg:\n\n> offers more support for custom domain aliasing\n\nBoth Addy and SimpleLogin handle custom domains very well out of the box.\n\nGrapeg:\n\n> ideally by populating the from field with the to address of the email to which I’m replying\n\nWhen you’ll receive an email from fancy.com, it will do:\n\n  * leaving fancy.com domain servers\n  * reach Addy’s alias email address\n  * Addy forwards it to you with the proper interpolation (what you call “encoding”)\n  * you receive it in your mail client with the proper ready-to-reply safe target\n  * this is the default behavior of any aliasing service with no additional config needed\n\n\n\nThe only exception is as I wrote above: when you do need to initialize the email at first, then you need to add it to an alias of your custom domain inside of Addy’s UI.\n\n* * *\n\narise1984:\n\n> I believe its called wildcard sending, basically the smtp server support sending from whatever address on the domain and when replying they’ll automatically populate the From field\n\nThat’s indeed a feature available in a lot of places, meanwhile this has nothing to do with aliasing and does not add anonymity in any way.\n\nYou don’t even need to use any kind of specific service or email server for that, a registrar like Porkbun can do such a thing out of the box.\n\nIt is also something available directly from Addy or SimpleLogin if setting up a custom domain.\n\n\n\nIt will probably also auto-populate the From field properly for you, no need to lock yourself into using a particular email client for such use-case.\n\n* * *\n\nI’d like to still emphasize that this has pretty much nothing to do with an aliasing in the sense of anonymity aspect.\nJust a wildcard domain catch-all and hence comfort/use of use.\n\nAt this point, I am not sure what you’re gaining aside from just giving the company a\nsimple and `hello@mycustomdomain.com`, then proceeding with email spam/blocking it or unsubscribing from their stuff.\n\nSure you could have those being valid:\n\n  * `ola@mycustomdomain.com`\n  * `bonjour@mycustomdomain.com`\n  * `asdaskllkjasdljlasd@mycustomdomain.com`\n\n\n\nworking totally fine and hence switch them off independently, but even if you block an `ola@mycustomdomain.com`, I can just still spam you on `ola-again@mycustomdomain.com` because the catch-all will just create the address on the fly and forward it towards your main email box.\nAll of the above emails will still be very much linked to you from A to Z with all the tracking associated with knowing to whom the email goes.\n\nI’m hence quite concerned about all of this being a huge misunderstanding on what we’re trying to achieve here.\n\nLast point I just read again but\n\n> my mailbox looking messy due to the encoded addresses\n\nThis shouldn’t be a problem in itself. You’re usually seeing your contacts name or the subject of the email. Or do you actually look at `billing@netflix.com` every time you do receive an email?\nIn which case, yes it will look more messy because you’ll have Addy/SimpleLogin being in front of it with the alias but that’s kinda the price to pay while dealing with a 3rd party that serves as anonymity intermediary.\n\nI mean, if you really want to go hard and it to look slick without adding the email senders as contacts, using folder or other kinds of filtering, I do think there are ways to forward/change the sender’s name on the fly and _unwrap_ all the filters so that even something like this\n\n> mmonium.purity671+store=fancy.com@addy.to\n\ncould still show up as\n\n> store@fancy.com\n\nin your mailbox.\n\nJust as you would have a John Doe being unwrapped into a john@doe.com.\nI just haven’t dove too deep on that topic because aesthetics do not matter too much for me.",
  "title": "Checking email from addresses"
}